ForumsSearch

Search results for "Posted by Scott Johnson"

Author	Message
Scott Johnson	Posted Dec 09, 2009 in: iPhone app Todo note edits lost switching applications Score: 0 Scott Johnson Posted: Dec 09, 2009 Score: 0 This isn't related to syncing-- it's related to not saving the complete state of the app when a context switch comes in. I'm a mobile device developer (since the days of the Palm Pilot) and I've had a lot of experience with this kind of thing. A mobile platform is not like a PC. It is subject to constant context switches that in some cases the user has no control over, like when calls come in. You can't hit "Done" if the incoming call screen has taken over the phone's display and, by then, your notes are toast because the app didn't save them when it was shut down by the context switch. When the app gets the "I'm shutting you down" notification, it needs to save ALL state-- including the fact that you're editing the note and the unsaved changes-- because when you come back to the app (after taking the call, for example) you should come back in exactly where you were, in the note editing window, with unsaved changes, waiting for you to finish editing the note. There will be an issue here that you can't do a sync-on-open with a note in the "edited, not saved" state, but I don't think anyone would expect you to sync in that case, because you're returning to where you were before the context switch took place. Now, I know that this is a big change, with lots of code to be done to implement it-- so of course I don't expect it done next week. That is, unless you'd like to hire me onto the dev team to implement it ;-) This message was edited Dec 09, 2009.

Author

Message

Posted Dec 09, 2009 in: iPhone app Todo note edits lost switching applications

Score: 0

Scott Johnson
Posted: Dec 09, 2009
Score: 0

This isn't related to syncing-- it's related to not saving the complete state of the app when a context switch comes in.

I'm a mobile device developer (since the days of the Palm Pilot) and I've had a *lot* of experience with this kind of thing. A mobile platform is not like a PC. It is subject to constant context switches that in some cases the user has no control over, like when calls come in. You can't hit "Done" if the incoming call screen has taken over the phone's display and, by then, your notes are toast because the app didn't save them when it was shut down by the context switch.

When the app gets the "I'm shutting you down" notification, it needs to save ALL state-- including the fact that you're editing the note and the unsaved changes-- because when you come back to the app (after taking the call, for example) you should come back in exactly where you were, in the note editing window, with unsaved changes, waiting for you to finish editing the note.

There will be an issue here that you can't do a sync-on-open with a note in the "edited, not saved" state, but I don't think anyone would *expect* you to sync in that case, because you're returning to where you were before the context switch took place.

Now, I know that this is a big change, with lots of code to be done to implement it-- so of course I don't expect it done next week.

That is, unless you'd like to hire me onto the dev team to implement it ;-)

This message was edited Dec 09, 2009.