Mobile app experiments must account for app store reviews, offline usage, and SDK constraints. This quiz tests rollout patterns, telemetry, and guardrails on iOS and Android.
A common mobile rollout pattern is to use feature flags with ______ percentage releases.
staged
random CSS
pixel‑based
one‑shot 100%
Because users can be offline, event uploads in apps are often ______ and delayed.
printed to logs only
blocked by CSS
buffered
deleted instantly
If a device identifier resets, users may be reassigned to a new bucket; this risks ______.
PNG gamma shift
sample contamination
font fallback
SVG overflow
On iOS, app review timing can delay experiment fixes; teams often keep a remote ______ to change behavior without a new binary.
config/feature flag
PNG sprite
camera roll
CSS grid
In‑app message tests should include guardrails like crash rate and ______ to catch harm early.
image EXIF
latency
scroll depth color
font kerning
For unbiased attribution, the randomization unit in apps is typically a stable ______ ID.
tab
pixel
user
font
Push notification experiments must consider quiet hours and ______ frequency caps.
user‑level
GIF‑level
screen‑level
font‑level
To analyze experiments across iOS and Android together, ensure consistent event names and ______.
icon sizes only
parameter schemas
color spaces
SVG paths
When rollout reaches 100%, keeping a small holdout helps estimate ______ lift over time.
EXIF
port
long‑run
pixel
Deep‑link A/B tests should track both open rate and downstream ______ to capture true value.
conversion
stroke width
palette
viewport
Starter
You’re new to experimentation in mobile apps. Review definitions, guardrails, and simple examples to build confidence.
Solid
Good grasp of experimentation in mobile apps. Tighten design choices and deepen your analysis habits.
Expert!
Excellent command of experimentation in mobile apps. You’re ready to operate at scale and mentor others.
