NodlumeAbout
The part of building apps worth designing
Every React project starts the same way: pick the framework, wire the conventions, install the component library, scaffold the folders — and only then get to the part that makes the application distinct. Nodlume exists to skip straight to that part. The foundation is opinionated and already decided; what you design is the product itself.
On the Nodlume canvas, an application is a connected system of pages, components, layouts, API routes, stores, and data models. You shape the relationships visually, then share the project with collaborators — and export a connected project skeleton targeting Next.js, Tauri, or React Native.
Foundations should be decided
Framework versions, file conventions, and component primitives are solved problems. Re-deciding them per project is where momentum goes to die.
Design the system, not the file
Pages, components, state, APIs, and data are one connected product. Seeing them as a graph keeps the architecture honest before any code exists.
Exports you actually own
Nodlume produces a real project skeleton in your stack — no runtime lock-in, no proprietary format standing between the design and the code.
Who makes Nodlume
Nodlume is built by QuokkaQuery, a small team that kept rebuilding the same React foundations and decided to build them once, well, instead. The product is young and opinionated on purpose — the roadmap lives in the open on the blog.