Stephen is out on jury duty today, and he's the expert on the persistence doc, so don't take my feedback as gospel....
I wrote a simple app, changed things on the initial view, closed the app, and my changes were present when I reopened it, so It looks like the data object gets created as you make changes to the first view.
That's my experience too. I have to say - the "data" concept is an odd one. In some cases it acts like an Arguments scope (ala ColdFusion) for Views. I can load a view and pass crap in and it works great. But it also acts like a "This is stuff you should care about!" scope in terms of persistence. It all kinda works but feels a bit underdocumented/fleshed out. I say that with all due respect. The confusion is probably all just me being new to it.
Yeah. Now that the dust has settled a bit, I'll ask Stephen to look in to this and see what else we can say.
Thanks for the feedback,
So how the persistenceManager works is when the application is shutdown, it will automatically save all the information that is stored in each view's data property, and any data set using the persistenceManager.setProperty() method. When the applicaiton is relaunched, the data property will be assigned to what it previously was. It is the responsibilty of the developer to initialize a view's state based on the data when the view is created.
All views, regardless of whether its the first one or not, has a data property, and the information will be saved. As stated above, you can also use the setProperty() method to save other data or more global information.
Hopefully that helped, if not, let me know.