<story><title>Why LinkedIn dumped HTML5 and went native for its mobile apps</title><url>http://venturebeat.com/2013/04/17/linkedin-mobile-web-breakup/#ygWxXrYeFLq8hzfF.99</url></story><parent_chain><item><author>gbog</author><text> Why on earth would you disable pinch zoom on mobile web?  It is the most useful feature,  it allows the reader to adjust the amount  and size of text  displayed. I  use it all the time and despise those web apps blocking it.&lt;p&gt;Html is elastic by nature,  and html 5 will win over native apps because it is elastic.</text></item><item><author>robocat</author><text>HTML5 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&apos;t make any sense to try and build a cross platform HTML5 solution.&lt;p&gt;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.&lt;p&gt;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.</text></item></parent_chain><comment><author>freyr</author><text>Thank you! The worst is when pinch-to-zoom is disabled on an image viewing/sharing page. I believe Twitter is guilty of this. It&apos;s idiotic.&lt;p&gt;I&apos;ve also heard many arguments that responsive design makes pinch-to-zoom unnecessary. A page should automagically adjust so that it&apos;s optimal for a 27&quot; monitor, a 2&quot; mobile display, or anything in between. It&apos;s a great idea in theory, but I&apos;ve yet to see it executed well in practice. I guess it&apos;s exceedingly difficult to design an effective UI that can automatically and seamlessly scale between a large-format screen and a small-format screen.</text></comment>
<story><title>Why LinkedIn dumped HTML5 and went native for its mobile apps</title><url>http://venturebeat.com/2013/04/17/linkedin-mobile-web-breakup/#ygWxXrYeFLq8hzfF.99</url></story><parent_chain><item><author>gbog</author><text> Why on earth would you disable pinch zoom on mobile web?  It is the most useful feature,  it allows the reader to adjust the amount  and size of text  displayed. I  use it all the time and despise those web apps blocking it.&lt;p&gt;Html is elastic by nature,  and html 5 will win over native apps because it is elastic.</text></item><item><author>robocat</author><text>HTML5 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&apos;t make any sense to try and build a cross platform HTML5 solution.&lt;p&gt;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.&lt;p&gt;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.</text></item></parent_chain><comment><author>miniatureape</author><text>In some browsers, removing the ability to zoom removes the 300ms delay that the click event has before it fires.&lt;p&gt;You can use &apos;touchend,&apos; but in certain cases this causes another set of bugs because the click event follows anyway.&lt;p&gt;To fix this in a cross-browser way, you need to write some extra logic. There are several implementations floating around of various quality.</text></comment>