There are two distinct paths for what the browser/web should become.. more appish like or more like a collection interactive documents. In the end they tried to mix both, but the appish view is eating whats left of the open world of data the web was designed to be.

This is the path Google decided it should go.. They have Android if the strong 'app list' contender wins over web and on the other end they can index the web with AI and Chrome whats left to be indexable (making it hard for contenders) and also bloating the browser (with a huge set of API's) making it hard for other players to try other visions for the web that require and can be done with a simple engine.

I get it that it had to compete somehow with the app store. But for me, the better option would be to split into two products, each one following one path, but with browsers not following the path that would eventually kill them.

I just see a 'dead end' with the web mostly being a framework to be embedded for rich apps(its also a great tech for this end).

Thats why im trying something new here.. a different sort of a "browser", but i dont think it can be called that way in the end.

I've started a couple of years ago, and im almost in the finish line now..

I hope that i can deliver a platform where information can flow free without leading to centralization and digital monopolies that can choke all the rest, but i cannot know if it will really deliver that, because its not just about the tech..

What that telling leaves out is the fact that the web is also an extremely popular way to distribute documents. When someone finishes writing a manifesto or a fan fiction and considers how to disseminate it, they never respond with, “I know: I’ll distribute my manifesto or fan fiction on the iOS and Android’s app stores.” That greatly reduces the harm done by the lack of indexability and linkability of mobile apps.