Live data from Hacker News

Introducing 1Password for Teams

blog.agilebits.com

121–130 of 151 posts

Re: Introducing 1Password for Teams

#121
post #39

Earlier quoted context omitted.

Not really a threat -- if they don't provide Linux support, then they know and accept already that people running Linux won't buy or recommend it.

It's more of a threat to us than you describe. If a potential team of N people have k members who need a Linux client, then that might cost us N customers, not just k.

Yes. We are a team of 3 and one of us uses Linux. What is missing when using the web app? Is there a feature comparison I can look at?

Re: Introducing 1Password for Teams

#123
post #43
post #25

Interesting - lack of active directory integration, and lack of on-prem solution is disappointing though. Edit: since someone is apparently upset over my comment - those two features are absolutely mandatory in almost all corporate environments. If you have a comment to the contrary, feel free to share it. Don't just downvote my comment because you don't personally need the features.

Really don't want to see anyone get down voted here for having an opinion. Different opinions are what drive conversation, so, I won't ignore your concerns here. I'm not super big on the terminology, but I assume on-prem is on-premise, meaning you'd like to self-host. If I have that correct then unfortunately I can't promise anything here. I will most definitely pass this along to our team though so that they know th…

We already use something like this product but with a vastly worse UI / UX from CyberArk. That's the kind of feature set you'll need to sell to companies that aren't already Mac users or larger than 1000 employees on a consistent basis. Unfortunately, you'll probably need to hire 5 new people per F100 customer at a minimum but if that sort of growth is what you want I assure you it's mandatory.

Please try, please help make the enterprise security software market suck less :(

Re: Introducing 1Password for Teams

#124
post #39

Earlier quoted context omitted.

Not really a threat -- if they don't provide Linux support, then they know and accept already that people running Linux won't buy or recommend it.

It's more of a threat to us than you describe. If a potential team of N people have k members who need a Linux client, then that might cost us N customers, not just k.

Yes, but that is still something you evaluated before not releasing a Linux client (opportunity cost, etc).

Re: Introducing 1Password for Teams

#125
post #69

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…

interesting post!

Re: Introducing 1Password for Teams

#126
Hi! I can tell you our experience at company I work. We were looking for any tool to make simple share "but not deliver control of password" because we wanted to show customers that "we take care" about their passwords.

Finally started use ZOHO Vault. It gave us why to create/manage/share to our developers "secrets" (passwords, PIN/PUK, Visa pin, etc) in webapp and mobile app. Now it is part of our "wellcome kit" to new worker. If you are alone you can use for free, and use to your personal or professional secrets.(Example code that was created to my profile by ZOHO Vault is like "x3Aq-JTyKg" -is not this! of course!)

Usually with any customer that see how we work... they copy "work method": if any other recommend us other better... of course we will test too to compare!! Cheers!

Re: Introducing 1Password for Teams

#127
post #105
post #91

Earlier quoted context omitted.

Sorry to hear that you're unhappy with it. I think you'll be happy with the progress when you see the next updates. There's some work being done to modernize the interface and some of your list will be tackled by that. I would encourage you to take a look at my other comment in this particular tree of comments about Android. It might offer some perspective, not that it's an excuse but it explains things a bit more an…

Thanks for the detailed reply. I do like 1Pw - it is so very well thought out on mac and ios that I expected something similar on the android side too. Good to see it is being worked on and will hopefully become a first class app alongside your other apps.

My Pleasure. I certainly hope it gets there sooner rather than later but it will get there :)

Kyle

AgileBits

Re: Introducing 1Password for Teams

#128
post #119
post #90

Earlier quoted context omitted.

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 gr…

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 un…

Happy to participate. I read Hacker News regularly myself so getting a chance to jump in and be involved is always fun :)

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

Re: Introducing 1Password for Teams

#129

Earlier quoted context omitted.

I use secure notes for that, personally.

I was thinking tighter integration than that. 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.

I actually had this idea back when I first started at AgileBits and had to really start maintaining ssh keys for work purposes. Prior to that it was mostly just side projects and my own personal stuff.

Maybe we'll have to kick this one in the pants and see what we can do. No promises of course but I'll be passing this along again since I have a personal investment in that idea :)

Kyle

AgileBits

Re: Introducing 1Password for Teams

#130
post #28

I had hoped AgileBits would step up their Windows offerings. I've recently bought the "real Windows application", since the Universal App doesn't allow to enter new logins (really?), only view existing ones. Unfortunately, KeePass was much more useful with its Alt-A shortcut. In 1Password I need to manually copy login data from the application, since I'm using Edge and there's obviously no plugin, yet (Edge's fault).…

I rely upon 1pw on iOS and Mac, so I was really happy with the Windows Store version of 1pw. It is billed as a work-in-progress, but on my terribly limited HP Stream 7 tablet (Windows 10), 1Password is no less stable than any of the other apps. I suspected that Windows development has been delayed by the need to support iOS MDM (mobile device management) for businesses. And here we are! I also suspect that Microsoft…

We actually have different teams working on each platform, mostly anyway (our iOS and Mac teams have people who rotate between the two in addition to having dedicated members for each). The drop in noticeable forward momentum (at least publicly) on all of our projects over the last several months has been due to getting Teams implemented, everything seems calm on the surface but underneath there's a lot happening.

Our Windows developers will get their day to shine soon enough as well and we hope you'll enjoy the work they've done. :)

Kyle

AgileBits

Post reply on HN