If the app used touch events, it would be lightning fast. There is nothing to be slow about it, it’s dead simple website, only with poor mobile optimization.

Just to be clear what I am talking about, try this:
http://trott.github.io/LightningTouch/#/lightning-main

Anyway this is perfect example of “writing an app with two buttons”. I see the problem in trying to make web apps behave like native apps with HW optimalization. Is it really necesary to force fade-in/out effects with jQuery animate(opacity) and fancy sliding by changing absolute positioning every millisecond even if thse frames are not rendered?

All in all web is not just javascript and it is different environment for different usage. It may be slow but on the other hand it may be much better than writing all those native apps, which the user has to install and keep updated!

Slow. Because even if the maps do come u, and your CDN rocked, and you have switched into a proxy server and pre-cached static content, your user experience is glacial. Sorry. But I think usability and perception come into the conversation fairly, because they are under-represented while be where the customer’s attention is riveted while the potential slow down takes place.

Wow. A good coffee morning – create between six and six fifteen AM.

have a beauty day!

Not the sme tech, not the same goals, not the same cost, … you compare Apples & Meal. This article is more likely to show how ignorant you are about this industry more than in which cases webapps is not a good idea (those cases are real, in both ways btw)