Software should convey a sense of calm
11–20 of 91 posts
Re: Software should convey a sense of calm
#12In festina lente
Re: Software should convey a sense of calm
#13Re: Software should convey a sense of calm
#14I think a lot of this depends on the target audience. If it is a wide-distribution consumer application, then I like the "swimming duck" analogy, where it looks smooth and calm, above water, but is paddling like hell, underneath. That's what I strive for, myself, in my standard consumer-level apps. Many of my apps look quite "boring," but actually have a lot of moving parts, invisible to the user. Selecting a screen may result in multiple server transactions, and the user only sees a throbber for a half second. No progress report.
The other side, is that, if you are marketing to engineers, or specific types of professionals (not all "pros," though. That's a wide net), you may want to present a very complex and "raw" UI. I have done this for admin dashboards.
Re: Software should convey a sense of calm
#15I am most familiar with Windows, so I will speak from that perspective.
Because software was an application, and the path of least resistance was to use the OS provided controls and menus, there was a sense of uniformity in how you accessed features. Keyboard shortcuts just worked and were pretty much the save (Ctrl-S, saved the document, etc).
OLE provided a uniform way to embed documents into other applications. Cut and paste worked consistently.
There were also a limited amount of frameworks (bare Win32, MFC, OWL, Visual Basic, and Delphi probably covered 95%+ of apps).
It seemed that most user interfaces at the time were actually made by programmers and not graphic designers. In addition, for the most part there was a lot of continuity from version to version in how a program looked.
Now it seems that every web app wants to look different for the sake of looking different. People want to change how an app looks on a regular basis, often for no other reason than that it needs to look "fresh.". There are a myriad of every changing front-end JS frameworks.
It seems that UI is driven by graphic designers looking to make something unique and standout and not programmers that just want to make a standard, low friction way the user can access the functionality and be done with it.
Also, all you data is siloed a lot more because it is stored in the "cloud". Whereas before you could easily have access to the raw output from all your programs (and if they supported OLE embed documents from one program in a completely different one), now it is somewhat of a pain if you want to get raw access to your data.
Web based apps do have a lot of advantages, but I feel we have given up a lot when we went from native desktops apps to web based.
Re: Software should convey a sense of calm
#160: http://quicksilver.be.washington.edu/courses/arch498cre/2.Re...
Re: Software should convey a sense of calm
#17I agree with most of the opinions in this article, but I don't like the idea that all software should convey calm, or the conflation between a simplified intuitive interface and calm. Video games are a great example of simplified, intuitive interfaces which are often the polar opposite of calm.
Elements like calm and intuitive are also extremely subjective. I find emacs calm, intuitive and extremely accessible. People with different context will have a comically different response. Humans need interfaces that cater to their different experiences.
Re: Software should convey a sense of calm
#18Re: Software should convey a sense of calm
#19> I want to find the same things in the same places How else will designers justify their jobs? I wonder if designer should be reworked to be a seasonal or consultancy job only, to only hire them when you're making a new product/big feature or there's a drastic need to change things but never otherwise. Having them as permanent staff leads to our present usability and accessability nightmare of everything constantly…
Re: Software should convey a sense of calm
#20Related: - https://en.wikipedia.org/wiki/Calm_technology - https://calmtech.com/book.html
Does the "calm tech" movement have much to say? I feel like a theory of learning for software is more important. Of course it should be done in a pleasant way but I wasn't able to get much actionable insight out of calm tech writings.
So the way you structure and write your code has very much to do with wanting to reduce the mental taxation of the reader (you included).
In the UI, UX and HCI world the concept has obviously a lot to say as well.