CorePlayer on OVI

[corecodec]

We have been working on CorePlayer 2.0 for about 2 years now (1.3.x is public atm) and before we release it later this year for all platforms, we were wondering how OVI will handle unique identifiers (ie; serial numbers) for purchased applications. There is no mention in the GUIDE on how this is handled. Is it assumed that its secure? We all know very well here as publishers that almost everyone one of our applications has been compromised at one point or another... so we are curious on how this is being handled.

Our normal method for resellers is to have them HTTP POST the purchasers information to our 'Core Account' system, we then generate a unique CoreNumber/Serial number for them and then post it back to the reseller.

I also have a few more questions....

- How about publishing updates? Is it as easy as updating the file and changing the version number to something greater then the current one?
- How about release notes? We often release several versions back-to-back and with 2.0 are moving towards an even faster release cycle.


Your help is appreciated.

[OviDario]

...we were wondering how OVI will handle unique identifiers (ie; serial numbers) for purchased applications...

The current system is very basic and simplistic, it has been described as a wrapper. Not being overly technical my self; the consumer's profile is tied to their mobile number. So, the file they've purchased can only be downloaded to the device with that number.

- How about publishing updates? Is it as easy as updating the file and changing the version number to something greater then the current one?

Once the file has been published yes. If the file were to be in other QA statuses and you wished to upload a better version or a slightly different one, then you could create another content file (differentiations could be on target devices, languages, geographical offerings).

- How about release notes? We often release several versions back-to-back and with 2.0 are moving towards an even faster release cycle.

These perhaps should be placed on your support page and made reference to on the file's menu.