They're some of the only new UIs to be made in the last decade. Almost everyone else stays in the browser (or something close like electron- claude code is actually mostly written in React, they couldn't get far from web dev). The problem is they need to interact with the local filesystem, and not many people have built apps for such a wide range of devices in a long time, and of that small talent pool I bet most are corpo coders- moving too slow and to focused on "the right way" to actually ship more than detailed Jira tickets. They also don't have time for stable releases because competition is so fierce.
But I almost always think of things from a talent-pool-first perspective. Perhaps there are actual technical issues like what Boris was referring to.
Luckily for them, every OS has (at least one) native way of building applications, and with the power of AI they could easily make 3 different desktop UIs, while reusing the same core logic.
If only there was an easy high-level language that's taught to first year students that allows them to write once, run anywhere.
If they're too lazy to learn java, haxe has hxwidgets[0]. Haxe is pretty damn close to js. If a dev can't handle that, they should turn in their keyboard and get a job that doesn't require a brain, like being a senator or federal judge.
There are lots of good answers in this thread but I think it's because they are AI companies and not UI companies. When you look at tools like AnythingLLM, OpenCode, pi, etc. you see all kinds of different interfaces, and while they might make disagreeable choices at least they do it with intentionality and direction.
Because 90% of those UIs is written by these new AI models. That is how they are able to churn so much new user facing stuff all the time. The fact that it works at all is proof that these new AI models are actually pretty decent.
Many people will say it’s because of the slop. I think it’s because they have no product vision. The roadmap is pretty much a random walk, which combined with the velocity of agentic coding is like digging a moat with atomic bombs.
They are moving at breakneck speed deploying on scales most of us can't even imagine. They are working in a space that's completely unexplored where getting information as quickly as possible is preferred above iterating on some feature until it's "done" while your competitor has released fifteen other features, all sucky, but one of which turns out to be a killer and makes a billion bucks overnight.
> They are moving at breakneck speed deploying on scales most of us can't even imagine. They are working in a space that's completely unexplored where getting information as quickly as possible is preferred above iterating on some feature until it's "done" while your competitor has released fifteen other features, all sucky, but one of which turns out to be a killer and makes a billion bucks overnight.
Not on the client, they're not. It's a chatbot as glue between different backend systems.
But I almost always think of things from a talent-pool-first perspective. Perhaps there are actual technical issues like what Boris was referring to.