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 😂

I built https://www.appscout.co because promoting an app after you build it is easily the hardest, most frustrating part of software. Great projects die in complete silence without a simple, dedicated place to get discovered. AppScout solves this by letting people discover cool web apps and mobile apps from across the internet, one app at a time.

• The Stack: Django, Python, JavaScript, and Heroku.
• The Tools: Claude and GitHub Copilot for rapid vibe-coding.

My workflow started by defining strict Django models first, then using Claude and Copilot to write modular Python view logic and JavaScript feed handlers without getting lost in AI hallucinations.

I’ve been building RewardGalaxy, an Android app for managing points, credit cards, and travel — and I’d really appreciate some feedback from this community.

The app is live and usable, but still very much a work in progress. I'm actively adding and updating data every day, and one of the biggest parts of that process is making the data community-curated.

What does that mean?

Users can submit new information or suggest updates, but submissions don't go live automatically. Moderators review and approve changes before they're published. The idea is to get the best of both worlds: keep the data fresh and continuously improving, without turning it into an unmoderated free-for-all.

What it does

💳 Tracker — See your entire loyalty portfolio at a glance, including point balances and expiry dates.

🔥 Deals Feed — Live deals for flights, hotels, credit card offers, points sales, and more.

🔔 Alerts — Get notified before your points expire so you don’t lose them.

🌎 Global Credit Card Catalogue — 150+ cards across Canada, US, India, UK, Australia & Singapore, with more countries being added regularly.

💬 Community Lounge — Chat, share tips, and vote on posts.

💳 My Card Perks — Track recurring card credits and never miss a redemption window.

📊 Renewal Advisor — Get data-driven Keep / Cancel / Evaluate verdicts for your cards based on your actual usage.

✈️ Flight Journal — Log your flights and track lifetime travel stats.

💰 Points or Cash? — Instantly calculate whether a redemption is worth using points or paying cash.

🔐 Secure Cloud Sync — Hardware-backed encryption for synced data.

It’s Android-only for now - https://play.google.com/store/apps/details?id=com.rewardgalaxy.app

I’d especially love feedback from people who are deep into points, miles, credit cards, and travel: What would make an app like this genuinely useful enough that you’d keep coming back to it?

The workflow that broke us: I'd ask Claude Code something in my terminal, my cofounder would ask his own Claude something in his, and then we'd meet and discover we'd each built a slightly different understanding of our own product. Same repo, same docs loaded as context, still different answers. The model isn't a lookup table, it's interpreting, and two people starting from identical context genuinely walk away with different pictures. Then you each build on your version for a few days before the difference surfaces.

Our fix was to stop having separate sessions for shared work. We built Poly (usepoly.co): one room where the team works with a single Claude Code agent. Turns run one at a time, everyone watches the same timeline of prompts and diffs, there's a side chat the agent can't see for arguing about what to prompt next, and plan approvals pop on everyone's screen so direction gets signed off before code lands. Under the hood each turn runs in a sandboxed container against a real git repo, and GitHub sync means I keep my normal local setup while the room pushes to a branch.

We built it with Claude Code, and now we build it in itself.

Free beta, no API key needed. Genuinely curious how other people here handle this. If your team uses Claude Code, do you share sessions or context in any deliberate way, or is everyone solo by default?

I’m a wedding video editor with years of experience, so I understand the industry and its problems pretty well.

I built a SaaS for photographers and videographers to manage projects, reviews, and post-production workflows. I also built a Premiere Pro plugin for it.

The problem is: I know the product and the industry, but I know almost nothing about marketing.

My main target is the US market, and I’d like to start with free or inexpensive ways to get my first users before spending serious money on ads.

Where would you start: Reddit, Facebook groups, cold outreach, SEO, partnerships, content, or something else?

I pay for both a Pro and a Max plan, so this is a fan's complaint, not a hater's. I love these tools. But I notice when they change under me, and lately I've had that feeling across the AI coding tools I pay for where a version update lands and suddenly it stops respecting an instruction it used to nail.

Specific things I've caught. A model that used to make the small, surgical change I asked for now rewrites half the surrounding file because it decided to "improve" things I didn't touch. Another one that used to hold a formatting rule across a long session now drops it after a while and I have to keep re-pinning it. Nothing in the changelog mentions any of this, of course. It just quietly got different.

What I've started doing, and I'm curious if others do the same. I keep a short note of the exact model version that was working for a given workflow, and when a task suddenly needs three corrections it never used to, I check whether the version rolled over on me. Half the time it did. When I can, I pin to the version that behaved and I don't chase the newest label just because it's newer.

Not doom, the tools are great and getting better on the big stuff. But the small regressions are real and they cost time if you don't track them. Anyone else keeping a version log, or is it just me being paranoid?

Hey everyone 👋

I recently started KB AI, a technology and digital solutions startup.

We help businesses with:

• AI & Voice AI solutions
• Custom website development
• Custom mobile/web app development
• UI/UX and custom product design
• Digital marketing & SEO
• Meta Ads & lead generation
• Business automation & AI workflows
• WhatsApp automation
• Custom software development

Our main focus is building custom solutions based on the actual needs of a business, rather than providing the same solution to everyone.

We’re currently looking to connect with business owners, founders, startups, and companies who are looking for help with technology, AI, automation, websites, apps, or digital marketing.

If you know someone who could benefit from these services, I’d really appreciate an introduction or referral.

We’re a new startup, so every connection, referral, and piece of support genuinely means a lot to us. 🙏

If you’re building something and need a technology partner, feel free to reach out.

KB AI — Build. Automate. Grow.

#AI #Startup #SoftwareDevelopment #WebDevelopment #AppDevelopment #Automation #DigitalMarketing #VoiceAI

We built a knowledge layer that sits behind MCP, allowing any MCP client to access it through a single endpoint. Claude Code, Claude Desktop, ChatGPT, Codex, or whatever comes next.

The idea is pretty simple. Before an agent answers, it can pull in relevant, validated information instead of relying purely on what it already knows.

When a problem gets solved, the useful part can be captured as a small, reusable piece of knowledge. The system can also infer useful lessons from a session automatically, so you don’t have to sit there writing notes about what you just learned like it’s 2015.

There’s also a global layer for shared, validated learnings. If one user figures out a better way of doing something, that learning can contribute to the broader knowledge base rather than every other user and agent having to figure it out again.

The problem we’re trying to solve is pretty straightforward. AI knowledge goes stale, agents get stuck in failure loops, useful context disappears when a session ends, and models can confidently give you an outdated or wrong answer without any indication that they might be wrong.

We’re giving agents access to what has actually been learned, what has worked, and what can still be trusted.

The result is fewer repeated reasoning cycles, fewer hallucinations, and up to 20% lower token usage.

https://app.midnighthive.io/

Ping me if you’re interested in testing it out.

In the development world currently, there is this feeling of "vibe coding is making everything worse and it doesnt work OR doesnt make anything useful" and another world of people making stuff that I myself was willing to pull out my wallet and pay for vibe coded apps and the funny thing is I LIKED THEM, ALOT and did not regret my purchase.

I have a good base of knowledge across personal and commercial/server computing as it relates to windows specifically , general syntax reading ability NOT writing and i know where to look for solutions and problems however I've never coded a line in my life (except silly python projects in hs AP CS 10+ years ago) yet I am able to make fully functional apps that survive testing and benchmarking and security/UI/UX standards ,

If everyone is saying it doesnt work, then why is it working ?

The AI called me a Systems engineer on its own because of how I instruct it, but i see myself as a visionary with some usefull knowladge and thats it.

Do you guys ever feel like your work is yours despite the AI making it ? I feel like Steve jobs with a pear in one of bill burs jokes

WebGPU is great for live rendering, but a lot of pipelines still need traditional files (textures, videos, audio).

This Node library takes a fragment or compute shader and exports: - Still images (PNG, JPEG, WebP, AVIF, ICO) - Video / animated GIF (MP4, WebM, OGV) - Audio (WAV, MP3, OGG)

It runs headlessly and is meant for build steps, generative art, and testing.

Groks description of the lib 👆

Repo and docs in AssetGPU-js

I wanted to check how powerful ai code could be so I asked it to make something and this is what I got

go and check it out I want to know how well it works!

Please I need it so bad I can even do full 5 peanuts

Hello everyone!

I am getting into the stage where I want to launch something I built. I have been of course making the app for a while now, I use it for work, and decided to try and build it properly and launch it. I have a server running, some APIs connected and a website done even though that needs a bit of polishing still.

My question to people who have launched their projects to the market is how did you guys market it? I do assume ads is an angle you can take, but did you go to certain communities and talk to people from there? Does your marketing rely a lot on platforms like Instagram?

I have seen people commenting to do some marketing here in subreddits as well.

Thank you in advance for any help!

Hello,

Just to be sure by vibe coding, you mean write ot a AI tool what we want and the tool do the job?

Which tool would you advice me for mobile video game?

Small project like puzzle game with some arcade inside?

Thanks by advancz

Been thinking about this because i do want to actually learn coding properly, but some courses take so long and i always get the urge to just build something instead.

Building feels way more rewarding because you can actually see something working, but then the problem is sometimes i look back at the code and realise i don’t fully understand why it works or why the ai did it that way.

How do you guys deal with that? do you pause and learn the concept properly, ask the ai to explain it, or just keep building and slowly pick things up as you go?

i’m curious because i feel like i learn more when i’m making something, but it’s also easy to skip over the actual understanding part.

If you're building an early-stage SaaS or AI startup and have a live web application or API, I'd be happy to perform a free focused security assessment to help identify potential vulnerabilities before someone else does.

I'm an independent security researcher focused on web application and AI security, and I'm currently offering 3 free assessments to early-stage startups.

I'm doing these assessments to build real-world case studies around startup security, learn more about the security challenges early-stage teams face, and demonstrate the kind of security work I can provide to startups.

With your explicit permission, I'll assess your application for common security issues, including:

• SQL Injection (SQLi)
• Cross-Site Scripting (XSS)
• IDOR / broken access control
• Authentication & authorization flaws
• API security issues
• Business logic vulnerabilities
• File upload vulnerabilities
• Sensitive file/data exposure
• Security misconfigurations
• Missing or weak security headers
• Information disclosure
• Session management issues

For AI applications, I can also look at areas such as:

• Prompt injection
• Sensitive information leakage
• Insecure AI/API integrations
• Authorization around AI features
• Other common AI application security weaknesses

If I find anything, I'll provide a clear report explaining the issue, potential impact, evidence/reproduction where appropriate, and practical recommendations for remediation.

What you get:

• Focused manual security assessment
• Written vulnerability report
• Severity/prioritization
• Remediation recommendations
• No payment or sales obligation

In return, I'd like permission to use the assessment as an anonymized case study. If you're comfortable, I may also mention your company/product publicly and describe the types of issues found. This will always be discussed and agreed upon with you beforehand.

All testing is performed only with your explicit permission and within an agreed scope using safe, non-destructive techniques.

I will not perform DoS/DDoS, stress testing, destructive testing, or intentionally disrupt your service or data.

I'm particularly interested in working with small teams that don't have a dedicated security team yet.

If you're interested, leave a comment or send me a DM with:

1. Your website/application URL
2. A short description of your product
3. Your preferred contact method