Re:Why LinkedIn dumped HTML5 and went native for its mobile ...
by radiusq on Thursday April 18, 2013 @10:46AM
(#5570870)
>The second reason we’ve gone native is trying to get some of the animations — the spinners and the way they work
Why in the world does an app like linkedin's need animations that are apparently too intensive for a browser? And they couldn't get a spinner to spin smoothly?
Why in the world does an app like linkedin's need animations that are apparently too intensive for a browser? And they couldn't get a spinner to spin smoothly?