Live data from Hacker News

Why LinkedIn dumped HTML5 and went native for its mobile apps

venturebeat.com

11–20 of 105 posts

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#11
"There are a few things that are critically missing. One is tooling support — having a debugger that actually works, performance tools that tell you where the memory is running out."

"The second big chunk we are struggling with is operability, runtime diagnostics information. ...there aren’t as many great tools to support that, as well."

Could be me but looks like there is an oppertunity for professional HTML5 performance and bug-tracking tools.

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#12
post #10

Are HTML5 web apps still viewed as wise first move into mobile app development? We're seeing companies consistently move from web to native... but generally only after hitting some performance barrier. Switching to native then seems to be like any other optimisation. So even if the web performance barely improves, does developing for web first still make sense (platform independence, rapid iterations etc) or should w…

if one builds an "app" , since it uses a "webview" inside a native application , it is always "native" ( except for firefox and likes os where the browser is the "os" ). Phonegap and likes use native code so one can bundle html+js into a native app.

I tell my clients , instead of using a wrapper , to build a webapp directly. most of the LOB-apps require an internet connection anyway , and things like camera can be accessed from the browser now , on most mobile os. And it is easy to explain clients how to bookmark a webapp to the home screen.

packaged webapps are overrated imho , in most cases a webapp makes more sense.

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#14
post #9

> We always have to support HTML5 because so much of our traffic comes from email Because LinkedIn are spamming scum.

that's quite an accusation. I assume you mean they're emailing you things, and you have an account there.

They seem to continuously invent new things to mail you about, as often as possible, which you then continuously have to uncheck on the site.

We can argue about definitions but in my mind LinkedIn are definitely spammers, that are now only tolerated because the site is too popular for jobs (especially if you're a contractor).

They didn't use to be like this, but they now have the questionable distinction of being the nr.1. deliverer of junk in my mailbox.

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#15

Was anyone else heavily on the HTML5 crew only to be rudely awakened to all these inconveniences? It seems like there's a constant, persistent migration away from HTML5 for mobile style devices...and while every dev group says something like "performance, debug tools, etc." However, I'd say that the ultimate reason to do so is because of user behavior - opening up safari mobile or chrome is not a "pleasant" experienc…

it depends. personnaly , i prefer the mobile websites when available.

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#16

> We always have to support HTML5 because so much of our traffic comes from email Because LinkedIn are spamming scum.

I'm rabidly anti-spam, to the extent of hosting and running my own mail server just so I have more control over my MX, and even I don't think that!

Re: Why LinkedIn dumped HTML5 and went native for its mobile apps

#18

> We always have to support HTML5 because so much of our traffic comes from email Because LinkedIn are spamming scum.

Their marketing is quite aggressive (I have been receiving "Last month to get Linkedin Premium for free" weekly for about an year!) but I wouldn't call them spammers.
Post reply on HN