Android P brings a bunch of new stuff to the table as an improvement over its previous version, which is Android O. These include new navigation gestures, Slices API, and new biometrics API and a lot of other balances and changes which affect how the OS works. Among these is the inclusion of a feature that takes the “App Not Responding” dialog box to the background. In the previous versions of Android, if the app which is currently running in foreground does not respond, the user is intimated. But now with Android P, the OS is just crashing the app without informing the user about it.
This is almost a shoutout to developers with this feature and Google’s way of asking them to find an efficient way to deal with an app that is not responding. Though developers are not supposed to run apps in the foreground thread, it if up to the developers to address the issue. As seen in the video below, Google has addressed solutions that involve the use of AsyncTask API. With Android’s recent limitations on background services developers should take care that their apps are not transitioned to a service.
This feature from Google will make it appear that app crashes are happening less often and is a good way to not throw up emergency signals in the head of the user. But this also means that developers will get less crash reports from users themselves and will have to rely on their tools like Firebase crash reporting for their intel. There is a way developers can bring back the app crash notifications and that is by enabling a setting in Developer Options.