What were the issues you had with the Android application?
Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users.
Thanks!
Kyle
AgileBits
Overall seems to be a low effort app. Not worth the money I paid for it. Considering switching to an alternative which is more Android friendly despite having laid almost a hundred bucks for ios and Mac apps.
We really do want everyone to love our Android application. Personally, I feel they've made great strides given the time they've had. It's just a matter of time and our Android application will be right up there with our iOS application. We have some super smart people working on it and they're very passionate about what they do. I can't help but be inspired by a group of people who fight tooth and nail to catch up to a product that's much older (our iOS application).
I showed your comment to our Android developers so they've seen what you're requesting :)
Thanks!
Kyle
AgileBits
Our iOS application also shares a great deal of underpinnings with Mac. That means when our Mac team implements something super great our iOS team gets some of that grunt work for free. Then it becomes an interface deal in many cases which may not be easy at all but at least some of the work was done.
The Android team, well, they have to implement everything themselves and it's simply going to take time. Combine this with UI changes and stuff that mean we have to rewrite existing things to match up with that and it just becomes very overwhelming sometimes. I work on our iOS application and it's incredible the amount of stuff you can do in a short period of time because groundwork has been laid for years. I don't envy our Android developers because they have none of that to work with. I'm sure it's both overwhelming and exhilarating for them.
I guess that's a long answer but really, it's simply going to take some time for our Android developers to catch up. I know it's tough as a user to see one so far ahead of the other but I hope the above information puts some of it into perspective. They'll get there :)
Thanks!
Kyle
AgileBits
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.
I'd also love to see it do something like Facebook Messenger where it provides a button on top of whatever active app is currently running.
https://blog.agilebits.com/2015/05/28/fingerprint-unlock-com...
That's fairly old, from May, but it does give a bit of a tease if you're familiar with Android and the look and feel of things.
Kyle
AgileBits
Imagine if ssh private keys could be stored inside 1Password. It would become a ssh-agent replacement.
No real reason to leave ssh private keys scattered on different user directories anymore.