31–40 of 97 posts
Earlier quoted context omitted.
Did you notice the enormous performance improvement in Facebook's app when they moved away from that type of solution to a native one?
Some of that was just bad code on their part. Try and compare it to LinkedIn's app instead. As far as I know, that's HTML5.
Sadly, Apple and/or Google have the power to retard the adoption of HTML5 as long as they like. "But ender7," you say, "both Mobile Safari and Chrome have great support for HTML5." Yes, they do. Sort of. Except for the crippling bugs in many of their implementations. Some of these bugs render the APIs in question essentially useless on mobile. Or just a giant pain in the ass to work around. Or have performance issues…
Not sure about how well their mobile counter-parts actually support HTML5, but at least you have a choice for a non-system-supplied browser.
On iOS you are, as you say, SOL because Apple has literally crippled the options you have down to one: The one they supply and update, once a year.
Lets get this straight, the limitations in performance on Mobile Safari are very much deliberate limitations. Do you seriously think a company like Apple who gets a pretty large chunk of app store sales is going to let something like HTML5, CSS3 and Javascript steal it's profits away? Fat chance. Although it even rings true for desktop browsers not being able to perform as optimally in regards to some HTML5 features…
"It has a Node.JS backend and uses a web wrapper to load it in, they even wrote up a blog post about how they squeezed every ounce of performance out of the web UIView and I think it works well." Can you give a link to that blog post? I took a quick look at LinkedIn's corporate and developer blogs but couldn't come across it.
http://engineering.linkedin.com/testing/continuous-integrati...
http://engineering.linkedin.com/nodejs/blazing-fast-nodejs-1...
The first link is the one I referenced in my comment RE: Node.JS and heavy HTML5 optimisation. Other people who haven't seen them might find them interesting as well.
A smartphone today can talk to all sorts of other devices: TV remotes over WiFi, watches and headphones over Bluetooth, health-sensors and car stereos through dock connectors, and TVs over AirPlay. All this is beyond the reach of HTML apps. That's almost the entire point of PhoneGap and similar frameworks, exposing these via APIs. He's confusing using HTML/CSS/JS for UI in a "native" app with making a web app.
(I wrote the original blog post.) You're right that things like PhoneGap give access to native features. However, the Native-API-implementations in these frameworks are 1) typically significantly behind the native OS (release date) 2) tend to have less-than-feature-parity So, often you're stuck writing your own native bridge, or tweaking the portability framework's version, which is time wasted (IMO) vs writing to th…
A smartphone today can talk to all sorts of other devices: TV remotes over WiFi, watches and headphones over Bluetooth, health-sensors and car stereos through dock connectors, and TVs over AirPlay. All this is beyond the reach of HTML apps. That's almost the entire point of PhoneGap and similar frameworks, exposing these via APIs. He's confusing using HTML/CSS/JS for UI in a "native" app with making a web app.
In a sense, PhoneGap apps are actually NOT Web apps, they are native apps built using Web technologies.
If you do believe that HTML5 will eventually be production ready, even if not for another 2 years, ask yourself this: when that time comes, do you want to be the guy with 2 years experience or the guy with none? When the industry is ready, 'HTML5 developers' are going to be all anybody wants and they'll want them all right now. If you want to jump on a moving train carriage then you have to start running towards it very early...
Lets get this straight, the limitations in performance on Mobile Safari are very much deliberate limitations. Do you seriously think a company like Apple who gets a pretty large chunk of app store sales is going to let something like HTML5, CSS3 and Javascript steal it's profits away? Fat chance. Although it even rings true for desktop browsers not being able to perform as optimally in regards to some HTML5 features…
"It has a Node.JS backend and uses a web wrapper to load it in, they even wrote up a blog post about how they squeezed every ounce of performance out of the web UIView and I think it works well." Can you give a link to that blog post? I took a quick look at LinkedIn's corporate and developer blogs but couldn't come across it.
This presentation from LinkedIn's Director of Engineering is worth watching too: http://www.youtube.com/watch?v=hMd45Ij2DYQ
Also see this piece from Venturebeat: http://venturebeat.com/2011/08/16/linkedin-node/
Sadly, Apple and/or Google have the power to retard the adoption of HTML5 as long as they like. "But ender7," you say, "both Mobile Safari and Chrome have great support for HTML5." Yes, they do. Sort of. Except for the crippling bugs in many of their implementations. Some of these bugs render the APIs in question essentially useless on mobile. Or just a giant pain in the ass to work around. Or have performance issues…
Which browser is the shining beacon of light for HTML5?
I've seen a couple of posts from people comparing iPad's Safari with IE6 (although, Safari has been improving in past few releases...) so not sure which is the favorite browser for people on iPad.