software development iPad, web services and social integration
From the to-do list: iPad app
✔ Application launch/exit
(Completed by Denis Slabakov on September 3, 2012)
Comments
Denis Slabakov on August 31, 2012:
Sudhir,
Please define two separate launch and exit processes.
Launch (non logged user) - start from scratch, ask user name and password, as it is now.
Launch (logged user) - restore status and proceed
Exit (home button) - save all user created data and current app screen, terminate
Exit (password) - check if upload to server proceeds, warn user if upload is not done that data will be lost, give an option to wait till upload is done. Show a warrning sign if there is no upload progress, does not matter what is the reason. Clear user login, terminate
Sudhir Kelappan on September 3, 2012:
Dear Denis,
>>Launch (logged user) - restore status and proceed
>>Exit (home button) - save all user created data and current app screen, terminate
Just to confirm, the default behaviour of an iPad app is : "On Home Button press the App is sent to the background". Is this the behaviour that is expected ? Or should the App really terminate by calling exit ( );
>>Exit (password) - check if upload to server proceeds, warn user if
upload is not >>done that data will be lost, give an option to wait till
upload is done. Show a >>warrning sign if there is no upload progress,
does not matter what is the reason. >>Clear user login, terminate
Current implementation of the FIFO does not discard the uploads on App exit. It tries to restart the upload when the App is launched again. It may be good to retain this feature as it will prevent accidental loss of data due to scenarios like device / App crash.
If this functionality is required for a use case e.g. (device being moved out of the venue to a new venue) we can think of alternate ways to handle such cases.
Comments
Denis Slabakov on August 31, 2012:
Please define two separate launch and exit processes.
Launch (non logged user) - start from scratch, ask user name and password, as it is now.
Launch (logged user) - restore status and proceed
Exit (home button) - save all user created data and current app screen, terminate
Exit (password) - check if upload to server proceeds, warn user if upload is not done that data will be lost, give an option to wait till upload is done. Show a warrning sign if there is no upload progress, does not matter what is the reason. Clear user login, terminate
Sudhir Kelappan on September 3, 2012:
>>Launch (logged user) - restore status and proceed
>>Exit (home button) - save all user created data and current app screen, terminate
Just to confirm, the default behaviour of an iPad app is :
"On Home Button press the App is sent to the background".
Is this the behaviour that is expected ? Or should the App really terminate by calling exit ( );
>>Exit (password) - check if upload to server proceeds, warn user if upload is not >>done that data will be lost, give an option to wait till upload is done. Show a >>warrning sign if there is no upload progress, does not matter what is the reason. >>Clear user login, terminate
Current implementation of the FIFO does not discard the uploads on App exit. It tries to restart the upload when the App is launched again. It may be good to retain this feature as it will prevent accidental loss of data due to scenarios like device / App crash.
If this functionality is required for a use case e.g. (device being moved out of the venue to a new venue) we can think of alternate ways to handle such cases.
Pls. advise.
-Sudhir
Denis Slabakov on September 3, 2012:
ok