#userInterfaces

Software Field Notessfnotes.page@sfnotes.page
2025-11-29

Shifting UI paradigms: Feed. Story. Chat.

Every five to ten years software engineering and computer interfaces seem to be getting a newer user interface control. Every new such UI control seems to be more popular than the previous era’s hero UI control. Right now, we are in what I call the “Chat” generation. The generation before was all about the “Story” UI — which gave way to “reels” or “shorts”, and even the base interactions in live video streams. The era before that saw the rise of the “Feed” UI, with my earliest memories of such interfaces dating back to Facebook’s Wall, or Orkut’s post feed.

The Chat era started in late 2022 with the release of ChatGPT. It was preceded by the Story era, starting around 2014 with Snapchat’s rise in popularity. Snapchat’s user interface control to tell vanishing visual stories with highlights and text overlays became popular and eventually pervasive. While it started with social media, it soon found its way to places like LinkedIn1 and Signal. Going as far back as 2008, we got the first draft of the modern-day social Feed, when Facebook first introduced the Wall. Facebook’s take was a refined version of feeds in MySpace or Orkut. But it paved the way to follow not just friends but social influencers.

None of these UI controls were new when they exploded in popularity. We have always had chat interfaces for instant messaging. RSS feeds with their focus on links likely seeded the idea for social media feeds. IRC chat streams gave way to information feeds we find ourselves in — both for group chats and microblogging feeds. The Story/Reel UI was a re-imagination of the photo carousel in portrait mode.

I sound reductive – although not intentionally. Truth is that these UI controls have undergone numerous iterations to situate themselves in newer information and interaction contexts. And while those iterations were key, such evolutions were driven by the demands and contexts of the time.

AI changed chat. The Chat interface had to evolve from a human-to-human paradigm to a human-to-bot paradigm. An explosion of multimedia – images and videos – compelled the creation of the Story control. The creators of the Story UI control needed fuse the complexity of annotations, fonts, colors and text boxes in PowerPoint presentations with the simplicity of photo slideshows. Social networking changed how we think about feeds in general. The feed of links had to iterate from serving a single-user experience in RSS readers to a social, multi-user experience that we find in modern social networks.

It is easy to pigeon-hole these advances as a product of social media. But the recent uptick in “chat” implementations has bucked that trend with applications in domains ranging from enterprise to programming. The Chat UI is a peculiar case for a different reason as well. Larger paradigm shifts like AI certainly evolved Chat as user interface control. But the UI control itself re-defined what social networks looked like. Even before AI took center stage, IM apps’ natural evolution to group messages reshaped what social media is. Think Slack, WhatsApp Telegram. Group messaging platforms took the 1-to-1 instant messaging interface, and expanded it to multiple users with one chat feed visible to all. At one point it caused Twitter to be relegated as nothing more than a public group chat. It also elevated IM apps like WhatsApp to a “social-network” status.

Each era offers a rich body for work for software engineers, designers, and product managers. That work entails reworking the whole software and product stack in light of these newer interfaces. In particular, think of — (a) implementing these frontend interfaces; (b) redesigning and re-implementing existing user-workflows around these newer interface paradigms; and (c) rewiring or tooling bank-end systems to support the evolving frontend.

The Chat era has been particularly replete with work, or re-work in many cases. So much so that we are now rethinking what browsers are. Interesting to see what UI control we get next, and what work it spurs.

  1. I think of LinkedIn more as a professional network, than a social network. But happy to concede that i am splitting hairs 😁 ↩︎

#chat #feed #product #reels #rss #snapchat #socialMedia #software #stories #userExperience #userInterfaces #whatsapp

2025-10-22

To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

Some simple examples:

❌ "Cannot connect to bluetooth device."
❓ "Okay, but why?"
✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

❌ "Cannot open file."
❓ "Which file? And again, why?"
✅ "Cannot open file 'testfile.txt' for reading: Permission denied"

❌ "Something went wrong when trying to load the website."
❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
But do not omit the details completely!

#usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting

A useless satirical error message box with the title "Oops!". The message reads: "Something went wrong. We will not tell you what exactly. If you want to fix this problem: Good luck!" The dialog has a confirmation button labeled "Great!".
N-gated Hacker Newsngate
2025-09-16

Ah, yes, the age-old of "Your" vs. "My" in user interfaces—the true battleground for the modern UI designer 😂. Because nothing screams like obsessing over possessive pronouns while just skips them altogether—genius! 🙄 Just remember, it's not "your" problem; it's "My" headache. 🤔🔍
adamsilver.io/blog/your-vs-my-

N-gated Hacker Newsngate
2025-08-30

🚨 Breaking news: Font used by phones pre-iPhone era found to be good for... user interfaces? 🚀 Next, we'll find out Comic Sans is perfect for . 🤔 Maybe we should dust off our old and start a font revolution. 📞💥
osnews.com/story/143222/it-tur

Accessibility.

This is one of the air conditioner/room climate control units I encountered during my recent storm chasing trip.

I woke up in the middle of the night, wanting to change the temperature the unit was trying to achieve. As I stumbled around in the dark in an unfamiliar hotel room, it was the sixth or seventh night of the stay, I found myself groping for buttons on the front of the panel.

There are none. Zero. Like everything aiming to be modern, hip, and edgy today, this unit has nothing but a touch panel, with the added bonus of providing absolutely no clue as to where on the touch panel I’m suppose to touch. Forget about trying to navigate the user interface in a darkened, unfamiliar hotel room. I found a light switch, flipped it, and was blinded by the light.

This is when I realized how idiotic user interfaces on standard pieces of technology have become, all in the name of growing profits.

There’s no reason to not put some sort of physical button, or even a raised area to indicate where one is suppose to interact, on this device. None. When I’m staying in a cheap hotel, I’m not really impressed by the smooth, sleek lines of an air conditioner propped up by wood blocks on the outside of the room. The unit was making quite a racket while it was doing its thing, so I don’t know if I was suppose to be impressed with the touch interface or not, but overall I was not impressed with the experience of this unit.

Then I got to realizing, as I sat there in my underwear under a bunch of lights I didn’t want to turn on so I could see what the heck I was doing: how in the world do blind people navigate all these newfangled electronic doo-dads? At least when we had membrane type buttons and other such things (in the interest of cost cutting and forced obsolescence), there could be a raised pad or mark or something so the person who can not see would know they’re actually touching a button. But this monstrosity had nothing of the sort, just a smooth piece of plastic with words screened in such a way that they had absolutely no texture.

What an absolutely awful design for our folks that don’t have the gift of sight!

The manufacturer of this device is GE, or more likely has licensed the GE brand. A quick look at Wikipedia reveals GE Appliances was sold to Haier in the mid 2010s. Haier has rights to the brand until 2056.

I hope they figure out how to bring buttons back by then.

#accessibility #userInterfaces #uxDesign

Hacker Newsh4ckernews
2025-04-23

Solidjs: Simple and performant reactivity for building user interfaces

solidjs.com/

2025-03-25

Welcome to #IUI2025! 🌍✨

The wait is over! IUI 2025 has officially kicked off! 🎉
Who and what are you most excited to see? Let us know in the comments! 👇🔥
#IUI2025 #AI #HCI #UserInterfaces #Cagliari

N-gated Hacker Newsngate
2025-03-24

✨🎉 Breaking News: A nearly 30-year-old software guide has been updated with 475 , because who doesn't love reading a novel's worth of annotations on obsolete technology? 📚🔍 Now you can finally revel in the subtle differences between user interfaces from the era of dial-up and the futuristic landscape of 2025. 😂🚀
blog.marcocantu.com/blog/2025-

Juan C Nunojuancnuno
2025-01-30

I wish app devs gave as much love to their app's settings as they do to the other parts. I really don't like WebViews being used for that purpose. At that point use the mobile browser, with the chrome so it's obvious it's the browser. From developer.android.com/referenc

> In most cases, we recommend using a standard web browser, like Chrome, to deliver content to the user

2024-09-21

@bitsplusatoms the wider world often forgets how much we owe #xerox for our present day computers. A certain Mr Jobs managed to convince them that #Apple did it :)

#gui #hci #userinterfaces

John Faithfull 🌍🇪🇺🏴󠁧󠁢󠁳󠁣󠁴󠁿🧡✊🏻✊🏿FaithfullJohn@mastodon.scot
2024-09-04

#ErrorMessages In a previous life I wrote and supported various bits of software. I am still secretly proud of this terrible error screen from my INCA museum catalogue, which I recently resurrected in a VM... Am I a bad person? 😂 #HardCheese #Software #UserInterfaces

A screenshot of an auld-style Windows XP error popup window. The title bar says: BLAST AND DRAT!!! 
and the window displays a form saying: 


HARD CHEESE! 

You have unearthed a bug or other program error. If the problem persists. noting the following values may help in tracing the problem:

 Program with error:  BREAKREL Error Number 52 Line number of enor: 7 Error Message: No table is in USE 
Line of code with error: No table is in USE
Juan C Nunojuancnuno
2024-05-24

If I'm understanding things correctly this person wrote a UI library from the ground up, with C. With lots of documentation. How cool! nakst.gitlab.io/tutorial/ui-pa

2024-04-23

When it comes to #UserInterfaces of internal applications for in-house expert users, I always choose #CLI over #TUI over #GUI.

For back-office applications, the GUI soaks up more than 90% of the development effort and offers less than 10% benefit to expert users. By contrast, a TUI offers efficiency and simplicity to the users and places very little burden upon the developers.

Juan C Nunojuancnuno
2024-04-14

As I understand, the file manager will take over the responsibility of the file dialog. That is so reasonable I can't believe it didn't occur to me myself. I've been programming for ages. floss.social/@debugpoint/11226

Axel Rauschmayerrauschma@fosstodon.org
2023-10-01

As a user, I find toggles much more difficult to figure out than checkboxes. This is one of the better toggle implementations but it also makes you wonder: Why not use a checkbox if it’s so similar to one?

More thoughts on checkboxes vs. toggles: uxplanet.org/checkbox-and-togg

#UserInterfaces #Usability

A circle inside a horizontal container with two positions:

On: Circle is on the right and contains a checkmark. The whole control is blue.

Off: Circle is on the left and empty. The whole control is gray.
2023-09-27

Does anyone know of a good introduction to core usability considerations, aimed at non-developers? Things like discoverability, predictability, consistency, latency vs throughput, Fitts' law? Some colleagues who don't have a software background are getting in to digital health endeavours and I think it would be helpful for them to have some shared understanding.

#usability #ux #userexperience #userinterfaces

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst