Google Tasks on iOS

Hi.

I am getting very used to being able to swap between applications on my iPhone or iPad using multitasking, to do this I just need to press the physical button on the device to swap between apps- and when I return to the first app it is still "running" where I left it.

However on GeeTasks when I press that button, and return to it (by selecting the app from the screen , or from the task bar) it restarts the app, losing the changes I had been making to that field (in this case a few pages of notes in the field for a task). Ideally it should retain the edits I was in the middle of.

I am guessing you may have code which is trying to restore the app to the position it was in when it was last used (to "fake" multitasking) which is no longer needed? Whilst this was fine when pressing the button meant quitting an app, that is no longer the case with other apps.

Note that it should probably also check to see if that field has changed in Google's copy since the editing started (by comparison to the original string) and not restore the text in this case? This would avoid losing subsequent edits made online, and seems a fair tradeoff.

I know its been a while since you updated, as you were in the middle of a big piece of code, I hope that this will be resolved in the next version. I am also glad to hear the ipad update is on its way.

Cheers

Peter

I appreciate the thought behind your not adding full backgrounding just yet, but I think you're underestimating your user base when you say that most "don't know how to kill an app…" and by implication, can't learn or figure it out on their own.

Your user base is self-selecting, particularly for the paid apps, and particularly so if they bought Pro to work with Google Apps accounts. They manage both an iTunes account and a Google account (a Google Apps account if they bought Pro), and probably had to go through no small amount of shenanigans to get their Google data to work on their iPad/iPhone (again, particularly so if it's a Google Apps account..Google's own instructions for Contacts for example are just wrong).

To put it more succinctly, they probably can figure it out, and most likely have already had to.

Can backgrounding be a switch (off by default) that a user could then select if he wanted it? That might be a workable solution if unsavvy users are a real concern (and Apple guidelines allow).