[deleted]
A touch of hyperbole perhaps? Losing control of your online identity is bad, but it's not HIV bad.
It depends. Look at DongleGate...
Why LinkedIn dumped HTML5 and went native for its mobile apps
21–30 of 105 posts
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#22HTML5 stinks on Android (due to bugs and fragmentation) and HTML5 stinks on Win8 tablets (due to IE10 bugs, implementation differences, also supporting mouse and touch together is hard to get right due to event models). So it regularly doesn't make any sense to try and build a cross platform HTML5 solution.
If you are producing a content app or business app, you might get away with it... Or if the app only needs a simple HTML UI that is OK.
The main problems I have encountered are: - good performance is very hard to achieve - making it reliable is difficult - HTML5 data input is hard if you want to do anything more than the standard controls (e.g. a searchable combo like searching for a contact, e.g. a typable time entry field that defaults to a numeric keyboard that you can also type a colon into). - pinch-zoom should be disabled (many many nasty bugs in iOS, Android, and IE10. Especially if also trying to use fixed position). - position:fixed is broken (e.g. on iOS, when an input gets focus and the input is scrolled to screen centre the fixed div is not placed properly. Android and IE10 have other problems). - all scrolling solutions have downsides.
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#23Honestly, it is kind of sad, rather disastrous, that a leading site such as Linkedin is unable to stir things up a bit and come out with the exact truth. When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interes…
It is very frustrating, mobile web is being held back to allow the walled Gardens to prosper. They expect the web to die and apps to rule the world but this is a fallacy since we will loose so much freedom and info if this had to happen. Also we are seeing the bad side of apps which are "redundancy" and a lot of pointless apps that should actually just be web apps. These apps don't use any of the device capabilities. Also apps decay really quick, if you have an older device you find that you end up updating the app and it runs really bad whereas on the web you can still use a Pentium 2 and browse the web. At some point i am hoping that the market moves towards providing the browsers access to the device api's, until then we have to crank out the objective C and Java!
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#24> We always have to support HTML5 because so much of our traffic comes from email. When we were [serving] a smaller group [of users], we were hoping we could duplicate all that mobile web work to make our clients faster in terms of code deploys. This has been my experience as well. When you click on a link in an email, the LinkedIn site would take you to the login screen. This screen is so heavy that it takes an inor…
This approach is the key to get things right on mobile. Because of its roots, common web development focuses on desktop first and mobile second. This usually means that we do: `loadContent(); if mobile: loadMobileContent();`. Instead we should build for mobile first and load desktop content when we encounter one: `loadContent(); if desktop: loadDesktopContent();`
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#25Honestly, it is kind of sad, rather disastrous, that a leading site such as Linkedin is unable to stir things up a bit and come out with the exact truth. When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interes…
It is very frustrating, mobile web is being held back to allow the walled Gardens to prosper. They expect the web to die and apps to rule the world but this is a fallacy since we will loose so much freedom and info if this had to happen. Also we are seeing the bad side of apps which are "redundancy" and a lot of pointless apps that should actually just be web apps. These apps don't use any of the device capabilities.…
With Firefox and Tizen OS the dream of web first should move closer to reality. Count on Mozilla to move the web forward!
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#26Honestly, it is kind of sad, rather disastrous, that a leading site such as Linkedin is unable to stir things up a bit and come out with the exact truth. When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interes…
Really Apple hasn't given enough support for web standards ?
Because I wonder where the world would be today without WebKit.
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#27Are 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 ac…
No need for the patronising scare quotes.
I'm talking about whether to base your app on web technologies like HTML5 and js (regardless of delivery method - web/native webview wrapper), or to use native UI elements/memory management etc of the OS.
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#28Honestly, it is kind of sad, rather disastrous, that a leading site such as Linkedin is unable to stir things up a bit and come out with the exact truth. When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interes…
Really Apple hasn't given enough support for web standards ? Because I wonder where the world would be today without WebKit.
In the same place ... the webkit revolution started with V8 when we saw how fast web stuff and javascript can be. As long as there was any kind of layout engine for google to stitch their VM to the revolution would have happened.
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#29Honestly, it is kind of sad, rather disastrous, that a leading site such as Linkedin is unable to stir things up a bit and come out with the exact truth. When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interes…
> When he says "... we’re seeing that more and more people are spending more time in the app, and the app is running out of memory ..." what he means here is that memory allocation to the browser on iPad (for example) is too little to handle the volume of user interest.
He's probably saying that the entire app is a single html page, and all the content is loaded using ajax and created programatically. This process naturally leaks memory unless you're very, very careful. Many ordinary websites have problems with leaks, but nobody notices until you're on a phone with limited RAM. Basically, this is the wrong way to write a mobile app or mobile website (or any website).
> This is certainly not the fault of HTML5/web developers, or lovers of open web, but only of the vendors who have not provided sufficient resources
I don't think theres any walled-garden conspiracy going on here - I honestly think this is the fault of the linkedin devs (or more likely project managers). What does a linkedin app need to do? Mostly they just need to do is display profile text and a few images inline. A mobile browser can display text and images perfectly fine - thats its bread and butter functionality. If you're having problems there, you done fucked up.
I bet the app had a bunch of unnecessary css animations, js widgets replacing html components, custom layouts done in javascript, etc. Was the old app ever released? Did anyone have a chance to use it?
Re: Why LinkedIn dumped HTML5 and went native for its mobile apps
#30> We always have to support HTML5 because so much of our traffic comes from email Because LinkedIn are spamming scum.
Settings > Email Preferences > 1) Select the types of messages you're willing to receive 2) Set the frequency of emails