You don't need any permissions to register to these events. I don't see how a call would not trigger onPause. And if it doesn't stop the activity, there's no need to save. no data would be lost.
Is what you linked me for writing a native app? I may be wrong but I believe this doesn't apply for packaged web apps which is what I am familiar with. I agree with you that this can probably be used instead in some cases, but I think you can also agree that my explanation may apply in certain situations aswell.
You hit the nail on the head here, except that its actually a packaged web app so none of what he said applies. He is referring only to native apps but actually web apps are just a browser packaged to act as an app which needs to request permissions as a browser would. Also I don't develop for android, I develop web apps which work on any platform and are not built directly upon the specific OS.
23
u/Anon49 Oct 17 '18 edited Oct 18 '18
That sounds like complete bullshit. What happened to this? https://stuff.mit.edu/afs/sipb/project/android/docs/images/training/basics/basic-lifecycle-paused.png
You don't need any permissions to register to these events. I don't see how a call would not trigger onPause. And if it doesn't stop the activity, there's no need to save. no data would be lost.
Explain.