Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Jev can generate interfaces in under 2 seconds. Almost zero cost. I took the shadcn component library... → hooked it to a custom style md file → made some basic UI rules of popular apps using the Mobbin MCP → Jev instantly decides based on the predefined library and...

39,383 Aufrufe • vor 5 Tagen •via X (Twitter)

46 Kommentare

Profilbild von Juraj Ivan @ QikBuild
Juraj Ivan @ QikBuildvor 5 Tagen

Cool use case — Jev picking shadcn pieces is sharp. Grabbed it for

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

🙌

Profilbild von Aditya Das
Aditya Dasvor 5 Tagen

is it technically "generation" tho? more like pick the right UI? 🤔

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

imagine a design system and a set of rules, it mixes both of them and picks the right thing and can fill in with some source/demo data. calling it jeverative (haha). check the architecture diagram in thread

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

Tighter and defined rules lead to more refined outputs.

Profilbild von Jonathan Moore
Jonathan Moorevor 5 Tagen

I got it down to 400ms

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

For small components, without much rules/styles to choose from- it is really fast

Profilbild von Ashish Singh
Ashish Singhvor 5 Tagen

Was discussing with @karrrtiiikkk how generative ui flows would be a possibility because of Jev.

Profilbild von EDDY VU
EDDY VUvor 5 Tagen

Using Mobbin MCP to establish the UI rules is super clever, how granular did you have to make that style file?

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

for now it just took some top fintech app references, for some complex queries Jev-only mode will throw an error. Jev+LLM might still be able to give something. Also, depending on your style filesize – Qwen has larger error rates but costs very less. Haiku does better outputs but costs more.

Profilbild von Kenneth Dsouza
Kenneth Dsouzavor 5 Tagen

@rohanchkrabrty Nice! Was thinking about this an hour back. I felt this would reduce hallucinations too and choose elements from the prescribed design system only.

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

@rohanchkrabrty yes. more rules and guidelines lead to better output. adding an llm to it is the most idea solution.

Profilbild von Kenneth Dsouza
Kenneth Dsouzavor 5 Tagen

@rohanchkrabrty So do you send the rules to jev in every request ?

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

@rohanchkrabrty not the entire rule set. based on prompt, a local code (or llm, in hybrid mode) does some filtering before passing on to Jev.

Profilbild von Kenneth Dsouza
Kenneth Dsouzavor 5 Tagen

@rohanchkrabrty This makes sense. In my today’s exploration, I choose to filter top 60 but it would make sense to add some logic filters prior to sending to Jev. But its definitely not as fast on my local app.

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 5 Tagen

@rohanchkrabrty what kind of logic filters are u passing? written md/schema

Profilbild von Kenneth Dsouza
Kenneth Dsouzavor 5 Tagen

@rohanchkrabrty I did like 5min work, not great. Just to explore how reliable Jev’s output is. Right now was just using top 60 tags from my bookmarking tag list. Ideally should send most relevant top tags for evaluation.

Profilbild von Alejandro Carbajo
Alejandro Carbajovor 5 Tagen

Same shape here, filling widgets instead of components. Two things bit me: options dilute (leader 0.99 -> 0.81 as I added them), and one extra sentence in a question dropped accuracy from 92% to 68%. Shortlist before Jev sees the library.

Profilbild von Arjun
Arjunvor 5 Tagen

Really neat demo!

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

🙌

Profilbild von ✦ Rahul Bhosale ✦
✦ Rahul Bhosale ✦vor 5 Tagen

boy is fast

Profilbild von Jeremy Bosma
Jeremy Bosmavor 5 Tagen

The style system is the real leverage

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

yes! Tighter rules lead to consistent outputs

Profilbild von Jeremy Bosma
Jeremy Bosmavor 4 Tagen

Exactly, less variance is the point

Profilbild von Soliman
Solimanvor 4 Tagen

The speed is impressive, but the style rules are doing more work than the model call. The useful next test is whether the generated interface stays coherent after several edits, not just whether the first screen looks right.

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

It can create some variations and live targetted edits. But prolly needs an LLM to do a lot of handholding

Profilbild von Asit
Asitvor 4 Tagen

You Sir, definitely need to do a closed door masterclass.

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

👀👀

Profilbild von Vedant
Vedantvor 5 Tagen

jeverative 🤣

Profilbild von Yashwin Ghosh
Yashwin Ghoshvor 5 Tagen

This is super cool! Had tried something similar with the components and slots for pages defined upfront, got really promising results, check it out :D

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

Reminds me of this. This one uses pure json schema shuffling (sensless shuffles)

Profilbild von 🇨🇦 Fauzul 📐🥑
🇨🇦 Fauzul 📐🥑vor 4 Tagen

Jev with component library is a good direction.

Profilbild von Nathalie 😻
Nathalie 😻vor 4 Tagen

reallly ? it's awesome

Profilbild von Brunex
Brunexvor 4 Tagen

It chooses from pre made components... its not really building something from scratch

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

that is the whole point of a model like Jev. it chooses fast, coz it doesnt have to build from scratch. And isnt it why libraries and DS exists in the first place?

Profilbild von ⚡️ nedzen.eth
⚡️ nedzen.ethvor 4 Tagen

did you put this on github ?

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

yes its private repo as of now.

Profilbild von Brjan | AI Builder
Brjan | AI Buildervor 4 Tagen

how does Jev handle edge cases or unique design requirements?

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

It simply cannot until there is a rule. Hence added a Jev+LLM composition which takes care of these cases

Profilbild von Denislav Jeliazkov
Denislav Jeliazkovvor 5 Tagen

@grok what is jev

Profilbild von James
Jamesvor 5 Tagen

Can you share the code?

Profilbild von COSMOS
COSMOSvor 4 Tagen

jv

Profilbild von Tushar Khairnar
Tushar Khairnarvor 4 Tagen

Generative ui is two tasks - choosing components + hierarchy and populating props - how are you able to do 2nd with JEV? first one is straightforward but getting JEV to fill-in values of props - is it JEV-only or llm layer does the population?

Profilbild von Rahul Chakraborty
Rahul Chakrabortyvor 4 Tagen

it populates from a mock data source in this demo. It needs a local code or llm to help do its job effectively

Profilbild von SummerLabs
SummerLabsvor 5 Tagen

Generating code at sub-second speed is trivial. The real cost is the inevitable accumulation of 'generated technical debt' that human maintainers have to untangle six months later.

Profilbild von Deepak Sethi 🇮🇳 ॐ
Deepak Sethi 🇮🇳 ॐvor 5 Tagen

UPI पर MDR चार्ज का असर व्यापारियों और ग्राहकों पर क्या हो सकता है? इस विषय एक छोटा सा इंटरव्यू जरूर देखिए और अपनी राय साझा कीजिए। 🙏 👇 पूरी बात यहाँ 🙏👆

Ähnliche Videos

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

194,422 Aufrufe • vor 5 Tagen