Building for Amazon Newbie Steps

Solar2D Android
#1

Hi,

I have successfully built an app for iPhone / iPad, it is on the store…joy!

Building for Amazon is completely foreign to me. Is there a high level step guide to generate an app for Amazon? I am talking like, first create a Amazon developers account, second, do whatever???

As far as coding: do people litter their code with device type checks to run the appropriate code (IOS versus Amazon etc) or do you create separate projects? I would prefer keeping all the source in one project.

I think the only areas of difference are IAP and Ads? Is there anything else???

Any hand holding would be appreciated,

Rick

#2

Hi,

I’ve put together an article outlining the Amazon App Store process here.

Let me know if you have any other questions.

Best.

#3

develephant!

Exactly what I was looking for…thanks I appreciate it.

-Rick

#4

Was my pleasure.  Best of luck.

#5

Hi,

I’ve put together an article outlining the Amazon App Store process here.

Let me know if you have any other questions.

Best.

#6

develephant!

Exactly what I was looking for…thanks I appreciate it.

-Rick

#7

Was my pleasure.  Best of luck.

#8

Fantastic post! Helped me all day when I try to convert my iOS app to Amazon. Something I noticed is that you did not talk about the back button (and volume) implementation. Is that because it is not required? I thought all Android devices have a back button. Thanks for shedding any light on the back button issue and Amazon. Mo. Ps: LOVE your blog!

#9

Hi LairdGames,

Thank you for the kind words.  I honestly have never had to deal with any special case in regards to the “back” and “volume” buttons.  The “back” button is built into the software interface on the device itself.  It operates exactly as you would expect on other Android devices.  The last couple Kindle hardware releases have a dedicated volume rocker.

Your question also brought something else to mind, and that is making sure that any interactive content, like ads, or buttons, do not cover the bottom 40 pixels or so of the screen.  The Kindle “control panel” tab is always visible on the bottom, or side, depending on the app orientation.

Thanks for pointing that out.  I will add that to the next revision of the post.

Have a great holiday.  Cheers. 

#10

Some app stores like Samsung want the back button to take you back to the previous app screen.  If you don’t trap it and handle it, it defaults to exiting the app, which may be fine.  In most cases you probably want the operating system to handle the volume controls, but for the back button you may want to handle it.

A few months ago we did a tutorial on “Androdizing” your app.  http://coronalabs.com/blog/2013/03/26/androidizing-your-mobile-app/

That covers suggestions on handling the back button among other things you need to be aware of.  With Amazon you need to be aware of what fonts are being used as well.

Rob

#11

Thank you guys for all the great info! NP develephant!

Mo

#12

Quick question! What is the file name and image size do I need use for a splashscreen on a Kindle Fire HD? Of course I am asking for app release to the Amazon store. For the life of me I can seem to find that info? I have a default.png from my ios app code but the size do not seems to correct for the Kindle Fire HD 7" when I run it on that device.

Thanks so much.

Mo

#13

This is a bit complex, so bear with me.  Android doesn’t use launcher images like iOS does.  Because people wanted a launcher image, Corona Labs engineers way back in the day added support for reading the iOS Default.png file.  In those days we just had a few screen sizes to support.  Now today with so many different screen sizes and shapes, its nearly impossible to make a Default.png that works universally.

Also, Apple encourages you to not do splash screens.  They think the Default.png should be as close to the first screen the users are going to see when they launch your app and that people should get to the app’s activity as soon as possible.  Because of these two ideas, we recommend that you simply provide a Black Default.png and let your app start displaying as soon as it can.  If you want a splash screen, implement it in your code and don’t expect the OS or Corona SDK to do it for you.

But to technically answer your question, Corona SDK is going to show your Default.png file, and there are no controls on your side to select anything else.

Rob

#14

Thanks Rob! I m sorry I meant the Default.png I can see (very fast) that the default image is somehow smaller than the Kindle Fire HD (7 inch) But I like your idea of just supplying a black Default.png image! That way I really do not have to worry about it size. Do I even need a Default.png if I am making an android/amazon app? Thanks a lot again Rob. That really helped. I was really going crazy figuring out the size need for Android! Mo

#15

You do not need it.

Rob

#16

Thank you! By the way Happy New Year and thank you for all the help you provides us all here in 2013! Mo

#17

Fantastic post! Helped me all day when I try to convert my iOS app to Amazon. Something I noticed is that you did not talk about the back button (and volume) implementation. Is that because it is not required? I thought all Android devices have a back button. Thanks for shedding any light on the back button issue and Amazon. Mo. Ps: LOVE your blog!

#18

Hi LairdGames,

Thank you for the kind words.  I honestly have never had to deal with any special case in regards to the “back” and “volume” buttons.  The “back” button is built into the software interface on the device itself.  It operates exactly as you would expect on other Android devices.  The last couple Kindle hardware releases have a dedicated volume rocker.

Your question also brought something else to mind, and that is making sure that any interactive content, like ads, or buttons, do not cover the bottom 40 pixels or so of the screen.  The Kindle “control panel” tab is always visible on the bottom, or side, depending on the app orientation.

Thanks for pointing that out.  I will add that to the next revision of the post.

Have a great holiday.  Cheers. 

#19

Some app stores like Samsung want the back button to take you back to the previous app screen.  If you don’t trap it and handle it, it defaults to exiting the app, which may be fine.  In most cases you probably want the operating system to handle the volume controls, but for the back button you may want to handle it.

A few months ago we did a tutorial on “Androdizing” your app.  http://coronalabs.com/blog/2013/03/26/androidizing-your-mobile-app/

That covers suggestions on handling the back button among other things you need to be aware of.  With Amazon you need to be aware of what fonts are being used as well.

Rob

#20

Thank you guys for all the great info! NP develephant!

Mo