← Writing
Android and iOS side by side
Keeping native Android and iOS apps in step: feature parity, permissions, and what should stay different on each platform.
- The App-Rescue PlaybookYour App Should Still Be Yours When the Developer LeavesMost handovers get the code across. The things that decide whether someone else can ship next week are the history, the keys, and whose name is on the accounts.September 24, 2026 · 7 min read
- The App-Rescue PlaybookCall, Text, and Share Without Asking for a Single PermissionThe obvious way to add a call button, a text button, and a save-to-contacts button reaches for permissions the app never needs. On Android one of them can get you pulled from the store; on iOS it puts you on record as touching data you never read. Here's the version that holds none of them — on both platforms.August 25, 2026 · 8 min read
- The App-Rescue PlaybookYour iOS and Android Apps Are Supposed to Be the Same Product. One of Them Isn't.Feature disparity between your platforms doesn't show up on any dashboard. It shows up in reviews that compare your app to itself — and in the churn of users who never knew what the other platform had.August 14, 2026 · 9 min read
- The App-Rescue PlaybookBefore You Rewrite an Inherited App, Stabilize ItWhat twelve years of inheriting other people's mobile codebases taught me about the 'just rewrite it' reflex.July 8, 2026 · 6 min read