|
|
|
|
|
|
by tb303
3885 days ago
|
|
|
Hi Kyle, thank you for participating in this conversation. I am sure everyone here appreciates it. It is true that as an android dev one has to implement many things themselves. It's an unpleasant part of developing for Android that Google does very little to address. The simplest approach you could take would be to copy and implement the design patterns presented in Google's material design guidelines. Yes, it is unfortunate they are guidelines and not SDK. However, there are enough patterns to provide a superior experience to the jumbled mess of an application that it is right now. https://www.google.com/design/spec/material-design/introduct... - Use the FAB for "search" since it is the most frequent user action.
- Use the navigation drawer https://www.google.com/design/spec/patterns/navigation-drawe... This is just a 1 minute recommendation and of course open to argument. However, simply redoing the app in a generic style adhering to these guidelines would be a drastic improvement. Thank you in advance for doing an android app in the first place. |
|
|
A design overhaul is definitely in the works. I think, but can't confirm, that it will alleviate some of your concerns. I don't have a time frame for it but given we're saying that the 1Password for Teams beta is going to last about 3 months we'd like to have Android ready to go for that launch as well. They're hard at work on making it happen now.
Thanks for the feedback! We're always happy to receive it and pass it along. It's how we drive development in a lot of cases. Teams came about from requests from our users. Multiple vaults came about from requests from our users. A lot of it is driven by user feedback so don't be afraid to send it in. No promises everything will be done but the more people that say they want a particular feature the higher that gets bumped up the priority list.
Kyle
AgileBits