Some users find your app on the App Store (or Google Play Store), and some find about it on the web. No matter how many visitors you manage to bring to your app website or landing page, if they don’t end up downloading your app then it’s useless. You can have an awesome app, the most compelling copywriting, the best design and screenshots…It’s not worth much if visitors don’t know (i.e. if you don’t tell them) how to download it.
Table of Content
- A prominent call-to-action
- cheap android installs
- buy ios app downlaods
- buy android review
There are several key elements you need to have on your app website: your app name and icon, a video, screenshots, showing the device, etc. They’re all important, but most of them lose a lot of that important if there is no clear call-to-action that invites visitors to actually download the app.
It really seems like common sense, but it’s not that rare to see an app landing page where the download button is hard to find.
What you need to do is to make that button the first thing people see when they get to your page. If they see it first, they know where to click when they actually decide to download your app. They can then take a look at the rest of your website and get convinced by all the great stuff you put on it.
If your app is not available yet, give users a way to enter their email address to get notified when the app launches (using MailChimp for example). If it’s already live, take a look at the following options to get your download call-to-action right.
THE MOBILE APP DOWNLOAD BUTTONS FOR THE APP STORES
This is the way most app developers do it, and what users have been pretty used to seeing. Both Apple and Google provide developers with badges. These badges have changed quite a lot since the beginning, and they are now pretty explicit and make good call to actions.
Apple recently added the more inviting “Download on the App Store” for online usage to the previous “Available on the App Store” official badge (now for offline usage), most likely to prevent developers from creating their own customized buttons (which you’re not supposed to do if you follow the quite strict marketing guidelines).
In the same way, Google went from the “Available in Android Market” badge to the actual “Get it on Google Play”. Here’s where you can get the most up-to-date Google Play download button.
These badges are pretty important for both companies, since getting them right can increase conversion and their bottom lines. And it’s the exact same thing for you.
The other aspect of it is branding: because these buttons were initially not clear call-to-actions and people were not all the time aware it was actually buttons they could click to download the app, several app developers/designers decided to create their own “download” or “get the app” buttons.
You can still do it, but it’s become less necessary.
If you go with using only the official badges make sure you always use the latest versions of the app download buttons.
MOBILE APP DISTRIBUTION VIA SMS
A “trend” that has been appearing lately on several website is a call-to-action where visitors enter their phone number and click on a “Text me”, “Get link” or “Get the app” button. They then receive a text message on their phone with a direct link to download the app.
Why Does it Make Sense?
There are a couple reasons why this approach makes sense.
- The most obvious one is that it can increase conversion rates quite significantly. Users get a link to your app directly on their device, and don’t have to look for it on the App Store or Google Play. I don’t know about you but sometimes I was just unable to find an app I wanted to download by using search on the App Store.
I don’t like downloading them on my computer first, and there was times where I ended up looking for the developer’s name to finally download the app. Also, what are the chances they get distracted by a “featured app” or start looking at other apps (your competition for instance)?
- Using app distribution via SMS, you make sure that not only they get directly to your app details page and can download the app straight away but also that they will have the link in their messages if they decide to come back to it later.
- You can have a single call-to-action, no matter if the user on the other hand is using an Android or iOS device. You can then either give 2 different links in the text message or just one that will automatically detect what phone your user is on. Using bit.ly links allows you to get statistics, too.
Here you go for the advantages. It’s not perfect though, and I see a couple ways you could lose users if you give them only this possibility:
- What about apps for devices that can’t receive SMS (iPod, iPad, tablets) ?
- What about users that are scared (or don’t want) to give their phone numbers?
Implementing Distribution Via SMS with Twilio
You might be thinking “this all sounds good, but how do I implement this?”. Well that’s where Twilio and my exceptional technical skills can help you. Ok, not really my skills: I kind of struggled understanding enough of it to explain that here, and was lucky to get some help from my friend Gwendal Mahe and also from the great team at GetMaid.
Start by signing up for free on Twilio and downloading their library here. We tried with php, but it’s really your choice. If you do use php, they are more likely to explain that stuff better than me and therefore I’d advise you to first follow their Twilio SMS PHP Quickstart.
Here is the code for the form (mobile number field and “Get link” button):
Here’s the modified sendnotifications.php file we used for testing (you’ll need to use your own Twilio AccountSid and AuthToken):
We haven’t really been further (yet), and if you need to check the status of your SMS (to display a confirmation/error) Twilio also allows you to get a callback.
How much is it going to cost you? It seems that Twilio can be used to send texts to users in most places of the world, and pricing differs from country to country. It’s 1cent to users in the US and Canada, and 7cents to users in France for example. You can check out their prices here. If your users generate revenues (paid app, in-app purchases, etc.), it can definitely be interesting and is worth a try.
What exactly should you send to your future users? Like I said above, either one link per store (App Store, Google Play) or a single link where the device used will be detected and the user automatically directed to the right store. For that last option, you can use the Mobile Detect php class (really easy to implement).
A Couple of Examples
What I really like on the Path website (besides the fact that they integrated an actual video of the app being used and their website is responsive) is that they give some instructions: users can either download the app through their browser, or receive the text message with the link. They also included both the App Store and Google Play badges, just in case.