On Apr 14, 9:16 am, westmeadboy <[email protected]> wrote: > Essentially, he's suggesting that the remote kill switch is not a very > good idea... Instead, he suggests a one time message to the user but > allowing them to continue using the app.
Technically, this is as simple as commenting out a call to Activity.finish() after an engaged "kill switch" is being detected. Now your users look at a nag screen (to help out with some parlance here). Devs will want to weight what fits their style and aspirations, user expectations, life cycle of the app and so forth. For an app with a relatively short life cycle for earning some half decent money, as Craigo's app seems to be, the full-on disabling of older versions would probably be the way to go. Rinse, repeat for the next app if you're inclined to roll another one. P.S. Reading the blog... where Saurik " basically told them that there was no solution to piracy". That of course is not the case. There are solutions, question is, how far a dev feels comfortable with inconveniencing paying customers with their particular solution. Remember Dongles? Super effective, but a PIA. Similar things can be said about DRMed AAC's. -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
