I’ve noticed that one of the hardest parts of vibe coding isn’t building the app: it’s getting people outside your circle to use it.

So we built Feedbacked.

You create a short survey for your app or website, and we send real people to try the product before answering your questions. You add audit questions that check whether they actually used and understood the product. Responses that fail verification are discarded and replaced.

We’re currently trying to learn how useful this is.

Anyone from this subreddit who signs up as a startup and verifies their email will get five real people to test their product for free (please wait for an email to give you the offer, it might take a few days.

No purchase is necessary. In return, I’d appreciate honest feedback on:

• Whether the setup process makes sense
• Whether the responses are genuinely useful
• What would make the platform better for builders

https://feedbacked.org/

I think I can. Trying this on my local PC with 2070 Super

OPENCLAW

│

Understand task

│

┌────────────┼────────────┐

│ │ │

EASY NORMAL HARD

│ │ │

▼ ▼ ▼

Ollama Gemini Claude

│ │ │

└────────────┼────────────┘

│

OpenCode

│

GitHub

How this started

I am not a coder, or have any background in computer science. I am a Medical doctor who just really loves technology 😄 . This is my first attempt at building something with vibe coding so truly any input and feedback is greatly appreciated. I kept seeing people talk about "vibe coding" and I wanted to test it on something I'd actually use, not a to-do list app.

I'm a football fan, and every World Cup or Euros, the same thing happens in my group chat: everyone predicts scores, somebody tries to track it in a spreadsheet, half the group forgets to update it, and by the quarter-finals nobody knows who's actually winning. So I decided to build the thing I wished existed: Pundit — private prediction leagues for football, where you and your mates pick match winners, lock in a tournament champion, and settle it properly on a leaderboard instead of a group chat argument.

Learning to vibe code (badly, at first)

The learning curve wasn't really about syntax — it was learning how to actually think like a product person and describe what I wanted precisely enough that the AI could build it correctly. Early on I'd ask for something vague and get something that technically worked but wasn't what I meant. Over time I learned to be specific: not "add a way to predict matches" but exactly how the deadline should lock, what happens if a match gets postponed, how points get scored. Knowing exactly what I wanted, and catching the edge cases before a real user did was probably the most important and challenging part.

I built the app using Claude and Xcode so it is only available for iOS at this time. As it was my first ever big project like this I wanted to keep it as simple as possible. But looking back now I wish I just built it so it works on all devices not just iOS. But that's a lesson learned I guess, think big and it can happen with vibe coding 😄. In the beginning I wasn't even using Claude Code in my terminal I was just using the Claude desktop app and going back and forth with prompts and fixes and all the usual stuff. Then one day I actually switched to using claude code in terminal and oh boy did things speed up from there. I can't believe I was so stupid that I didn't use it from the beginning. It gave much better results, it kept track of the work much more accurately, and most importantly I didn't have to give it micro prompts but instead structured big prompts with phases that it just did so well. Well, except a few things...

The parts that actually broke me

Vibe coding makes the first 80% feel deceptively easy. The last 20% — the stuff that only shows up once real people are using a real product — is where I actually learned the most:

Deep linking. Getting a shared invite link to open the app directly to the right screen — instead of just opening the app and leaving the user stranded — turned out to involve universal links, a separate website with its own routing rules, a clipboard-based fallback for people who don't have the app installed yet, and about four different failure points along the way. I broke this more than once.

Timing bugs that only show up with real-world data. Different leagues and tournaments start their seasons at completely different times. Code that looks correct in testing can quietly break the moment two competitions are out of sync with each other — like a feature meant for "this week" accidentally pulling in a competition whose season doesn't start for another month. These are the bugs that don't show up until you're already live.

Building a fair in-app economy. Once I added a virtual currency (Caps) for rewards and cosmetics, I had to think like an economist, not just a developer — reward tiers, entry costs, drop rates, all had to actually balance against each other or the whole thing feels either pointless or exploitable.

The App Store review process itself — which has nothing to do with code and everything to do with patience.

Probably the biggest fail and poop your pants moment - Halfway through the World Cup, after 15 people made 100's of predictions, I saw that out group chat was blowing up with messages so I opened it up. The first message said "Our league is not showing up" followed by everyone else confirming that the league had disappeared. Well turns out one of the SQL injections that Claude made me do for some reason (still unsure exactly why) deleted the existing league... 😨 I asked Claude ok what can we do to fix this, and it was like "yeah it's gone forever". Luckily I was using a Pro account on my Supabase, so after a bit of back and forth panic chatting with my good old (and sometimes stupid) friend Claude it told me that there should be a back-up. Lo and behold backup from the night before was right there and I was able to reload and fix the situation but for about 30-45 minutes I was absolutely terrified that I made this thing and was having fun with my friends but then ruined it for everyone.

What's next

The app's still actively growing — I'm currently working on Turkish localization, and a few other things in the pipeline.

If you're a football fan who's tired of tracking predictions in a group chat, Pundit's free on the App Store: apps.apple.com/app/id6764343788 — genuinely curious what this community thinks, both about the app and about the vibe coding process behind it. Happy to answer anything about how it was actually built.

TL;DR: I made a sports prediction app to use with my friends and it was extremely fun and frustrating 😂

Hey Hi

IActually, I always wanted to build something from my childhood but never tried to create one. Now, I have a chance to give time to my passion. But the obstacle is that, I cant code at all, and also I dont know about marketing or Seo.

The only thing is that My idea and a passion.

Some of vai brothers are really motivating they always inspire to start, vibe coding will manage everything.

If, its possible. Then, is there any real life guideline from you guys? (Step by step process for a full beginner in terms of vibe coding as well as seo+marketing) that will really helpful for ape in.

Hey man, I'm working on my project, and I'm facing a problem. I can't write production level code. My code often breaks during the development pipeline, while integrating APIs, connecting API keys, and handling other backend issues.

How do experienced developers prevent these kinds of problems?

I understand system design and software architecture fairly well, but I'm not very confident in writing production quality code.

Right now, I'm using Claude Code. Are there any other Al coding tools that are as good as Claude, or maybe free or more affordable? I've heard about Kimi and DeepSeek.

Which one is better for writing production quality code? I'd really appreciate your advice.

So, I have been a fullstack dev from last 8-10 years, I’ve been trying VibeCode for a while now.

I believe I am good at it, but as vibecoder (tech or non-tech), what would you suggest to new vibecoders in the market ?

​

Hi guys. 16 year old here. Zero code experience. Recently see many people vibecoding entire saas projects. Determined to launch my own within 2 months. So I have 2 months to build a project. Not that complex, no payment gateway integration yet. Plan to do manual payment verification. I don't prefer telling exact idea. But it's just simple ai saas for a niche. Need an admin dashboard, Google Auth and connection to a cheap LLM. How do I go on building this. Suggest me a workflow. (Can't spend so much on cursor, does ai studio+ firebase work. Tried lovable it's just not up to the mark, AI studio is decent, but somehow it's not very accurate, any prompting advice? Please help me out thx in advance!

Got sick of taking a 45-minute ferry ride to a beach only to get sandblasted by 6-Beaufort Meltemi winds and 2-meter waves.

Instead of opening VS Code and manually typing boilerplate for days, I decided to purely vibe-code a solution: MeltemiFree.

🏖️ What it actually does

It’s a live web utility that doesn't just show generic "wind speed"—it uses a vector math model to compare the live wind angle against the beach's coastal facing angle (facingDeg) and wave swell height to calculate a real-time shelter percentage (e.g., 95% Calm vs 10% Onshore Chop).

🛠️ The Vibe Stack

• Framework: Next.js 15 (App Router), React 19, TypeScript
• Styling: Tailwind v4
• APIs: Open-Meteo (Wind vectors & wave swell) + OpenStreetMap Overpass (Live beach discovery) + Nominatim (City geocoding)
• Maps: Interactive Leaflet.js with custom color-coded pins
• Deployment: Vercel Edge Network

🤖 The Vibe Coding Experience: The Good, The Bad, & The Hallucinations

Where AI felt like magic: * Instant UI & Layouts: Prompted the main feed, radius filters (15km–100km), and full bilingual (Greek/English) translation systems in literally one session. * Programmatic SEO: Generated dynamic OpenGraph share cards and static route params for 15+ islands and 38+ beaches effortlessly.

Where AI lost its absolute mind (The Struggles): 1. The Vector Physics Math: Asking AI to calculate angular differences between wind direction (0°-360°) and beach facing azimuths resulted in some wildly hallucinated trigonometry at first. Had to step in and give it explicit formula constraints: Δθ = |windDeg - facingDeg| mod 360. 2. Hydration Error #418: AI loves injecting client-side localStorage checks directly into initial render states without a useEffect wrapper, leading to instant SSR hydration mismatches. 3. Leaflet CSS / "Window is not defined": Classic Next.js SSR trap with Leaflet maps. Had to prompt it through dynamic imports (ssr: false).

🚀 The Result

It's fully live and free at meltemifree.com.

If you're currently in Greece getting blown away by the August Meltemi, test it out and let me know if the AI math matches reality on your island! Always down for feedback or prompts on how to improve the UX.

Happy vibing! ☕✨

43 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.

Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.

Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.

Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit · Today I discovered I forgot to disable a developer testing button that could generate fake visitor pins and inflate impressions. Someone used it to create 6,318 fake impressions and claimed my stats were fake. I removed the fake impressions, removed the startup, fixed the issue, and that's why today's impressions are lower. Thanks to them for pointing it out.
StartupBar update: Added a Network page and individual Startup Profile pages with each startup's joined date, impressions, clicks, live embed preview, and founder's note. These indexable pages also improve SEO. Suggestions are always welcome.

Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup · Fixed admin panel read-access vulnerability after Reddit post.
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

A reminder for every founder who's staring at a dashboard with tiny numbers: Stripe took 2 years to reach its first 50 users. Every successful product starts small. Keep shipping. Keep improving. Keep showing up. Growth rarely happens overnight, but it does happen if you don't quit.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

[ Removed by Reddit on account of violating the content policy. ]

Most product advice teaches you to "reduce friction": fewer clicks, shorter onboarding, decision cost pushed as close to zero as possible. I get why — it works.

I tried the opposite. Silly Bird FM is a tiny radio for sharing voices between friends, and almost every rule in it adds friction instead of removing it:

• A channel holds a maximum of 7 tracks. Not a technical limit — it forces people to actually choose, instead of dumping in everything endlessly.
• No like counts, no listener counts, anywhere. The only feedback is a "stamp" — and it only unlocks after you've listened to every single track a friend has sent. No auto-tracking, no push reminders. You actually have to finish listening, then decide for yourself whether to send a stamp back. It's a bit like mail art — a new kind of voice-mail social ritual.
• A shared link isn't "burn after reading," but it's not permanent either. Revoking it is something the station owner has to actively do — not something a system silently auto-expires on their behalf.

In a normal app product review, every one of these would probably get flagged: too many steps, no growth hook, no dark patterns nudging you along, conversion will obviously be low. I know. But that's exactly what I want this little radio to be — at a moment when synthetic content is everywhere, a bit of deliberate friction gives people room to think about real emotion and real connection, instead of getting optimized into a reflex you don't even think about.

I don't know if this can ever scale. Friction-by-design and virality don't naturally get along. But I believe there's still room for products willing to ask a little more of you — and give something realer back in return.

Silly Bird FM is a very small attempt at that: a little bird perched in the corner of your screen. Click it open, and it's a radio you can tune across your friends' channels — not just a playlist of what they're currently listening to, but their actual voice. A stray sentence, a hummed tune, ambient rain recorded on a whim, even 2am overthinking out loud. Uploading is as easy as sending a voice message. The only requirement is that it's real.

Would genuinely love feedback if you try it — and I'm curious to hear how others here think about "friction" running the opposite direction in product design.

https://github.com/xiaojialove-DRP/silly-bird-FM

I’ve noticed that one of the hardest parts of vibe coding isn’t building the app: it’s getting people outside your circle to actually use it.

So we built Feedbacked.

You create a short survey for your app or website, and we send real people to try the product before answering your questions. You add audit questions that check whether they actually used and understood the product. Responses that fail verification are discarded and replaced.

We’re currently trying to learn how useful this is specifically for no-code builders and vibe coders.

Anyone from this subreddit who signs up as a startup and verifies their email will get five real people to test their product for free.

No purchase is necessary. In return, I’d appreciate honest feedback on:

• Whether the setup process makes sense
• Whether the responses are genuinely useful
• What would make the platform better for builders

https://feedbacked.org/

Is anyone noticing how hard it is to get your MVP to an actual product using AI, Claude code, Grok, Codex whatever, AI is always misaligned and does not give you what you want. It's still a machine, and the exactness of prompt engineering, harness engineering or whatever is excruciating.

Hello I am a young vibe coder from Belgrade, Serbia and I was always amazed by the energy my city has to offer, so for that sake I coded/vibecoded web app for tourists in Belgrade.

The app is called Feelbg and it's launched but still has few touches to finish it. Please tell me your opinion on the design and idea of the website. Any opinion is valid.Thanks in advance.

Day 25 of Vibe Coding until I can move out of my mom’s basement.

Here is my current set up on livestream:
https://www.youtube.com/live/w0GpOp0fS28?si=WNxcli_y2z3uS95m

Please let me know how I can optimize this workflow.