5 ms·

They take offense to Zuckerburg's "HTML5 isn't quite there yet" comment but in order to keep their implementation quick they had to build a custom iframe framew

They take offense to Zuckerburg's "HTML5 isn't quite there yet" comment but in order to keep their implementation quick they had to build a custom iframe framework in addition to their TaskQueue and AnimationQueue implementations to replicate the fb timeline. It seems like that was part of Zuck's point - why would a company with a deadline take on all that technical debt to replicate things that you essentially get for free on a native platform?

marknutter 14y ago
You're forgetting one small point: you have to write two (or more) native apps once you go that route. Hence the reason Facebook's Android native app came out roughly 6 months after their iOS native app did.
- tterrace 14y ago
  That's true but wouldn't you (as of today) still be much more comfortable going that route with a non-trivial project? Less time spent on the cutting edge battling the idiosyncrasies of the platform and more time building your app.
  - marknutter 14y ago
    It depends on the resources available. If I were a CEO and the company was flush with cash, I'd just brute force it by hiring native developers across all platforms or farm it out to specialized native dev shops. If was a CEO of a smaller company tight on cash with a bunch of web developers, however, I'd go the HTML5 or hybrid route because it'd be the best utilization of my company's time and resources. This isn't a black and white issue.
    - suprfresh 14y ago
      Definitely agree. I'm not sure why many people think its just so cut and dry. The tradeoffs between html5 vs native are pretty much known at this point. Take those and rationalize along with the resources you have available, the cost, and time you can afford. Just ship something.
- RandallBrown 14y ago
  you also need to write two (or more) web apps too. Each OS has dramatically different user interface paradigms. Sure, you can run an iOS looking app on Android or Windows Phone, but it's going to be awkward and out of place.
  - marknutter 14y ago
    Having a second stylesheet is not the same as re-writing the entire app from scratch.
hnmullany 14y ago
Actually, you don't get those things for free on a native platform either. What we did in Fastbook has a lot of similarities to what the Facebook team had to build for themselves on top of Android: https://www.facebook.com/notes/facebook-engineering/under-the-hood-rebuilding-facebook-for-android/10151189598933920 https://www.facebook.com/notes/facebook-engineering/under-th...

marknutter 14y ago

You're forgetting one small point: you have to write two (or more) native apps once you go that route. Hence the reason Facebook's Android native app came out roughly 6 months after their iOS native app did.

tterrace 14y ago
That's true but wouldn't you (as of today) still be much more comfortable going that route with a non-trivial project? Less time spent on the cutting edge battling the idiosyncrasies of the platform and more time building your app.
- marknutter 14y ago
  It depends on the resources available. If I were a CEO and the company was flush with cash, I'd just brute force it by hiring native developers across all platforms or farm it out to specialized native dev shops. If was a CEO of a smaller company tight on cash with a bunch of web developers, however, I'd go the HTML5 or hybrid route because it'd be the best utilization of my company's time and resources. This isn't a black and white issue.
  - suprfresh 14y ago
    Definitely agree. I'm not sure why many people think its just so cut and dry. The tradeoffs between html5 vs native are pretty much known at this point. Take those and rationalize along with the resources you have available, the cost, and time you can afford. Just ship something.
RandallBrown 14y ago
you also need to write two (or more) web apps too. Each OS has dramatically different user interface paradigms. Sure, you can run an iOS looking app on Android or Windows Phone, but it's going to be awkward and out of place.
- marknutter 14y ago
  Having a second stylesheet is not the same as re-writing the entire app from scratch.

hnmullany 14y ago

Actually, you don't get those things for free on a native platform either. What we did in Fastbook has a lot of similarities to what the Facebook team had to build for themselves on top of Android: https://www.facebook.com/notes/facebook-engineering/under-the-hood-rebuilding-facebook-for-android/10151189598933920 https://www.facebook.com/notes/facebook-engineering/under-th...