Explore 924 articles on Android performance
Showing 20 of 924 articles (Page 40 of 47)
Dmytro Khmelenko shares how a job candidate's pointed question about their 63 MB APK sparked a complete optimization overhaul. The results? A 62% size reduction that every Android team should study.
Joris Abale from Coupang reveals how they rescued a massive Android app drowning in God Activities and Fragment chaos. Their journey from architectural debt to 80% test coverage is a masterclass in pragmatic re...
Yelp's Android team cut search render time nearly in half while slashing dropped frames by 48%. Here's how they did it.
Teamweek just made a bold move: they killed their native mobile apps. Instead of maintaining separate iOS and Android codebases, they bet everything on a mobile-optimized web experience.
Pat Kua from N26 shares how the fintech company moved from Java to Kotlin for backend services. Their pragmatic, incremental approach turned a language migration into a productivity win.
Yelp users were literally grunting while waiting for search results to load. That's when the Android team knew they had a performance problem.
Todd Santaniello from Strava reveals what happened when their entire Android team stopped shipping features for a week. The goal? Break apart a 6.5-year-old monolithic codebase that was crushing build times and...
LinkedIn processes massive volumes of mobile crash data to keep their app stable for millions of users. Here's how they built the pipeline.
Tad Book from Square reveals how they built a datastore that handles massive merchant catalogs while keeping mobile devices in sync, even when offline for days. The secret? An append-only architecture that make...
Alizée Camarasa from BlaBlaCar shares hard-won lessons from migrating to Android O. Spoiler: their first solution caused app-wide deadlocks.
Kotlin's built-in TODO() is great, except it crashes your app in production. Kaushik Gopal built something smarter.
Meta's engineers were spending days or months debugging performance issues they couldn't reproduce in their device labs. Sound familiar?
LINE Engineering ditched expensive cloud testing services and built their own Docker-based infrastructure. The result? Flexible, cost-effective testing for both web and mobile.
Flipkart slashed their Android app size by 40% in 21 months. The result? A 34% drop in uninstall rates and massive gains in emerging markets.
Raj Varma from Bumble's engineering team reveals how to give your Appium tests superpowers. His solution lets test code directly call methods inside your Android app—solving problems that seemed impossible.
Dmytro Khmelenko reveals how Freeletics turned localization from a bottleneck into a fully automated pipeline. The results? Measurable revenue spikes in newly localized markets and zero manual translation work.
Vishnu Rajeevan from Trello shares how his team went from 0% to 30.8% Kotlin in just over a year. Their strategy? Start with tests, then make every new feature Kotlin-only.
Mihaly Nagy from Groupon reveals you don't need IntelliJ IDEA to build Android Studio plugins—just Gradle and a text editor. If you've automated tasks 3 times, it's time to build a custom IDE tool.
Ever wonder how Twitter's delightful logo-to-app loading animation actually works? Eli White reverse-engineered it and the solution is counterintuitive.
Saurabh Arora from Viki cut their Android app's memory footprint by 27% while preparing for the Next Billion Users. His team's optimization work landed them as an Android GO launch partner.