A great example of a really nice information dense app is the Bloomberg terminal. Maybe it’s ugly (a lot of people say this, but I personally don’t think so), but all the right design choices have been made. High Contrast, monospaced fonts, extensive keybindings, absolutely no wasted space. And, most essential, it’s not a web app.
I used to work at a portfolio analytics company who’s explicit goal was: to have all of Wall St use Bloomberg on one screen, and our product on the other.
Our app was probably the anti-thesis to the Bloomberg Terminal in almost everyway: “modern” design, tons of white space, a web app, making you have to log in every 30 minutes for “security”, no keybindings.
I’m sure most of HN have never used the terminal, but let me give an analogy. The Bloomberg Terminal is like using Emacs or Vim, they make you feel powerful, they make you feel like a wizard.
Our app was like google docs, you never felt like you were in direct control of it. You never felt like it was an extension of yourself. Unsurprisingly, even though our app was incredibly useful and provided portfolio analytics that you could only get from excel (our biggest competitor), it, and the company, was largely a failure. Instead of being worth billions, we were capped at a valuation of 200m for over 5 years.
I believe completely that the company’s failure was due to our “modern” white space heavy app.
> You never felt like it was an extension of yourself.
Not a better phrase to describe a Bloomberg Terminal. Everything is there, mainly data, quick charts, Messenger and with it 'social' (yes, Bloomberg Support do make restaurant recommendations if asked), quick facilitation to sometimes complex questions through these services, handy linking to Excel, and where data quality was questionable a quick response.
I think what Bloomberg did/do was/is listen to their customers. A Bloomberg today is much like when I first touched it 20 years ago, but it isn't. It feels the same, or similar, the screens are vastly larger, does what it has always done, scales. There are no redesigns that stop a user doing what they've done before, yet allow them to do more. It is what is expected and surprises, sometimes frustrates, but a learning curve and pleasure comes from learning.
The Terminal is probably the best and greatest app that's ever existed. There's just this ineffable feeling you have when using it.. like all the knowledge in the entire world is available at your fingertips. Using it just feels good, you feel powerful, and in control.
For people that haven't used it, I know it sounds like porn. But it's incredible.
I love the Bloomberg Terminal style. I watched one of my users retrieve some product information yesterday, a few key presses and it was there. Much faster than a web application.
The colour scheme also looks good. A black background gives you many more high contrast choices. Try using yellow or cyan on a light background. It seems most of the colours are based on the old 8-bit selection; red, green, blue, cyan, yellow, white and black. Orange seems to have been added as well.
Actually orange is the oldest. The story goes that when the Bloomberg terminal was created in the early 80s all the consoles where monochrome, and the only choices were green or orange (on black in both cases, of course). Everyone else used green so they went with orange to be distinctive.
> The story goes that when the Bloomberg terminal was created in the early 80s all the consoles where monochrome, and the only choices were green or orange (on black in both cases, of course).
It's probably not entirely true given there were dozens of known phosphors, and there were monochrome displays in other colors (e.g. the 1980 Apple Monitor III was available in green and white).
However assuming they went with pretty standard equipments green was by far the most common followed by amber. Amber is also somewhat softer on the eyes, which might have been an argument in favour given they'd have folks looking at these displays all day long, especially for charts which would fill the terminal with <color>: green monitors were OK when you had mostly black (text, curses interfaces) but it was way too harsh otherwise.
Our first computer actually had both green and amber displays, the amber display was dedicated for games and the like, anything which would light up a significant fraction of the display at once would go to the smaller amber monitor instead of the larger green one.
I was going to post about Bloomberg Terminals, but figured since I'm late to the story, someone else already did. Yeup.
It's funny how little credit we give to business users these days, and how much marketing UX there can be.
There was a time when business students attending college and their crufty professors could manage using email by telneting into the mainframe to use Pine. And the technology was a wonderment to them.
People who say Bloomberg is ugly have a very shallow view of what design means. It's the form over function way of seeing things. These are the people Apple markets its products to.
> I used to work at a portfolio analytics company who’s explicit goal was: to have all of Wall St use Bloomberg on one screen, and our product on the other.
Me too! I wonder if it was the same company?
> Our app was probably the anti-thesis to the Bloomberg Terminal in almost everyway: “modern” design, tons of white space
Mine rhymed with "grim soup". To be honest, although there was a portfolio management tool of sorts, it only had one customer, and the company's real focus was on trade ideas. It sounds like the top brass had similar levels of ambition, though.
For the same reason that monospaced fonts are the correct choice for code: so text can line up. If you you’ve used the terminal, it displays structured information really nicely because of this.
Also in regards to the monospaced fonts, you can easily calculate how much space a block of text will take on the screen.
They do have the Bloomberg anywhere portal which is web-based, but the main app isn’t web based.
This is how I feel about computing in general. GUIs in general were a mistake. Vim is fucking awesome, and there's no replacing a shell and the myriad CLI utilities you have at your disposal. The computer is there to automate repetitive tasks, not create virtual busywork.
GUIs generally represent the sacrifice of power and automation for approachability by the lowest common denominator.
> The computer is there to automate repetitive tasks, not create virtual busywork.
The GUI eliminated the busy work of setting up your environment to make your workflows easy. It instead provides an environment where a wide variety of workflows are easy by default, although maybe not as easy as they could be with specific configuration like setting up customized keybindings, etc.
Easy but time consuming. I.e. not ergonomic. Also point&click UIs tend to sacrifice composability, whereas keyboard-driven interfaces tend to allow to chain operations and modifiers in a way that makes it ergonomically cover much larger space of possible workflows.
But learning is time consuming, too. Keyboard-driven interfaces can be more efficient but they are not discoverable. Maybe keyboard-driven interfaces make sense for the domain specific tasks that you do every day, but would you want a keyboard-driven interface for every random website you come across?
> would you want a keyboard-driven interface for every random website you come across?
Definitely, no. But you can have both at the same time; in fact, in 90s-era applications and in professional desktop software, this is the norm. You build your discoverable UI, but ensure every action is attached to a keyboard shortcut, and that keyboard shortcut is also discoverable. Call it "progressive enhancement" of UI ergonomics, if you like; the point is not to put the ceiling for regular users on the level of your average first-time user.
> But learning is time consuming, too.
Not as much as time wasted if you don't provide a "faster path" to learn. I'm trying hard to understand, why modern UX designers react to the possibility (not even requirement) of users learning like devil to holy water. That is, beyond the obvious reason - pretty but useless software sells better, as you rate looks on first impression, but ergonomics on repeated use (i.e. after sale).
Vim has a GUI (or a UI I guess), but it allows you to input commands. For some reason we think of GUI as mouse based interfaces in which you click around. There’s no reason why this has to be the case.
The most powerful form of computing is having the command line for input but also allowing a UI for the display of information.
I have also thought this through to the following logical conclusion: Imagine computer users being fluent in SQL and everyone sharing one giant database.
Let’s check Twitter...
select message, username
from TWEETS
order by date desc
limit 10
Slightly more realistic is the “semantic web” concept.
The trend of GraphQL in JS-land is helping move a little bit towards this, since it's a strong reason to have row-level user authentication and access control so that queries can live in the frontend.
I used to work at a portfolio analytics company who’s explicit goal was: to have all of Wall St use Bloomberg on one screen, and our product on the other.
Our app was probably the anti-thesis to the Bloomberg Terminal in almost everyway: “modern” design, tons of white space, a web app, making you have to log in every 30 minutes for “security”, no keybindings.
I’m sure most of HN have never used the terminal, but let me give an analogy. The Bloomberg Terminal is like using Emacs or Vim, they make you feel powerful, they make you feel like a wizard.
Our app was like google docs, you never felt like you were in direct control of it. You never felt like it was an extension of yourself. Unsurprisingly, even though our app was incredibly useful and provided portfolio analytics that you could only get from excel (our biggest competitor), it, and the company, was largely a failure. Instead of being worth billions, we were capped at a valuation of 200m for over 5 years.
I believe completely that the company’s failure was due to our “modern” white space heavy app.