is to give the user the choice to have local encryption setup work in two different modes (using a master password to lock all notes, OR use a password for each note), not both together.
What I mean is only choose one for your proposal because the project is already big and you should not increase the scope further
Notebook password does not bulk encrypt/decrypt notes, It acts as an access gate: once the notebook is unlocked, the user can see and open its notes.
Ok I didn’t realise that. That is a problem, because there is a lot more complexity involved with hiding contained encrypted notes and notebooks (because notebooks can be nested in an encrypted notebook too) across all areas, managing moving notes / notebooks between encrypted / not encrypted notebooks. Also if you are hiding notes within encrypted notebooks it gives the impression that everything inside is encrypted (including note and notebook titles), so you then should really add encrypted titles, which adds more layers of complexity.
I recommended to other candidates to not implement real encrypted notebooks because it increases the scope of the project too much.