How Robinhood removes 30% of its iOS crashes
Original post Removing 30% of our iOS crashes
Article Summary
Robinhood's iOS team eliminated 30% of ALL app crashes by refactoring a single screen. Here's how they turned their most critical (and most broken) feature into a performance win.
The Robinhood engineering team shares their journey refactoring the Options Chain screen on iOS, a feature that handled roughly 30% of company revenue but was responsible for nearly a third of all crashes. They migrated from a legacy 5-year-old implementation to their modern NAPA architecture and Titan data framework.
Key Takeaways
- Single screen refactor eliminated 30% of all iOS crashes across the app
- Switching between calls and puts became 200% faster with new architecture
- Reduced codebase by 30% while improving testability with 28 snapshot test variations
- Used RxSwift optimizations and custom UIScheduler to fix scrolling performance issues
By migrating their highest-revenue screen from legacy Core Data to modern architecture patterns, Robinhood achieved dramatic stability and performance gains while reducing code complexity.
Continue reading
Meta
Aug 24, 2015
More from Robinhood
How Server Driven UI is Helping Frontend Engineers Scale Impact
Robinhood
May 15, 2023
Also on iOS
Never Miss a Critical App Crash Again: Integrating Firebase Crashlytics with Google Chat
PickMe
May 10, 2026
This page summarizes “Removing 30% of our iOS crashes” by Robinhood, published Jun 21, 2022. All credit for the original work goes to the authors.
