> single package file containing everything that can be distributed for an HTML5 game. Like an SWF.
That's not necessarily an unqualified advantage. I'll say this for HTML5 and having multiple files: you can easily choose what to load and when, which means if you're smart you can load your game very quickly by prioritising only the most essential assets and degrading gracefully until the rest of loaded in the background. This means that people don't have to wait to start playing.
It is more work to do this, although not as much as you might imagine (particularly for sounds and music), but I'd say worth it.
I don't really know Flash - had very limited exposure to it about 17 or 18 years ago - so it's entirely possible similar mechanisms might have existed that I just don't know about.
You can also easily package up your game into a single file for deployment on mobile devices using something like Cordova, which basically just zips everything up.
That's not necessarily an unqualified advantage. I'll say this for HTML5 and having multiple files: you can easily choose what to load and when, which means if you're smart you can load your game very quickly by prioritising only the most essential assets and degrading gracefully until the rest of loaded in the background. This means that people don't have to wait to start playing.
It is more work to do this, although not as much as you might imagine (particularly for sounds and music), but I'd say worth it.
I don't really know Flash - had very limited exposure to it about 17 or 18 years ago - so it's entirely possible similar mechanisms might have existed that I just don't know about.
You can also easily package up your game into a single file for deployment on mobile devices using something like Cordova, which basically just zips everything up.