Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 5 дней назад •via X (Twitter)

Комментарии: 46

Фото профиля Juraj Ivan @ QikBuild
Juraj Ivan @ QikBuild5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

🙌

Фото профиля Aditya Das
Aditya Das5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

Tighter and defined rules lead to more refined outputs.

Фото профиля Jonathan Moore
Jonathan Moore5 дней назад

I got it down to 400ms

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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

Фото профиля Ashish Singh
Ashish Singh5 дней назад

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

Фото профиля EDDY VU
EDDY VU5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

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.

Фото профиля Kenneth Dsouza
Kenneth Dsouza5 дней назад

@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.

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

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

Фото профиля Kenneth Dsouza
Kenneth Dsouza5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

@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.

Фото профиля Kenneth Dsouza
Kenneth Dsouza5 дней назад

@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.

Фото профиля Rahul Chakraborty
Rahul Chakraborty5 дней назад

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

Фото профиля Kenneth Dsouza
Kenneth Dsouza5 дней назад

@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.

Фото профиля Alejandro Carbajo
Alejandro Carbajo5 дней назад

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.

Фото профиля Arjun
Arjun5 дней назад

Really neat demo!

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

🙌

Фото профиля ✦ Rahul Bhosale ✦
✦ Rahul Bhosale ✦5 дней назад

boy is fast

Фото профиля Jeremy Bosma
Jeremy Bosma5 дней назад

The style system is the real leverage

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

yes! Tighter rules lead to consistent outputs

Фото профиля Jeremy Bosma
Jeremy Bosma4 дней назад

Exactly, less variance is the point

Фото профиля Soliman
Soliman5 дней назад

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.

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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

Фото профиля Asit
Asit4 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

👀👀

Фото профиля Vedant
Vedant5 дней назад

jeverative 🤣

Фото профиля Yashwin Ghosh
Yashwin Ghosh5 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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

Фото профиля 🇨🇦 Fauzul 📐🥑
🇨🇦 Fauzul 📐🥑5 дней назад

Jev with component library is a good direction.

Фото профиля Nathalie 😻
Nathalie 😻4 дней назад

reallly ? it's awesome

Фото профиля Brunex
Brunex4 дней назад

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

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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?

Фото профиля ⚡️ nedzen.eth
⚡️ nedzen.eth4 дней назад

did you put this on github ?

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

yes its private repo as of now.

Фото профиля Brjan | AI Builder
Brjan | AI Builder4 дней назад

how does Jev handle edge cases or unique design requirements?

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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

Фото профиля Denislav Jeliazkov
Denislav Jeliazkov5 дней назад

@grok what is jev

Фото профиля James
James5 дней назад

Can you share the code?

Фото профиля COSMOS
COSMOS4 дней назад

jv

Фото профиля Tushar Khairnar
Tushar Khairnar4 дней назад

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?

Фото профиля Rahul Chakraborty
Rahul Chakraborty4 дней назад

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

Фото профиля SummerLabs
SummerLabs5 дней назад

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.

Фото профиля Deepak Sethi 🇮🇳 ॐ
Deepak Sethi 🇮🇳 ॐ5 дней назад

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

Похожие видео

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

199,392 просмотров • 5 дней назад