Web Loom
Keep application logic reusable as your rendering framework changes.
Made for application developers.
Overview
This engineering project is under active development. The scope below describes its intended design; deployment readiness and supported capabilities must be confirmed for each engagement.
Frontend applications often bind important product logic to a component framework. A redesign or framework change can then require rewriting rules that have little to do with rendering.
Web Loom gives those rules an explicit home. Models manage data and validation; ViewModels expose reactive state and commands; a view connects that state to the chosen rendering layer. Demonstration applications use the same architectural approach in React, Vue, Angular, Solid, Lit, Marko, vanilla JavaScript, and React Native.
The value is architectural continuity: teams can change how a feature is presented while retaining a separately testable model of how it works.
What it provides
Signals and MVVM
The core foundation
Signals provide reactive values, derived computations, effects, and batching. MVVM foundations build on them with model and ViewModel primitives, API-oriented models, and commands.
A ViewModel can expose its data, loading state, error state, and available actions without importing the rendering framework. Each view subscribes through its own bridge, keeping the framework integration at the boundary. Validation belongs with the data model rather than being scattered across every presentation component.
Application libraries
Compose a product
The ecosystem includes server-state queries with caching and refetching, client-state storage, forms with Zod integration, and typed event communication. Headless UI behaviours handle interaction patterns such as dialogs, selection, and roving focus, while composed patterns build on those foundations for flows such as wizards and master-detail screens.
Design tokens and theming provide a related visual foundation. The libraries can be adopted selectively, allowing an application to begin with one architectural concern and bring in other pieces as its needs become clearer.
Native template rendering and tooling
Web Loom also provides a signal-native template engine. Its bindings subscribe directly to reactive state and update the relevant DOM nodes. The same ViewModel architecture can therefore be used with an existing framework or with Web Loom's own template view.
Vite integration, server-rendering infrastructure, template diagnostics, linting, and source-linked tooling support that rendering path. Demonstration applications include catalogue/cart/checkout flows and a dashboard, making the integration concrete rather than limiting it to a counter example.
Developer enablement
A scaffolding CLI and MCP server support feature construction and discovery of the toolkit's patterns. The MCP tools provide package guidance, documentation, and scaffolding for models, ViewModels, views, and forms.
These tools encode the architecture into repeatable examples. They help a team understand where data rules, actions, and rendering belong when starting a new feature.
Integration example
A team builds a catalogue ViewModel that exposes products, loading and error signals, and an action to refresh the list. A React view subscribes to those signals, while a Vue view or a Web Loom template can render the same logic through its own binding layer.
The change in view does not require moving catalogue rules into a new component model. The application still needs platform-specific integration, but the reusable logic has a stable owner and can be tested independently.
Built with
Baobab built the architecture primitives, supporting libraries, rendering path, and working examples as one ecosystem. Its engineering contribution includes reactive-system design, typed API and state boundaries, headless interaction modelling, template compilation, and developer tooling.
Web Loom's MIT license supports reuse of the toolkit. The portfolio demonstrates a long-lived approach to frontend application structure backed by code and multiple integration examples.
Resources
Questions
Is this available for deployment?
Deployment readiness has not yet been verified for this catalogue entry. Contact us to discuss current scope, release gates, and your requirements.
Who owns this software?
This is owned engineering work from The Baobab, a brand of Fortezza Nuova Enterprise. Deployment and licensing terms are agreed for the relevant product.
Use Web Loom in your product
Discuss the capabilities you need, deployment environment, and integration responsibilities. We will confirm current readiness and agree a scope before committing to a release.