93 articles on Architecture for Android performance
Showing 20 of 93 articles (Page 4 of 5)
Rob Pridham from BBC Sport ditched the trendy frameworks and went old school—callback listeners and view controllers—to modernize their Android app. Controversial? Maybe. Effective? Absolutely.
Netflix Android engineers migrated 170 API endpoints from a monolith to a new microservice without users noticing. Here's how they pulled it off over a year.
Yehezkiel L from Tokopedia cut their dependency injection boilerplate dramatically by migrating from Dagger Android to Hilt. The result? Cleaner code, faster onboarding, and way less confusion for their team.
The React Native team at Facebook just pulled back the curtain on how they decide what to build next. Spoiler: cross-platform consistency isn't their top priority.
Ninad MG from JioHotstar challenged Android best practices and won. His team's unconventional approach to RecyclerView architecture now powers a social feed with 20+ card types across multiple teams.
Slack's desktop client was grinding to a halt as teams scaled. The culprit? An over-reliance on browser LocalStorage that seemed smart at first.
Cash App's Android team chose presenters over ViewModels and MVVM. Here's why their "boring" code wins.
Roman Iatcyna from Revolut reveals how they built a reactive data layer that handles offline-first architecture at scale. Their solution? A custom DataObservableDelegate that abstracts away the complexity of mu...
Alifa Nurani Putri and Yusuf Cahyo Nugroho from Traveloka reveal how their single Dagger component ballooned to 17,705 lines of code across 25+ products. Their refactoring journey cut initialization time and bu...
Kevin, a Staff Engineer at Slack, shares how a distributed mobile team ships features across Vancouver and San Francisco without stepping on each other's toes. His secret? Strategic work separation and dogfoodi...
Eyal Guthmann from Dropbox shares a hard truth: writing code once in C++ cost them more than writing it twice in native languages. Here's why their cross-platform strategy backfired.
Andrew Winata from Blibli shows how ditching raw SQLite queries for Room cut boilerplate code and made database operations type-safe at compile time. The migration took just a few strategic refactoring steps.
Gojek's driver app serves 2 million+ partners who depend on it for their daily income. When the app goes down for even an hour, drivers lose significant earnings—so a rewrite was high stakes.
Seongchul Park from Coupang reveals how their Android team escaped the 'big ball of mud' by rethinking how they organize code. Spoiler: it wasn't just about modules.
Carlos Palacin Rubio from Groupon's Android team reveals why your "optimized" UI code is actually killing reusability. Spoiler: that single ConstraintLayout you're so proud of? It's a maintenance nightmare.
Seongchul Park from Coupang reveals how they tackled a monolithic Android codebase with hundreds of thousands of lines of code. The solution? Strategic modularization that transformed both build times and code ...
Zsolt Kocsi from Bumble reveals how his team tamed the chaos of reactive Android components. The secret? Two minimal interfaces and a powerful abstraction that makes subscription management disappear.
Zsolt Kocsi from Bumble reveals how their chat module had bugs so elusive that QA could record them happening but developers could never reproduce them. The culprit? Uncontrolled state management in a massively...
Zsolt Kocsi from Badoo reveals how their chat module kept losing first messages despite a full Clean Architecture rewrite. The culprit? Uncontrolled state mutations in a massively asynchronous app.
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...