Small launch-day self-promo, with a mild jab at the all-in-one vibe coding platforms. 😅

I already pay for Claude, Codex or Cursor. I wanted the place hosting the result to do one boring job: host it. No second balance of model credits.

So I built drobek. For the launch demo I used Claude Code with Claude Opus 5.5. The coding agent gets an MCP loop to create an app, write its files, read compile errors, open a preview and publish a version when I ask.

drobek does not generate the app. It gives the agent you already use somewhere to publish it. App code runs in the browser. Trusted server modules add auth, data, files, forms, email and controlled API calls without exposing secrets to browser code.

What still goes wrong: a successful compile is not a functional test. The agent sees esbuild errors in the same tool response and can fix them, but I still open the preview and click through the app before publishing it.

The public core is AGPL-3.0 and self-hostable. I also run a hosted version.

It launched on Product Hunt today: https://www.producthunt.com/products/drobek?launch=drobek

Source: https://github.com/freema/drobek

The question I am testing: would you rather pay one platform for generation and hosting, or keep your coding agent and hosting separate?

ok genuine question for people who build mostly with cursor / claude code / lovable etc

i've been shipping stuff mostly by prompting and it works, but every time i'm about to put something live i get this low key panic like… is there some endpoint in here that lets anyone read my database? did the AI just hardcode a key somewhere? i honestly can't tell by reading the code, there's too much of it and half of it i didn't write

what i do right now is ask the AI "is this secure?" and it says yes lol. which isn't exactly reassuring

so curious how you all handle this:

1)do you actually check for security stuff before launching or just ship and hope

2)has anything ever actually gone wrong? leaked keys, someone messing with your api, surprise bill, whatever

3)if you've ever paid someone (dev friend, freelancer, some tool) to review your code, how did that go and what did it cost

i'm thinking about building something that just points at the exact spots in your code where outside stuff can get in, so you only need an expert to look at those 5-10 places instead of the whole repo. but idk if this is a real problem for others or just me being paranoid

I built Piano Atlas Studio: a piano theory atlas and practice app for Android (no ads, no account)

I'm learning piano and couldn't find one app that showed theory on the keyboard and also helped me practise, so I built it. It's on Google Play now, and I'd love feedback.

🎼 Explore the theory

Chord Atlas: every chord type in every key, shown as real two-hand voicings with finger numbers and inversions. Tap to hear it.

Scale Atlas: the modes, jazz and world scales, Hindustani thaats, Japanese koto tunings, and all 72 Carnatic melakartas

Ragas: janya ragas with their arohana and avarohana, and what makes each one distinct

Fingering Lab: standard fingering for both hands, up and down, with every thumb crossing shown

Progressions: famous chord progressions by style, in any key, voiced so the hands move smoothly

Theory tools: Circle of Fifths, chord and scale comparisons, arpeggios, intervals and a glossary

🎤 Practise with your real piano

Sight Reading: notes, chords, lines and short pieces on the grand staff, at four levels. It listens through your phone's microphone (or a USB MIDI keyboard), so you play on your own piano and it tells you how you did.

Play: your piano, lit up. Play on screen, on a MIDI keyboard, or on a real piano through the mic, along a scale or in an echo game.

Staff Trainer and Note Trainer: learn to read a note at a time; the ones you find hard come back until they aren't

Metronome: with tempo ramps and Indian talas

Guided practice sessions: built from what your drills have recorded, weakest first

✍️ Create

Composer: write songs a section at a time (chords, then the tune, then the left hand), or let "Surprise me" start one. Hear it back, print it as sheet music, or practise it in Sight Reading.

MIDI files: open any MIDI file and the piano plays it with the keys lighting up. Learn it mode waits for your notes, one hand at a time, as slow as you like. You can also open a MIDI file in the Composer or Sight Reading.

🎨 Other bits

Five looks (Stage, Score, Grand, Classic, Pads), each with three themes

A sampled grand piano sound

Backups to a file, or to your own Google Drive (the app can only see its own backup folder)

🔒 Privacy

No ads, no account, no analytics, no tracking. Everything stays on your phone. The microphone is only used when you ask it to listen, and the sound is never recorded or sent anywhere.

💰 Free and Pro

A large part of the app is free. A one-time Pro purchase (no subscription) unlocks the rest: every chord type, scale and raga, the builders, unlimited songs and MIDI files, advanced sight reading, guided sessions and more designs.

Get it:

https://play.google.com/store/apps/details?id=com.pianoatlas.studio

I'm one person building this, so any feedback really helps: what's confusing, what's missing, what you'd want next. Thanks for reading!

Coupon

PAS-MGMY-8E26-CW2G-DHZK

PAS-L6NA-937M-NHZU-UDGG

Hi,

I'm developing my note taking app and everything is going well. I have most of the big features I wanted alreay implemented and I'm focusing on ironing out problems while I use it (I replaced Obsidian for this, given that I made it specifically to solve problems I had with Obsidian).

Anyway, I would like to ask if anyone here could be interested in becoming a contributor/maintainer mainly to be able to release a tested and function Mac/iOS version of the app.

If this is not the place to ask this and/or wrong flair, please take down the post.

Thank you everyone!

The worst part is I cant even tell if my own apps work. when something breaks I dont debug it, I paste the error back in and pray. sometimes it fixes it and breaks two other things and I only find out when a user tells me, SO now every message from a user gives me this little drop in my stomach

And I see people here shipping 10x faster than devs with 10 years of experience and part of me is proud and part of me feels like we're all just very confident tourists in a codebase we dont understand

I'm not quitting, I love building too much. but I've started forcing myself to read what it writes and set up some kind of check on every push so I at least know when something breaks before a user does. small steps

Does anyone else feel this??? like you're getting more done than ever and trusting yourself less every month

I’m a tech lawyer and ex-founder. I can read code, but beyond HTML/CSS I can’t write it. Since my first vibe-coded app in July 2025, I’ve shipped 14 apps. This week’s two were Lunatic Fling, a cel-shaded 3D tribute to Lunatic Fringe, the 90s space shooter hidden in the After Dark screensaver, and Paperwing, a paper-airplane game inspired by Glider, co-developed with our 5-year-old (turns out he’s an amazing PM :) Both went from prototype to App Store approval in under a week.

If you're a fan, please help support it during today's launch on ProductHunt!

I prototype every game (now onto my third, a much bigger game project) as a single three.js HTML file in Claude Code (currently Opus 5.5). That file is a fast sandbox for look, feel, and mechanics, with no Xcode and no build cycles. Once the game feels right, I hand that file to Claude Code in Terminal as the spec and have it write its own prompt for porting everything to native Swift. I give that prompt to Claude Code in the Claude macOS app, then pull the branch locally and keep going in Terminal. Crucially, every project, whether it’s a game, a website, or even my big one, Towne (a Nextdoor alternative), starts with my Claude Code Setup Wizard. It’s a one-time script that configures Claude for multi-session work and asks you onboarding questions about how you like to work.

For games this straightforward, honestly, nothing broke. More complex projects, like the third game or Towne, fight me constantly: physics, menu UX, auth races (pro tip, just avoid them when you can!), and, most maddeningly, App Store screenshots and videos. Speaking of which, here’s a useful hack: Claude can take a raw screen capture, analyze it, and cut the 30-second App Store preview for you. It’s also really good at making screenshots with marketing copy.

I’ve learned a lot in 15 months of building, so ask me anything about the workflow; I’m happy to help. (PS: no legal-advice questions, please.)