I'm new to fragments and the like, but I'm suspicious of this article. Is saving fragment state on a application really a good idea?
3 plus ones
Shared publicly•View activity
View 13 previous comments
- Hi, it's been a few moths, but what happened with this?Oct 26, 2014
- Unfortunately this fell off my priority list :D. Having said that, the reservations expressed by fall under two broad categories:
1) The use of a custom Application class to save the fragment back stack state. This was just an example - you could use a singleton or any other mechanism you wish to.
2) Misplaced use of Fragments in the first place. In the recent weeks there have been few articles denouncing the use of Fragments altogether (for example Square wrote a blog post advocating against the use of Fragments). While I do not agree with those opinions, Adam Powell makes a point that people often opt for a Fragment where a custom View would suffice. This is especially true of nested fragments.
If there are specific questions you have I'd be glad to discuss.Nov 6, 2014
- We've been a little busy getting this Lollipop thing out the door so I haven't had time to write anything up on this just yet. I haven't forgotten about it though.Nov 6, 2014
- Hi! I'm interested in this topic, since I don't find a clean way to do this. I would love any explanation of the concepts involved here. Best regards!Nov 20, 2014
- Any update on this?Feb 9, 2015
- As I mentioned in a previous comment, this is no longer on my list of priorities. Having said that, if there is any specific point you'd like to discuss, I'd be glad to.Feb 9, 2015