I share a proposed solution for this further down. See StackOverflow – Difference between using Throwable and Exception in a try catch for why this should not be always be done. This also means it catches Errors like OutOfMemoryError. While using Result with this runCatching method is very simple, there are some flaws: If you simply want to use the return value inside an existing try-catch or don’t care about if it fails, you can take a look at getOrThrow() and getOrNull().

Difficult to locate missing try-catches: ✅ Fixed! You can focus on writing success/error handling when needed only without having to worry about exceptions popping up unexpectedly.

That way, you have only two solid return types to deal with.

No more surprises! If you use Flow, you could make use cases return either Result or Flow directly. Inconsistent API: ✅ Fixed! Every use case returns the Result wrapper.With the runCatching extension you do not have to manually instantiate the Result class: class PostCommentUseCase(). There are useful methods to handle either of these values. The Result class is a simple data structure to wrap data using Result.success(myData) or an exception using Result.failure(ex). Airplane mode could prevent code that actually throws exceptions from ever being reached.

Difficult to find where try-catch is missing.

Inconsistent API if some use cases throw exceptions while others don’t require any try-catch.

No obligation to catch exceptions, easy to forget.

Writing plain try-catches around every use case you call works fine, but has some disadvantages: Try-catchįirst, let us see what problem Result solves.

The Result class can solve this issue and help make your code more resilient, but there are some pitfalls to be aware of. the compiler does not enforce you to catch anything), it is easy to forget to add the required error handling in calling locations. Since Kotlin does not have checked exceptions (i.e. For example, we would probably expect a PostCommentUseCase to throw some sort of network exception when it fails. When writing use case classes, an important thing to consider is the output for failures.

Kotlin use