Hi andybak, I work on the Sandstorm team and it seems pretty clear that you're not an idiot.
I'll see if there's something we can do to make this essential UI element more discoverable.
To some extent, it's a matter of learning about Sandstorm -- Sandstorm's role in the web app ecosystem is basically to add sharing & access control, so maybe everyone has to learn this. But hopefully we can help people figure it out more easily.
It did take me a while to figure out how to delete "grains" (I would've thought from the list of grains, instead I had to open one and click the delete button).
Also, I don't quite understand why I started out with five wekan grains from the get-go? Maybe a bug.
Also, I think first-time users might need some more hints (like unintrusive first-run popups or something) that the top bar is the Sandstorm stuff, while the rest is the app itself. I don't know what would be the best way, it seems quite challenging to design something like this :-)
What does the key icon do? (No hover text.)
Maybe "Share" should say "Share app"? (So I don't get confused into thinking it means "share this one wekan note" or "share this particular song from groovebasin".)
Being able to delete and rename grains and stuff from the list is something I've been nudging them about. :)
Yesterday in particular Oasis was under heavy load from HN, if you clicked on New Wekan a bunch of times before it did it, it might have made a bunch. Usually it's near instant so this sort of thing doesn't happen.
paulproteus will love all your feedback. He likes feedback. :D
Your assumptions seem pretty fair to me. We have to do a better job of teaching people that the topbar contains grain-related functionality -- specifically, functionality that is mediated by Sandstorm, like access control.
FWIW, the first version of Sandstorm let you copy/paste the URL from the address bar, and I'm definitely a fan of that model. But, a lot of people are uncomfortable with that. It "feels" insecure. So we're trying to find a happy middle ground, where the people who like URL sharing can use it, and those that don't can avoid it. It will take some experimentation to get right.
I kinda miss the copy/paste link for certain types of documents. But yeah, sometimes the assurance is nice that absolutely no matter what you need my account to log into something, even if I happen to have a URL in a screenshot or something like that.
I can't figure out how to make etherpads public by default.
Which rather kills the primary use-case of etherpads for me (frictionless collaborative documents - non-guessable urls are the only authentication)