Refresh Mobile
I've just been to a
Forum Nokia developer event here in London. It was very well organised and well
attended. I can say there was a real attempt and promise that Nokia are
trying their hardest to solve as many issues to help developers as possible and I
really believe they are doing good work here. There was some friction in the
room when issues to do with developers, the Ovi Store QA Process and Ovistore in
general and I realised I should do this post which gives a few hints and tips on
using the Ovistore. Just a bit of background. I have written and
submitted more than 20 apps to Ovi store, 3 to iPhone Appstore and more than
20 to Blackberry Appworld and do think I can put all the issues into context of
what its like with all the appstores.
1) The QA process is frustrating on all the
appstores. In fact by far the worst is Apple in my personal experience. One
issue is they all fail to explain the real reason adequately for a rejection -
its seems to be in everyone's system that they send a standard e-mail rejection
where the reason for the rejection is unclear, So Ovistore is not bad in this
context -it could be easier though.
2) On Ovi your app needs a certificate if its
Symbian or Java but does not need a certificate for WRT. So, for ease of
submission I'd recommend WRT (although the number of handsets supported is fewer
than a Java submission for example. Then the question is how to sign it. The
answer is you can self sign (forget java siged) and I'd recommend using the
Thawte certificate for Java not a Versign (Thawte is cheaper anyway). Both have
issues - neither have root certificate on all devices. But Thawte is best. If
you use Thawte then deselect the following handsets 2730, 3208, 6263, 6600i,
2720 fold, 3710 fold, 3720, 7020 and 7050.
3) WRT and the N95. The N95 had WRT support in
later versions. In reality most people have upgraded and therefore its usually
safe to select the N95 and N958G, but it seems that sometimes the QA people
don't know this and sometimes get rejection from them which you should sort out
by commenting back to them. A further problem occurs with N95 because you often
you get "content missing" in Ovi store if an N95 tries to download a WRT (this
is simply a bug in Ovistore which I am sure will be fixed sometime
soon).
4) QA is only part of the process to getting
your app live. It can take up to a week for it to actually go live after it's
passed QA before it appears. If you watch the "Published to" flag it will
initially say 0/1 channels and later say "1/1 channel". When it does this it
means its about to go live... it still takes up to a further 24 hours to
actually appear. People often think its not there when it really is, because it
depends which devices you published it to. So you should really look with a
real phone (or use a user agent switcher plugin inside Firefox). Finally there
are often cases with content which never appears in these circumstances. This
is because someone in Ovi made a mistake (of course in a well designed system it
should not be possible to make this sort of mistake-but I'd better not go
there). In this case just fill out a comment in the content in publishers. I
find they are helpful and you'll get a solution.
5) Finally depending on your content you may get
the "sensitive content" email. This happens for example if you have pictures of
girls in bikinis or even men in shorts in your content. Your get a list of
contries you need to de-select (mostly moslem countries). This list is
annoyingly long and the chances are you'll make a mistake entering the
selections for the list. For until they have a "sensitive countries template"
you'll have to live with this frustration.
.