DEV Community

Cover image for How much can be done on the client side? Created a web operating system as a demonstration.
my god
my god

Posted on

How much can be done on the client side? Created a web operating system as a demonstration.

Have been working on an architectural problem: how much of a traditional
OS can we move into the browser?

In my current project I created an experimental browser-based OS which
includes:

  • Window manager, file system, terminal
  • AI kernel with tool-calling abilities
  • No backend (only indexedDB/localStorage)

The experiment seems to be successful, but what really matters is the
discussion.

Questions are:

  1. Architecture: Pure client-side approach to solve some problems or do we fight the platform?
  2. AI integration: The OS has AI which is capable to control the UI via virtual cursor. Useful pattern or just overengineered?
  3. State management: IndexedDB + localStorage for all - scalable approach or a road to hell?
  4. Extensibility: Added an app registry system. Any patterns to share with developers of plugin architectures?

This is not an issue thread about bug-fixing. Core works well. It's more
like architecture discussion: is there any sense of going this way.

Project repo: https://github.com/hjk-maker/Solips-webos

So, what do you think about thick-client web apps?

Top comments (0)