I recently released RubyApp, a deep linked Facebook App.
RubyApp allows users to send a bouquet of pictures, and a short love message. You can tag the recipient of your message (which prompts the recipient that they have been tagged), make the message public, or both.
Facebook Deep Linking is a feature provided by Facebook to make your mobile app an extension of the Facebook experience. When a user clicks a Facebook news feed message associated with the deep linked app, instead of opening a website, Facebook opens the mobile app, and passes information about the clicked message to the mobile app, so the mobile app can immediately present the media associated with the message.
If the deep linked mobile app is not yet installed, Facebook prompts the user to install the app.
As you can imagine, this is a terrific way of driving viral mobile app installation – people see a Facebook post which interests them, click the post, and painlessly download and install yet another copy of your app. They then use the app to post their own media, which all their friends can see – and so on.
And this is exactly what is happening with RubyApp. A few people tried the app, loved it, and it is now spreading throughout the Facebook community – with no publicity effort from me whatsoever.
What happens if a user is not using an iOS device? For them, there is the RubyApp website – https://apps.facebook.com/ruby__app/.
Why build a deep linked Facebook mobile app, if you already have a Facebook website? The rationale for building a deep linked Facebook mobile app was that I wanted to include a soundtrack with the bouquet of pictures. iPhones do not automatically play sounds presented by websites – so the solution to creating a high quality user experience for iPhone and iPad users was to bypass this limitation, by creating RubyApp.
If you would like to know more about how Facebook deep linking can drive downloads of your app, and what opportunities Facebook deep linking presents to content providers, please contact me at firstname.lastname@example.org.