Curated Engineering Reads

The Best Reads on Mobile App Performance

How top companies optimize their apps for the best customer experience.

Clear Filters

Showing 20 of 1516 articles (Page 11 of 76)

Shingt from Mercari reveals how they transformed a single-product iOS codebase into a monorepo supporting multiple apps—without halting work for 50+ active engineers. The result? A 38.8MB binary despite 900+ mo...

Nightly Swift SDK for Android

Company: Swift.org Blog · Oct 24, 2025
Platform: Android

Joannis Orlandos just announced something that could reshape mobile development: you can now write Android apps in Swift. After a decade of Swift expanding to cloud, Windows, and browsers, it's finally landing ...

Nicolas Mayer Weiler from leboncoin shows why your 'accessible' Android component might still be failing users. Three stepper implementations, wildly different user experiences.

Google just dropped a comprehensive guide for Android XR performance optimization, and the stakes are higher than traditional mobile: miss your frame rate target and users get motion sickness, not just frustrat...

Delivering Mobile App Updates Faster

Company: Mercari · Oct 22, 2025
Platform: Android / iOS

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 ...

Mohomed Nawab reveals how QA became the unsung hero in PickMe's driver app overhaul. Most teams treat testing as a final checkpoint, but this approach flipped the script entirely.

The Groww Engineering Team just open-sourced their playbook for building trading charts that render 2,000+ candlesticks at 60fps. No third-party libraries, pure native Android.

Jacob Clausen from Expo shows how to break free from SDK limitations. Building custom native modules doesn't mean abandoning Expo's developer experience.

NavigationStack in SwiftUI works great until you're hunting through ten files to figure out why Settings opened the wrong screen. The coordinator pattern changes everything.

Real-time audio in React Native isn't just about playing files anymore. Callstack's engineering team reveals why buffer-based pipelines are becoming essential for voice AI, live streaming, and audio processing ...

Flutter's biggest performance criticism just got answered. Impeller, the new rendering engine, is rewriting the rules on cross-platform smoothness.

Esraa Eid from Deloitte UK tackles Swift code generation with a deep dive into SwiftSyntax and OpenAPI. If you've ever struggled with generating type-safe models from specs, this comparison will change how you ...

Students and recent grads: JetBrains is offering free trips to Munich for building Kotlin Multiplatform projects. The 2026 contest is open now, and the bar might be lower than you think.

Very Good Ventures reveals why global leaders like Disney, Toyota, and BMW are ditching fragmented native development for a single framework. The shift isn't just technical—it's transformational.

Google just dropped an experimental Flutter extension that turns Gemini CLI into an AI coding assistant that can build production-ready apps from scratch. This isn't just autocomplete: it's an agent that plans,...

React Native just dropped its most significant release ever. Version 0.82 completely removes the Legacy Architecture, marking what the team calls 'the start of a new era' for mobile development.

Esraa Eid from Deloitte UK reveals how to make Swift code generate Swift code—no low-level languages required. She explores three powerful approaches to transform JSON schemas into production-ready Swift struct...

Pierrick CAEN from Medium thought upgrading Apollo Kotlin would be straightforward. Instead, it exposed hidden cache issues that had been silently failing for months.

HelloFresh was running 6 mobile apps on 2 completely different tech stacks. Their teams couldn't ship features fast enough, and customers were getting inconsistent experiences across brands.

Loading articles...