A staged rollout you control on one store and not on the others
Four channels, four halt latencies, and only one of them is under your hand.
release
13 posts
The shared module cost 400KB on Android and 11MB on iOS
Android shrinks against a runtime already on the device. iOS links yours in.
Four crash reporters, one shared module, and the traces nobody could read
The reporting SDK is platform code and the crash is in shared code.
One version, four numbering schemes, and a release that could not be rolled back
A monotonic integer, a build string, a semantic version and a cache-busting hash have to agree. Deriving all four from one source is the only shape that survives a hotfix.
Partial translation is a number, not a feeling
Per-locale coverage against the base key set is a number you can compute every release — without it, shipping a language is a guess nobody owns.
Where a secret lives should never be a decision
Six consumers each deciding where a keystore lives agree until one changes. One registry keyed by stack and category, one resolver, no direct reads.
The Play Store checks you only fail once
Price schedule, content rating, data safety, target API: the first-release prerequisites that reject a submission after the build already succeeded.
A release is phases, not a button
Collapsing a release into one command removes the only place a person could stop it. Separate the mechanical phases from the single judgement about timing.
Two prefixes decide who owns a credential
Whether a credential is organisation-wide or per-app has to be visible in its name, because the name is what every manifest and resolver decides from.
The placeholder listing that almost went live
A template store listing reaches production unless promoting the real one is a human gate that refuses. Why the failure is silent and what has to block on it.
Version state belongs in exactly one file
A version repeated across build files, manifests and tags is one fact with several caches. Decide which copies are derived and forbid everything else.
Shipping a model in your APK without breaking the size budget
Bundling a model trades download size for a guarantee. The decision turns on first-run experience, and the budget needs a gate rather than good intentions.