As I understand it, when I used the back button to “exit” an app, Android effectively just “pauses” the app, keeping it in memory ready to run if the user “starts” the app again. And Android may “unload” my "paused" app completely if it needs more memory at any time. My apologies if I do not know the correct terms for these operations.
When a B4A app is in this paused state, what happens to a service that the app has started? Is the service also paused, or does/can it continue to run in the background?
And what about timers? Are they paused as well? And if so, when the app starts again, does the timer continue from where it was (ie part way through the timer interval), or does the timer event fire if the time interval has expired while the app was paused?
Also, when an app is restarted from the paused state, is it restarted in exactly the same way as if the app had never been running?
On a kind of related note, why is it considered “bad” for an app to have an “exit” button? Might it not be easier for someone to press a button in the app rather than the official back button when they want to get back to the Android desktop?
When a B4A app is in this paused state, what happens to a service that the app has started? Is the service also paused, or does/can it continue to run in the background?
And what about timers? Are they paused as well? And if so, when the app starts again, does the timer continue from where it was (ie part way through the timer interval), or does the timer event fire if the time interval has expired while the app was paused?
Also, when an app is restarted from the paused state, is it restarted in exactly the same way as if the app had never been running?
On a kind of related note, why is it considered “bad” for an app to have an “exit” button? Might it not be easier for someone to press a button in the app rather than the official back button when they want to get back to the Android desktop?
Last edited:
