
Originally Posted by
rippe
Good about Java Verified:
-Independent testing of your application. This is important to small developers who would not necessarily have a decent QA process available.
-The "signature" is valid for ten years. Comparing to some code signing certificates where the "signature" cannot be valid for longer than the signing keys are. Example: A year valid certificate purchased ten months ago can only give signatures which are valid for two months.
-No error messages at installation
-The application can have All ways allowed privileges when set by the user
Bad about Java Verified:
-The process should be made more straight forward -> we are working on that
-There should be decent help of how to use the process -> we are working on that
-There should be a way for the developer to test the application as signed before the application is submitted -> coming up
-There should be a way for the portal to automatically check if the application will work after being signed -> evaluating options
-As Java ME devices are very fragmented, there should be away to reduce cost of Java Verified -> on its way as soon as we get the next version of the criteria out. I've been calculating cost reductions up to 65% with applications to Nokia devices.
Cheers,
Risto