What You Can Learn From Facebook's Approach And Mistakes In Building Mobile Services

I listened to the Mark Zuckerberg interview from the  TechCrunch Disrupt event in San Francisco this week. 

There were a few choice quotes (I'll paraphrase them here - these are not literally a transcription. You can find the video/audio on the TechCrunch site):

"The biggest mistake we made (with our mobile services) was relying too much on HTML5 and for too long." 

"We finally realized that a good enough mobile experience would fall short. We needed a great mobile experience. The only path to great is native on iOS and Android." 

"Our mobile users are more engaged and use our services more frequently." 

"All of our code is for mobile."

"We'll build native code for iOS and Android." (And it is building for iOS first)

"Ads can't be standalone on a sidebar in mobile. They need to be integrated into our product." 

"We reorganized. A year ago, 90% of the code check-ins were from the core mobile team. Now 90% comes from other parts of the organization." 

"We reorganized. We were in functional silos. We now have product teams (responsible for delivery)." 

"A Facebook phone doesn't make any sense." 

Some context. Certainly, Facebook is unique with it being a media-centric company and very global. It does need mobile Web to reach much of its audience - now nearing 950M. For many companies, mobile Web will continue to be a relatively low-cost, broad-reach play to get to most of the phones. Mobile Web doesn't go away, but it is not where the differentiation will happen - at least in the near term. 

Read more