Skip to content
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.

UX - spec Android back button #1545

Closed
xmatthewx opened this issue Apr 23, 2015 · 4 comments
Closed

UX - spec Android back button #1545

xmatthewx opened this issue Apr 23, 2015 · 4 comments
Assignees
Labels
Milestone

Comments

@xmatthewx
Copy link
Contributor

Define how system back button should behave.

Here's a first attempt:

  • dismiss dialogs
  • close keyboard
  • back to prior tab (make/discover)
  • back to prior view (from user profile, tinker mode, element editor, project settings,...)
  • zoom out from page view to map view
  • zoom in ?? (I vote never)
  • exit a project (with a confirmation??)
  • exit the application only if there's absolutely nothing else to do (I've seen accidental exists intercepted with a prompt, "tap back again to exit app.")
@xmatthewx
Copy link
Contributor Author

cc @flukeout

@flukeout
Copy link
Contributor

Seems like back arrow to zoom out is the most important one - saw lots of going back to Discover view by 'accident'.

Not sure about back to previous tab (between make & discover) - seems like you'd get stuck in a cycle going back and forth? Doesn't seem like the right interaction, is that what you meant?

@xmatthewx
Copy link
Contributor Author

Seems like back arrow to zoom out is the most important one

Agreed. Important and unique.

back to previous tab

I think it would go back to whatever you did before you hit the tab, not add your tab-via-back-button to the queue. I agree it's a bit confusing. We should just follow material design's lead on this one.

@xmatthewx
Copy link
Contributor Author

closing. ready to implement in #1546

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants