Making Facebook's native mobile app faster using HTML5

Post by macspoofing » Mon, Dec 17, 2012, 5:22 PM UTC

rimantas wrote: post #46

brianchu wrote: post #11

I ran the HTML5 app on my iTouch 4G running iOS 6 (roughly equivalent to iPhone 3GS) and compared it to the native FB app. The HTML5 app had noticeable lag in the swipe transitions. It also crashed once when loading a photo (only once though). Not to mention that they implement almost everything differently and leave out 90% of FB's features. That being said, it was really smooth on my iTouch 5G. The demo HTML5 app a…

Even when browsers are powerfull enough the mess what is trying to shoehorn technologies created for hyperlinked text into apps development will still be a mess. It may appeal for those who know only the said technologies, but frankly, they would be better of by just learning the native instead of spending time traying to fight quirks. As for the appeal "run everythere"—that's just some more quirks. Good luck with th…

Post by marknutter » Mon, Dec 17, 2012, 5:23 PM UTC

tehwebguy wrote: post #43

marknutter wrote: post #38

Earlier quoted context omitted.

But this argument makes no sense. When you go native, you have to write N number of apps for N number of platforms you want to support. The point is that making a great mobile app is hard no matter what stack you choose to use. It's also a bit disingenuous to say you are forced to optimize every HTML5 app. The whole point of Sencha's blog post is to advertise the fact that they've abstracted away all those optimizati…

Maybe people that make this argument only care about supporting one (or two) platforms.

Post by micampe » Mon, Dec 17, 2012, 5:30 PM UTC

drivebyacct2 wrote: post #55

micampe wrote: post #10

Why do we see plenty of articles saying that HTML5 can be as good or better than native code and no actual applications doing it? Facebook and Google tried and miserably failed, LinkedIn and Twitter are probably the ones closest to actually doing it, but users still prefer the native version, why? One I think is a big reason is clearly visible in the video: scrolling physics are different. It's annoying and feels wro…

Google has failed miserably? You might want to tell them that. I'm pretty sure their iOS dept will be shocked to hear that. The scrolling physics are wrong because they made the horrid decision to emulate that stupid bouncy scrolling. The damn stuff makes my head hurt compared to the subtle, glow effect rather than shit bouncing around my screen. If they would let Chrome for Android handle the scrolling natively, I'm…

Post by spiantino » Mon, Dec 17, 2012, 5:39 PM UTC

brianchu wrote: post #11

I ran the HTML5 app on my iTouch 4G running iOS 6 (roughly equivalent to iPhone 3GS) and compared it to the native FB app. The HTML5 app had noticeable lag in the swipe transitions. It also crashed once when loading a photo (only once though). Not to mention that they implement almost everything differently and leave out 90% of FB's features. That being said, it was really smooth on my iTouch 5G. The demo HTML5 app a…

Post by dmackerman » Mon, Dec 17, 2012, 5:43 PM UTC

mtrimpe wrote: post #60

rimantas wrote: post #46

Earlier quoted context omitted.

Even when browsers are powerfull enough the mess what is trying to shoehorn technologies created for hyperlinked text into apps development will still be a mess. It may appeal for those who know only the said technologies, but frankly, they would be better of by just learning the native instead of spending time traying to fight quirks. As for the appeal "run everythere"—that's just some more quirks. Good luck with th…

It's all about who is able to get their VM in the most places; Java already lost that battle and Flash is on the way out. It seems like JavaScript is the new ActionScript.