StartActivityForResult is Deprecated!
Rate this article
Android has been on the edge of evolution for a while recently, with updates to
1.2.0. It has deprecated
startActivityForResult in favour of
It was one of the first fundamentals that any Android developer has learned, and the backbone of Android's way of communicating between two components. API design was simple enough to get started quickly but had its cons, like how it’s hard to find the caller in real-world applications (except for cmd+F in the project 😂), getting results on the fragment, results missed if the component is recreated, conflicts with the same request code, etc.
Let’s try to understand how to use the new API with a few examples.
As you would have noticed,
registerForActivityResult takes two parameters. The first defines the type of action/interaction needed (
ActivityResultContracts) and the second is a callback function where we receive the result.
Nothing much has changed, right? Let’s check another example.
The above snippet is the complete code getting a preview image from the camera. No need for permission request code, as this is taken care of automatically for us!
Another benefit of using the new API is that it forces developers to use the right contract. For example, with
ActivityResultContracts.TakePicture() — which returns the full image — you need to pass a
URI as a parameter to
launch, which reduces the development time and chance of errors.
This has been another issue with the old system, with no clean implementation available, but the new API works consistently across activities and fragments. Therefore, we refer and add the snippet from example 1 to our fragments.
Old Way: 😄
With the new API, this is possible using
I have found the registerForActivityResult useful and clean. Some of the pros, in my opinion, are:
- Improve the code readability, no need to remember to jump to
registerForActivityResultused to launch components, clearly defining the input parameter for desired results.
- Removed the boilerplate code for requesting permission from the user.
Hope this was informative and enjoyed reading it.