1password 8 is a step back

I loved 1Password since it was available for Nokia and blackberry and I still love it today but I have to point out that 1passsord 8 UX is worst than 1Password 7. There are not all capabilities that we found on 1Password 7, many call to action are more confusing than previous version and in some cases they take more gestures (tap or other one) to reach the same function than previous one. Finally I think perhaps someone wanted to force the UI refresh of an already almost perfect UX and it is a shame. I’m always enthusiastic when new version of App or product comes out but in this case If I could do it I would to rollback to 1Password 7.

@RobTX I guess that the person was used to pressing the field once and it brought up the menu to either reveal, copy, or show in large type. I personally am used to the small menu popping up and I do believe that there should be an option to change it.

Sorry if this didn’t make too much sense, my English is pretty bad as it isn’t my first language,

I'm afraid it's back to v7 for me until PIN unlock and sorting Favourites alphabetically return, quite a step backward for an app that I've considered a constant.

Indeed a step back! I'm going back to v7, or looking elsewhere.

Looking to dump 1password for something that people who develop it actually use it--obviously NOT the delveopers of 8...

Really missing the feature in 1P7 where it would prompt me from the iOS keyboard suggestions area to input a password. Having to go into the safari extensions and then search for the correct one, because it isn't automatically suggested as it was before, is so frustrating and time-consuming. Also when in an app on my iPhone it no longer suggests the correct password. Just tried logging in to the Vudu app and instead of the correct suggestion where I just need to tap it, I have to leave the Vudu app, open 1Password, search for Vudu, copy the password and then go back to the app. Seriously bad design. Maybe someone knows of a setting I missed turning on but come on devs. This is so bad I'm looking for a different product to use now that has these features.

It’s kind of annoying too how the support staff has basically been AWOL from the iOS sub-forum since Thursday. After having what’s arguably the most important iOS app release in the company’s history last Monday, you’d think their management would want to ensure plenty of coverage for at least the next few weeks.

It is so sad to watch a previously great app being badly designed

I agree with everything you just said.

This is the opposite of a customer-centric release. I suspect (based entirely on what we're seeing with this version -- I don't have any inside knowledge) is that this version reflects internal chaos at the company, rather than it being something customers want.

Well the team doesn’t need a break. I respect developer work. I have no idea how much work they had to do this past two years for the rebuild. But the product manager / heading team / CEO are in fault in my opinion . They probably gave developer a calendar that didn’t allow them to launch a complete app on the scheduled date, they probably fixed the launch date first and didn’t took account about the bugs that need to be fixed before launch. Never mind the clients if investors are happy that the launch date was respected…
The unify of the code is an agilebits problem not their client problem. We don’t care how the app is written, the only thing we care is the app to stay at least as usable it was before, at least as well designed, optionally faster, lighter. (Spoiler alert : for around the same features the app is 25% larger).

Good luck for agilebits développera to fix unplanned features that where in the app since years but not planned by head of AgileBits. It is so sad to watch a previously great app being badly designed :/

why should we be giving them a break for such an absurd decision?

Having been a software developer for many years, I have sympathy for receiving bad feedback from end users.

However... I think the responsibility for this half-baked version lies squarely on the product managers. Surely if they'd delivered this version to a wide field of beta testers they would have received the same feedback we are giving them now. And with that feedback, they shouldn't have released a version that is so poorly received.

So I don't see much reason for "giving them a break". We are paying customers who should expect to have a usable product that's been well-designed, thoroughly tested, and reflects our real-world usage.