Hacker News Reader

Comment by OneDeuxTriSeiGo | Hacker News Reader

FWIW if you listen to Signals and Threads (the Jane Street podcast) they talk about this.

They have dedicated UX designers who do relatively little code but focus entirely on making the UX as optimal for the traders as possible and one of them was on an episode.

They talked about how most of the normal UX rules for SW go out the window because quants and traders have such different needs than "normal software".

View on HN

This matters. Beyond performance (a universal good), the definition of "good" UX is strictly dependent on the user. Fintech platforms for traders who open a multi-window thick client application(s) and spend hours in it every day have little in common with consumer mobile apps designed to hold your attention for maybe a minute. It's mind-bogglingly lazy to choose something like MUI (Material UI) as if it were some kind of reasonable foundation irrespective of context.

Is there any professional software that wouldn't benefit from high information density? Most software design is optimized for the non-users who have to approve it.

You can have high information density and still not have words running into each-other. Taking all of the space out from around text and information graphics makes them less legible, even for experienced "power users".

I think the goal here is more an aesthetic of being for "serious traders only" rather than a UI optimized for speed and clarity. The UI designers probably have little choice but to match the preferences of the user group though, even when those preferences are empirically detrimental.

Yeah safety critical software needs to avoid high UI density for the interface itself. For diagnostics and monitoring or general stats you can still do high density but the actual "action space" needs to be kept as low density as possible and preferably with physical separation in the UI (i.e. via physical buttons and displays instead of just a big touch screen or monitor+Mouse and kbd).

Higher information density is ideal but when people are working in less than ideal conditions (stress, lack of sleep, alarms going off, etc) you need to prioritise information clarity and clarity of actions over raw density.

"non-users" are also big targets for software. If you run a software business, chances are you want people who've never used your software to start using your software. In that case, discoverability trumps high information density.

It only adds discoverability for the things that fit the screen. In other words, you have to make it simple. I.e. the lazy way to make something "user-friendly", do as little as possible and force the user to adapt to your ways instead.

It has to be the right information, filtered and presented in such a way that supports the task. Any kind of human in the loop UI has to manage user cognitive loading. Task saturation is real.

this - most of the internal software at my job that's actually important is very dense, with keyboard navigation and shortcuts. The ones that somebody makes to sell themselves to upper management while angling for a promotion look very pretty, and never get used.

And yet, we make such beautiful and vacant software ourselves for our clients, because again, its b2b, so you aren't selling to the people who actually have to use the software. Im glad at least we arent forced that often to use specific internal tools, the better ones just get adopted organically

Fair point

I guess JS doesn't have to care about this at all because they're not selling their UI to others, just making it in house for in house use

JavaScript?

No, OCaml

Think node, except the other direction. They write their backend in OCaml, and then they also write their web ui in OCaml with a translation layer

Or think of gwt (java) awhile back

JaneStreet, see post title.

Reply on news.ycombinator.com