19 articles on Release Management for Android performance
Showing 19 of 19 articles (Page 1 of 1)
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.
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.
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.
Uber rewrote their entire driver app serving 3 million drivers. How do you ship that without breaking your business?
Alejandro Rodriguez Salamanca from Shopify reveals how manual mobile releases were killing their velocity. The solution? A platform that cut release cycles from 3 weeks to 1 week.
Daniel Schramm from Google Play just dropped new analytics tools that could transform how you think about subscription revenue. If you're leaving money on the table with failed payments, this matters.
Emily Putze from Google Play reveals why your mobile game launch strategy is probably outdated. The old playbook that worked in 2014's gold rush era is now a recipe for expensive failure.
Jeff Remer from Strava explains why their mobile app jumped from version 5.14 to 14.0 in just four months. Spoiler: it wasn't feature bloat.
React Native upgrades used to be a nightmare of merge conflicts and lost changes. The React Native team just changed that with a clever Git-based solution.
LinkedIn went from monthly releases to shipping mobile code 3x per day. Here's how they automated their way out of a month-long release cycle.
Purnima Kochikar from Google Play reveals how Android developers earned over $5 billion in payouts. With 1 billion active Android users, the platform just rolled out a suite of tools to help developers scale gl...