It’s not performance issues, like speed or rendering, but it’s still a big problem. The primary reason for that is, we’re seeing that more and more people are spending more time in the app, and the app is running out of memory. Prasad: We have definitely shifted from HTML5 to native.

Did you just say these apps are native? Isn’t that the exact opposite of where you guys were philosophically the last time we talked about mobile? VentureBeat: Wait, let’s go back a second. Here’s the bulk of our chat with Prasad on engineering topics around the new apps: What he did say shows that HTML5 for the mobile web still has a bright future - but only if developers are willing to build the tools to support it. Prasad said performance issues weren’t causing crashes or making the app run slowly. In a revealing chat with Kiran Prasad (pictured), LinkedIn’s senior director for mobile engineering, we learned exactly why - and it’s not what you think. Now, all that’s gone, as is some of the optimism about the current capabilities of the mobile web. Less than a year ago, the company was touting its iPad app as fully mobile-web based, with just one screen, the homescreen, running natively.

Linkedin mobile site