Indeed that can work for some, at the expense of a bloated APK (ZXing is about twice as large as my app, so it would likely triple my APK size), and at the expense of updates to ZXing not automatically becoming available to your users until you release your own update that bundles an updated ZXing, or unless you add additional checks to see if ZXing is already installed and use that external one instead of your baked-in copy of ZXing.
For me this approach would not work anyway, because apart from ZXing my app also launches Google Goggles and if not installed searches for it on Android Market, while I am working on third-party product referrals via Android Market. Again I have no idea if those third- party products will ever land in the Amazon Appstore. In relation to some discussion notes by others: I welcome alternatives for Android Market, and I distribute my app also via for instance Phoload, AndAppStore and Getjar, as well as via my own website, but in all those cases I need not change a bit to my APK and can rely on Android Market for extending basic functionality of my app. Amazon Appstore sets a precedent, and leaves the whole burden of sorting out how to best deal with it to the developer. Thanks On Jan 15, 4:14 am, Brill Pappin <[email protected]> wrote: > @blindfold I have an experimental app that does the same thing. Luck > for us, the Xzing code can be pulled down an added to your local app. > However this is apparently a drawback to multiple app stores! > > - Brill Pappin > > On Jan 14, 4:26 pm, blindfold <[email protected]> wrote: > > > My app got rejected by Amazon Appstore today because it searches for a > > third-party app (the well-known free ZXing barcode reader) on Android -- 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
