(Privacy related) New Page: give the user the opportunity to choose the target Space
What could be better?
I usually create a new Page by middle-clicking on the "New object" button on top of the Favorites in the side menu.
After that, I type my text, or paste web snippet etc.
The problem happens when I then want to add the desired Collection to the Page:
In that moment I suddenly realize that I was in the wrong Space. :-(
-- This has already multiple times happen to me. :-(
It's cumbersome manual work to correct that.
The privacy Problem with that:
When AnyTwo later gets a similar history function as Anytype has: everything becomes recorded in the history and it's hard (or partially impossible) to delete stuff traceless.
Imagine the user has already put a bunch of highly sensitive data into the new Page when he finally realizes that he was in the wrong Space!
He wants to get this stuff immediately out from here without leaving any traces.
Request:
- A raw new Page should become created only in the RAM memory, until the user chooses the Collection(s) he want to attach to the Page.
- If the user realizes (in the moment of choosing the Collections) that he was in the wrong Space (he sees that, because there appear unexpected Collections in the list), he should have the opportunity to choose the wanted target Space.
-- Only after adding at least one Collection, the Page should become physically created in that target Space.
Before that moment, everything has happen only in the RAM memory.
And no traces in the history!
Concrete suggestion for the UI:
When the user clicks the "+" button in the Page's header, to add the wanted Collection(s), there should be a large button on top of the drop down list that shows the name of the actual target Space. If he clicks this button, another drop down list opens, that lets him choose one of the other available Spaces.
4 Comments
Sign in to comment
·about 3 hours agoIt is definitely a problem: too easy for a user to accidentally create an object in the wrong space. However I'm not sure the prevention trigger should be tied to assigning Collections because many users may never assign one. Imagine a user creates a quick journal/note entry and usually triages them later (assigns collections), this can end up living in the wrong space for a long time until discovered. While having a notification toast after creation is helpful, it won't prevent the error.
What I can think of:
- Create button has name of space. E.g. Create in Anytwo Assembly
- Force user to confirm space before object gets created in shared spaces. E.g. Are you sure you want to create this in Anytwo Assembly?
- User sets default space and must manually change it each time (no contextual space is set based on current view).
- Draft objects (not yet created) should be temporarily be held in a holding space.
Good ideas, but I see then new problems.
Actually, if you create the new Page by right clicking the New Object" button, there is no button (it appears only if you left click that button, but I don't like that left-click way and its behavior).
If the devs add such a button also for the middle-click generation, there is a conflict with your example:
Imagine the user creates a bunch of new Pages for triaging them later.
-- Where do the Pages "live" as long as the new "Create in XY Space" button wasn't pressed?
It may happen, that he ends up with a dozen new and unfinished Pages that live in limbo. What when he closes the App in that situation?
-- Admittedly, I've also not thought about this scenario when I wrote my request.
Actually I like the workflow of the middle-click on "New object" very much!. It's so nicely quick and easy!
But we need a solution for the topic of this request.
Suggestion:
After middle-clicking on "New object", when the new Page appears (but lives in the RAM for the moment), a very eye-catching red warning message with two buttons appears as a single line direct over the Title of the new Page.
The user can confirm what it says, or choose a different Space.
Only after confirming or choosing the target Space, the Page becomes physically created there.
·about 3 hours agoThanks for flagging this — the privacy angle around unintended Space context and history traces is a real concern.
To make sure we scope this right: when you middle-click "New object" today, does the page get created immediately in whatever Space you're currently viewing, or does it stay unsaved until you add a Collection? And when you realize you're in the wrong Space, what's the actual friction — is it that you have to delete the page and start over, or move it post-hoc, or both?
Also, for the UI flow you're picturing: when the Collection picker opens and you switch Spaces there, should the page stay in RAM until a Collection is actually added, or would you want the Space switch to save the page to the new Space first?
What I don't understand is the framing of this issue.
1. Currently, you're already able to choose the target space for your new objects in the top left corner? I'm not sure why this should be applied again to the page header.
2. When it comes to leaving traces, I can check with the developers, but I don't think any object traces are left in any spaces until after the object is created. That is, you can flip between different spaces while your object is in 'limbo'.
3. We haven't properly implemented the UX/UI for this create button, but there is no ability to add collections yet. What are you seeing?