What's the best strategy for deploying version for upcoming Kindle Fire HD
First let me lay the groundwork for my question: Right now, I have one executable for both the 7" and 8.9" versions of the Kindle Fire HD. Until I get my hands on the 8.9", I won't know how well some things will work, since using a camera with the emulator doesn't really tell you how the real device will behave. I have set up the emulator to use my computer's web cam, and can actually take still pictures using the 8.9" emulator, so I have done everything I can to insure the app works properly with the 8.9. But I won't really know how it behaves on the actual 8.9" until I can get one. I preordered an 8.9" early on, but I won't get it until week after next. I will try to pick up an 8.9" in a store next week. I will thoroughly test the app once I get the physical 8.9" tablet, and make necessary adjustments. Obviously if there are issues that I discover, I will want to push out an updated binary ASAP. Now here is the question: Which will be faster to get reviewed and approved: One binary for both the 7" and the 8.9", or separate binaries for the 7" and 8.9"? If I have to make adjustments for the 8.9", can I submit just a 8.9" updated version or do I need to submit both together?
I was able to pick up a 8.9 at Best Buy today, and it is exactly as I feared - there was a SURPRISE! when I ran my app on it. Now the question is no longer academic, I need to get a different binary for the 8.9 onto the App Store ASAP. I'm afraid of going through the normal channels (ie. submitting a support request) because of how I got shafted the last time I requested something out of the ordinary. I don't want my app to get pulled off the market entirely again like last time.
Hi Thanks for posting on the forums and testing the app on different available physical device. However the forums are mostly used for answering general questions, and the developer community to contribute to app development. This specific case would need more details about the app and we would request to log a ContactUs (
https://developer.amazon.com/help/contactus.html) with us and one of our support engineers will help you fix the issue.