Experiment #4 – New interface in 1Password.com’s vault view

I hope you can get the enhanced security to work so it behaves more like the old view with regards to only logging in once in the browser

Icannotturnoffqa I hope so too, but again, the old view worked the same way. It's never been possible to open 1Password in a new tab and still be signed in.

can you add this (Screenshot ⤵︎) that has on the Old Version.

MrNice this may be something we can do in the future. For now, you would just have to add a new field and delete the old one.

There is a link in the browser extension which states "Let us know what you think" and it links me here.

rrrobot ok, but I promise you that's not the browser extension. :) I'm guessing what happened is that you clicked "Edit" or something else that took you from the browser extension to the web app, which is the only place that link appears. So I think we are on the same page, talking about the web app, and my previous post here discusses several performance considerations if you're interested.

Given the state of modern app development, I'm close to 99% certain that the same or extremely similar codebase is being used for the website, mobile app and browser extension. It's the curse of rewrites in the 2020's - There's no "native" apps anymore, which contributes directly to the concern I raised in my comment.

rrrobot we're sharing as much code as possible between the desktop app and the web app. The browser extension is mostly its own thing, although it shares some code with other apps. For more complex tasks it sends you to the desktop app or web app. The mobile apps don't have any web-related code. They share Rust code, but the UI is native (Kotlin for Android, SwiftUI for iOS).

Regardless, we intend for our desktop and mobile apps in particular to be very performant because of their offline cache of data and the fact that you aren't downloading the app every time you use it (like you are with the web app). So the problem you're seeing with the Android app is definitely not expected, and I'll pass it on. If you'd like to follow up on it, I'd recommend making a post in the Android category of the forum.

My personal rough definition of "stable" software is that it should be able to go some nontrivial amount of time (let's say a month or so) without requiring any changes that a typical user would notice. The old web UI has been meeting that criteria for some time now.

d9a I can appreciate this perspective coming from someone who is both content with the old version and participating in this thread.

If I can offer a different perspective, we have over a hundred open issues filed against the old version. Some issues have already been closed solely because they'll be addressed by the new version. The fact that we're not regularly fixing these issues in the old version does, in a sense, make it more stable, but it doesn't make it better, in my opinion. I would rather be actively improving the user experience than leaving it static for the sake of stability.

UI changes (and to an extent, even new features) should, in my view, only be happening once or twice a year max

d9a I'm sorry for your sake that we won't be meeting that expectation. The reason for shipping changes more frequently is to please customers. If your opinion was held by the majority, I'm sure we'd all go back to waterfall workflows. 🤷‍♂️

as I recall from the days of 1Password 8 being released and users asking for a way to keep support for 7 going, a similar proposal was put forth and ultimately not taken up

d9a To be fair, 1Password 7 is still supported. Even the later versions of 1Password 6 are still supported.

It's a bit harder to keep serving two versions of a web app long term, though.

I make very heavy use of private browsing windows ... I much prefer keeping the persistence of sensitive data on my machine to an absolute minimum.

d9a this explains a lot. 😅 Sadly, I don't think you're going to be happy with the long-term direction of the web app in this case. Many users want the web app to mirror the functionality of the desktop including advanced full-content search, suggestions based on other items, and so on. To make those features possible, we have to give the web app an offline database and download all items. This will mean that the first load will take longer than the old version, but subsequent uses will be snappy because the data will already be there. This is how the browser extension, desktop, and mobile apps already work. But if you're in a private browsing window, you won't get any of that benefit. However! ⬇️

I realize this is incredibly out of scope for this particular project/discussion, but adding the ability to create/edit saved items directly within the browser extension itself sounds like it would perfectly address the bulk of my issues.

d9a we're actually looking at doing this! I agree it will probably make your life a lot easier because you will get the benefits of a local database, and you won't have to go anywhere for simple edits.

It is great - except I cannot work out how to add a logo to my entries. This used to be easy.

ETHELDOG yes, this is something we've removed for now. It's still possible to set custom icons in the desktop apps, though, and they will be shown in the web app. It will likely come back in a future version, but we don't consider it one of our most critical features.

cc: wooderm

Actually the Home page is a bit irrelevant (for me as a non-admin user), and I'd like to go straight to /app after the login?

SvendK we're considering making this change for non-admin users. Thanks for letting us know you'd like it.

Regarding performance, my previous post and this one go into that a bit.

QtWebkit-based browser, the beta "copy" button does not work, and it is no longer possible to select via mouse or keyboard a revealed password text for copy/paste.

legendwaffles we'll look into the broken copy button, sorry about that. I've not heard of that browser before. I hear you on the text selection. A workaround for now is to edit the item and select the text in the text field.