UX Issues with Notion
111–120 of 160 posts
Re: UX Issues with Notion
#112Just as a counter, I use Notion personally, for my side projects and at my day job. I haven’t run into any of the same issues the author has had. Most of the comments seem to be rather small compared to the overall use and productivity gains that something like Notion offers.
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…
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 me (and most people that try it).
Re: UX Issues with Notion
#113I see comments in this HN thread about word processors and agile development and I'm thinking... isn't Notion a tool to take notes?
Some of the things people are saying here that they can’t stand about Notion are some of the things that I like the most about it, and some of the improvements people are suggesting here are things that would make me abandon Notion if they changed it to be in line with what they suggest, and I think a lot of that is from difference in expected use case (I use it as a personal knowledge base)
It is definitely a weakness of their product.
Re: UX Issues with Notion
#114Re: UX Issues with Notion
#115Re: UX Issues with Notion
#116Earlier quoted context omitted.
It's an economic tradeoff. Engineers are expensive and businesses choose what is most productive for them to what customers respond to. Also performance work is not fun and more work than new features. Performance bugs are harder to detect and quantify than normal crash bugs and such because they are statistical ranges, not binary on off states. Performance is taken into account when it matters for the product, you'l…
> Performance is taken into account when it matters for the product, you'll notice this in games where they do a lot of perf improvement work. I think most development shops chronically underestimate how much application performance matters for sales. Most people will never file bug reports when software is slow. They just "won't like that program for some reason". (Or worse, misattribute the reason they don't like y…
For games, it's not a 'culture', it's because games become very frustrating to play when non-responsive in anything fast paced, and thus will review badly and become 'not fun' and thus will not sell. It's directly connected to sales metrics, which is why management in game companies give space for it, and why CDPR recently offered refunds for a game because of bad perf on the PS4 tier of consoles, which is fairly unprecedented. You'll notice worse performance in slower paced games typically, such as Civ 6.
Also I've worked on trying to improve swift build perf and have worked on large C++ codebases before. The reason why C++ is slow to compile typically is because templates cause an explosion in code generation, everyone uses boost & the stdlib smart pointers & containers, which all template heavily and result in slow build perf and large binary sizes. Swift & rust do that, often implicitly and in an invisible to the programmer way and type inference are the typical reasons why it is slow and they too, create large binaries. When I started running into swift's build problems, I internally said to myself "oh boy, it's C++ again" and if you go to WWDC and talk to Xcode's engineers or swift compiler engineers, they often call swift 'new c++' and other not as nice names. Swift and rust are also incredibly complicated languages with a lot of edge cases when you start getting into the weeds, on par with C++.
Why are these languages using features such as type inference, stricter and more complicated type systems along with heavy templating? It's because now computers are fast enough to provide these 'developer ergonomics' and 'multithreaded memory safety without locks' that these features become viable in the compilers of today vs. the compilers of yesterday. If they could deliver such abilities in the past without having a compiler that takes too long, they would have. In the past C++ was known as a slow compiling language, like swift is today. You also notice slow build times in other 'statically sophisticated' languages such as scala or haskell.
Golang was specifically designed as a language to provide fast compile times. When they were designing the language, if they had to decide between cool language feature and fast build time, they chose fast build time.
Try to expand your horizons, just because you like something, it doesn't mean most people like it. I wish most people liked performance improvement work.
Re: UX Issues with Notion
#117Earlier quoted context omitted.
>Likewise, wouldn’t you be baffled if you needed to click a “Start Editing” button in Word or Google Docs? Likewise, wouldn't you be baffled if you opened up a wikipedia article and found you were automatically editing it, and now you need to worry about making an accident every time you visit the site because you had no intentions of editing content, instead just consuming it. But that's just because people are usin…
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.
Re: UX Issues with Notion
#118(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 enjoyed the time I had with notion, but ultimately it didn't feel "worth it" to keep around. The free tier is too restrictive, and while I preferred the premium experience, the price was ultimately much too high to stomach.
Re: UX Issues with Notion
#119I moved my team of 6 people to Notion when the company stopped paying for Dropbox Paper and moved to Google Docs. I'm a little taken aback by the tone: > I am an unfortunate user of Notion. I have to use it in my day to day job because it is the tool of my company choice. I suffer every time I'm doing anything in it. I put a good bit of time looking at alternatives to paper that allowed for concurrent editing by mult…
Same. I don’t have a particular dog in this fight, though I have been playing with Notion, but the idea you came from Confluence and are upset by the UX of Notion is confusing to me. I still don’t understand when which versions of half ass Markdown work when as I swap between Jira ticket bodies, Jira comments and Confluence.
Re: UX Issues with Notion
#120When I read people like or love Notion, I wish I could watch them use it. Obviously they are doing things very differently than I do... Typing latency while writing or editing a page is really high (bad). Every keypress you do, must be going through a long chain of "what can we interpret the user to be wanting ?" questions. Guess what!? The user is probably just trying to fucking type! Special features and options sh…
> Typing slash ( / ), for any reason apparently, and in any context, pops up the Basic Blocks selection window. If you type, for example, "10 / 2 = 5", or perhaps "a/b testing", or any other very common valid use of the slash symbol, you are left with that stupid popup on the screen. You have to hit ESC to close it. Pity the fool who has a touchbar Mac. And if for some reason you wanted to end your line with a slash,…
I know of no other app which does what they do. Other apps do things like cmd-space (spotlight, which I use ALL the time), ctrl-space (which I have mapped instead of ctrl-b in tmux), shift-shift, which opens search in JetBrains IDEs, etc. Notion could have made cmd or ctrl-/ open that menu at the current cursor location. Adding that one modifier requirement would eliminate so much badness.
As it is now, if your /-whatever is at the end of a line, you're stuck with that popup (hit ESC or mouseclick elsewhere). They even act on the / key within an inline ` code block! So if you want to type a code sample, and you happen to use / toward the end and then hit return as you naturally would, you will in fact select any match in that popup. Who edits code and manually applies styles to auto-syntax-highlighted code?
You may like the slash feature, but I believe strongly that UX educated people would consider this user-hostile. At minimum it is a visual disruption. You can type right on past it and it may eventually go away, but as a user you have to learn to ignore it. It is also absolutely consuming resources while it is going search filtering on every keypress you make until it gives up and goes away. If all you do is use Notion, then it may not be noticeable. But if you are a dev with multiple projects open, multiple local servers running, and other load, you do not need apps that simply waste resources.