Striking the Balance in Ad-Supported Content

There’s been lots of talk about the bright future for ad-supported, versus paid, mobile content. I’m generally pretty bullish on the idea — if it’s done correctly. A big point to consider is the balance between content and advertising, and making sure that you’re not overwhelming your customers with too many ads, outweighing the value of the content you’re giving them, or making it too difficult for users to actually get the content.

What spurred this was seeing a post over at Symbian-Guru about a software company that’s made its whole catalog “free.” To get the “free” content, users have to earn credits by viewing ads — and the ads are prompted by phone events like ending a call or getting an SMS (heh, brings to mind something like: “This hangup was brought to you by Coke! Have a Coke, a smile, and shut the hell up!”). Ricky from Symbian-Guru says he didn’t find the ads too intrusive, but personally, I feel like having common phone events generate ads would bother me.

Another example comes from US operator Cricket, which recently launched its Myperks program. Users can sign up for it and get content delivered to their idle screen, along with ads and coupons. This sort of thing’s been mulled over for a long time, and lots of people seem to feel like a phone’s idle screen is fair game for ads mixed in with some content. Again, I’m not so sure, both personally, but also because the ads don’t take any sort of context into consideration.

What do you think? How best should content providers balance this? Do these examples go too far?

—–>Follow us on Twitter too: @russellbuckley and @caaarlo

Share this post:
  • Facebook
  • Twitter
  • del.icio.us
  • StumbleUpon
  • Digg
  • LinkedIn
  • Google Bookmarks
  • Suggest to Techmeme via Twitter
  • Reddit
  • Kalador has an interesting scheme where an ad application is attached to your own app (no changes required on the developer's part) and serves ads via mobile web pages before the application starts. As a user you can choose to pay a fee and that way get rid of the ads. In both cases the developer gets revenue, provided of course the application is at all used.

    For some applications this will not work, if the burden to go through the ads outweighs the value/usefulness of the application, but for many others this might be the way to go. Frankly, people don't tend to want to pay for mobile applications.

    I'm actually trying this out right now for a bunch of my MIDlets. They have so far not made me rich and famous. Whether this will make me no more rich but infamous instead is to be investigated.

    In one specific case, EasyCall, an application that was designed to make calling and messaging extremely easy to young ones etc, this would obviously not be a suitable scheme.

    The burden/nuisance vs perceived value ratio must be considered when serving ads.

    Also, one thing never mentioned is that ads cost money for the end-user, unless on a flat-rate sub. That goes for all the AdMobs, Mobvisions etc out there as well. Especially when serving picture ads, that can easily be much larger byte-wise than the content page served. On slow networks, the experience can also be deteriorated.
  • Andy
    Anyone who's accidentally picked up a copy of American GQ instead of the UK version at the airport will quickly realise that the balance is different in different countries. There were 30, yes 30 pages of adverts in the American GQ before any editorial content was to be seen. In UK GQ it tends to be 3-5 max.

    The value of advertising to the user still needs some improvement. Moving from passive 'see the ad' to active 'interact with the ad' is critical to the mobile space. If my favorite brand gives me a game/video/competition/voucher/exclusuve/... they can use my mobile screen. If they just want to steal a part of it to show me an ad - I'm not listening (or watching!).
blog comments powered by Disqus