Interactive 3D Entertainment Web Experience Optimization Plan
Create a rigorous performance optimization and delivery plan for an interactive WebGL promotional campaign site.
Use this template when preparing high-end interactive 3D web campaigns for film launches, games, or album releases. It establishes strict asset budgeting, shader optimization, and device-tier adaptation.
Role: Senior Creative Technologist specializing in WebGL performance engineering and interactive web storytelling.
Context
- Feature project: {{movie_campaign_title}}
- Target framerate baseline: {{target_framerate_budget}}
- Initial bundle size cap: {{max_initial_bundle_size}}
- Rendering engine: {{primary_webgl_library}}
- Baseline hardware target: {{target_low_end_device_profile}}
- Observability stack: {{analytics_telemetry_provider}}
Task
Draft an optimization and release plan for the {{movie_campaign_title}} web experience that maintains {{target_framerate_budget}} across diverse desktop and mobile browsers.
Method
- Analyze 3D asset compression workflows (Draco, Meshopt, KTX2/Basis Universal) to conform strictly to {{max_initial_bundle_size}}.
- Design progressive scene loading and asset streaming pipelines using {{primary_webgl_library}} to allow instant user interaction.
- Define dynamic GPU tier detection algorithms that downgrade post-processing passes and shadow maps on {{target_low_end_device_profile}}.
- Audit shader complexity, draw calls, and vertex counts, establishing hard budgets per interactive scene.
- Specify memory management policies to clean up WebGL textures and buffers during route transitions without memory leaks.
- Integrate performance telemetry through {{analytics_telemetry_provider}} to track real-time frame drops and canvas context loss events.
- Detail accessible fallback interactions for screen readers and environments where hardware acceleration is disabled.
Constraints
- Initial render MUST occur within 2.5 seconds over standard 4G mobile connections.
- Memory consumption MUST NOT exceed 300MB VRAM on mobile browsers to prevent out-of-memory context crashes.
- The application MUST include a full canvas context recovery handler without forcing a page reload.
- Critical interactive affordances must support WCAG 2.1 AA non-canvas navigation alternatives.
Output format
Provide a technical blueprint across five sections: Asset Optimization Matrix, Dynamic Rendering Tiering, Memory & Lifecycle Controls, Telemetry Integration, and Pre-Launch Verification. Keep length within 750 to 1000 words.
Self-review
- Ensure memory disposal steps directly reference object disposal routines in {{primary_webgl_library}}.
- Confirm that device capability thresholds account specifically for {{target_low_end_device_profile}}.
- Verify bundle size constraints conform directly to {{max_initial_bundle_size}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.