Responding to a post from Android Dev, but this is more of a discuss answer.
Is it legal for both Apple and Android's rules to make a Wap app first, charge that as Paypal or google Checkout, then offer a free client for Android and iPhone client that mainly repeats the same functionality, but with some native integration and better assets? That way you will have always charged over the browser, but you are on both market places, without violating terms? Like I pay Pandora $10 a year, but I enjoy both Android and iPod touch clients? If so I think I recommend this method. I don't want to advice anything that will lead to Apple rejection, or Google takedown. Of course I'm not aware of any significant Google takedown. It'd be cool to be be the first :-) What helps is you can quickly deliver the iPhone and Android apps, since both can run javascript and html. Also on Android, it's easy to mimic the native browser from in your app, or to hide that it's a browser at all. Although it'd be great if it was even easier. Go web apps! On Nov 14, 4:12 am, jax <[email protected]> wrote: > I am wondering how I might go about securing a paid app on Android. > > I am thinking of selling the application from my own website via > PayPal, however, how will I stop people from sharing it with their > friends etc. Does Android have any type of native support for this? -- 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.
