Embed Technology & Viewport Resolution
ViewCore presents web applications, prototypes, and landing pages inside precise, pixel-accurate mobile hardware viewports. This guide outlines how iframe presentation, header security, and edge streaming operate across different web applications.
1. Direct Mode Rendering
Zero-latency native browser embedding
By default, ViewCore attempts to load web targets in Direct Mode. In Direct Mode, your target application renders straight inside an HTML5 inline frame (<iframe>) set to mobile dimensions (e.g. 393×852).
Key Advantages of Direct Mode:
- 100% OAuth Login Compatibility: Google Sign-In, Firebase Auth, and SSO popups communicate natively with origin servers without cookie restrictions.
- Zero Latency: Assets, scripts, and media load directly from your host origin.
- Localhost Support: Instant previewing for local development servers (
localhost:3000).
2. Proxy Mode & Frame-Busting Protocols
Bypassing restrictive HTTP response headers
Certain production websites (e.g. Google, GitHub, Notion, Figma, Twitter/X) emit security HTTP headers to prevent third-party embedding:
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self'
When target domains specify these headers, standard browser engines block direct iframe rendering. ViewCore automatically detects these restrictions and relays presentation through Proxy Mode, processing asset delivery to ensure responsive mobile viewport presentation.
3. Client Isolation & Security Model
Strict browser sandboxing enforcement
ViewCore enforces W3C HTML5 iframe sandboxing rules across all viewports to isolate host client state from target application code:
This ensures that target scripts execute safely within their own context while giving creators full interactive fidelity.
© 2026 ViewCore. All rights reserved.