I believe we should split the main interactive app from a passive screen saver. We may even make the default screen saver part of the native app rather than the downloaded web app.
The screen saver should be extremely simple, and run at all times uses cached URLs even if the app is otherwise broken or unavailable.
When a user taps anywhere on the screen saver, it should attempt to launch the app. If it fails it should:
display a friendly error message
notify the server
The screen saver should also kick in automatically if the user has been passive for the timeout period (5 minutes?).
The screen saver could also be responsible for downloading and validating new versions of the app.
I believe we should split the main interactive app from a passive screen saver. We may even make the default screen saver part of the native app rather than the downloaded web app.
The screen saver should be extremely simple, and run at all times uses cached URLs even if the app is otherwise broken or unavailable.
When a user taps anywhere on the screen saver, it should attempt to launch the app. If it fails it should:
The screen saver should also kick in automatically if the user has been passive for the timeout period (5 minutes?).
The screen saver could also be responsible for downloading and validating new versions of the app.