Published: Jun 28 2012 / 09:06
FB doesn't agree and is in fact reversing this with a native IOS app. Seriously, Gillmour gang have been talking about this for awhile now and discussing with FB mobile dev team...
But here's another recent
I actually acknowledged this overall in the article. Given how horrible their android app is, it may even be the right decision. However, it is a pretty temporary thing. Do you REALLY see coding in native compiled Objective-C just for one mobile device in the face of an acceptable alternative?
Sorry for the late reply: 1. You use the word "acceptable alternative" too loosely. The fact of the matter is that FB mobile dev team attempted the "accepted alternative" first and it failed. "Acceptable alternative" it cannot be acknowledged by the fact they are rewriting their mobile apps to use the native sdks. 2. You are wrong about "one mobile device". FB mobile dev team is not coding in native Obj C for one mobile device, they are coding in native Obj C etc. for an entire mobile platform / ecosystem which has a significant % of the entire marketshare of mobile if we are talking about IOS. Additionally, I think they are doing the right thing from a business / end user perspective -- Gillmour gang repeated a stat that said 80% of N America FB user's with an iPhone heavily interact with the iphone app; I don't know the revenue numbers from these users but with that much user share on the IOS app, it could certainly make sense from a business perspective to provide the best experience possible to their "customers". 3. If it's truly an accepted alternative, I'd like to see concrete examples of SDK maker's eating their own dog food. Can you highlight any awesome / killer HTML5 apps that either Apple or Google publish? I can reel off a number of google FOSS android apps that are done natively, and Google of all companies should be able to produce such w3 killer apps. And the new Android Chrome is still not accessible for being the basis of HTML5 apps in Android. https://developers.google.com/chrome/mobile/docs/faq Does Chrome for Android now support the embedded WebView for a hybrid native/web app? We are evaluating ways we can support WebView with Chrome but do not have any plans to announce at this time. It's quite clear that both Google and IOS (and RIM and MSFT) continue to "move the needle" using the native SDK's. Until the creators start moving the needle using w3 on mobile, the long death of fat clients is premature I think... PS. I personally like w3 and I hate learning another proprietary form of UI layout as all these platforms require for native. However unless I'm writing "just another media / content / feed / rss viewer" like the FT, the benefits do not outweight the costs for my business. I acknowledge businesses vary.
The Zuck spoke...if you have the resources and having a great user experience is integral to you and most especially your business, then don't go HTML5 on mobile apps (please note that I did not say mobile websites) http://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest-mistake-with-mobile-was-betting-too-much-on-html5/
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.