Tuesday, 10 March 2009

MomoLondon: What have operators done for you lately?

Not quite as snappy and energetic as last month’s event, but still a good evening. I think tonight was missing some demos or video examples to get the crowd excited before the panel session. As it was, it took until the last few questions before we got to the nitty gritty.

O2 Litmus

James Parton, Head of O2 Litmus

James Parton gave a polished presentation about O2 Litmus with lots of pithy quotes. Some examples:

O2’s feedback from the developer community about what was wanted from an operator:

  1. get out of the way
  2. be transparent and honest
  3. show me how to make some money

“Developers can get their app in front of customers in 18 minutes, not 18 months”

“The customer API is the real value”: refine ideas with feedback from real customers

The benefits of O2 Litmus: developers have access to customers; and customers get a voice, early access and rewards.

Operators and Operands, a Love Story

Terence Eden

Terence wanted to get across the network effect — the killer app of a mobile communication device being the people with whom you communicate.

He started by scaling up from the iPhone, selling 20 million worldwide so far. Quite a few people in the audience had one, unsurprisingly. But the largest selling phone across all operators in the UK is the Nokia 6300 — basic mobile web & Java apps only, but used mainly for talking and text. Scaling up still further, the Nokia 1100 sells more than any other phone worldwide, and its greatest feature is a built-in torch!

Operators exist to generate the network effect. The network effect is the real power. What operators really want is for people to say, “I enjoy using my phone, I want to use it more.”

To a certain point, I agree with him. Until you have a certain number of devices in the market, the most important thing is getting people to use more devices. However, we’re long past that in Europe. The latest stats from the UN say that Europe has 111% penetration of mobile devices. That’s more devices than people.

Once you have a network, it’s time to think about how to leverage it more than how to grow it. Treating connectivity as a given has led to most of the exciting and new services and business models of the recent years. Google Docs, Dropbox, Twitter — they don’t exist to encourage people to use the internet; they only exist because everyone is already on the internet.

That’s an area where the iPhone has stormed ahead in mobile. It assumes you’re connected and moves beyond that. Nokia is still stuck on helping you to connect.

Panel

  • Chair: Anna Gudmundson, Ad.IQ
  • James Parton, O2 Litmus
  • Steve Wolkak, Betavine
  • Jo Rabin, dotMobi
    • investors include Google, Symbian, Microsoft, etc
  • David Wood, Symbian

How did Betavine begin?

  • Engaging those outside of your workplace (now called crowdsourcing)
  • Thinking of ways that we could encourage the developer community to move towards mobile
  • Any application uploaded to Betavine.net visible on portal in Germany, Spain, UK and South Africa

Where’s it going next?

  • Direct feedback from developer community
  • Feedback from Vodafone
  • Things that the team think are fun
    • at the moment, looking at emerging markets

What is the dotMobi business model?

  • We derive revenue from domain sales, development software and services

Which apps get cherry-picked from O2 Litmus?

  • We use “endorsements” — not just downloads, but feedback on forums etc
  • Not just O2 staff that make the decision, but real customers
  • Once app is endorsed, then

Why would you develop on Symbian?

  • Since open sourced, trying to encourage a wider community
  • Now want to make developers have a great experience so that the platform as widely used as possible

Why is there fragmentation across operators?

  • JP: fairly happy if a developer joins O2, works with customers to develop an app, then leaves and sells the app on Orange or Voda
    • customers have had the experience, which is what counts
    • challenge to JP to make Litmus a place to stay, but of course it won’t be exclusive
    • Litmus is part of the marketing strategy — not led by the tech department
  • DW: if you allow customers the freedom to move away, they’re more likely to come to you in the first place
  • JP & SW: we meet up for coffee, it’s all good :-)

The iPhone question: How are you planning to get more user-centred design into your process?

  • DW: Set up four councils, including one on UI. This one has been disappointing — no take up from members of Symbian Foundation.
    • but can you really design an interface by committee
  • SW: put up betavine.mobi on redesignme.com for suggestions, but appreciate that iPhone was driven by one man’s vision
  • JR: iPhone was executed well on all axes. Interestingly it was a vertically-oriented experience that didn’t have a parallel in the existing mobile landscape…

That sounds good, but what about reality? Isn’t there a £1000 fee to have a game listed on O2 Active?

  • JP: Direct access to real customers from self-registration on Litmus
    • I sit here as an operator and know that we’ve screwed things up previously
  • SW: Again, you can upload an app and see it on portal

What is customer experience?

  • JP: Selecting customers who have all you can eat data service and latest phones
    • No point selecting customers just for numbers’ sake

What about app discovery?

  • DW: Symbian won’t be running an App Store, will be running a warehouse that can be queried by lots of different app stores
  • SW: From portal: Home > Mobile Apps > Free Apps
  • JP: Don’t need to be a member to browse the catalogue, just to download

Do operators have a role in educating the market and if so, how? (Patrick from GetJar)

  • Terence Eden: Putting apps front an centre on Vodafone Live. Homepage Beta is encouraging people to upload web widgets.
  • JP: Not going to be placing TV ads — too broad. Instead targeting specific customer segments

How much money is actually going to developers?

  • JP: we paid our first developer last week!
  • Terence Eden: it’s all very well providing you with a connection to our customers, but what you really want is a connection to their wallet!
  • JP: really want to create incentives for customers — Mob4Hire doing that

How many customers are you seeing?

  • JP: email campaign to a selective audience: normal open rate is 10%, but 27% rate for Litmus email
    • typical market survey 5,000 customers, and already well in excess of that

How do you expect to protect your customers against viruses?

  • JP: moderators check submissions for viruses
  • SW: betavine the same

Clarify going from free to paid:

  • JP: within Litmus, you can sell at different price points. While in Litmus, you can control that
    • if you want to go outside Litmus (to 260 million Telefonica customers) you still have to talk to O2 commercial team

Jo Rabin’s wishlist

  • What I’d really like to see is a way of monetize mobile web services rather than apps

Announcements:

  • April’s event: how to finance your business during a credit crunch…
    • Not on a Monday and in the middle of April
  • May: mobile marketing/media

Tuesday, 10 February 2009

MomoLondon: Mobile Web & Widgets

This was a great Mobile Monday London. Short, snappy presentations; an exciting and relevant topic with a real buzz going on; announcements that you heard here first; and really useful networking afterwards.

Many thanks to Dan, Alex, Jo & Helen!

GSMA One API

Kevin Smith — Vodafone

Kevin works closely with Dan Applequist.

Aim to produce network enabler APIs across mobile operators — charging, location, messaging, user profile, connection profile. They’re a network-level complement to OMTP BONDI, using a RESTful and lightweight web services system.

Major European & Asian operators all involved.

Have a reference implementation (beta) available at http://oneapi.aepona.com. Go try it out!

OMTP BONDI

Nick Allott — OMTP

I went to the OMTP BONDI codefest back in January (sorry, I ran out of time to blog about it). So I didn’t take many notes on this presentation.

OMTP is an organisation of mobile operators working together (who would have thought!), with manufacturers and system providers joining in the fun. They’re working on defining a javascript API through which a web runtime environment can access and interact with device-specific information.

So there’s a location API (compatible with the W3C spec as it goes), access to calendar and contacts, etc. Crucially, they’re actually building a reference implementation in order to figure out how the API should work. That way they can change their spec as they discover that it doesn’t quite work in real situations. The spec so far looks good — more details and the downloadable SDK at http://bondi.omtp.org.

The only problem is that the reference implementation is built on Pocket Internet Explorer. Great access to device information, but really hard to make a good-looking, functional widget using web standards…

They’ve got one demo widget so far:

  • EMCC Gig Guide w/last.fm
    • location
    • cached feeds
    • syncing calendars

And here’s where to find the latest widgets: http://bondi.omtp.org/widget-gallery/

Ikivo Enrich

Samuel Sweet, VP Sales

T-Omnia widget solution launched November 2008 in Korea. Based on Samsung, Windows Mobile & Ikivo Enrich.

  • SVG display engine (provided by Ikivo)
  • Javascript w/device APIs & AJAX support
  • Aiming to support HTML display engine later
  • W3C widget spec

“Putting lipstick on a pig” for Windows Mobile!

SK Telecom have had 300% increase in shipments month on month since they’ve launched the new interface.

Importantly, the W3C Widget spec now allows SVG as an alternate rendering option for widgets. This means that the Ikivo widget engine can be W3C-compatible.

Announcement tonight: Ikivo will be supporting BONDI

Firefox Mobile

Christian Sejersen

Currently called Fennec but will be called Firefox when it gets released. It runs on the same codebase.

Some countries currently have more than 50% Firefox usage. Mozilla are starting to wonder what they should do when they get a monopoly…

Fennec for Windows Mobile coming out soon (April?); Symbian version started not so long ago.

Shows a demo of running Fennec on Nokia N810 (Maemo) — Fennec Alpha Walkthrough on Vimeo

Browser controls are off the edge of the page to the left and right. Just scroll that way to see them.

Firefox Addons can be made compatible with Fennec. 20 or 30 Addons are available after a month, with no promotion from Mozilla.

There is full API compatibility between mobile and desktop, so once they add location & camera access to mobile, these APIs are available from the desktop build too.

My thoughts

As per Bruce Lawson’s talk at the Betavine birthday party, the browser writers don’t see the difference between mobile and desktop. I agree with them that the APIs and browser can be very similar, but I still think there’s a difference in how you would design a service.

A mobile service needs to take one particular function and “polish the hell out of it” (as goes the recommendation for iPhone app design). A desktop web app still needs to be polished, but has more leeway in its design. There’s also the interaction styles: a mouse is not a finger is not a d-pad, and you need to make the interface appropriate for each of these styles. Sure some of this can be done with stylesheets, but when you’ve got less screen space you want to deprioritise certain content off the screen completely.

Panel session

Chaired by Dan Appelquist

  • Francois Daoust (W3C)
  • Graham Thomas (T-Mobile)
    • 8 years at Nokia on UI & UX
    • Also bringing games into market (Club Nokia)
    • Been at T-Mobile for 7 years, now Head of Multimedia
    • T-Mobile very active in mobile internet — have iPhone and G1
  • Christian Sejersen (Mozilla)
  • Kevin Smith (Vodafone)
  • Brad Sipes (CTO, Ikivo)
  • Nick Allott (OMTP)

T-Mobile widget roadmap — want to have develop once, run across all handsets. Enabling the long tail…

SVG helps to bridge the gap between different screen sizes — since scalable. But Brad sees it more to “make things fun”.

Q: How does BONDI fit in with other web runtime initiatives, like Adobe AIR or Mozilla Prism?

  • CS: Prism currently in labs (local look & feel for web-based content). But don’t really have anything to say as Mozilla…
  • NA: OMTP did due diligence and found 25 different ways of doing the same thing. Operators decided on a common standard and then broke it in 25 different ways…
  • NA: 3 parts to standardisation
    1. APIs
    2. Display engine
    3. Security (one of the big problems for Java on mobile — see signed apps…)

Q: Sounds like lots of separate bits. Do they fit together?

  • NA: Yes. At least all the people on this panel do… OMTP working with W3C. SVG long-established as rendering tech. OMTP location API is W3C compatible, and could use One API as implementation by getting location from http query.

Q: How do I make money out of writing a widget?

  • GT: Key benefit of widgets — start using internet more, like iPhone & G1.
  • KS: Earn £20K from Voda competition…?
  • FD: sell the widget like the iPhone app store.

One advantage of interoperable widgets is that you can buy your widget from anywhere. You can have your own payment mechanism

  • DA: Can we build interoperable application stores? Micropayments never really went anywhere with the web. Will we get there with widgets?
  • FD: There were some standards about micropayments 10-15 years ago, but they werer never finished… Maybe it’s time to dust them off and complete them.

Q: What benefits do I get from a widget that I don’t get from HTML5? (Hugo from Google)

  • FD: Widgets give you more context, but it’s just a wrapper.
  • CS: A lot of the widget issues have come up because of security issues. But in essence it’s the same thing that needs to be solved across mobile and desktop.
  • BS: Widgets give you local application feel that HTML5 isn’t aiming for initially. But HTML5 will converge in the longer term.
  • NA: Some of the widget stuff has been created as a sticking plaster to avoid 15-20 different solutions while HTML5 gets itself ready.
  • DA: BONDI allows HTML5 over https to take advantage of secured APIs.

Q: My question: widgets on the standby screen? What about battery life?

  • GT: want them on the idle screen, with notification etc. Want eBay etc event-based dynamic.
  • CS: Palm Pre will be fully web-based
  • BS: T-Omnia has widget framework attached to button on the side of the phone. Can have lightweight widget framework on low-level phones that aren’t capable of running full HTML5 browser.
  • NA: battery notification & event APIs planned for BONDI 1.1

Q: What sort of security model?

  • NA: BONDI — consumer delegates trust to an entity. Doesn’t work to prompt the user for everything. Instead they should be able to trust Norton, Google, T-Mobile, etc.
  • DA: using XML digital certificates within the widget

Q: If you had one widget, what would it be and how would you interact?

  • BS: weather. would beep at me if thunderstorm coming in.
  • KS: widget that tells me if my 8 year old daughter has turned off her light…
  • CS: can I have a browser instead?
  • FD: tells me which way I should vote on W3C…
  • GT: M25 road traffic info
  • NA: a widget that syncs my contacts
  • DA: location-based ski conditions. What’s important is that the bar is lowered. I want my mom to write widgets!

Q: Have Palm come up with a way to make webapps feel like native apps? (Hugo, Google)

  • CS: Mozilla often have discussions about how to make the browser look native. But people don’t care. They want Facebook to look like Facebook, not a T-Mobile application.

Q: What do operators feel about making widgets more available? (David Stone)

  • GH: Shortly launching service with idle screen. Demo on idle screen. Gallery also available.

Monday, 2 February 2009

Cat at the gate!