MUAZUABU
SENIOR MOBILE ENGINEER
.muazu
Delivery
Mar 3, 2025

Cutting Mobile Release Time From 48 Hours to 3

Cutting Mobile Release Time From 48 Hours to 3

A release that takes two days is not just slow, it changes behavior. Engineers batch changes to avoid the pain, which makes each release bigger and riskier, which makes the next one slower still. Breaking that loop was the highest-leverage delivery work I did, and it did not require a bigger team, just a pipeline that removed the manual steps.

I built the pipeline on GitHub Actions for orchestration, with Fastlane handling signing and store submission, Bitrise for native build capacity, and EAS for managed builds and over-the-air updates. A merge to the release branch now produces signed builds for both stores automatically, with versioning, changelogs, and upload to TestFlight and the Play console handled without anyone babysitting a terminal.

The unlock was not any single tool, it was removing the humans from the critical path. Every manual step is a place a release can stall overnight waiting for someone to wake up. Automating signing and submission is where most of the two days actually disappeared.

The payoff compounds. When shipping a fix takes three hours instead of two days, you ship more fixes, you ship them smaller, and you stop fearing the deploy. Over-the-air updates via EAS took it further, letting urgent JavaScript-only fixes reach users without waiting on a full store review at all.

more notes
.say hello

have a product to ship? i'm open for contract or full-time roles, let's talk about what i can take off your plate

contact me