User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it a good design pattern, in this case for Android, to persist the application state for wherever the user is, or should this be done just for the first level of depth?

share|improve this question
What your app is about? It totally depends on what the application is. Mostly you should not save the state coz it can confuse the user. But since this question popped into your head, it might be good for your app! – kBisla May 11 '14 at 2:25
@BlueFlame by saving the state I mean saving what screen the user is at if he closes the app/rotates the device. It is a shopping list app. – autrilla May 11 '14 at 9:24
up vote 1 down vote accepted

Generally its not good to save the state because the user can get confused easily. But for a shopping list app, it might be a good idea.

When I go out for shopping, I want to see my list quickly. I'm overwhelmed at the store and my hands are already busy picking things. I'd appreciate if the saved state can save me a button press or two.

Btw I can't imagine a deep hierarchy for a shopping list app. There could be categories of lists and that's all; even sub-categories would be too much in my opinion. I'd reckon you save the state. But do keep a button to go back to the top level.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.