3 ms·
If facebook's HTML5 fiasco is any lesson, I would rather go with Native.
by sidcool 13y ago
If facebook's HTML5 fiasco is any lesson, I would rather go with Native.
- Antwan 13y agofb.html5isready.com
- kayoone 13y agoWhile thats pretty nice, it still proves that HTML5 is indeed not ready
- dpedu 13y agoReally? On my Nexus 7 this runs much smoother than the official Facebook app - ignoring missing features of course.
- tim333 13y agoJust tried that on ios7 and it crashes every 20s or so. Not that that really proves anything
- easy_rider 13y agofastbkapp will receive the following info: your public profile, friend list, email address, custom friends lists, messages, friend requests, News Feed, relationships, relationship interests, birthday, chat status, notes, work history, status updates, education history, events, groups, hometown, interests, current city, Photos, religious and political views, videos, website, personal description and likes and your friends' relationships, relationship interests, birthdays, chat statuses, notes, work histories, status updates, education histories, events, groups, hometowns, interests, current cities, photos, religious and political views, videos, websites, personal description and likes. hmm, nah.
- nobleach 13y agoSo will the native facebook app. Of COURSE the fastbkapp will receive that info.
- easy_rider 13y agoOF COURSE. That does not mean I want to give ALL that to ANOTHER third party.
- nobleach 13y agoThe native app didn't help much. The biggest deal with the HTML5 app was adding DOM content as the user scrolled. They were experiencing memory leaks. The native app may have fixed that part, but their backend API service was still sucking pretty badly for months after that. Even now, on an iPhone4, the performance of the native app kinda sucks. It's better on a 5 or 5s, but still fairly slow to get a JSON stream, parse it and build dynamic views.