Explore 891 articles on Android performance
Showing 20 of 891 articles (Page 38 of 45)
Slack's engineering team faced a classic scale problem: three platforms, three definitions of 'app launch,' and zero ability to compare performance meaningfully.
Cesario Putera from Blibli.com shows how Google's ML Kit brings powerful face detection to Android apps with surprisingly little code. No PhD required.
Jamal Eason from Google just opened up hardware-accelerated Android emulation to thousands of developers who were stuck with slow software emulation. If you've been running AMD processors or Hyper-V, this chang...
Dmytro Khmelenko breaks down how Android App Bundle reduced their app size by 20% without changing a single line of code. Here's how Google's 2018 feature actually works under the hood.
Ahmad Fadli Basyari from Traveloka watched build times balloon from 3 minutes to 10 minutes as the app grew from 3 products to 20+. His team's solution? Rewrite the entire app twice in three years.
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.
Zalando proved that every 100ms of loading time equals real money: a 0.7% revenue lift per session. When 75% of your traffic is mobile, milliseconds become millions.
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.