1 decade ago by Arantor
Like last time I asked about both, I don't really have a preference at this point, asking more ahead of time to judge which is the best solution for me.
For normal web based stuff, if you want to save the user's progress, you have the choice of doing something with AJAX and sending it off to a server, or there's always localStorage (any browser that has a canvas will support localStorage), which means for savegames etc, there's flexibility in how you approach it.
But when you're doing it on a native app, it's a different ballgame. So I'm wondering how you'd tackle it in either of the above environments.
Main reason I thought about it was that I'd been playing Dizzy - Prince of the Yolkfolk that was recently ported to iOS, and noticed that it had save states, since it's a bit too long to be completed in one sitting in the 'usual mobile timeframe' (it takes about half an hour or so if you know what you're doing, longer if you don't)
Sure, the game suspends normally if you head back to the home screen, but it will also retain your progress if you actually terminate it, because it's saved that progress as you go. Some of what I have in mind would benefit from doing something similar (though probably a shade less clunky than it comes across in D-PotYF) so I'm just wondering how that might be achieved.
Of course, something similar would be required in the case of high score tables or other progress-saving anyway, and I'm expressly not interested in AJAX or anything that requires internet access. I would want my players to be able to save their progress on their device without having to be connected (e.g. playing the game on the train outside network areas)
For normal web based stuff, if you want to save the user's progress, you have the choice of doing something with AJAX and sending it off to a server, or there's always localStorage (any browser that has a canvas will support localStorage), which means for savegames etc, there's flexibility in how you approach it.
But when you're doing it on a native app, it's a different ballgame. So I'm wondering how you'd tackle it in either of the above environments.
Main reason I thought about it was that I'd been playing Dizzy - Prince of the Yolkfolk that was recently ported to iOS, and noticed that it had save states, since it's a bit too long to be completed in one sitting in the 'usual mobile timeframe' (it takes about half an hour or so if you know what you're doing, longer if you don't)
Sure, the game suspends normally if you head back to the home screen, but it will also retain your progress if you actually terminate it, because it's saved that progress as you go. Some of what I have in mind would benefit from doing something similar (though probably a shade less clunky than it comes across in D-PotYF) so I'm just wondering how that might be achieved.
Of course, something similar would be required in the case of high score tables or other progress-saving anyway, and I'm expressly not interested in AJAX or anything that requires internet access. I would want my players to be able to save their progress on their device without having to be connected (e.g. playing the game on the train outside network areas)