Flipline, I kind of understand what you are saying, and kind of don't. I already keep one code base and either export the app for Apple or Android as you suggest, which is easy as pie. I will be able to keep doing that with the ANE that I have for in-app purchases, which can test whether I am using an Apple or Android device and use the ANE accordingly, so I will still be able to export as either IPA or APK, easy peasy. But now, I will have to keep a separate code base with an Amazon ANE for in-app purchases, and Amazon functions to handle the purchases, and export this to an APK for Amazon. This means that if I add any new features or code to one app, I now have to add it to the Amazon version as well. I call this inefficient. I would much rather have one code base and ask questions like this: If this is an apple device { run Apple in-app purchase code } Else if this is an Android device { If this is an Amazon Android device { run Amazon Android in-app purchase code } else { run Google Play in-app purchase code } } Then I could keep all code under one roof, export it as an IPA or APK, and upload it to the appropriate App Store. Of course, to do this, I need to know what kind of Android device Air is running on. You guys are telling me that you do not do it this way, you just upload Google specific in-app purchase code to the Apple Play store, and Amazon AppStore specific in-app purchase code to the Amazon store, right?
... View more