Vibecoding is dangerously addicting
Last week I built 12 apps
Most of them took 1-2 prompts
with @rork + Opus 4.5
But here’s what really matters
In the next prompt,
you make it completely your own:
→ your own taste
→ your own positioning
→ tailored to your niche
But we both already know something
That’s not how you end up making millions
Those $10M apps didn’t just get lucky
Their onboarding & app loops
are years of trial and error
The real game is focus:
→ Pick 1-2 validated App ideas
→ Add your own taste + positioning
→ Then scale them aggressively
So why waste time and money
rediscovering what already works?
So I made a decision
Only 1 new app as I scale my others
“Flow State”
I’ll be building and scaling this one
in public
Next post:
Update #3
Holy sh*t.
Gemini can now produce fully interactive images on any topic.
Such an insane resource for learning → highlight any region, and it gives you a full explanation 🤯
Gemini 3's hidden power = Awesome UI Animator
It actually contains good knowledge around popular animation libraries
You just need right prompt spec + process to unlock it
Here is my process 🧵👇
Vibe design is finally here.
I’ve spent the past few days playing around with Stitch (from @GoogleLabs) and I think we can finally generate designs that don’t suck.
Watch me prompt a UI design, edit with Nano Banana Pro, translate it to code, and then deploy on AI Studio 👇
UI/UX Designers, you can now access a complete set of mobile UI components without starting from scratch.
I found this amazing resource called Wise Design System, it’s one of the cleanest UI components collection out there and well documented from action buttons to pulldown menus. Each component comes with anatomy, states & behavior, plus design do’s and don’ts to guide you.
Bookmark it for later 💜
The "Coding With AI Course" is coming along. I am scripting everything out and starting to record. This will be a very comprehensive course with a solid workflow that you can use in your own projects with prototyping, custom commands, subagents, context files, etc.
I mainly use Claude Code, but explain things in a way where you can implement in your own tool (Cursor, Codex, etc).
It should be ready in January. Here is the cirriculum so far. I just started section 12 We are building a tool called Devstash, which I will actually be launching as a real product.
Meet Gemini 3 Flash, now available in Figma Make
Some things to know:
→ Explain the functionality you want in clear, specific language
→ If reproducing Figma design frames, try attaching the frame in multiple sections
→ It’s exceptionally quick, returning most prompt results in 30-60s
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
FRONTEND JOBS ARE GONE
UI/UX designers, get on Cursor. The future is changing fast, a new reality is here, and you don’t want to be left behind. Start with the free plan, learn MCP, convert your designs to code, and edit them in Cursor.
We’re not there yet, but soon, you won’t be a designer if you can’t code with AI.
🧵 1/5 Important Update: S3 buyback Wrap-Up, airdrop and S4 buyback update
We're excited to share some key milestones and upcoming plans for $ASTER buybacks.
S3 Buybacks is now completed: We've successfully executed all buybacks for S3, 55,720,650 $ASTER tokens were bought back. Total buyback to date now stands at 155,720,656 $ASTER, strengthening our token's value and rewarding our holders.
Buyback addresses:
https://t.co/NybEdyCRNM
https://t.co/Yw6qter8Uh
You're a frontend dev. You just built a killer UI.
Now you're stuck.
You need a backend. You need a database. You need user auth. And that "weekend project" just became a 3-month infrastructure nightmare.
You think, "I need a server, an RDS instance, I need to write 50 Express routes for CRUD, I need to implement JWTs, bcrypt, password reset..."
This is the exact moment 90% of indie projects die.
For years, the answer was Firebase. But that meant getting locked into a NoSQL world (Firestore) that's not always the right fit.
Today, I really dove into Supabase, and I'm stunned. It’s the open-source alternative built on the one thing we all trust: Postgres.
I was expecting just a database. What I got was a production-ready, scalable backend in minutes.
Here was my journey:
Level 1: The Database API
I created my project. Supabase gives you a full, grown-up Postgres database.
I went to the SQL Editor and created a table: `create table posts (...)`.
The second I saved it, Supabase instantly and automatically generated a full RESTful API for it.
My `GET /posts` and `POST /posts` endpoints just... existed. I didn't write a single line of backend code.
Level 2: The Auth (and the real genius)
I needed user sign-ups. This is usually the part I hate.
I clicked the "Auth" tab. It just handles it. Google, GitHub, email/password, magic links... it's all there.
But here is the genius part. It’s not separate from the database. It's built on it using Postgres's Row Level Security (RLS).
I wrote ONE simple SQL policy:
`create policy "Users can only see their own posts."
on posts for select
using ( auth.uid() = author_id );`
And that's it. My API was secure. Supabase's API automatically enforces this. No more `if (https://t.co/NAFMfNoARo !== https://t.co/9w1bCxVuKL_id)` logic in my backend. It’s handled at the database layer.
Level 3: The "Wait, what?" Features
- Storage: "I need users to upload profile pictures." Click "Storage." It's an S3-compatible bucket, already hooked into your RLS policies.
- Realtime: "I want to show a 'New Post!' notification." Click "Realtime." Now I can subscribe to any change in my database *instantly*. No websockets, no setup.
Level 4: The "Pro Escape Hatch" (What I Used Today)
This is what sold me. The auto-generated API is great, but I needed custom logic.
My Problem: "When a new user signs up, I need to call the Resend API to send them a welcome email."
My old workflow: Spin up a separate Vercel function, figure out webhooks, manage API keys... it's a mess.
My new workflow:
1. I wrote a Supabase Edge Function. It's just a TypeScript file using Deno that lives right in my Supabase project.
2. The function's code was simple: pull the new user's email from the request and `fetch` the Resend API.
3. I deployed it.
4. I told Supabase to trigger this function as a webhook every time a new row is inserted into the `auth.users` table.
The entire process took 10 minutes.
My custom backend logic is now serverless, deployed globally, and co-located with my database.
Supabase isn't a "toy" BaaS. It's an insane accelerator built on top of pro-grade, open-source tools. It’s the first platform that feels like it’s helping me, not limiting me.
It's the cheat code to go from frontend to full-stack.