Internal reports of the iOS version losing state and thus reseting the game, this appear to happen when the app is back-grounded and then brought back again.
Feedback was that iOS needs to support the page-lifecycle API, and that this will be hard because session storage is needed - possibly because of multiple tabs being open.
PK Note: for an added to home-screen experience there can only be one open instance of the app, and I thought that it didn't share state with the browser, therefore local persistence might be OK.
Internal reports of the iOS version losing state and thus reseting the game, this appear to happen when the app is back-grounded and then brought back again.
Feedback was that iOS needs to support the page-lifecycle API, and that this will be hard because session storage is needed - possibly because of multiple tabs being open.
PK Note: for an added to home-screen experience there can only be one open instance of the app, and I thought that it didn't share state with the browser, therefore local persistence might be OK.