Discover 209 articles on Architecture in mobile performance
Showing 20 of 209 articles (Page 9 of 11)
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.
Jesse Wilson from Square tackles a problem every mobile team knows too well: building everything twice. His solution? Stop treating iOS and Android as separate worlds.
Emily Fortuna from Flutter reveals why most developers use Keys wrong—and when you actually need them. Spoiler: it's not as often as you think.
Engin Deniz Usta from Connected2me shows how generic protocols can eliminate boilerplate code that iOS developers write dozens of times per project. No more casting, no more repetitive XIB and Storyboard initia...
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.
Marli Oshlack from Airbnb reveals how they slashed iOS screen development time from weeks to hours. The secret? Rethinking the entire approach to UI layout.
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.
Alexis Santos from Bumble reveals how his team transformed iOS UI development from chaotic to scalable. The secret? A custom framework that cut compilation time and eliminated code duplication.
Tobias Carryer from Hootsuite built a reusable iOS framework during his summer internship—a sliding drawer component inspired by Apple Maps. Here's how he turned it into a production-ready, testable framework t...
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.
Valerii Che from Badoo's iOS team reveals why they ditched Storyboards and XIBs entirely. Their code-first approach handles weekly feature releases without breaking existing functionality.