Instead of wiring every button to a specific screen, you register the components your app can show.

Instead of wiring every button to a specific screen, you register the components your app can show. When someone clicks, Jev gets the button text, surrounding content, and app state, then picks what to show next. Change "Buy Pro" to "Compare plans" and that wording can change the behavior without editing the click handler. I built NoFlow because I wanted to see how much UI logic I could replace with Jev before regretting it. Yes, I'm putting a model between a button and a modal. Try me. The runtime limits it to registered components, with confidence thresholds, fallbacks, and confirmation checks. I'm curious where it becomes useful and where you'd absolutely refuse to use it. https://noflow.casungo.workers.dev/? - https://github.com/casungo/noflow-runtime - https://www.npmjs.com/package/noflow-runtime