>> Users require an activation key to run your app, and the users are sending those requests through their devices to you, which in turn contains their region data that their device is running? Is that correct?
Long story here. My app is a trialware - 30 days free, then you pay. In the first release, I had a required registration step - on the first run, the users would provide their e-mail, name and password for subsequent access, then click "Register". The back-end would store all that and issue a 30-day license. Along with that stuff, the system would transmit some basic device properties - including the system language.
Then I decided the scheme was too complicated, and I was losing potential users on that. I simplified the startup UI - now there's just a button that says "Free trial". When they click it, a similar message goes to the back-end - the same system specs, but no e-mail/name/password, instead, an "anonymous registration" flag so that the back-end can tell. In this setup, I'm still getting a record for each new device, but no user info.
Completely avoiding some kind of registration on startup would be a potential trial violation vector waiting to be exploited.
>> Very interesting stuff on the Chinese market, I'd really like to see how many apps are available in the Chinese Marketplace, and other Marketplaces for that matter. Does anyone else know a good way to do this through our emulators?
Download a Chinese emulator image?