We do plan to update the research soon after Ovi Store is launched.

Regarding your questions:
1. Yes, if you are talking about developing applications for mass-market devices, which is the route taken by games developers. Think of Java as the lowest common denominator in terms of development environment across mobile devices.

2. I don’t think there’s a single SDK, as there is no single Java flavour out there.

3. Ovi Store should be launched in May and billing is done centrally via credit card. I ‘m not sure if operator billing will also be done centrally 100% of the times

4. There are a few companies offering global billing solutions (e.g. Tanla, Bango, Qpass, etc), but there are no widely deployed app stores on Java yet AFAIK.

Andreas

Very good article, need to update a little bit regarding the Nokia Ovi as you mentioned.

If I’m now exploring the best way to enter the MAS community as a developer, and my specialty is Java, what would be your answer to the following questions?

1. Does java give the most wide solution for a variety of devices?

2. What Java sdk is the most common and recommended since each manufacturer recommends his own extended sdk?

3. Regarding OVI, I see there is a link to the developers website, so how is the billing can be done centrally?

4. Is there a need for centralized billing solution in the market and who is leading it now?

That’s for now.

Thanks a lot

Ohad.

Indeed – Nokia has big plans for Ovi Store and seem to be finally catching up.

We need to update this article, as so much has happened since November when it was written. Watch this space

Andreas

Everypoint’s Nemo brings together an enhanced Java runtime with a vector graphics engine, sync APIs, a on-device-storefront and a marketplace for submitting applications and settling rev shares.

As such Nemo offers some really key technology bricks (much like what In-Fusio was doing 5 years ago) and the important marketplace + on-device storefront infrastructure. However it lacks key billing and distribution deals.

The solution would be perfect if acquired by an OEM or Sun (who’s Java ODP solution is too little too late), but on its own Nemo has a long uphill battle to fight against the so many App Store me-toos.

Andreas

Good question. I tend to think that niche MAS offerings will not be viable, as the set-up costs are too high. Unless you skip the home-grown solution and related costs and simply brand someone else’s white label MAS offering (e.g. Handango, GetJar) and offer a hand-picked set of apps for a vertical segment (e.g. financial).

However, trying to compete with Apple’s App Store or anything similar with a home-grown MAS solution is no small feat – which is why I think most network operators/carriers won’t succeed in getting app download revenue from home-built MAS solutions – only through white labeling.

One successful recipe in this new MAS market might be to act as the matchmaker and integrator – offering a choice of billing integrators (e.g. Bango, Tanla), app catalogues (e.g. Handango, GetJar), on-device storefronts (e.g. mPortal, Everypoint Nemo), and distribution deals through handset OEMs.

The industry players with the most to make here will be the middlemen who can customise and scale white label MAS solutions.

Andreas

Where do you think the best area to develope a small miche that would serve a specific marketplace. An MAS for a specific service -financial fir example or targeting development for certian types of phones, smart phones for example.

Where can someone lookimg got investor funding in this space (ptentially) find a nuche) for 2009. Whats the latest trend as you see it. I’m looking to pitch an idea of an MAS store offering everything the big guys don’t (the best of all worlds and giving more revenue to the developers…

I only have anecdotal evidence on the impact of MAS on smarpthone sales – and that comes purely from personal experience, and so is non-significant statistically. But it may be helpful in extrapolating and drawing some early conclusions that are generalisable.

The diversity of applications on the iPhone, coupled with discoverability, catalogue management, search, etc, makes it easy to find the application that’s best suited for each user (i.e. comes very close to 1-2-1 targeting of apps for users). This in turn creates passionate users, as they can find applications they care for. This in turn creates word of mouth marketing, blogging and generally viral marketing. If a campaign can target the opinion leaders (alpha users) then the viral effect is more pronounced.

I have seen this effect apply to the iPhone, from personal experience. That is, the ‘I love this application on your phone, how can I get this phone?’.

One thing for sure is that users/people think in terms of use cases, not platforms or technology. The use-case focus is also behind the rise of application-specific phones (e.g. Three’s SkypePhone and ING’s Facebook phone). So in answer to your question, I would say that users would buy a phone if they find that it is particularly good in a task or use-case, whether that is listening to music, getting the latest gossip on facebook, making them look cool, or being small enough to fit in their pocket. I don’t think that the ‘average’ phone buyer would buy into the potential/technology/platform aspects of a smartphone (and there is no average buyer

BTW, the word smartphone should be banned – it’s is an industry term that doesn’t translate in the userland.

Andreas