Hey @Hope , thanks for reaching out - the questions you pose are legitimate, let me try and address them one by one.
This is already implemented in KeyOS 1.3.0, which we should be wrapping up this week. Let me give you a quick heads up of what’s coming:
-
The new “Home” screen for the vault will now have two buttons, “Import” and “New”.
-
Import will allow you to manually import external seed words, passwords, or scan seed words or nsecs (if you use nostr)
-
“New” will generate derived stuff from your master seed - including Passwords! This will also be a new addition in KeyOS1.3.0
-
We will use BIP85 for password generation, using BASE85, which provides more entropy per character than BASE64 (defaulted to by other wallets in the space). We will default to a length of 21, but both the length and the Index will be adjustable in the Advanced Settings, and the Password filed here will be read only (for obvious reasons, but worth pointing out)
You can currently add a Password manually if you need freeform text input, but I hear you that it is not the most comfortable one for long texts or lists (we added scrolling for text fields in 1.3.0 as well). A standalone notes app is already in the backlog (SFT-2433), but is regrettably not ready for the upcoming version. We have been prioritizing the readiness of the SDK so anyone could build apps for Passport Prime (see our documentation page for developers), hoping this will yield in a wider app variety for our users. Someone might even vibecode a secure notes app before we ship a first party app for that too! Hope not, but this is an open platform where anyone can build anything, so who knows haha.
This is in fact in our short term plans! I can’t commit to any deadlines, but you should see us announcing this in a not too distant future.
Regrettably, no. This was a tough business decision for us, but it was the one that made the most sense. You can read the announcement we made here: From QR Air-Gapping to QuantumLink: What Comes Next – Foundation Blog
Believe it or not, this is one of the reasons why we were delayed. While it’s true that we now have even non technical team members writing production code and applying fixes (this is why the KeySO 1.3.0 and Envoy 2.3.0 release notes will be so bulky), these AI tools also helped us identify a ton of underlying problems of varying urgency that needed patching and absorbed a lot of technical work time that delayed the release of both KeyOS 1.3.0 and Envoy 2.3.0. So instead of moving faster with the flashy new apps and features, we spent a lot of time making sure the underlying software is rock solid and stable.
Thank you! We are a relatively small team but are aiming high, so please bear with us while we smooth out all the rough edges =)