Android Back Button question

Solar2D Android
#1

So I was reading the Android requirements from http://developer.android.com/distribute/googleplay/quality/core.html and it says:

“App supports standard system Back button navigation and does not make use of any custom, on-screen “Back button” prompts.”

Are we really forced to remove all on-screen Back buttons for android devices and leave only their back button functionality? I can understand adding back button functionality for the android device, but having to remove the back button on screen seems overkill? [import]uid: 77199 topic_id: 36179 reply_id: 336179[/import]

#2

We’ve left the Back button on screen in Forever Lost for both Google Play and Amazon and both are fine so far. [import]uid: 119420 topic_id: 36179 reply_id: 143700[/import]

#3

Keep in mind that the Google quality suggestions are merely suggestions to help maintain the look and feel across all apps on an Android device. Since Android devices have a dedicated back button, it is wise to be a good steward of the system and maintain its usability and to not disable it (or in Corona’s case, make it usable). If you keep the back button disabled, you will have your fair share of users that complain about it and to be honest with you, as an Android user, it is frustrating when the back button doesn’t do what I expect it to do.

So, all that being said, you can keep the back button disabled and have your own in-app buttons to handle this, but the best practices are to have the back button enabled.
[import]uid: 92150 topic_id: 36179 reply_id: 143731[/import]

#4

We’ve got a new version ready that takes advantage of it, just need to fix a couple other things first :slight_smile: [import]uid: 119420 topic_id: 36179 reply_id: 143738[/import]

#5

We’ve left the Back button on screen in Forever Lost for both Google Play and Amazon and both are fine so far. [import]uid: 119420 topic_id: 36179 reply_id: 143700[/import]

#6

Keep in mind that the Google quality suggestions are merely suggestions to help maintain the look and feel across all apps on an Android device. Since Android devices have a dedicated back button, it is wise to be a good steward of the system and maintain its usability and to not disable it (or in Corona’s case, make it usable). If you keep the back button disabled, you will have your fair share of users that complain about it and to be honest with you, as an Android user, it is frustrating when the back button doesn’t do what I expect it to do.

So, all that being said, you can keep the back button disabled and have your own in-app buttons to handle this, but the best practices are to have the back button enabled.
[import]uid: 92150 topic_id: 36179 reply_id: 143731[/import]

#7

Hey quick question.

Does anyone know of any way you can test the android back button in the simulator? [import]uid: 77199 topic_id: 36179 reply_id: 144570[/import]

#8

We’ve got a new version ready that takes advantage of it, just need to fix a couple other things first :slight_smile: [import]uid: 119420 topic_id: 36179 reply_id: 143738[/import]

#9

Hey quick question.

Does anyone know of any way you can test the android back button in the simulator? [import]uid: 77199 topic_id: 36179 reply_id: 144570[/import]

#10

We’ve left the Back button on screen in Forever Lost for both Google Play and Amazon and both are fine so far. [import]uid: 119420 topic_id: 36179 reply_id: 143700[/import]

#11

Keep in mind that the Google quality suggestions are merely suggestions to help maintain the look and feel across all apps on an Android device. Since Android devices have a dedicated back button, it is wise to be a good steward of the system and maintain its usability and to not disable it (or in Corona’s case, make it usable). If you keep the back button disabled, you will have your fair share of users that complain about it and to be honest with you, as an Android user, it is frustrating when the back button doesn’t do what I expect it to do.

So, all that being said, you can keep the back button disabled and have your own in-app buttons to handle this, but the best practices are to have the back button enabled.
[import]uid: 92150 topic_id: 36179 reply_id: 143731[/import]

#12

We’ve got a new version ready that takes advantage of it, just need to fix a couple other things first :slight_smile: [import]uid: 119420 topic_id: 36179 reply_id: 143738[/import]

#13

Hey quick question.

Does anyone know of any way you can test the android back button in the simulator? [import]uid: 77199 topic_id: 36179 reply_id: 144570[/import]

#14

We’ve left the Back button on screen in Forever Lost for both Google Play and Amazon and both are fine so far. [import]uid: 119420 topic_id: 36179 reply_id: 143700[/import]

#15

Keep in mind that the Google quality suggestions are merely suggestions to help maintain the look and feel across all apps on an Android device. Since Android devices have a dedicated back button, it is wise to be a good steward of the system and maintain its usability and to not disable it (or in Corona’s case, make it usable). If you keep the back button disabled, you will have your fair share of users that complain about it and to be honest with you, as an Android user, it is frustrating when the back button doesn’t do what I expect it to do.

So, all that being said, you can keep the back button disabled and have your own in-app buttons to handle this, but the best practices are to have the back button enabled.
[import]uid: 92150 topic_id: 36179 reply_id: 143731[/import]

#16

We’ve got a new version ready that takes advantage of it, just need to fix a couple other things first :slight_smile: [import]uid: 119420 topic_id: 36179 reply_id: 143738[/import]

#17

Hey quick question.

Does anyone know of any way you can test the android back button in the simulator? [import]uid: 77199 topic_id: 36179 reply_id: 144570[/import]