On Jan 14, 11:07 am, Shane Isbell <[email protected]> wrote: > Detect whether AndroidMarket is installed on the device using the > packagemanager. If it is installed, enable the open-market functionality > within your app. This will allow you to do a single build. > > Shane >
I don't think that will meet Amazon's guidelines. Their policy doesn't state that you can refer to the Android Market if available. Yes, there is some pain involved in creating a different binary. But think of it as an opportunity to automate your builds. Perhaps there are other business opportunities that would benefit. In Windows Mobile days, I did have to have separate builds for Handango, PocketGear, and my own web site. It was compile time constants, not branching. That was helpful when I was able to build a trial version bundled on a device, and then an OEM version, with specific customizations. While still using compile time specifications, it was a bit messier than I would want by the time I got the OEM version done. But I tend to forget the pain if there is money involved. I wonder, since this is requiring a custom build, if it is worth using a different package name for Amazon. It could relieve Amazon's dangerous price control. After all, that's how manufacturers and retailers avoid price matching and price dilution: use a different SKU number for an almost identical product. I may be too late for that since the app is already going through review. If no custom builds is the overriding goal, then the way to accomplish is not to link to other apps, period. Nathan -- 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.
