Non-fatals vs. Crashes, which ones are more important?
You could argue that crashes are more vital since they "break the app." However, non-fatals can break the app as well but are often recoverable.
This week at WeTransfer, we discussed our process around handling non-fatals, in which we agreed that we should handle them the same as crashes. With that, we mostly mean prioritizing non-fatals just like crashes and fixing them if they occur for many users.
If a non-fatal occurs a lot but does not become a reason for action, we consider logging such an error no longer. This way, we will end up with a list of critical non-fatal errors only.
In a way, this reminds me of many discussions around force unwrapping. Many engineers try to avoid force unwrapping as much as possible, prevent their apps from crashing. It makes it easy to say, "my app is 99.3% crash-free!". Though, does that mean your app is performing great?
You should take non-fatals just as seriously as crashes since they likely hurt user experience.
----
This week is full of articles, so prepare yourself. Enjoy this week's SwiftLee Weekly! |
