Good code examples with screenshots showing what the UI looks like. Apple's documentation usually lacks screenshots showing what particular SwiftUI components look like or how they function – it's up to third-party developers to provide this information.

Just ffmpeg in the browser, useful

Just a simple demo of transforming one iOS app design to another where upon using an app we try to ask to the following questions:

- Where am I?

The app should make it clear right away, so Im not left wondering where I am or how I got here

- What can I do?

I shouldn't have to guess – actions should be clear and easy to understand

- Where can I go?

A clear sense of next steps to keep the flow going and helps me avoid hesitation or second-guessing

I wish some professional software answered those questions. As well as mine, really. Should rewatch it from time to time.

The language models’ greatest feat is also their most significant drawback—by absorbing the personal voice from every piece of content they have ever encountered, they produce a whole bunch of nonspecific, generic, mean-reverting Whatever that manages to say much but convey very little. All it can ever be is a circumlocution machine. It won’t tell deeply embarrassing tales of its youth, wear its grudges on its sleeve, passionately hold an unpopular position, or tug at threads without knowing ahead of time what the other end might be attached to. It doesn’t wander off onto interesting tangents that bring the reader along on a little shared journey of discovery. It has no discernible soul, no passion for its work, no real ability to justify the screen space it has filled up—let alone the time and attention the reader is now giving it. We can tell when it’s genuine. God dammit, we can tell.

The latter consequence of low expectations is the more serious one. It's something that some people may never recover from. The average career of a paramedic is 6-8 years because of the physical and psychological strain the job puts on a person. The career of a physiotherapist is about the same, mainly because they become someone's personal psychologist 8 times a day while treating back pain or a sore knee. The trajectory of a data or software engineer seems to be a bit different: they burn out from the mental stress of working in dishonest and fraudulent cultures that produce unsatisfying work, but the engineer stays in the profession. Only they're a shell of a human. How many developers or programmers do you know who are a little sad all the time? I wonder what caused them to be like that.

So much of building tech stuff is a figurative conversation - between you and the machine, you and the abstraction, you and the people who will use what you build, you and the people who will maintain it, you and those who came before you. To understand such a varied audience you need to anchor on your understanding of yourself. Improve the one tool you can never replace - you.

Designing for UI density goes beyond the visual aspects of an interface. It includes all the implicit and explicit design decisions we make, and all the information we choose to show on the screen. It includes all time and the actions a user takes to get something valuable out of the software.

So, finally, a concrete definition of UI density: UI density is the value a user gets from the interface divided by the time and space the interface occupies.

Speed, usability, consistency, predictability, information richness, and functionality all play an important role in this equation. By taking account of all these aspects, we can understand why some interfaces succeed and others fail. And by designing for density, we can help people get more value out of the software we build.

It seems that Linux distributions were more accessible for blind people in 2012 than in 2025. It hurts my soul. Accessibility is not a question of "if", it's about "when" - you and me don't get any younger with each passing day - our vision might get blurrier, our programmers hands will get tired pressing those keys every day.

I hope my projects doing a little bit better in that regard.

FediIndex data on Betula. Very interesting! 1.3.0 is still used by some, 1.2.0 has ceased to exist. Third of all instances are hosted in Russia.

I wish it knew more Betula instances though.