Discover 28 articles on Release Management in mobile performance
Showing 20 of 28 articles (Page 1 of 2)
Umair Ali from ZAR reveals how his fintech team ships bug fixes to production in minutes instead of waiting days for App Store review. Their secret? A battle-tested OTA update system that's changed everything a...
Ishika Chakraborty from Expo breaks down how React Native teams ship multiple times daily without breaking production. The difference between 'it works' and 'I trust it' comes down to five key patterns.
Daniel Tome from Qantas reveals why mobile releases are fundamentally different: once your code ships to a user's phone, you've lost control of it forever.
React Native just unlocked a new platform: Meta's Horizon Store for VR apps. Callstack shows how to take your existing mobile codebase into virtual reality with minimal friction.
Manoj Kumar Gubba from Mercari's iOS team reveals how they ship mobile updates in just 3-7 days. Most teams take 1-2 weeks, but Mercari's approach cuts that in half while maintaining stability.
Manoj Kumar Gubba from Mercari's iOS team shares how they cut mobile release cycles from weeks to just 3-7 days. Their secret? A combination of trunk-based development and aggressive automation that most teams ...
Jawad Mashhadiea from Flink reveals how his team ships 4 mobile apps every single week with almost zero manual work. The secret? Treating releases like trains, not planes.
DoorDash was shipping experiments that crashed their app and degraded performance for weeks before anyone could identify the cause. They built an automated system to catch issues before customers feel the pain.
Alan Cooke from Squarespace reveals how Unfold turned chaotic mobile releases into boring background events. Boring is the goal, and here's why that's brilliant.
Illia Kucheriavyi from Revolut reveals how 120+ iOS engineers ship weekly releases across 5 apps while maintaining 150,000+ automated tests. Their secret? A mono-repo with 160 shared modules and build times tha...
Jamon Holmgren from Infinite Red breaks down Microsoft's App Center shutdown and maps out the migration path React Native developers need to take before March 2025.
DoorDash ships a new iOS app version every single week. Here's how they coordinate testing, releases, and hotfixes across multiple teams without losing their minds.
Manolo Sañudo from DoorDash reveals how their iOS team ships weekly releases without breaking things. Spoiler: it's not about having more QA people.
Swiggy got 700,000 users to update their app in one week without sending them to the Play Store. Here's how they did it.
Swiggy's Android team serves 1M+ downloads weekly with 52% of users updating within 5 days. That velocity could be a disaster without bulletproof automation.
Shubhnik Singh Mann from Razorpay reveals why most mobile teams are testing wrong. Their approach eliminated P0 production issues entirely.
GitHub Mobile ships to production every single week with a tiny team. Their secret? Ruthless automation that turns a multi-day release process into a Saturday morning workflow.
Dominik Sokal from Software Mansion shows how Expo's EAS Build changed the game: you can now build iOS apps from Windows, no Mac required. The React Native vs Expo debate just got a lot simpler.
Guillermo Mazzola from Glovo cracked a problem most teams avoid: using Kotlin Multiplatform without forcing everyone into a monorepo. His solution? Publishing native CocoaPods and NPM packages directly from KMP...
Uber rewrote their entire driver app serving 3 million drivers. How do you ship that without breaking your business?