There will be errors you don't expect. We want information about why something failed to make the best possible change or to help the user respond.

BrightDigit Newsletter

Issue #34

Hello <>,

With this crazy year coming to a close, I wanted to talk about errors. It is now essential to know how to plan for, and respond to, Swift-based errors in your app. 

There will always be errors you do not expect. We want as much information about how and why something failed to either make the best possible change to the code or to help the user respond. However, what is most helpful for the developer is not always so helpful for the user, which is critical to understand if you want a successful app.

Our latest article is designed to help both developers and team managers:

• create a plan for dealing with errors; and
• offer examples of how to effectively handle the most common errors you’ll encounter.

In this article, I cover the three main ways you need to design for errors: **** https://brightdigit.com/blog/2020/12/08/swift-error-handling/

• Tracking Errors
• Testing for Errors
• Clear Communication to the User

As the year comes to a close with me and we can discuss your plans for 2021 and more: https://doodle.com/mm/leodion/book-a-time

Thanks, Leo