Jucie - Stop Mocking, Start Making

Adrian Miller — Sun, 04 Jan 2026 16:28:13 +0000

This is a submission for the DEV's Worldwide Show and Tell Challenge Presented by Mux

What I Built

Jucie is a collaborative environment for building real web applications visually, without breaking the connection to code.

It looks familiar at first glance. It resembles a design tool. But Jucie is not for mockups.

Everything created in Jucie is a live, running application with real structure, real state, and real logic. There is no export step, no handoff, and no rewrite later. What you build is the product.

Jucie supports React, Preact, and Vue, and is designed for serious developers and designers who want to move faster without sacrificing integrity, control, or ownership of their code.

My Pitch Video

Demo

https://demo.jucie.app/eJxFjDkOgDAMBP_iOiR9fsAzkG1BUA4rFwXi75iKcmY1ewPnCR6kFhrYQ8lgIBVidcQt7B9n5ZXA5xGjgVZRx6N3ad454lQWrU_Gbs-Bge0m4rSaga__5XkBeOcj2Q

Login credentials:
Username: demo@jucie.app
Password: I-am-a-demo-user-123!!

No install required. Everything runs in the browser.

The Story Behind It

Modern product teams spend an enormous amount of time translating intent between tools.

Design happens in one place. Code happens somewhere else. The gap between them is filled with exports, tickets, misunderstandings, rewrites, and throwaway work.

I built Jucie to remove that gap entirely.

The idea is simple: if you are designing something that already has structure, behavior, and constraints, you should be building it as software from the start. Not documenting it. Not simulating it. Building it.

Jucie is a response to the growing frustration with tools that promise speed but create debt. It keeps the flexibility of code while offering the immediacy of direct manipulation.

This is a solo project, built from the ground up, driven by years of working at the intersection of design and front-end engineering.

Technical Highlights

Real Applications, Not Prototypes Jucie renders live applications using React, Preact, or Vue. Components, state, events, and bindings are all real.
Visual + Code Workflow You can manipulate UI visually or work directly in your editor. Both paths stay in sync.
CLI-First Project Setup Projects are created and run locally using a CLI, just like any modern development workflow.
Collaborative by Design Multiple users can work on the same application in real time, shaping structure and logic together.
No Lock-In Jucie does not invent a new framework. It builds on the ecosystems developers already use. (React, Preact, Vue)

This approach makes Jucie fundamentally different from no-code tools. It does not abstract software away.

Use of Mux

The submission video is a single-take, one-minute walkthrough designed to clearly show the product working in real time. Mux made it easy to focus on storytelling and clarity without worrying about video delivery or performance.

Future Use of Mux

Beyond hosting the pitch video, I am actively exploring deeper integration with Mux as part of Jucie’s modular architecture.

Video is a common element in modern web applications, but it is often treated as a placeholder during design and prototyping. A Mux-backed Jucie module would allow teams to upload, manage, and bind real video assets directly inside an application while it is being built.

Mux’s APIs and platform model align well with Jucie’s approach to composable, production-ready modules. This would make video a first-class, real component in Jucie projects, not something wired up after the fact.

While this integration is still exploratory, Mux is a strong candidate for enabling robust, scalable video workflows inside Jucie without reinventing infrastructure that already works.

Closing Thoughts

Jucie is built on a simple belief: the fastest path to good software is fewer translations and less pretending.

Design tools helped teams collaborate. Now they are slowing teams down.

It is time to stop mocking software and start making it.

Forem: Adrian Miller