Crash-free ≠ successful
In mobile interviews, I often discuss one question: what happens to a feature after rollout?
Not the ticket in the tracker.
The feature itself.
How does the team know it didn’t just reach users, but actually works?
A feature can be broken without crashing the app once.
The hardest kind of mobile release is the quiet one. Pre-release checks didn’t show anything critical, Crashlytics is quiet, alerts are silent.
Then a day later you see it: users are entering the flow, but not reaching the result.
Somewhere an early return fired, a condition filtered out part of the audience, and the path just stopped. The app is alive. Formally, there is no incident.
But for those users, the feature doesn’t work.
In mobile development, “doesn’t crash” and “works” are two different system states.
Especially when the issue lives in one segment: an older app version, a specific OS, remote config,...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
