The main reason for developing software is, of course, earning money. 🙂 For desktop applications, the most common way of monetization is directly purchasing a license – the user pays a specific sum and gets to use the software. In the case of mobile development however, apps need to be very addictive or very useful, and overall need a lot of effort put into them to be successfully sold directly for a price. Another aspect of mobile apps is that paying for applications is usually a new (and alien) concept for many mobile users, and you can guess that they don’t like it much (I’ve seen many cases where a user gives bad ratings to a quite good game priced at a few dollars, just because it wasn’t free).

Click the image and view it in full size. You’ll see that “paid” apps require a lot of work to be successful (most of them are games, too).
This situation has resulted in alternative monetization techniques for mobile apps. One of them was adding trial versions which gave the users a taste of the app, and told them to buy it if they liked it. Another was to make the app free but to add in-app purchases such as removing limits or adding new items, characters or levels. And the final one was to put ads to gain revenue, either by making the app free and using ads as the main funding source, or making two versions of the app (a free version with (usually annoying) ads and a paid version without them).
In this article, we’ll see how we can go with using ads, and we’ll create an example Windows Store app that uses them. For this purpose, we have Microsoft Advertising SDK (for Windows Phone and Windows 8), that makes it very easy for us to include ads in our apps (with nice features such as using location to show more relevant ads). Now, I haven’t seen anyone who likes ads, but they are actually quite effective if used correctly, especially if your app has a high usage value (that is, if users would not just open your app once and don’t touch it ever again). This way, you can actually have a slow and steady income.
➤ This article has been sponsored by Nescafe and Visual Studio (no, not really)