> If you use suggested techniques like reflection to determine what > functionality is available to you at runtime, you only need one version of > your app. Or keep going the way your going and enjoy your maintenance > nightmare.
It's not much fun adding text-to-speech via reflection, lot of functions there. My particular problem is that my app covers a large proportion of the API. Nevertheless, everything since donut I have added via reflection. > > Why do you need a separate Market and non-Market version anyway? > Because after launch of the direct purchase version, I found that my package name was blocked when publishing to market because it had been an ADC2 entry. And because Google doesn't provide any method for me to test if the app was bought on the market. And now, because I can't do BT control with a market app for cupcake/donut. Don't get me wrong, Google are doing some great things with Android. There are just some little things that would make developer life much easier. Pent -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
