Explore 25 articles from Bumble on mobile performance
Showing 20 of 25 articles (Page 1 of 2)
Yury from Bumble Tech tackles a problem every Android team faces: how do you build design system components that are both easy to use and flexible enough for edge cases?
Mike Pesate from Bumble breaks down Publishers in SwiftUI and Combine with real-world examples. If you're still confused about when to use CurrentValueSubject vs PassthroughSubject, this one's for you.
Andrey Kovalev from Bumble's engineering team challenges a fundamental assumption: what if Jetpack Compose Navigation's string-based routes and hardcoded BackStack are holding your Android app back?
Zsolt Kocsi discovered that Jetpack Compose's lack of shared element transitions wasn't a limitation. It was an opportunity to build something better.
Zsolt Kocsi from Bumble built a chess app in Jetpack Compose to solve a problem that's frustrated beginners for years: engines tell you a move is bad, but never explain why.
Alexander Kulabukhov from Bumble Tech reveals the hidden costs of iOS modularization that nobody warns you about. Spoiler: visualizing 50+ module dependencies looks like a tangled mess, and your CI will cry for...
Lachlan McKee from Bumble Tech tackles a critical scalability problem in Jetpack Compose Navigation that Google's docs don't address. His solution? Delegate route creation to feature modules using Dagger Hilt f...
Bumble's iOS team hit a wall: dozens of engineers, hundreds of modules, and Xcode was buckling under the pressure. Sound familiar?
Bumble's iOS team migrated their entire codebase to Tuist in Q2 2023, choosing it over SPM and Bazel. Here's what happened after the dust settled.
Bumble's iOS team faced a critical choice: which build system could handle hundreds of modules and future growth without crushing developer productivity?
Alexander Kulabukhov from Bumble reveals how his team scaled from a monolithic iOS app to 110+ modules across Badoo and Bumble. The journey wasn't just about splitting code—it was about building a sustainable p...
Bumble's Android app was bleeding users to ANR dialogs. Their ANR rate sat above Google Play's threshold, threatening search rankings and user trust.
Bumble's Android team slashed their ANR (Application Not Responding) rate by 6x. Here's how they debugged one of mobile's most frustrating problems.
lem from Bumble Tech tackles a tricky iOS challenge: how do you bundle legacy C libraries into modern Swift frameworks without breaking portability?
Kateryna Sprynsian from Bumble Tech shares a hard truth: when iOS 12 launched, 60% of their users updated within 8 weeks. Were they ready? Here's how they avoided disaster.
Konstantin Yakushev from Bumble reveals the brutal truth about universal links: Apple and Google's 'simple' solution is riddled with undocumented bugs that break user experience. Here's how Badoo's team catalog...
Arseny Batyrov from Badoo's QA team built the mobile testing guide he couldn't find anywhere else. After combing the internet for tool comparisons and finding nothing comprehensive, he created this definitive b...
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.
Muhammad Shuaib Khan from Bumble Tech explains why Swift 4.1 killed off a popular method. The culprit? A naming confusion that was breaking code in subtle, dangerous ways.
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.