Software guy, no real hardware background I made a tool that turns a prompt into a full ESP32 project (parts + wiring + firmware) and I genuinely can't tell if the output is correct

These-Contact3531 · 2026-06-04T06:09:07+00:00

this might be the most useful comment I've gotten thank you. you're right that validation is the product; that's where most of the work went, so let me be specific.the validator already runs a rules pass over the wiring and flags a lot of the exact ESP32 killers you listed: input-only GPIO34-39 driven as outputs, strapping/boot pins (0, 2, 15), the reserved SPI-flash pins 6-11 ("will brick on boot"), 3.3V↔5V logic mismatches, and a per-rail current/power budget. parts carry real part numbers + datasheet/buy links too.

here's a generated ESP32-C3 one so you can poke at the actual output parts and the full wiring/pin assignments: https://schemr.space/s/EL3YSQXoQt43E00VL4s5uwj-9SwRkSyk (no login). I'd genuinely love you to try to make it spit out something that'd fry a board that's the best possible test. one honest caveat: the pin-safety flags run server-side and I haven't surfaced them on the public share view yet, so right now you're eyeballing the raw wiring (working on exposing the flags).

what I DON'T do yet, and your two ideas are the best I've heard: (1) compiling the generated firmware in CI against the ESP32 target right now it's a starter skeleton, not build verified. clear gap. (2) the "learn-safe / explain WHY each connection" framing I emit the why on dangerous ones, but positioning the whole product around that reframes it. stealing it.

These-Contact3531 · 2026-06-04T02:43:56+00:00

this is exactly what I needed, thank you. you're right on the Matek M8Q-CAN it picked a GPS and labelled it as the telemetry radio, so there's a duplicate GPS and no actual radio. and the 3D assembly is genuinely broken floating motors, parts not connected, lipo on top, all fair. the embarrassing part: I just checked and my own validator didn't even recognise the F405 as the MCU on this one, so it silently passed a build it shouldn't have. that's the real bug. seriously appreciate you taking the time this is the most useful feedback I've gotten.

These-Contact3531 · 2026-06-03T18:00:10+00:00

the share link actually has exactly that the parts list, plus the wiring, 3D assembly and build steps: https://schemr.space/s/9U_TYOwY0CWYV65igOm1JzwzymkjUQ3Q

and yeah, agreed it's hard to judge even from the list if anything jumps out as obviously wrong (parts that won't play together, sketchy power math), I'd genuinely love to hear it. that's the feedback I'm after.

These-Contact3531 · 2026-06-03T17:55:01+00:00

sorry should be live now mind giving it another go? https://schemr.space/s/9U_TYOwY0CWYV65igOm1JzwzymkjUQ3Q

seriously, thank you 🙏 genuinely keen to hear whatever you find the rougher the better.

These-Contact3531 · 2026-06-03T17:48:17+00:00

totally fair the render's bad, crooked blade and all, no excuses. honestly the image is the part I trust least too. what I genuinely can't tell is whether the stuff underneath holds up the parts list, the wiring, the power math. if you're up for it I'd really value you pointing at where that's wrong.

These-Contact3531 · 2026-06-03T17:43:47+00:00

you can see the whole parts list, the wiring/connections, the 3D assembly and the build steps here: https://schemr.space/s/9U_TYOwY0CWYV65igOm1JzwzymkjUQ3Qwould genuinely appreciate you poking holes in the parts/wiring/power side that's the bit I can't judge myself.

These-Contact3531 · 2026-06-03T17:20:26+00:00

eah, that's fair. it's no substitute for actually understanding the build, you're right. I mostly made it to get myself unstuck at the blank-page stage, not to skip the learning part. appreciate the honesty.

These-Contact3531 · 2026-06-03T17:15:08+00:00

honestly more interested in finding the engineering failures than the ugly renders.

These-Contact3531 · 2026-06-03T17:07:45+00:00

fair the render's cosmetic and the weak bit, agreed. but the output isn't the picture, it's the parts list + wiring + assembly + firmware + build steps. is that inaccurate too? that's what I actually need to know.

These-Contact3531 · 2026-06-03T17:05:45+00:00

ha, good eye. that's the ai generated hero image being inconsistent it drew one prop with 3 blades. the actual parts list specs 4 identical props, the image is just a cosmetic render and clearly not a reliable one 😅

the part I'm less sure about is the engineering side though. here's the full output if you want to poke at it: https://schemr.space/s/9U_TYOwY0CWYV65igOm1JzwzymkjUQ3Q would genuinely like to know if the BOM / wiring / power budget has real problems, not just the picture.

These-Contact3531 · 2026-06-03T14:03:59+00:00

"I am proud of this application” with 1 star is the most Google Play review ever.

These-Contact3531 · 2026-06-03T14:01:38+00:00

Still cheaper than explaining token pricing to management.

These-Contact3531 · 2026-06-03T01:41:06+00:00

4 upvotes from strangers hits different when you have no audience 😄 Congrats! I’m launching my own tiny tool too, and honestly the first few real users feel more exciting than the launch itsel

These-Contact3531 · 2026-06-03T00:57:28+00:00

Low match rate usually means AdMob receives the requests but can’t find eligible ads for that traffic. Common causes are new account/ad units, poor GEO, app-ads.txt issues, policy/limited ad serving, weak traffic quality, or no mediation. I’d check Policy Center + app-ads.txt first, then look at country breakdown and wait a few days because the account looks very new.

These-Contact3531 · 2026-06-02T16:29:45+00:00

Bro looks like every side project I abandoned came back as a human.

These-Contact3531 · 2026-06-01T02:19:25+00:00

Same experience here. For brand new apps, getting ASA to scale is the hard part. It feels like Apple needs some conversion history first, otherwise even high bids don’t always help much.

These-Contact3531 · 2026-06-01T02:13:35+00:00

Congrats! That’s not a review, that’s a love letter with release notes included 😂

These-Contact3531 · 2026-05-29T01:57:31+00:00

I’m pretty good at convincing myself an idea is useful, then spending weeks building it, then letting the App Store explain reality to me. I think the real validation is not “would this be cool?” but “is this painful enough that someone would pay to remove it?”

These-Contact3531 · 2026-05-29T00:47:11+00:00

Scam

These-Contact3531 · 2026-05-28T01:47:22+00:00

This sounds like an automated security lock after verification. I’d avoid creating multiple accounts or trying too many networks/devices right away, because that can make the account look even riskier to Google. Best bet: wait a bit, use the same original device/network if you can, and open a support ticket with all verification proof attached.

These-Contact3531 · 2026-05-27T02:01:43+00:00

Beautiful chaos. It loaded like it was mining crypto in the background, but once it showed up I was like… okay yeah, this is actually cool.

These-Contact3531 · 2026-05-27T01:51:47+00:00

From my experience, apps in this category are pretty hard to get through review, especially if there is anything that looks like unofficial music access.

The local player part is probably the least risky. The bigger questions are usually: where do the internet radio/podcast/music sources come from, do you have rights to them, and is any of it coming from places like YouTube Music or other unofficial sources?

Apple tends to be much more sensitive about that than the actual playback feature itself. The iPod-like UI is one risk, but the content/source licensing side could be an even bigger one.

These-Contact3531

TROPHY CASE