For HTML5-standalone 'newcomers'.
Possible reasons for a 'not-working-as-expected' withdownload or performance of HTML5 standalones
= at the example of my 'demos'
= at the current 'experimental' state of LiveCode.(1) You should use a desktop computer.
Mobiles usually are not fast enough at this experimental LC phase. Even if the download works fast, then the running the engine is usually too slow (if it is running at all).(2) The LC version.
This is author's thing. Engine loading only once is true if the author uses for different standalone _exactly the same LC version_ and prepares the server for that.
I did it and you may watch the caching of your browser with _all_ 53 links for 8.0.2, one after the other, or the _one_ link for 9.0.0dp2 from the index pages (US: hh.on-rev.com/html5/ or EU:hyperhh.org/html5/). May be one of these is faster for you, also depending on the hour of usage. I have not the time to recompile all 53 other versions with each new developer preview (this is not fully scriptable, because 'side-conditions' change with each new version of the HTML5 standalone builder).(3) The download speed: Client part.
This is a combination of provider and browser used. Currently the caching is best with Safari, then Firefox and Chrome/Opera. (4) The download speed: Server part.
At the index (or index-large) there is the possibility to switch the server. The LC-server located in the USA (hh.on-rev.com) is on days that offer new links, incl. new LC versions, to the community certainly a bit slower than the EU-server (hyperhh.org). Some providers do also a better caching than others.
The download size is at about 27 MByte for the engine (8 MByte if the server supports compressing) + stack resources. Of course, for compressed files the browser needs more time before starting up the standalone.(5) The performance: Browser part
, using latest versions.
HTML5 standalones doing animations have, compared from a local server to the IDE on the same machine currently the following 'slow-down' factors:
Safari 2-3, Firefox 4-5, Chrome and Opera 8-9.
Good for comparing/testing (visually) download and performance is the standalone "TerminalZero"
. It is small and provides the full 8.0.2-HTML5 engine. You can 'test' for availability of commands etc. in the standalone, just like from a primitive message box.
Details for preparing the webserver
(this is also true for local webservers) were part of my Edinburgh'16 speech, the link to the pdf is here: viewtopic.php?p=145519#p145519
Plagiarism is basic to all culture.
(Pete Seeger in a concert, he didn't name an author ...)