[Interest] considerations for developing handset applications
Atlant Schmidt
aschmidt at dekaresearch.com
Wed Mar 14 15:59:09 CET 2012
Sivan:
> I'd appreciate help creating this list with as many
> items needed and different trade offs.
n. Checkpoint your critical data, settings, and state
frequently as you never know when you will be
abruptly evicted from memory.
n+1. Be able to "resume" (from the human user's point
of view) based on that checkpoint data so that the
user perceives your operation as having been
continuous, even if you were evicted from memory
while your user was "away".
o. Conform your setup data to the prevailing
"Settings" system in use on the targeted
handset(s).
p. Provide the necessary "reset" interface to allow
the user to recover your application should
something become wedged.
q. Ensure your application can be cleanly deleted
from the handset.
Atlant
This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Thank you.
Please consider the environment before printing this email.
More information about the Interest
mailing list