Image 1 — Ich baue einen Editor, das aus einer Beschreibung ein Modell aus echten, kaufbaren Teilen macht, und hätte gern vorher eure Meinung
Image 2 — Ich baue einen Editor, das aus einer Beschreibung ein Modell aus echten, kaufbaren Teilen macht, und hätte gern vorher eure Meinung

Ich baue einen Editor, das aus einer Beschreibung ein Modell aus echten, kaufbaren Teilen macht, und hätte gern vorher eure Meinung

Ich arbeite seit einer Weile allein an Brickcompose und will es hier zeigen, bevor die Seite richtig losgeht, weil mich interessiert, ob Leute, die selbst bauen, damit überhaupt etwas anfangen können.

Man schreibt, was man bauen will, zum Beispiel ein Alpenchalet mit dunkelrotem Dach, Balkon und Blumenbeeten, eine KI macht daraus einen groben Entwurf, und dann setzt eine eigene Engine das in echte Teile um. An dem zweiten Teil saß ich am längsten, weil die KI von sich aus nicht weiß, welche Steine es gibt. Die Engine prüft bei jedem Teil, ob es wirklich mit einem anderen verbunden ist, und nimmt nur Teile, die es in der Farbe seit 2010 in mindestens drei Sets gab, damit man die Liste bei Brick Owl auch zusammenbekommt. Raus kommen eine Bauanleitung Schritt für Schritt und eine Teileliste, das Chalet im Video hat 578 Teile in 49 Sorten.

Wer lieber selbst baut, bekommt einen Editor mit rund 40.000 Teilen in 3D, die Suche geht auf Deutsch und Englisch, und Studio- und LDraw-Dateien lassen sich öffnen und weiterbauen.

Häuser und Burgen klappen inzwischen gut, bei Fahrzeugen und allem Runden bin ich mir noch nicht sicher, der Traktor hat mehrere Anläufe gebraucht und überzeugt mich bis heute nicht ganz. Was mich am meisten interessiert: würdet ihr so ein Modell nachbauen, oder liegt der Spaß für euch gerade im Selbst-Entwerfen?

Die Beispielmodelle kann man auf brickcompose.com drehen und durchblättern, auch ohne sich einzutragen.

u/wwwery-good-apps — 6 days ago
▲ 0 r/vercel

Weekly price decay on a Vercel Cron, and the part I got wrong the first time

I built a page that sells one ad slot per week, and the only technically interesting part is that the price falls continuously until someone pays, so the whole thing turned out to be a cron job and a price function rather than a checkout flow.

The cron runs hourly and my first version had it write the current price into the database, which felt natural and was wrong. Vercel Cron is best effort, not a guarantee, and a missed run left a stale price sitting on the page while Stripe still had the amount from the last successful write. Two numbers, one truth, and no way to tell from the outside which one was real.

What I do now is derive the price from the elapsed time on every request and store nothing, with the cron only responsible for the week rollover. A missed run costs me a late rollover, which is visible and annoying, instead of a wrong price on a live payment, which is neither.

The other thing that caught me was the week boundary, because a week is a business concept and not a UTC one, and I had the rollover firing at a moment that landed on a different weekday depending on where the visitor was sitting. Not fully sure my current fix is right either, I pinned everything to one timezone and display it explicitly, but I suspect that just moves the confusion somewhere else.

It's at [droptick.io](https://droptick.io/?utm\_source=reddit&utm\_medium=vercel) if you want to watch the curve move, it updates while the page is open. The idea itself may well be bad, week one's numbers suggest the starting price is far too high, but the cron part I would build the same way again.

u/wwwery-good-apps — 1 month ago

I got curious and pulled about a year of this subreddit into a spreadsheet. Almost half the posts here get zero comments, and it has very little to do with the product.

This started because I kept scrolling past launch posts that had been up for hours with not a single reply, and I wanted to know if that was normal or if I was just catching bad days.

It's normal. Out of roughly a year of posts, just under half got zero comments, none at all. And for the ones that did get a reply, the median was around fifteen minutes to the first one, which basically means if nothing happens in that first quarter of an hour your post is already gone, buried under the next batch of "I built X" that showed up while you were still refreshing.

What actually got traction surprised me. It wasn't the launches or the clean wins. The posts that pulled hundreds of comments were the honest messes, someone who put 300k into a healthcare app nobody used got something like 700 replies, a solo founder breaking down 20k MRR with no ad spend did huge numbers. And the single biggest thread I came across, over a thousand comments, was just a guy saying he had 180k in software budget expiring in six weeks and asking what to spend it on. That one stuck with me, it's about the only post in the whole pile that reads like an actual buyer instead of a seller, and the room went wild for it.

The "drop your SaaS" threads are their own thing, they look busy with four or five hundred comments but it's all founders dropping links at each other, everyone posting and nobody really reading, and I doubt a single real customer ever walked out of one of those.

I don't fully know why the failure stories beat the wins by this much. My rough guess is everyone here has shipped something that went nowhere and almost nobody has shipped the big success, so the flop is the thing people actually recognize themselves in. Either way, if you have a launch queued up for tomorrow, the numbers are kind of brutal about it, the scar travels and the screenshot doesn't.

reddit.com
u/wwwery-good-apps — 3 months ago

I got curious and pulled about a year of this subreddit into a spreadsheet. Almost half the posts here get zero comments, and it has very little to do with the product.

This started because I kept scrolling past launch posts that had been up for hours with not a single reply, and I wanted to know if that was normal or if I was just catching bad days.

It's normal. Out of roughly a year of posts, just under half got zero comments, none at all. And for the ones that did get a reply, the median was around fifteen minutes to the first one, which basically means if nothing happens in that first quarter of an hour your post is already gone, buried under the next batch of "I built X" that showed up while you were still refreshing.

What actually got traction surprised me. It wasn't the launches or the clean wins. The posts that pulled hundreds of comments were the honest messes, someone who put 300k into a healthcare app nobody used got something like 700 replies, a solo founder breaking down 20k MRR with no ad spend did huge numbers. And the single biggest thread I came across, over a thousand comments, was just a guy saying he had 180k in software budget expiring in six weeks and asking what to spend it on. That one stuck with me, it's about the only post in the whole pile that reads like an actual buyer instead of a seller, and the room went wild for it.

The "drop your SaaS" threads are their own thing, they look busy with four or five hundred comments but it's all founders dropping links at each other, everyone posting and nobody really reading, and I doubt a single real customer ever walked out of one of those.

I don't fully know why the failure stories beat the wins by this much. My rough guess is everyone here has shipped something that went nowhere and almost nobody has shipped the big success, so the flop is the thing people actually recognize themselves in. Either way, if you have a launch queued up for tomorrow, the numbers are kind of brutal about it, the scar travels and the screenshot doesn't.

reddit.com
u/wwwery-good-apps — 3 months ago
▲ 29 r/KI_Welt+4 crossposts

I open-sourced the Bricks MCP server — 105 tools, full page building from AI prompts

Three months ago I shared a demo of the Bricks API Bridge here and the response kind of caught me off guard — 40 comments, almost 100 shares, people asking when they could try it themselves. Took a while to clean things up for public release, but here it is.

The whole system is now on GitHub under MIT. Plugin and MCP server, everything you need to connect Claude Code or Cursor directly to your Bricks site.

In the video I'm dropping a screenshot of a design into Claude Code and it builds the full page live — structure, styling, GSAP animations, the works. About 10 minutes from prompt to published page, no drag and drop involved.

What grew since February: started at 37 tools, now sitting at 105. Added a full SEO toolkit with auto-fix and bulk updates, a backup system with named snapshots so you can roll back if the AI gets creative, BEM component generation, multi-site switching so you can jump between staging and production mid-conversation, and batch operations that push up to 20 changes in a single API call.

The stack is pretty minimal — MCP SDK, the REST API plugin for WordPress, and Bricks Builder doing the rendering. Three npm dependencies total. Setup takes about five minutes if you already have Bricks running.

What I've been using it for mostly is client handoff pages — the kind where you'd normally spend two hours arranging testimonial grids and pricing tables. That part is genuinely fast now. The delta updates are probably the feature I underestimated most, being able to surgically change one heading without touching the rest of the page saves a lot of back-and-forth.

Not sure how many people here are already working with MCP servers, curious what your setup looks like if you are.

GitHub: https://github.com/developer2013/bricks-mcp-open

u/wwwery-good-apps — 2 months ago

I open-sourced the Bricks MCP server — 105 tools, full page building from AI prompts

Three months ago I shared a demo of the Bricks API Bridge here and the response kind of caught me off guard — 40 comments, almost 100 shares, people asking when they could try it themselves. Took a while to clean things up for public release, but here it is.

The whole system is now on GitHub under MIT. Plugin and MCP server, everything you need to connect Claude Code or Cursor directly to your Bricks site.

In the video I'm dropping a screenshot of a design into Claude Code and it builds the full page live — structure, styling, GSAP animations, the works. About 10 minutes from prompt to published page, no drag and drop involved.

What grew since February: started at 37 tools, now sitting at 105. Added a full SEO toolkit with auto-fix and bulk updates, a backup system with named snapshots so you can roll back if the AI gets creative, BEM component generation, multi-site switching so you can jump between staging and production mid-conversation, and batch operations that push up to 20 changes in a single API call.

The stack is pretty minimal — MCP SDK, the REST API plugin for WordPress, and Bricks Builder doing the rendering. Three npm dependencies total. Setup takes about five minutes if you already have Bricks running.

What I've been using it for mostly is client handoff pages — the kind where you'd normally spend two hours arranging testimonial grids and pricing tables. That part is genuinely fast now. The delta updates are probably the feature I underestimated most, being able to surgically change one heading without touching the rest of the page saves a lot of back-and-forth.

Not sure how many people here are already working with MCP servers, curious what your setup looks like if you are.

GitHub: https://github.com/developer2013/bricks-mcp-open

reddit.com
u/wwwery-good-apps — 5 months ago

Made an iOS pantry tracker to stop throwing food away. $2.99 one-time, no subscription.

Spent the last few months building this for myself because every existing pantry app I tried wanted a monthly subscription for what is basically a date reminder.

Fridoo lets you scan a barcode, set an expiry date, and get a notification before the item goes bad. Product info comes from OpenFoodFacts so I didn't have to build a product database from scratch, and only the barcode number leaves the phone, everything else stays local. Color-coded list at a glance, swipe items as consumed or wasted to track your actual eating-versus-bin ratio.

Built in SwiftUI with SwiftData, optional iCloud sync goes through the user's own Apple account so there is no Fridoo server to leak. Works in English, German, Spanish, and French with live in-app switching.

It is $2.99 one-time on the App Store, no IAP, no subscription. Happy to answer anything about the architecture or the OpenFoodFacts integration.

u/wwwery-good-apps — 5 months ago

Spent the last few months building this for myself because every existing pantry app I tried wanted a monthly subscription for what is basically a date reminder.

Fridoo lets you scan a barcode, set an expiry date, and get a notification before the item goes bad. Product info comes from OpenFoodFacts so I didn't have to build a product database from scratch, and only the barcode number leaves the phone, everything else stays local. Color-coded list at a glance, swipe items as consumed or wasted to track your actual eating-versus-bin ratio.

Built in SwiftUI with SwiftData, optional iCloud sync goes through the user's own Apple account so there is no Fridoo server to leak. Works in English, German, Spanish, and French with live in-app switching.

It is $2.99 one-time on the App Store, no IAP, no subscription. Happy to answer anything about the architecture or the OpenFoodFacts integration.

u/wwwery-good-apps — 6 months ago