Discover 46 articles on CI/CD in mobile performance
Showing 20 of 46 articles (Page 1 of 3)
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...
Emre Erkek from Getir reveals how they turned Maestro from a simple testing tool into a deterministic platform that runs thousands of tests daily. Most teams fail at E2E testing scale—here's the architecture th...
Expo just unified mobile CI/CD orchestration into a single YAML file. EAS Workflows now handles builds, tests, submissions, and OTA updates without juggling multiple tools.
Umair Ali from ZAR Engineering turned weeks of mobile development work into single days by eliminating a hidden productivity killer. The secret? Rethinking how Git worktrees interact with AI coding assistants.
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.
Reddit's mobile team had zero professional CI experience. Then they cut build times in half and transformed developer happiness.
Your React Native CI builds are probably slower and more expensive than they need to be. Callstack just shared a practical caching strategy that could change that.
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...
Alberto De Bortoli from Just Eat Takeaway reveals how his team built a fully automated iOS CI system that supports 40+ developers with just 5 bare metal instances. No manual SSH. No weekend waste. Pure infrastr...
Bevan Christian from IDN Engineering breaks down a CI/CD cost problem most teams ignore: GitHub Actions bills can hit $1,440/month for a 10-person team doing basic PR testing. His solution? Move testing local w...
Bevan Christian from IDN Engineering cut iOS CI/CD time by 76.85% with one platform switch. Here's how a simple migration delivered results most teams only dream about.
Square manages hundreds of mobile engineers in a monorepo, all contributing to apps that must stay under Google Play's 150 MB limit. How do they prevent app bloat at scale?
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
Slack's 8-person Mobile DevXp team saved $240K annually just by improving PR notifications. Most companies are massively underinvesting in developer experience.
Johnson Li from Coupang reveals how migrating from Mac minis to AWS EC2 transformed their mobile CI/CD pipeline. Their team was drowning in 3,000+ daily builds with 1-hour wait times.
Swiggy's iOS team slashed build wait times by 80% and cut 8-10 minutes off every build. Here's the detailed playbook they used with Bitrise.
Swiggy's mobile team was drowning in Jenkins bottlenecks. Build times were slow, machines crashed frequently, and manual interventions killed velocity.
Pierre Abi-aad from leboncoin took Xcode Cloud for a test drive with a 28-developer iOS team. His verdict? Not ready for complex architectures, but Apple's onto something.
Very Good Ventures just open-sourced their internal CI/CD secret weapon for Flutter teams. If you're still writing GitHub Actions from scratch for every project, you're working way too hard.