6 ms·

Maybe I'll be the only 1Password fanboy in here. I use 1pw personally and LastPass for work (shared between team of a dozen or so technicians). To compare the

by jmuguy 11y ago

Maybe I'll be the only 1Password fanboy in here. I use 1pw personally and LastPass for work (shared between team of a dozen or so technicians). To compare the two - 1pw is basically one of my favorite programs. LastPass is um... adequate? We have a lot of items in our LastPass vault and anytime we search it, add or change an item there is a 5-10 second lag. This according to LastPass support is unavoidable. Something to do with each item being individually encrypted/decrypted each time. In anycase if 1Password for Teams is half as good 1Password I assume it will blow LastPass out of the water. And my experience with the Agilebits team gives me confidence that they'll work on actually improving the product instead of just looking for an exit.

leftnode 11y ago
1PW is without a doubt one of the nicest iOS and Mac programs I have ever used. It is gorgeous and just works. Well worth however much I spent on it.
AGRob 11y ago
Thanks for the kind words! We don't plan to disappoint. :) Rob AgileBits
Shebanator 11y ago
Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.
- AGKyle 11y ago
  Hi! 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
  - 77ko 11y ago
    I recently switched to Android from ios and literally everything on 1password Android is vastly inferior to the ios version. It's like the ios app is developed by a crack team of experts while the Android app is developed by a part time intern working for free.
    - AGKyle 11y ago
      With respect to our Android developers they have an uphill climb to catch up to iOS. Our iOS application has been in development for something like 4 years now, and several years before that as a previous incarnation (version 4 was a complete rewrite). 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
      - tb303 11y 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/introduction.html 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-drawer.html 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.
- keeper 11y ago
  Hi - have you tried Keeper? We have 9M users - and as a benefit for someone like you we're platform-wide with native apps across all OS's, devices and browsers - our users love our Android experience. www.keepersecurity.com
dazzla 11y ago
Keeper Security encrypts records with individual keys. Doesn't have the 5/10 sec lag.
joseperezSZ 11y ago
interesting post!

by jmuguy 11y ago

leftnode 11y ago

1PW is without a doubt one of the nicest iOS and Mac programs I have ever used. It is gorgeous and just works. Well worth however much I spent on it.

AGRob 11y ago

Thanks for the kind words! We don't plan to disappoint. :) Rob AgileBits

Shebanator 11y ago

Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.

AGKyle 11y ago
Hi! 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
- 77ko 11y ago
  I recently switched to Android from ios and literally everything on 1password Android is vastly inferior to the ios version. It's like the ios app is developed by a crack team of experts while the Android app is developed by a part time intern working for free.
  - AGKyle 11y ago
    With respect to our Android developers they have an uphill climb to catch up to iOS. Our iOS application has been in development for something like 4 years now, and several years before that as a previous incarnation (version 4 was a complete rewrite). 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
    - tb303 11y 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/introduction.html 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-drawer.html 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.
keeper 11y ago
Hi - have you tried Keeper? We have 9M users - and as a benefit for someone like you we're platform-wide with native apps across all OS's, devices and browsers - our users love our Android experience. www.keepersecurity.com

dazzla 11y ago

Keeper Security encrypts records with individual keys. Doesn't have the 5/10 sec lag.

joseperezSZ 11y ago

interesting post!