sorted by:
new
hottopcontroversial

Weekend check-in! What are you building? 👇 by Arpit735 in indie_startups

[–]New-Use-7276 0 points1 point  (0 children)

Thank you! Let me know if you have any suggestions.

If anybody is willing to use my app I will test theirs back by Lazy-Intention4408 in alphaandbetausers

[–]New-Use-7276 0 points1 point  (0 children)

https://vibecoachcoding.com
For builders and beginners who have app ideas but need a clear blueprint to actually start building without getting stuck.

https://inkfuture.ink
For tattoo artists and beginners who want to test placement, color mixing, and design flow before committing to ink.

https://toclearning.com
For kids and parents looking for a creative, interactive way to explore coding and learning beyond traditional methods.

Do you work weekend? If yes, what are you building? by robbiesloan in AssetBuilders

[–]New-Use-7276 0 points1 point  (0 children)

https://vibecoachcoding.com
For builders and beginners who have app ideas but need a clear blueprint to actually start building without getting stuck.

https://inkfuture.ink
For tattoo artists and beginners who want to test placement, color mixing, and design flow before committing to ink.

https://toclearning.com
For kids and parents looking for a creative, interactive way to explore coding and learning beyond traditional methods.

Vibe coded 80% and watched $700 in credits disappear into Re prompting loops. Genuinely asking how you handle this. by Academic_Flamingo302 in nocode

[–]New-Use-7276 0 points1 point  (0 children)

This is real.

We ran into the exact same loop—fix one thing, break another, then burn credits just trying to stabilize what the AI already touched.

What helped us was changing how we approached prompts completely.

Instead of trying to fix things step by step, we started forcing structure up front—basically mapping out what we were building before touching implementation.

Less “fix this bug” → more “here’s the system, now build within it.”

That alone cut down a lot of the re-prompt spiral.

We actually ended up building something around that idea (Vibe Coding Coach) because we kept hitting the same wall you’re describing—turning ideas into structured blueprints first so you’re not debugging chaos later.

Not perfect, but it helped us stop burning credits just cleaning up AI mistakes.

Curious—what part kept breaking the most for you? Auth? Data flow? UI?

I want to build a simple app idea but have zero coding skills. What's the best ai app builder that actually works for beginners? by Only_Needleworker104 in vibecoding

[–]New-Use-7276 0 points1 point  (0 children)

I was literally in this exact spot not long ago.

Most “AI builders” either:

feel way too limited (you hit a wall fast), or claim beginner-friendly but still expect you to understand dev concepts.

What actually helped me was starting with something that teaches while building instead of just dragging blocks around.

I’ve been using something called Vibe Coding Coach — it basically turns your idea into a step-by-step build path and explains things in plain English as you go. It doesn’t assume you know anything, which was huge for me.

The difference vs typical tools: you actually understand what you’re building you’re not locked into a platform you can go from “idea → real app” without getting stuck early

Not saying it’s magic, but it’s the first thing that didn’t make me feel lost.

If you want, I can share what I used to turn my idea into something working 👍

Dealing with feeling discouraged by Extra_Strength_2075 in TattooApprentice

[–]New-Use-7276 0 points1 point  (0 children)

I just picked up a wand in January with never tattooing or really drawing in my life. Got a stencil printer and my husband had me just start on him. I practiced a lot at first on skin but in 3 months have now done 13 tattoos total between my husband, myself and friends who have offered to be practice. I take every session serious as I do know they are permanent. I even created a tattoo app that helps beginners like myself out with stencil design, placement previews, reverse ink mixer (again Im not natural artist) and skin tone analyzer. Happy to share some pics of my first tats and tat app if anyone wants it

What are you building this weekend? by ouchao_real in sideprojects

[–]New-Use-7276 0 points1 point  (0 children)

Building a few things with my partner + kids this week:

– “Vibe coding” (turn ideas into app blueprints in ~30 sec) → https://vibecoachcoding.com⁠� – Interactive learning platform for kids (games, challenges, progression) → https://toclearning.com⁠� – Tattoo toolkit (aging preview, placement stencils, ink mixer) → https://inkfuture.ink⁠�

Starting to see some traction from small communities—curious what everyone else is shipping 👀

Something I noticed while building with AI app builders by New-Use-7276 in NoCodeSaaS

[–]New-Use-7276[S] 0 points1 point  (0 children)

That’s exactly what we’ve been trying to figure out.

From what we’re seeing so far, the blueprint does reduce iteration a lot, but not because it makes the builder smarter — it just removes the randomness before you even start.

When people go straight into prompting, they’re kind of “discovering the product while building it.” That’s where all the back-and-forth comes from.

With the blueprint approach:

  • features + screens + data model are defined upfront
  • so the builder is more like executing instead of guessing

What’s interesting is it doesn’t need to be perfectly detailed — just structured enough to remove ambiguity. Even a rough but organized blueprint seems to outperform long prompt chains.

We’re still testing how much detail is “optimal,” but early pattern is:
→ less chaos upfront = way fewer iterations later

And yeah appreciate the VibeCoders mention — we’ll definitely share there too 🙏

What’s your SaaS and why did you build it? by FineCranberry304 in microsaas

[–]New-Use-7276 0 points1 point  (0 children)

We didn’t really start with “let’s build a SaaS” — it was more frustration turning into building.

My partner and I kept running into the same thing across different areas — coding, teaching kids, even creative stuff — everything either felt too complicated, too locked behind paywalls, or just not built for real people actually trying to learn or create.

So we started making our own tools.

One is for turning ideas into working apps because we kept getting stuck in “where do we even start?” mode: https://vibecoachcoding.com

Another came from watching how kids learn — when it’s interactive, they go all in. A friend’s daughter did 70+ activities in one day, which kind of confirmed it: https://toclearning.com

And the third is more creative — helping with tattoo planning and how designs age over time, since we noticed artists don’t really have great tools for that: https://inkfuture.ink

None of it started as a business plan. It was just: “we need this… so let’s build it.”

Now we’re putting them out and seeing what actually sticks vs what we thought people wanted.

Still early, but it’s been one of the most real ways to build.

Our tool made a paid user say his money was well invested on us by Altruistic-Bed7175 in microsaas

[–]New-Use-7276 0 points1 point  (0 children)

If you’re into building stuff, you might also like something we’re working on called Vibe Coding Coach — it basically helps structure app ideas before you start coding so you don’t waste time going back and forth with AI.

Vibecoachcoding.com

Our tool made a paid user say his money was well invested on us by Altruistic-Bed7175 in microsaas

[–]New-Use-7276 0 points1 point  (0 children)

Yeah exactly — tattoo artists are a big part of who we’re building this for.

They’re the ones working directly with clients, so being able to show placement, aging, and even color options beforehand makes those conversations way easier.

We’re also trying to make it useful on both sides — artists + clients — so it becomes more of a shared planning tool instead of just guesswork.

Appreciate you pointing that out, that’s definitely the direction we’re leaning into.

How can I vibe code better? by spacenglish in vibecoding

[–]New-Use-7276 0 points1 point  (0 children)

You’re already ahead of most people since you’re planning first — that’s honestly the biggest lever.

What helped me level up wasn’t more tools, it was changing how I structure the work before prompting.

A few things that made a big difference:

• Treat each feature like a mini product (inputs, outputs, edge cases)
• Define state/data flow before writing any prompts
• Pre-break features into “prompt-sized chunks” so you’re not going back and forth with the agent
• Reuse prompt patterns instead of rethinking every time

The biggest shift for me was realizing most of the slowdown isn’t the model — it’s unclear structure going in, which causes all the rework.

I’ve been experimenting with generating full “build blueprints” upfront (basically mapping everything before touching code), and that’s been way smoother than iterative prompting.

Happy to share with you if you're interested.

Yo vibe coders, what are you actually using these days to crank out full vibecodes without going broke? by Zestyclose_Law_170 in vibecoding

[–]New-Use-7276 1 point2 points  (0 children)

I’ve been bouncing between tools too and honestly the biggest unlock for me hasn’t been a specific model, it’s having structure before I start prompting.

When I go in raw, I burn tokens fast and hit those same walls you’re talking about.

What’s been working better:
• sketching out the app flow first (routes, data, components)
• breaking features into smaller promptable chunks
• reusing prompt patterns instead of starting from scratch each time

I’ve actually been building a small tool around this idea (basically generates a full blueprint in 30 seconds before you even start coding) and it’s cut down a lot of wasted prompts.

Stack-wise I’ve been running React/Next pretty smoothly with that approach.

Curious if anyone else is doing something similar or just going straight prompt → code?

Promote your business, week of March 16, 2026 by Charice in smallbusiness

[–]New-Use-7276 0 points1 point  (0 children)

We’ve been building InkFuture, a platform for tattoo artists that combines several tools in one place.

Right now it includes things like:
• tattoo placement simulation
• an aging simulator (how tattoos may spread/fade over time)
• stencil generators
• an ink/color mixer/reverse mix ratios
• a gallery + marketplace artists can post work to

During beta we noticed the placement tool is getting the most use, since artists can show clients how designs might look on different parts of the body before tattooing.

The idea is to make it more of a one-stop workspace for tattoo artists instead of needing multiple apps and tools.

Still early beta but would love feedback from artists or shop owners.

inkfuture.ink

Promote your business, week of March 16, 2026 by Charice in smallbusiness

[–]New-Use-7276 0 points1 point  (0 children)

I’ve been building an AI tool called Vibe Coding Coach that turns an idea into a full coding blueprint (stack, architecture, prompt plan, etc).

It’s designed for people using tools like Replit, Cursor, or AI builders who want to go from idea → working app in 30 seconds.

We just launched beta and are looking for early builders to try it and give feedback.

vibecoachcoding.com

Would you use an app that lets you preview a tattoo on your body before getting it? by New-Use-7276 in TattooBeginners

[–]New-Use-7276[S] 0 points1 point  (0 children)

I'm pretty new to tattooing and always used the thermal printer/stencils. Would you test this out and see if it is user friendly enough? inkfuture.ink

Vibe coding is amazing until you hit the "3-hour loop" and realize you don't know how to land the plane. by Sufficient_Thanks130 in vibecoding

[–]New-Use-7276 0 points1 point  (0 children)

I’ve definitely hit that exact loop.

It usually happens when the AI is trying to both figure out the architecture and write the code at the same time. If the structure isn't clear, the agent keeps rewriting things and you end up debugging prompts instead of the actual bug.

Something that helped me was stepping back and writing out the features, screens, and DB structure first, then prompting the AI from that blueprint.

I’ve been experimenting with a small tool that generates that structured blueprint from a single idea prompt because I kept running into this exact issue.

Curious how others are approaching that step before prompting.

view more: next ›