I dunno, most of the stuff in Fleet looks to me like it benefits from being a native thin-client rather than a browser-based app (e.g. SSH to your remotes, run the language server locally, etc).
I can see that a web-UI option could be built atop the "Space-hosted everything" architecture they are putting together, but I don't see any evidence that's actually what their core strategy is, as GP suggested. They spend a bunch of time discussing running things on "Your machine" too, which doesn't sound like a browser-first strategy.
As I see it, their secret sauce is building client-side applications that are faster than other companies can build. I just don't see them giving up that performance edge to make a browser-based client their primary strategy.
I can see that a web-UI option could be built atop the "Space-hosted everything" architecture they are putting together, but I don't see any evidence that's actually what their core strategy is, as GP suggested. They spend a bunch of time discussing running things on "Your machine" too, which doesn't sound like a browser-first strategy.
As I see it, their secret sauce is building client-side applications that are faster than other companies can build. I just don't see them giving up that performance edge to make a browser-based client their primary strategy.