Databases
StackOverflow2013
Postsdbo
POIOS Saving State For Complex Apps
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIOS Saving State For Complex Apps
    primarykey
    data
    text
    <p>I'm building a fairly complex business application on the iPad IOS 4.2: 4 tabs, with potentially deep navigational paths on each tab.</p> <p>In the opinion of some of your more experienced IOS developers, what would the general expectation of a user be with respect to saving application state between launches (i.e. after an app's been fully terminated and subsequently restarted)? I'm using Core Data and have all the data issues covered, but I'm concerned about the application's navigational tree. If the user had left the 1st tab on screen 3, the 2nd tab on screen 4, the third on screen 2, where he left the entry of a new record half-complete, and was, at the time of the app entering the background, working on the 4th tab on screen 3...do you think the average user would expect the application to remember all that the next time it launched? (My gut says yes, though I'm unsure for how long.)</p> <p>If the answer is yes, can you suggest a general strategy for handling this (and, again, I'm talking about the navigational tree here, not Core Data stuff)? For example, if navigational controllers were used as the root view controller for each tab, it would be simple enough to record enough info about their navigational stacks to be able to restore them later. But what about things like popovers, alert/action sheets, or modal VCs created on the fly? Should each view controller record the state of its UI objects and, if so, what is the recommended way to do this?</p> <p>I know a lot of this is up to the user, but I'm asking for the general perspective on these issues, i.e. the voice of experience.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShalfer
    1. USwayne
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIOS Saving State For Complex Apps
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIOS Saving State For Complex Apps
      1. USBP.
      1. VTFavorite
    3. VO
      singulars
      1. POIOS Saving State For Complex Apps
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI guess you can use `NSCoding` with `NSKeyedArchiver` and `NSKeyedUnarchiver` to archive all view controllers. Not sure if it works, but `UIViewController` does conform to `NSCoding`.
      singulars
      1. POIOS Saving State For Complex Apps
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload