Dear all, I know this has been discussed in the past, but I haven't been able to find the answer to my question.� Please help to direct me to past posts if applicable.
I'm thinking of making a registration process for my app.� there is a trial period where the user can use it for 5 days, then after that, certain features will be disabled until the user enters a registration code (based on the hotsync name). from reading through the documentation, there are 3 places where i could put the registration state:� (there are many schemes, but whatever the scheme, i still have to save the state somewhere...) save as a preference: deleted when the user removes the application, therefore when the user hotsyncs the app on again, the app becomes deregistered.� also, if the user has not registered, he/she can remove the application, re-hotsync it, and will have another 5 days of usage! save as a feature: stays on palm when user removes application, but deleted when user resets the palm.� therefore it's not a good place to put it, since a soft reset is like a reboot.� save as a seperate database: the documentation calls this "shadowing".� still sucks because it solves the problems in the previous 2 ways, but leaves behind a DB on the user's palm even if the user doesn't want to have anything to do with my app.� and also, it's can be easily removed. so is there another place where i can store this registration information that's more secure?� what are other people using to encourage registration of your software?� or is it just that the hassle of delete/re-hotsync motivating enough for people to pay and register? thanks! -Hugh � __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
