We're all really excited about Ovi, but this signing is an ongoing issue with Java ME. As the world's leader you've given us tools to play with and a market to target. For that we're grateful - however.
As you know, the operators worldwide have done their level best to control Java ME with draconian security policies on their branded handsets and severely restricted ISVs as a consequence. Under the guise of maintaining subscriber safety it's a direct revenue pipeline for them - so you pay to join their developer program (and each one is different with another fee) so you can get your app signed into their custom protection domain.
Just so that then, in theory, you can use JSR-75 to open a simple text file without 18 prompts.
Imagine buying a PC and having your ISP decide what applications you can install on it and what they're allowed to do. Or you write an application that uses Notepad but have to get it signed by Microsoft before you can use it - even if it's just for your own amusement.
The only reason they've got away with this over the last 10 years is that the general public isn't aware that this is happening. It's absurd.
For God's sake Nokia - you're big enough to set the rules here! Let us sign into the manufacturer's protection domain (or some useful new one) and let's put this rubbish behind us!
This is a real (and maybe final) chance for you to un-f&%#k the Java ME signing industry and keep the operators out of the process. We're all keen to sell directly to the consumer and I for one am happy with 70% rev share if it means that I don't have to bend over and touch my toes for telcos.
So given this statement:
"Java and Symbian applications must be signed appropriately, no signing related warning messages are allowed at any circumstances"
We'll need some help to make Ovi a success in the Java ME space.
Symbian apps are no problem because the telcos can't control Symbian Signed (thank the Lord).
But when it comes to Java ME access rights, you, Nokia, need to help us - the people out here trying to explain this joke to non-technical clients and customers, overcome stupid API policies on branded handsets such as AT&T (http://wiki.forum.nokia.com/index.ph...cess_rights_v3).
If nothing else we'll need to access IMEI and/or IMSI info for licensing. I know we can do this in the manufacturer's domain - so how about a tutorial/walkthrough on the Ovi homepage for getting that working via Java Verified? At least make it clear that almost every operator will shutdown API access on branded handsets so that the developer market for Ovi doesn't get stung this time around.
If the telcos don't want to play (and they won't) then eventually less people will get caught with branded handsets in the future. I know I'm helping spread the word on that here in Oz.
Either way, let's sort this out hey? It'd be unbelievable to see Ovi have the same success as the Apple app store and we want to help.