Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Bottom Floating Buttons #4

Open
DaveFerBear opened this issue Apr 16, 2016 · 4 comments
Open

Bottom Floating Buttons #4

DaveFerBear opened this issue Apr 16, 2016 · 4 comments

Comments

@DaveFerBear
Copy link
Contributor

@peacefulhuman
Copy link
Collaborator

I implemented SVG icons for satellite view buttons - check my pull request to see if I did it correctly. Also, functionality for that button works, but I don't know if I implemented it correctly

@peacefulhuman
Copy link
Collaborator

Dave and Randy - I did some research on floating action buttons; google suggests using only one per screen for the primary action a user would need. Would you guys recommend zooming to current location or getting directions to a pin? Also, where should we implement satellite views and all other necessary features? Should we do a bottom action bar since there is a search toolbar on the top?

@DaveFerBear
Copy link
Contributor Author

Sorry for not being able to commit much time recently - just got back to
school and things have been hectic.

My personal preference is to use the expandable action button
https://raw.githubusercontent.com/futuresimple/android-floating-action-button/master/screenshots/menu.gif.
This is done in several apps (including one of facebooks) and seems to
adhere to material design. We also have the options menu, inside of which
we can put the satellite view/other options.

I'd stay away from a bottom action bar. Considering this is a maps
application, I think a large main screen should be the priority.

On Wed, May 4, 2016 at 7:54 PM, Craig Morrison notifications@github.com
wrote:

Dave and Randy - I did some research on floating action buttons; google
suggests using only one per screen for the primary action a user would
need. Would you guys recommend zooming to current location or getting
directions to a pin? Also, where should we implement satellite views and
all other necessary features? Should we do a bottom action bar since there
is a search toolbar on the top?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#4 (comment)

@peacefulhuman
Copy link
Collaborator

Agree with the bottom action bar. what actions would you use in the expanding action button? directions and current location? should we leave layers in the options menu? what are your thoughts on the most intuitive way to implement that?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants