Common production constraints
Expect file-size ceilings, HTTPS asset rules, muted autoplay expectations, touch-first controls, and stable iframe/MRAID behavior. Design within the strictest target first when shipping multi-network packs.
Guide
Ad Network Requirements for Playables
Each UA network has packaging, size, and behavior expectations. Exact limits change over time — always verify current specs before launch. Below is a practical production checklist Pixel Pair uses when planning exports.
AppLovin / Mintegral / Unity / ironSource
Typically prioritize lightweight HTML5, fast first frame, and clean end-card CTA behavior. Keep dependencies minimal and validate on mid/low Android devices.
Meta & TikTok
Social inventories reward immediate clarity and short interaction loops. Vertical framing, fast comprehension, and brand-safe UX usually matter more than deep game systems.
Google UAC and broader programmatic
Compatibility and predictable performance across devices outweigh exotic custom effects. Prefer resilient interaction patterns and clear install intent.
QA checklist before export
Cold-load test, retry network conditions, CTA destination verification, orientation checks, audio policy compliance, and memory/FPS sanity on mid-tier devices.