Most playable ads are a single HTML file that runs on both iPhones and Android phones. That is one of the format's advantages: one build, two platforms. But the two platforms are not the same environment. The store the CTA opens, the way sound and video are allowed to start, the range of devices and the measurement that follows the click all differ.
This guide covers the differences that affect how you design, test and measure a playable. It is written for advertisers and producers rather than SDK engineers.
Where the CTA leads
The install button has to open the right store: the App Store on an iPhone, Google Play on Android. There are two common ways this happens.
- The network's container handles it. The ad calls the network's own open or install function, and the network opens its store page, often as a sheet inside the app rather than leaving it. This is the usual route in in-app networks, and it is why networks ask for their specific call.
- The ad chooses the link itself. When the ad must pick, it detects the platform and opens the App Store link or the Google Play link accordingly.
Either way, both store links must be correct, and both should be tested on a real device. A wrong link on one platform halves the ad's effectiveness without any error appearing. Check that the link points at the right country storefront if the app is not available everywhere.
Sound and video
Both platforms restrict media that starts on its own. On iOS, WebKit's published policy allows muted video, or video with no audio track, to play without a user gesture, while video with sound needs one; if a video gains sound without a gesture, it pauses. On Android, web views have a setting that requires a user gesture before media plays, and it is on by default. In both cases the app showing the ad controls the web view's settings, so behaviour varies between networks and apps.
The practical rules are the same on both platforms:
- Start silent. Assume no sound until the viewer touches the ad.
- Start any music or sound effects on the first touch, which counts as the gesture.
- Make every important moment work without sound.
- Respect the network's mute setting where it provides one.
Playable ad audio covers sound design for muted autoplay, and blank screens and silent audio diagnosed covers what to do when sound never starts.
Device range and performance
The iPhone range is narrow: a limited number of models, a predictable set of screen shapes and fast processors even several generations back. Android spans a huge range, from flagship phones to inexpensive devices with modest memory and slow processors, and screen shapes from tall and narrow to almost square.
That makes Android the harder target for performance. A playable that runs smoothly on a recent iPhone can stutter on a budget Android phone, especially with heavy images, many effects or real 3D. Since inexpensive Android devices are common in many fast-growing markets, an ad that only works well on high-end phones quietly loses those audiences.
- Keep the first scene light so it appears quickly on slow devices.
- Test on at least one low-end Android phone, not just an emulator.
- Watch frame rate during the busiest moment of the ad, not just at the start.
- Check layouts on very tall and nearly square screens; Android has both.
Playable ad performance has detailed budgets.
Screens, notches and system bars
Both platforms have notches and cut-outs, but they differ in shape and position: iPhones put the camera area at the top centre and a home indicator at the bottom, while Android phones may have a hole-punch camera in a corner or the centre, and either gesture navigation or a button bar. Design text and buttons inside generous margins rather than for one phone's shape. Safe zones in mobile ads covers this.
Fonts and rendering
Each platform has its own system fonts, so text set in a system font looks different on each, and wraps at different points. If the layout depends on exact text widths, embed the font in the playable. Make sure the embedded font covers every character the ad uses, or the device will substitute its own font for the missing characters. Custom fonts in playable ads explains how.
Measurement after the click
Measurement differs the most. On iOS, since iOS 14.5 apps must ask permission through App Tracking Transparency before tracking users across other companies' apps, and many people decline. Install measurement for those users relies on Apple's privacy-preserving frameworks, SKAdNetwork and its successor AdAttributionKit, which report results in aggregated, delayed form. On Android, device-level attribution is still more widely available, although users can delete or reset their advertising ID and privacy rules keep changing, so check the current position for the markets you target.
The result is that creative comparisons are usually faster and more granular on Android, and coarser on iOS. Some teams test new creative concepts on Android first and then confirm the winners on iOS. SKAdNetwork and playable ads and AdAttributionKit vs SKAdNetwork cover iOS measurement in depth.
Store pages and policies
The click lands on a different store page on each platform, with different screenshots, ratings and text. If the ad promises something, both store pages should show it. Both stores also let you build alternative pages for specific campaigns: custom product pages on the App Store and custom store listings on Google Play. Custom product pages for playable ads explains how to match the landing page to the ad.
A two-platform test checklist
- Open the exported file on a real iPhone and a real Android phone, including one inexpensive Android model.
- Confirm the first frame appears quickly and the first touch responds at once.
- Confirm sound starts on the first touch, and the ad still makes sense muted.
- Tap the CTA on both and confirm each opens the right store listing in the right country.
- Rotate both phones if the placement allows both orientations.
- Preview in each network's own test tool, which runs inside its real container.
Playable Ads Maker exports one file that opens the right store on each platform and packages it for each of 12 ad networks with the store call that network expects. How to test a playable ad properly has the full QA process.
Create playable end cards in minutes—no code required.
Open Playable Ads Maker