Showing posts with label litmus. Show all posts
Showing posts with label litmus. Show all posts

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, 16 December 2008

O2 Litmus launch

I went to the launch of O2 Litmus on Friday — in the form of a hack day at the O2. It was interesting to see an operator directly running a hack day. Usually they’re involved as the supporting acts in a semi-official way, like Vodafone Betavine supporting OverTheAir. The guys at O2 did a reasonable job — finding people via twitter and other events and providing solid wifi and lots of power supplies. They didn’t leave quite enough time for the hacking though, allowing too much time for O2 Litmus partners to advertise their wares in the morning.

O2 Litmus itself seems like a good proposition in business terms — the same 30/70 revenue split as the Apple App Store; a system to let developers test apps with early adopters before releasing them into the wild; and money coming through to developers just 5 weeks after purchases. O2 are also trying to support app development through their partners, providing testing and business development support.

There are a couple of pieces missing, however. One great advantage of the Apple App Store is the ease of download — one click and the app automatically downloads to your iPhone and appears in your home screen. This is much harder for general phones at large — not only do you have to make sure you’ve got the right build for your phone (a problem that Apple has avoided for now by just having one platform), but you then have to figure out your phone’s weird and wonderful download experience. Do I really want to install something that my phone tells me could be a security risk? Do I want to install it in Games or Applications? And now it’s downloaded, where did it go? (Nokia Series 60, I’m talking to you here…)

At the moment, O2 Litmus requires a separate application and description for each build, with no provision for combining builds with automatic detection, and no support for external hosting either. I suggested that they consider allowing URLs for downloads and they seemed interested — this also opens the door to web apps instead of downloadable apps. They might also consider partnering with one of the companies who make a point of providing effective provisioning systems — like Paxmodept, GetJar or even ourselves.

The other piece that is missing is direct access to the store from the phone. O2 say they will email their early adopters in a few weeks to get them involved in the web site, but even those who do will not have the ability to see what their friends are doing and download the same thing. Spreading applications virally requires immediate access to the app as and when you see someone else using it. Miss the moment and the viral effect dies. The iPhone provides the App Store on the device itself to help with this — it’s not the easiest solution but at least it’s possible. Since J2ME apps make sharing apps intentionally hard (security to stop people sharing paid-for games…), O2 need to provide some access to Litmus from their phones.

As I mentioned above, the hacking competition itself was a little rushed — we only had about 3 hours to get something ready. As a result most of the entries were screenshot prototypes and sometimes not even that. I started putting together a simple J2ME version of our iPhone MyRail Lite app but NetBeans wasn’t behaving itself. Instead I made a paper prototype integrating MyRail Lite with twitter so that you can meet friends on the train and as they arrive:

Share your train journeys on twitter with myRail Lite on iPhone. Click the Tweet button on your departure, select your destination and carriage and it will send a tweet for you. Also see which train your friends are on and track them as they go.

The idea caught the attention of the judges (I imagine it was the idea rather than my sketched interface!) and I won second prize — 30 hours on DeviceAnywhere.

Here’s my full notes from the day if you want a bit more detail:

Why Litmus?

  • Came to the conclusion about a year ago that O2 is quite difficult to do business with…
    • Just like the other network operators! Except O2 hasn’t had a developer program recently.
  • Enabling O2 customer base to test apps and feedback
  • Developers can test apps and get feedback
    • Can control how many customers can download it and test it out
  • Developers can also put apps on sale directly
    • O2 take 30% cut of sales — exactly the same as the Apple App Store
  • Plans to incentive customers to get involved
    • Any customer that has tested your app will get the app for free when you go commercial
    • So controlling numbers of testers is crucial
  • O2 Marketing will monitor forums & feedback and launch popular apps into main customer base
  • Money comes through to developers after five weeks

Litmus Tools

  • O2 APIs
    • Connection Status API
    • Location API
  • Supporting services:
    • DeviceAnywhere — remote device testing
    • Rackspace — hosting
    • Segala — expert testing

Mobile Social Networks — Ewan Spence

Poking from your mobile

  • Involved in running Wubud — still in stealth mode
    • 100% focus on mobile, but with web client too, linking to other social networks
  • itsmy.com makes money from users buying widgets
  • facebook 0.3% CPM…

Mobile Developers Dilemma — Paul Golding

Slides available online

  • Still has his Source O2 badge from O2’s previous developer outreach programme
  • Expert member of MIDP3 group
  • Chief app architect for Motorola in 90s
  • What should you build?
    • Open APIs
    • Involve a community to build weight & momentum
    • Provide service & support
  • Mobile UX: should exploit context
  • Use microformats — if there isn’t a suitable one then invent one!
  • Jitterbug — successful phone for old people in US
  • Social Business Model: share ideas with frenemies
    • Share the risk
    • Exploit mashups
    • Create or be part of an ecosystem, so that even if people click out of your app, they haven’t left the ecosystem and are therefore more likely to come back
  • Paul’s 9 year-old son is an iPhone developer :-)
  • Growth areas:
    • Enterprise social software
    • Services to support SOHO users

Inspiring New Ways of Design and Development — Anthony Ribot

Slides available online

As usual, Anthony gave a good presentation on mobile design. The Ribot guys were on a lucky streak on Friday, winning both a Sony Ericsson C905 in the raffle and coming first in the hacking competition with a proposed mashup of dopplr and your phone address book — find out who’s in town and then call them straight away. Well done guys!

  • The user-centred developer is a new type of role that should exist
    • Should develop with the user in mind
    • Not a role for every developer
  • Clients from web medium come with a long list of 15 features
    • We tell them we’ll only implement the top 3 items, or even just the top 1
  • Data-snacking is the most common experience on mobile
    • 30-60 seconds experience — small snippets of info
  • Important to re-use the learnt behaviours of the device
    • Makes the first experience of the app that much better
  • Mobile not about making things smaller!
    • Must take in context of use and figure out what the user actually wants to do
    • Cameron Moll: Mobile Web Design book
  • It’s all about the subtleties
    • e.g. working around the 3G icon on Nokia devices — Opera Mini indents the page title
  • Try and make the experience support reward-based design
    • e.g. Opera Mini (again) — right arrow does clever things based on context
  • Dealing with diversity
    • Use statistics (e.g. admob) to work out top 5 handsets for your target audience
  • Use rapid prototyping
    • The sooner you can get something tangible in your users’ hands, the better
    • Paper prototyping is good, but having something real is so much better
    • Finding that there’s less application stuff and more motion
      • Harder to describe in paper prototypes and screenshots
    • Tools available:
      • Flash (lite v3)
      • XHTML + CSS
      • Nokia Web Runtime
      • Silverlight (coming to Windows Mobile early next year, Symbian & Apple targeted too)
      • Dashcode

Partner adverts

We then had presentations from Rackspace, NAVTEQ, DeviceAnywhere, Mob4Hire and Segala.com. These were interesting in parts, but generally not much more than we could have got from flyers — a bit of a waste of time when the audience was mainly developers. We know what hosting is, thank you.

Rackspace — Matt ???

  • 2600 employees (40-50 in London)
  • growing about 50% year on year
  • have “positive churn” (1.5%)
  • 24/7 live “fanatical” support
  • 80 new devices launched with GPS in H1 2008
  • 74m GPS phone devices sold in EMEA next year
    • 55m smart phones, others feature phones
  • NAVTEQ Network for Developers
    • Online developer community
    • Includes sample map data
  • NAVTEQ Connections Web Portal
    • matchmaking, promotion
  • 6th year of NAVTEQ Global LBS Challenge
    • 2009 prizes include cash, tool & data licenses and handsets
  • O2 segments:
    • Ambitious Status Seekers
    • Frenetic Families
    • Fun Loving Socialisers

DeviceAnywhere — Leila Modarres

We use DeviceAnywhere for testing our JavaME apps (such as the National Express East Coast Timetable to Mobile) and find it very effective. I didn't take many notes on this session as I already know how it works. Go see their site if you want further details.

  • Screens only turn on when the device is in use
  • Will hand out 30 free hours today
    • I won them!

Mob4hire — Paul Poutanen

  • Mobile developers can leverage the value of existing handsets to test for other developers
    • Earn money on mob4hire…
  • Developers can use Litmus system to take advantage of 25,000 early adopter customer base on mob4hire
  • Roadmap:
    • Certified testers
    • Remote emulation — competing with deviceanywhere (using LogMeIn)
    • Coder4Hire
    • Market research — localisation etc.

Segala.com — Paul Walsh

  • Expert testing services