I’ve written before that successful social networks are geared towards encouraging sharing. In its desktop mode, Facebook achieved this by virtue of simplicity and a default group of circles. But in the mobile space it is struggling and I think I know the reason why. There are two broad activities that make a social network: sharing and reading.

Now Facebook actually have mastered the second on mobile apps. I realised this as I downloaded Google’s new Google+ app for the iPhone (interestingly available there but not yet available on Android). It is really slick and at the same time it is really horrible for reading lots of posts. Basically, it fits a summary of one and a half per screen. Fortunately there aren’t lots of posts so this shouldn’t prove a constraint but given their aspirations, this is an issue. The best reading apps are the Twitter ones but Twitter has the advantage of the 140 character limit. Facebook has some limits too and so can fit in more but what it does that Google doesn’t is not waste space. Nonetheless, on the mobile device, the Facebook app works out just fine for reading.

It is when it comes to sharing that things get harder. The main issue is that you need to share from the app. This is fine if you want to share a quick update or perhaps a check-in but it is harder for photos and prohibitive for links. Now if you are reading a story in an app with Facebook integration, you can probably share easily but each one of these requires verification. It is far from seamless.

Compare this with Twitter in its ‘baked into iOS’ form. I can tweet from anywhere on the phone and I don’t have to login again. I can take a picture and share it instantly. If I am reading a webpage, it can be tweeted in nanoseconds. In comparison, Facebook is positively clunky. (I’m operating under an assumption that Google+ will eventually be baked into Android although given its many variants, it is hard to know).

The notion that Facebook has failed to capture mobile sharing is clearly what is behind the Instagram purchase. That is an app which succeeded where Facebook failed. It demonstrates that a click or two can make all the difference. But herein lies the problem for Facebook. To really capitalise on sharing, it needs to be backed into a mobile OS. One option is to go the Twitter route. There were rumours of this with the iPhone but it didn’t happen. Another would be to build is own mobile OS, modify an Android one or perhaps move forward with Microsoft but all those would have far less in market share than Facebook’s aspirational 100%. Finally, it could bake itself in app by app like it has now with photos. But that seems limited compared to a deep integration with an operating system and a single verified login.

My point is that while it works out a solution to the mobile sharing problem, there is a vulnerability to Facebook. As sharing moves from desktops to mobile devices, that is where the content is coming from that will support reading and it is reading where the ads will surely be.

5 Responses to Why Facebook needs to be baked into mobile OS

  1. I should point out that on Android any app can register that it supports certain features, such as “sharing”. So, for example, when I am in my photo gallery and I click “Share”, it pops up a list of apps that is actually longer than my screen (well, by default, it picks 3 items, and if you click “more” you get a longer list). Facebook is in that list, along with google+, SMS, Gmail, Blogger, and various other apps that I have installed.

    Even in the Camera app, I can take a picture, then tap the thumbnail of that picture and some sharing buttons appear right there. It’s very convenient.

    This makes it easy to share stuff in your favourite apps but also it doesn’t require tying any particular app into the OS.

    I can’t say what iOS does in these situations, because I don’t have any Apple devices. But for Android, I’d say the problem is pretty much solved.

  2. Mike says:

    I assume IOS will eventually copy Android’s “intents” (at least the share intent) because the experience is awful without them.

  3. Flapple says:

    It may make technical sense to bake facebook into iOS, but I don’t know if politically it is likely, although with Steve gone maybe it will be different…

    Remember when Steve launched Ping, the social network for music and it had facebook integration? And then facebook didn’t agree to this and changed their API to lock apple out days latter? And then Ping died within days of launch?

    I think apple remembers things like that. Like when it remembered how Adobe refused to support Apple by porting Photoshop to Rhapsody and they had to change their whole OS X strategy to deal with that? I think Apple remembered that when it came time to consider Flash for iOS.

    And I think Apple will remember Ping when considering Facebook integration.

    And I think they will consider Facebook’s “plan” to take over the internet. Twitter is a much less threatening partner.

  4. @HandNF says:

    Have you used Android? Google+ integration is already there. Although the ‘intents’ system means I can share links or photos to any social network whether it be G+, Facebook, or Twitter. iOS is just behind.

  5. […] read rather than send because Twitter have, at the same time, been encouraging apps, and indeed operating systems, that allow people to tweet. So Twitter acquired Tweetie and TweetDeck and made them their own. At […]

Leave a Reply

%d bloggers like this: