Here's how I work with WeWeb ๐ค
You have a senior engineer: Claude at work 24/7. Then...
Why does an experienced design engineer still build in WeWeb?
"๐๐ฆ๐๐ฆ๐ฃ ๐ฐ๐ง๐ง๐ฆ๐ณ๐ด ๐ฎ๐ฆ ๐ข ๐ด๐ต๐ณ๐ถ๐ค๐ต๐ถ๐ณ๐ฆ๐ฅ ๐ฑ๐ญ๐ข๐ค๐ฆ ๐ต๐ฐ ๐ฃ๐ถ๐ช๐ญ๐ฅ. ๐ ๐ฌ๐ฏ๐ฐ๐ธ ๐ธ๐ฉ๐ฆ๐ณ๐ฆ ๐ฆ๐ท๐ฆ๐ณ๐บ๐ต๐ฉ๐ช๐ฏ๐จ ๐ช๐ด ๐ฅ๐ฆ๐ง๐ช๐ฏ๐ฆ๐ฅ ๐ช๐ง ๐ ๐ฏ๐ฆ๐ฆ๐ฅ ๐ต๐ฐ ๐ฑ๐ถ๐ต ๐ฎ๐บ ๐ฉ๐ข๐ฏ๐ฅ๐ด ๐ช๐ฏ ๐ช๐ต.โ ~ @jptrinhh
He shipped Carrousl in just over three weeks.
It's a photo library that turns your pictures into Instagram and TikTok carousels.
He builds in Claude Code, connected to WeWeb through MCP.
WeWeb handles frontend, backend, auth and database. Stripe for payments. Resend for email. Cloudflare for hosting.
Here's the playbook he has used to take 10+ apps from idea to production since he started working with the WeWeb MCP in Claude:
๐ญ. ๐๐ฒ๐๐ถ๐ด๐ป ๐ณ๐ถ๐ฟ๐๐. He uses Claude to pull references from Mobbin and create mockups in Paper, working out the spec before implementation.
๐ฎ. ๐๐๐ถ๐น๐ฑ ๐ถ๐ป ๐ช๐ฒ๐ช๐ฒ๐ฏ, ๐๐ถ๐ฎ ๐ ๐๐ฃ. He established a design system early, so Claude reuses existing tokens and no-code components.
๐ฏ. ๐๐ฑ๐ฑ ๐ฐ๐๐๐๐ผ๐บ ๐ฐ๐ผ๐บ๐ฝ๐ผ๐ป๐ฒ๐ป๐๐ ๐๐ต๐ฒ๐ฟ๐ฒ ๐ป๐ฒ๐ฒ๐ฑ๐ฒ๐ฑ. His image cropper, for example, lives in GitHub. He edits the code, pushes it, and syncs the component into WeWeb.
๐ฐ. ๐ฅ๐ฒ๐๐ถ๐ฒ๐ ๐ถ๐ป ๐๐ต๐ฒ ๐ฒ๐ฑ๐ถ๐๐ผ๐ฟ, ๐๐ต๐ฒ๐ป ๐๐ฒ๐๐. He checks the CSS and workflow logic before testing in preview and staging.
An isolated bug gets a manual fix.
An issue affecting several components goes back to Claude.
๐ฑ. ๐ฃ๐๐ฏ๐น๐ถ๐๐ต, ๐ฒ๐
๐ฝ๐ผ๐ฟ๐ & ๐๐ฒ๐น๐ณ-๐ต๐ผ๐๐. Publishing triggers an export, and Cloudflare rebuilds the app.
The agent does most of the building.
WeWeb gives JP an app editor to see it, fix it and decide what ships.
Hereโs Carrousl ๐
7
215
I was experimenting with self-hosting a fullstack WeWeb app: Cloudflare for the frontend and Coolify on a Hetzner server for the backend.
It works great (accommodations-map.jptrinh.cโฆ). So i wanted to push it further and it sparked an idea: a map of places I go to that are worth documenting.
This is the current starting point, an Airbnb-style layout and my MapLibre component. It's a place where I'll break things and design something personal!
I updated my signature pad component I made for @weweb_io
Instead of showcasing it as a simple white box I wanted to do something a bit different. So I built a photo annotation tool on top of it. Users can take a picture, draw on it and the annotation is saved onto the image.
The toolbar, colors, stroke and logic can be adapted to match your worfklows and design.
๐บ Full demo and breakthrough on Youtube in the comments!
Popups are everywhere in an app: confirming an action, showing product details, presenting a sign-in form... And you don't need to rebuild them from scratch every time. In this tutorial I go through the 3 features that turn popups into reusable building blocks in @weweb_io
๐บ Link in the comments
jp trinh retweeted
WeWeb is now a verified @claudeai Connector! ๐
Coding agents are democratizing the power to build across teams.
Thatโs great... until IT is left worrying about the security and maintainability of what gets shipped.
Thatโs where WeWeb MCP comes in ๐
I made a Calendar component for @weweb_io ๐
WeWeb as one you can use out of the box, but styling it the way I wanted was hard. So I built my own, based on shadcn.
Drop it flat on the page, behind a dropdown, or inside a popup. It allows for full customization of the behavior and the style to match your design system.
Link to the full video and to the demo in the comments
WeWeb released pre-rendering for pages. It makes building static pages relevant in WeWeb now that they can be properly indexed by search engines. In this video, I'm building a marketing page to see how WeWeb handles it. And I'm reviewing what Claude and the WeWeb MCP managed to build in one pass.
๐บ Link to the full video in the comments
Replying to @weweb_io
@weweb_io released pre-rendering for pages. It makes building static pages relevant in WeWeb now that they can be properly indexed by search engines. In this video, I'm building a marketing page to see how WeWeb handles it. And I'm reviewing what Claude and the WeWeb MCP managed to build in one pass.
๐บ Link to the full video in the comments
๐ฌ๐ผ๐๐ฟ ๐ฝ๐๐ฏ๐น๐ถ๐ฐ ๐ช๐ฒ๐ช๐ฒ๐ฏ ๐ฝ๐ฎ๐ด๐ฒ๐ ๐ฎ๐ฟ๐ฒ ๐ป๐ผ๐ ๐ฒ๐ฎ๐๐ถ๐ฒ๐ฟ ๐๐ผ ๐ฑ๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ ๐ฅณ
New public pages are ๐ฝ๐ฟ๐ฒ-๐ฟ๐ฒ๐ป๐ฑ๐ฒ๐ฟ๐ฒ๐ฑ by default. That means:
โก Faster page loads
๐ Better visibility on search engines like Google & Bing
๐ค More accessible to AI answer engines like ChatGPT, Claude, and Perplexity
Already have public pages? You can turn on pre-rendering under ๐๐๐๐ ๐๐๐ฉ๐ฉ๐๐ฃ๐๐จ โ ๐๐ง๐-๐ง๐๐ฃ๐๐๐ง๐๐ฃ๐.
I used the @weweb_io MCP to do 80% of the implementation: creating the popup, the design and the logic. And it can also fix backend errors with access to the logs. It allows me to jump in at the end with the polish that turns the experience from just working into something great!
Full video on YouTube in the comments ๐บ











