Blog

MWC 2012 – Day Two, Focus On Monetization

On the second day at MWC I had a little more time to converse with some exhibitors. It’s not possible to meet them all, or to describe them all (the exhibition catalog is 300 pages long!), so my visits were focused on application monetization services. I briefly describe three of the most interesting below.

  Updated   2 min read

The MWC this morning
The MWC this morning

Smaato

The Smaato booth, Hall 7 (AppPlanet)
The Smaato booth, Hall 7 (AppPlanet)
Smaato is a service that helps optimize advertising revenue generated by a mobile application. Their approach is interesting: their technology is compatible with more than 80 monetization services (including adMob and MobPartner, both of which you already know). For every advertising call, their technology is responsible for showing the most relevant ad among the available offers. The concept is simple and logical.

AirPush

The AirPush booth, Hall 7 (AppPlanet)
The AirPush booth, Hall 7 (AppPlanet)
AirPush is a monetization solution that focuses 100% on Android. Through use of notification sending systems, they promise to monetize even inactive users – now that’s rare enough to be noted! The overall approach seems quite interesting and innovative and so does the promised performance.

MoPub

MoPub booklet
MoPub booklet
MoPub is a service similar to Smaato, but its focus is more on the American market. Technically, MoPub offers a marketplace where you can buy and sell advertising inventory: this solution should significantly increase the revenue generated by the application.

General Atmosphere

The Google Android booth, Hall 8
The Google Android booth, Hall 8
I also used the day to explore the new Android and Windows Phone devices. Tomorrow morning I’ll take some pictures of those devices, as well as the manufacturers’ booths that are competing to attract a crowd.

Keep reading

  6 min read

AI Extension Builder: the agent tests your sections and can create your app's database

Take a sports club that wants its members to choose the date of its tournament. In its Create with AI section, it writes: “Add a poll to choose the tournament date, with the results.”The agent first reads the app's context: its palette, its fonts, its logo, the files already added. It looks up GoodBarber's design system, written by our designers. Then it writes the section's files.The votes have to be shared between all the members. The agent spots this and asks the question, with three answers:Create the app's database: one database, run by GoodBarber. Its tables start empty.Connect my Supabase: the data goes to the club's Supabase project.Cancel: the agent builds the section without a database, and each phone sees only its own votes.The club picks the GoodBarber database. The agent then opens the section in a browser, at the width of a phone, and tries its buttons. It looks for errors: a script that crashes, a broken image, text that runs off the screen. It fixes what it finds, then saves the section.The members vote, and everyone sees the results. Each member can change only their own vote.