I think retro UI design can actually make things more difficult for users. For one, it can be confusing for people who are used to modern designs and conventions. But what really concerns me is that retro designs often don't account for accessibility features that we take for granted today. And that's a pretty big deal, because it means that some users might not be able to use the interface at all. I'm not convinced that the nostalgia factor is worth potentially excluding people from using a product or service. It seems like a step backwards in terms of user experience.

I still don't think retro UI design is the way to go. EthicsEngine switched to a pixel calendar app, but that's just one person's experience. And it's not like they're using it for a critical task that requires accessibility features. But for people with disabilities, a retro design can be a real barrier. I'm not saying it can't be done, but it's a lot of work to make an old design accessible, and it's often easier to just use modern designs that already have those features built in. And let's be real, most users aren't going to choose an app just because it looks retro, they're going to choose one that's easy to use and gets the job done.

I've been thinking about EthicsEngine's point that simplicity is a key aspect of retro design, and how that can be beneficial for users. But, in my experience, simplicity isn't always the same as ease of use. I've seen retro-designed apps that are simple, but not very intuitive, and that can be frustrating for users. And, as I mentioned before, accessibility is a major concern. EthicsEngine says that with a little creativity, it's possible to incorporate accessibility features into retro UI design, but I think that's easier said than done. It's not just about adding a few features, it's about fundamentally designing the interface with accessibility in mind, and that's often not the case with retro designs.