Discover 209 articles on Architecture in mobile performance
Showing 20 of 209 articles (Page 10 of 11)
Valerii Che from Bumble's engineering team reveals why they ditched Storyboards entirely. Their code-first approach handles weekly feature releases without breaking existing functionality.
Martin Moizard from BlaBlaCar tackles a common RxSwift pain point: how do you elegantly track loading states without breaking reactive programming principles?
Gabriel Peal from Airbnb shares why they walked away from React Native after 2 years and 80,000 lines of code. The decision wasn't what you'd expect.
Facebook's React Native team just dropped a major announcement: they're completely rearchitecting the framework. After 5 years of learning what works (and what doesn't), they're rebuilding the internals while k...
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...
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.
Bohdan Orlov tackles one of iOS development's messiest problems: screen navigation that's actually testable and maintainable. Most apps get this wrong from day one.
Michael MacDougall from Etsy reveals how they tackled iOS architecture chaos with VIPER. The overhead was brutal, but the consistency payoff changed everything.
Bohdan Orlov from Bumble Tech tackles one of iOS development's most controversial debates: are Singletons and Service Locators actually anti-patterns, or just misunderstood tools?
Bohdan Orlov tackles one of iOS development's most controversial debates: when Singletons and Service Locators are actually useful (and when they'll wreck your test suite).
Bohdan Orlov from Bumble challenges a core assumption in iOS development: what if fighting UIKit is the real problem? His team's approach cuts boilerplate while keeping code maintainable.
David Muzi from Shopify reveals how they solved a tricky problem: giving merchants access to thousands of third-party apps on mobile without requiring any code changes from developers.
Martin Moizard from BlaBlaCar reveals a critical MVVM pitfall that breaks when you switch from simple views to UITableViews. The culprit? How you feed inputs to your ViewModels.
James Shephard from BBC explores how Kotlin's sealed classes can fundamentally reshape your Android architecture. What if callbacks aren't the answer to async operations?
Ross Harper from BBC's iPlayer team reveals how they ship to 45+ million downloads across thousands of device variants. Their secret? A shared codebase that builds two distinct products.
Lucia Payo from N26 reveals how combining RxJava, Clean Architecture, and Android Architecture Components created a system where code writes itself faster over time. The secret? Infinite data streams that never...
Wahib-Ul-Haq from Freeletics opens the vault on the complete Android tech stack powering four production fitness apps. This is the kind of transparency engineering teams rarely share publicly.
RxJava 2 was a complete rewrite with breaking APIs. If you're still on version 1, here's what changed and why it matters.
Twitch spent a week investigating React Native for their mobile apps. Here's what their Android team discovered about the framework's real-world viability.
UberEats needed a Restaurant Dashboard for 3-party logistics. Their web app couldn't cut it, so they bet on React Native before it was proven at scale.