How does android:noHistory=”true” work?

From the docs about noHistory:

A value of “true” means that the activity will not leave a historical trace. It will not remain in the activity stack for the task, so the user will not be able to return to it.

Regarding your question:

does the true stack of A, B, A, B, A, B exist?

The docs would indicate no.

I’m concerned with resource issues and not slowing down a users android device.

You really don’t need to worry about this. The OS should handle the cleanup of activities when memory is getting low. Its more likely that poor use of bitmaps or logic in your activities will result in performance slowdowns.

Leave a Comment