Share live apps outside Vibecodr
Embed Sharing
Embed sharing helps a host page include a vibe while preserving visibility, sandbox, and live-or-exact release intent.
User-facing embed sharing guide for live and exact Vibecodr runtime delivery.
Implementation focus
Use this when copying embed code from Vibecodr, choosing live or exact behavior, setting accessible titles, or diagnosing embed failures.
Expected outcomes
- Choose live or exact embed behavior.
- Use accessible iframe titles and responsive sizing.
- Know when a host product can use structured embed metadata automatically.
- Debug visibility, allowlist, and host-page frame failures.
Choose live or exact embed behavior
An embed can follow the live app identity or point at an exact published cut. Live embeds are best when the host page should keep following BUMP IT updates. Exact embeds are best for docs, audits, lessons, and demos where behavior must not change underneath the reader.
Both forms still depend on visibility, embed settings, and sandbox rules. A valid iframe tag cannot override a project that is private, disallowed for embedding, or pointed at an unavailable artifact.
- Use live embeds for active apps that should update in place.
- Use exact embeds for reproducible examples.
- Use Vibecodr's product-provided embed controls instead of hand-building embed URLs.
- Keep embed titles and descriptions aligned with the public post.
Copy embed code from the product controls
Embed code should be boring and explicit: an iframe source chosen by Vibecodr, a descriptive title, a stable size, and no extra permissions beyond the embed controls. The host page owns surrounding layout; the vibe owns the runtime inside the frame.
If an embed fails, check whether the embed was copied for the intended live or exact behavior, whether the app allows embedding, whether the published cut still exists, and whether the host site blocks frames through its own policy.
- Use a descriptive iframe `title` for accessibility.
- Keep the iframe responsive when the host page is responsive.
- Do not add camera, microphone, payment, or location permissions unless the public embed contract adds them later.
- Use host-provided structured embed support when another product can discover Vibecodr embed metadata automatically.
Example and read next
Example: a docs site needs a stable demo. Use the product embed controls to choose exact behavior when the example must not drift, and keep the iframe title aligned with the public post.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: Embeds
- Read next: BUMP IT
- Read next: Source & Versions
- Read next: Runtime Presentation