Live data from Hacker News

UX Issues with Notion

telegra.ph

131–140 of 160 posts

Re: UX Issues with Notion

#131
post #93

> This one is a real shame. I still can't believe it. If you select any text block, you can't navigate using Page Up and Page Down keys. So? That's probably used by less than 5% of people anyway. Seeing regular users most would just use the mouse...

5% is a lot! But even if it wasn't, it is not a proper justification for breaking basic things.

Re: UX Issues with Notion

#132
I'd like to say thank you for Notion team to support proper work with IME (at least for Japanese, Win/Linux/Android) from at least 1.5 years ago.

SPA apps made by English speaker tend to have broken input field (Even twitter's tweet field) but Notion isn't even though it has complex features.

Re: UX Issues with Notion

#133
post #116

Earlier quoted context omitted.

I work in improving performance at a big tech company. It can be like dragging feet to get executives, managers and developers to care about improving performance because incentives are misaligned and it's frankly a chore compared to the million other things you have to be doing. It's also significantly harder to show the business metric improvement that comes from performance improvements than it does from simple A/…

Fair enough; thanks for taking the time to chat about this. I'm not sure I agree, but I appreciate your perspective and experience. For all that you've said, I still strongly suspect that a standalone rust / swift compiler designed for speed above all else could achieve many times the performance of the current LLVM based designs. The resulting binaries might need to lean heavily on dynamic dispatch over monomorphiza…

AFAIK swift and rust were actually initially design and made by one engineer for a couple of years before anyone else worked on it, and were led for years by those specific engineers. Chris Lattner for swift and Graydon Hoare for rust.

Re: UX Issues with Notion

#134
post #22

(Disclaimer: I work on Notion) To me, the most interesting feedback here is that seamless-editable-by-default is a negative for this user, and as a work-around, this organization locks/unlocks every page. This is surprising to me because I find content locks and editing friction very annoying. For example I used Quip for many years, which locks any block currently being edited by someone else, which can be quite frus…

We used it for live discussion in college lasses and our text being edited out by another person was very annoying

Re: UX Issues with Notion

#135
post #48

Earlier quoted context omitted.

This is good feedback! Thank you.

Do you really need to "lock" it as in OP? When you share you get the option to choose whether the person being shared can edit, comment or duplicate. If you disallow sharee editing, you can still edit your document.

I want some people to edit some parts only.

Re: UX Issues with Notion

#136
post #90
post #85

Earlier quoted context omitted.

Notion is a not a good tool to create a knowledge base, the same way Google drive is a not a good tool to create a knowledge base. If you think a bit more, notion is more or less a Google drive with smileys. Which is not a critic.

What have you found is a good tool to create a knowledge base, at a small to medium sized company?

Confluence, the product is very far from perfect, but still does the job well. I'm working on building the perfect knowledge base tool, but that would be for big companies

Re: UX Issues with Notion

#137

Earlier quoted context omitted.

People value what they are used to. I write code in an editor every day, and I use my editor somewhat deeply, using plenty of shortcuts to manipulate text quickly. When editing text in Notion it feels unproductive because I'm used to a code editor. Someone with a different background may have no problem with the text editing, because they're not used to anything substantially different, but may have an issue with ano…

Totally fair, but I wouldn’t expect Notion to work exactly like a code editor. What I do like is they stick to the universal language of “working apps”. So slash commands, markdown support, code snippets, dark mode, keyboard shortcuts, rich embeds, etc. Those are the bare minimum for me, but I don’t think any of their competitors actually have all of these features which is one of the reasons Notion is a good fit for…

You're right about not being a code editor, but I guess by that I mean that I expect regular text navigation to work flawlessly. Things like alt+arrow keys/holding shift for selections, cmd+up/down for start and end, and the rest. These combinations are often composable for selection, so cmd+shift+up should select to the beginning of the document. These work in my text editor, text fields in every app, Notes, TextEdit, etc, but they often fail in subtle ways in Notion.

Re: UX Issues with Notion

#138
post #22

(Disclaimer: I work on Notion) To me, the most interesting feedback here is that seamless-editable-by-default is a negative for this user, and as a work-around, this organization locks/unlocks every page. This is surprising to me because I find content locks and editing friction very annoying. For example I used Quip for many years, which locks any block currently being edited by someone else, which can be quite frus…

> Likewise, wouldn’t you be baffled if you needed to click a “Start Editing” button in Word

That's absolutely the default behaviour for Word when opening a Doc sent from somebody else ("enable editing"), and it does make sense like this.

Re: UX Issues with Notion

#139
post #93

> This one is a real shame. I still can't believe it. If you select any text block, you can't navigate using Page Up and Page Down keys. So? That's probably used by less than 5% of people anyway. Seeing regular users most would just use the mouse...

No gain for 95% and a loss for 5% seems like an even worse outcome of changing default behaviour

Re: UX Issues with Notion

#140
post #22

(Disclaimer: I work on Notion) To me, the most interesting feedback here is that seamless-editable-by-default is a negative for this user, and as a work-around, this organization locks/unlocks every page. This is surprising to me because I find content locks and editing friction very annoying. For example I used Quip for many years, which locks any block currently being edited by someone else, which can be quite frus…

I’m sure it’s been discussed internally but would a rich API for third-party developers to build alternative clients, integrations or plugins ease some of these issues? I can see situations where a simple plugin could help companies to paper over parts of Notion that don’t perfectly fit their workflows. If a company prefers a read heavy workflow they can modify some behaviour.
Post reply on HN