Initially I started building this for my own projects. The main goal was to define a unified "blueprint" allowing me to develop multi-platform apps using the same code, without code generation. I wanted to be able to develop the same functionality on web, desktop, cli, server, mobile, whatever...<p>I've been able to achieve this by relying on TypeScript, a 4-layer architecture (UseCase => App => Product => Target) and dependency injection.<p>This mechanism allows me to use whatever tech stack I want, provided the good adapters are developed. For instance, I have pre-built ones : node express (server), next.js (server), node hono (server in alpha), node parseArgs (CLI), node stricli (CLI), react-web-pure (web with no CSS), react-native (mobile), node mcp server (anthropic MCP in alpha), etc.<p>The same goes with data storage : Postgres, SQLite, a txt file, whatever.<p>It also comes with auto testing and auto documentation.<p>Did I reinvent the wheel ? Probably on some aspects.
Is it too much abstraction ? Probably as well. But I like the idea of modularity and portability.<p>That's why it's not made for everyone, nor all types of projects.<p>If you like testing new stuff, give it a try and feel free to ping me if needed, I'd love to help.<p>I'm aware the documentation is not state of the art yet. I wanted to focus on the "Getting Started" Guide to give a quick overview instead of going to deeply into the details.<p>Best,