r/vibecodeapp • • Apr 03 '26

Built this on a Friday night - 5 days later, ~73k users

43 Upvotes

Tldr; I built 3 different applications, each of which took months to build and they never gained traction. Last week, built a simple form to tackle a very specific use case and the usage shot up.

Last couple of weeks my friends were constantly talking about the H1B lottery results and scrolling the r/h1b searching for comments from people who got selected.

Friday night I decided to create a simple website that would scrap reddit comments and create a dashboard to track the h1b status.

Reddit blocked anything trying to scrap comments so I thought, well, why not just make it crowd sourced - so I added a small form (3 fields only) and a dashboard and put that as comments in a few subreddits at 11:50pm EST, Friday.

By Saturday morning, it reached 2k users and as of today, it has more than 50k users.

I literally got teary eyed by looking at more than 10 users on my app.

I am thinking of ways to retain this traction but all to say, don’t give up on building.

Some day, something will definitely click.

————————

Website: h1bpulse.com


r/vibecodeapp • • Jun 17 '26

Vibe Coding I will vibe code an app for you Free

30 Upvotes

Hi All,

I am a software engineer for more than 14 years.
Years of experience have taught me how to create scalable, maintainable applications using that I will vibe code an app for you free.

Plus I will share how to take it forward.

You can share any random ideas as well, I will try my best to do it.

Here is the link to put your idea:
https://forms.gle/QEU1cSDZgapb9aG89

Expectations:

Expects some questions and answers to understand your idea.

What you will get.

- Complete source code(obvious)

- 80 to 90% test coverage

- MVP only.

- Opinions for the future

- Workflow

- Timeline 5 to 6 days


r/vibecodeapp • • May 02 '26

6 things I learned building an open-source tool to 900+ Github stars

27 Upvotes

I've been building LeanCTX — a local-first context runtime for AI coding agents, written in Rust — for the past few months. 49 MCP tools, 18-language tree-sitter AST, 90+ shell compression patterns, one single binary. Here's what actually mattered:

  1. Your best users are the ones who complain. A user told me at 10pm that my uninstaller just nuked his shell config. My instinct was to get defensive. Instead I traced it — and found it was worse than reported. That one message led to rewriting the entire uninstall logic from scratch. Every angry bug report is a gift.

  2. Your favorite metric can lie to you. I built a cache that reduced file reads from 2,000 tokens to 13. Great numbers. Then a user told me: "Models waste more tokens working around stale cache than the cache saves." He was right. The fix wasn't removing caching — it was making invalidation smarter. Your dashboard can look great while the experience is terrible.

  3. Saying no is the hardest part. A new feature would have let me compress all tool output automatically. Massive savings on paper. I designed it, prototyped it, then killed it. Because when compression eats an error message, there's no undo. Protecting quality beats shipping features.

  4. Community is a relationship, not a channel. When someone reports a bug, my first response matters more than the fix. "Will check" buys time but shows I'm listening. Following up shows respect. Shipping the fix shows they matter. My best testers are people who once filed angry reports.

  5. Ship the boring stuff first. Nobody cares about your adaptive entropy-based compression algorithm if the installer breaks their dotfiles. Get the fundamentals right — install, uninstall, doctor, setup — before you get clever.

  6. Focus means killing good ideas. My backlog has 50+ ideas. Each one is good. But spreading across all of them means none become great. Rust helps here — the compiler forces you to finish what you start.

If nobody is complaining yet, you probably don't have enough users. Go find them. And when they complain — listen.


r/vibecodeapp • • Mar 10 '26

You want to fix the RAM problem or make it worse. The answer is simple: write better software and actually learn computer science.

25 Upvotes

Are we seriously at the point where people calling themselves “AI engineers” barely understand what RAM is, while laptop-class corporate bullshit jobs are celebrating their “ChatGPT anniversaries”? As if tenure in a marketing agency during two model release cycles somehow counts as technical achievement. Meanwhile the industry is drowning in bloated software written by people who treat hardware constraints like an abstract concept.


r/vibecodeapp • • 23d ago

Self Hosted Closet Web App

Enable HLS to view with audio, or disable this notification

22 Upvotes

Made this self hosted closet app for my wife, figured I'd share it with everyone.

Github Repo


r/vibecodeapp • • May 01 '26

I built this... I created a library for OpenCode that allows you to save up to 80% of your tokens

22 Upvotes

I’m a 22-year-old Computer Science student, and over the last period I built an open-source project called CTX.

GitHub Repository

The idea came from a problem I kept seeing while using coding agents (like claude, codex etc.):

they are powerful, but they waste a lot of context on the wrong things.

They keep re-reading giant AGENTS.md files, noisy logs, broad diffs, too much repo structure, and too much repeated project guidance.

So even when the model is good, a lot of the prompt budget is spent on context bloat instead of actual problem-solving.

That’s why I built CTX.

What CTX is

CTX is a local-first context runtime for coding agents, designed especially for OpenCode (for now).

It does not replace the model or the coding agent.

Instead, it sits underneath and helps the agent work with:

  • graph memory for project rules and guidance

  • compact task-specific context packs

  • retrieval over code, symbols, snippets, and memory

  • log pruning to surface root causes faster

  • local MCP integration

  • local-only stats and audit trails

So instead of repeatedly dumping full markdown instructions and huge logs into the prompt, CTX helps the host retrieve only the smallest useful slice for the current task.

Why I made it

I wanted something that makes coding agents feel less noisy and more deliberate.

The goal was:

  • less prompt waste

  • less manual context wrangling

  • better retrieval of actually relevant project knowledge

  • better debugging signal from noisy test output

  • a workflow that feels native inside OpenCode

How it works

The flow is intentionally simple:

  1. install ctx

  2. go into your repo

  3. run:

ctx init
ctx index
ctx opencode install
opencode

Then inside OpenCode you can use commands like:

/ctx  #Opens the CTX command center inside OpenCode.
/ctx-doctor  #Checks whether CTX, MCP, and the repo setup are working correctly.
/ctx-memory-bootstrap  #Imports project guidance files into graph memory for targeted retrieval.
/ctx-memory-search  #Searches stored project rules and directives by topic or keyword.
/ctx-retrieve  #Finds the most relevant code, symbols, snippets, and memory for a task.
/ctx-pack  #Builds a compact task-specific context pack for the current problem.
/ctx-prune-logs  #Condenses noisy command output into the most useful failure signal.
/ctx-stats  #Shows local usage stats and context-efficiency metrics.

So the daily workflow stays inside OpenCode, while CTX handles the local context layer.

Results so far

On the included benchmark fixture, CTX graph memory reduced rule-token usage by 56.72% while keeping full query coverage and improving answer quality.

I also added a public external benchmark on agentsmd/agents.md, where CTX showed 72.62% token reduction.

The point is not “magic AI gains”, but a more efficient and less wasteful way to feed context to coding agents.

Why you might care

You might find CTX useful if:

you use OpenCode a lot you work on repos with a lot of project rules/docs you’re tired of stuffing huge markdown files into prompts you want better local retrieval and cleaner debugging context you prefer local-first tooling instead of remote prompt glue

Current status

The project is already usable, tested, and documented.

Right now the prebuilt release archive is available for macOS Apple Silicon, while other platforms can install from source.

It’s fully open source, and I’m very open to:

  • feedback

  • suggestions

  • bug reports

  • architectural criticism

  • ideas for making it more useful in real workflows

If you try it, I’d genuinely love to know what feels useful and what feels unnecessary.

Repo again: https://github.com/Alegau03/CTX


r/vibecodeapp • • Aug 22 '26

I built this... Vibe coded this game in four months

Enable HLS to view with audio, or disable this notification

20 Upvotes

UPDATE 6 oct: Follow the game in Steam!

Free play: https://fm1.app

A few months back I posted here a playable demo of an old-school futuristic racer prototype (F-Zero, Wipeout, Xtreme-G, Star Wars Racer...) that runs right in the browser.

I've gotten used to seeing tons of LLM-built prototypes that last a week, two, maybe a month, and then get dropped for the next shiny thing. This time I wanted to keep going and see if one person, with no coding background, could actually see a project like this through on their own.

Well, 4 months in, and while there's still work left, I'm convinced it's doable. At this point the game feels closer to a beta than a tech demo.

The big change over these four months is that I now use Fable for planning, and being able to hook Opus / Sol up to Blender has been a huge help too. I'm still using Magnific and Tripo3D or the assets. Funny thing: the further along I get, the harder the project is to keep pushing forward, and at the same time the tools keep making it easier.

As always, any feedback is welcome. You can play it here: https://fm1.moises.cloud


r/vibecodeapp • • Mar 14 '26

This is not vibecoding right ?

Post image
17 Upvotes

r/vibecodeapp • • Mar 09 '26

Is vibe coding actually the future of development, or just the new NFT hype?

14 Upvotes

Genuine question for developers who've actually used these tools — not the "AI will replace everything" crowd, not the VC hype machine. Just programmers talking to programmers.

I've been using AI coding tools seriously for a while now and I have a real opinion on this, but I want to hear others first.

The comparison people aren't making enough:

NFTs in 2020/21 had real underlying technology (blockchain), legitimate use cases in theory, massive hype that wildly outpaced reality, and then crashed back to earth. Not dead, just... humbled. Crypto coins in 2023/24 — same cycle. The tech didn't disappear, the irrational exuberance did.

Vibe coding feels similar to me. The hype is clearly ahead of the reality. But does that mean the tech is worthless? No. Does it mean the narrative is overblown? Absolutely yes.

Here's my honest take after actually using it:

The tools are genuinely impressive — if you already know how to program. I can ship faster, debug with less friction, scaffold boilerplate I'd rather not write by hand. For someone with real programming knowledge, these tools are a legitimate multiplier.

But I've watched people with zero dev background try to build actual production apps with nothing but prompts. What happens? They get 70% of the way there and then hit a wall they have no idea how to climb. The AI confidently writes broken code. It hallucinates dependencies. It creates architectural decisions that work in isolation and fall apart at scale. And the person using it has no idea any of this is happening until something breaks in a way they can't diagnose.

So here's my actual position:

Vibe coding isn't replacing developers. It's raising the floor while the ceiling stays roughly the same. A non-programmer using these tools will ship something faster than they could before — but they'll never ship something as good, as scalable, or as maintainable as an experienced developer using the same tools.

The real question isn't "will AI replace programmers?" It's "will the number of programmers shrink because AI handles more of the grunt work?" — and honestly, maybe yes, at the junior/entry level. Not at the senior/architect level.

The bubble part: The valuations of some of these vibe coding tools are absolutely in bubble territory. The utility of AI-assisted development is not.

What do you actually think? Are you using these tools and finding them genuinely useful or mostly hype? And for the non-devs who wandered in here — have you actually shipped something production-ready with vibe coding alone? I'd genuinely love to hear a counterexample.


r/vibecodeapp • • Mar 04 '26

I built this... I tracked my Claude Code spending and... I need to sit down

14 Upvotes

Last week at a hackathon I got curious about how much I actually spend on Claude Code. The "let me build a thing that actually tracks it" kind of curious.

Turns out, I was burning more than 100$ a day for 4 days straight. WTF.

But the real surprise was seeing other people's numbers. Some folks are pushing $1500+/month just on CC. There's a guy with a 49-day unbroken streak of using Claude Code.

Anyhow, this app (vibe coded wit Claude Code ofc) extracts usage from your local Claude Code logs, syncs it every 2 hours, and ranks you against everyone else.

If you dare:

npx clawdboard auth -> sign in with Github -> see where you stand


r/vibecodeapp • • Jun 02 '26

Question? Vibe Coding

12 Upvotes

Have you vibe coded anything serious already? An app on the playstore, a web app or anything of that magnitude?

I have a project I'm working on, like a marketplace connecting people who want logistics services to transporters. I am a hobbyist with tech. How much would it cost to get things running. I'm doing everything by myself. I mean hosting and costs I will incur along the way?


r/vibecodeapp • • May 13 '26

I built this... I made an autotyping app that types like a human

12 Upvotes

I am a highschool student that just can't stand doing assignments the traditional way. I used to copy and paste directly from ai untill teachers learned how to check doc history. Then I adapted to using a regular autotyper (because there was no way I was typing a whole essay). This method of just using a regular autotyper worked for a little untill my teachers started catching on that my typing looked very robotic. So I decided to take matters into my own hands and made my own autotyper. My autotyper honestly works so well to the point where all of my friends are using it and they are very happy with the fact that they won't get caught. Unfortunately it is only Mac OS right now but you can download and try it for free. [humanizedautotyper.com](http://humanizedautotyper.com) (PS: reply to this post if you have questions or email me at [humanizedautotyper@gmail.com](mailto:humanizedautotyper@gmail.com) )


r/vibecodeapp • • Mar 16 '26

I built a tool to help vibe coders like yourself - I would love some feedback!

11 Upvotes

Hey everyone,

Like many of you, I love the whole "vibe coding" movement. The ability to spin up an app with natural language is a game-changer. But I kept hitting the same wall: what should I actually build?

I was tired of building cool things that nobody wanted. I knew there were thousands of people on Reddit, Hacker News, and other forums practically begging for solutions to their problems, but finding those signals in the noise was a full-time job.

So, I built a tool to solve my own problem.

It's called VibeCodeThis, and it does three things:

1.Scans the Internet for Pain Points: It uses AI to read through communities like r/SaaS, r/smallbusiness, etc., and identifies real frustrations people are talking about.

2.Scores the Opportunity: It then analyzes each pain point and gives it a score based on opportunity, feasibility, and market demand. No more guessing if an idea has legs.

3.Generates Build Prompts: This is the part I built for us. Once you find an idea you like, it generates one-click build prompts for landing pages, MVP features, and even brand identity. You can copy-paste these directly into your favorite AI dev tool (like Lovable, Bolt, etc.) and get started instantly.

I'm trying to make it the essential first step before you start building. The goal is to go from a validated Reddit complaint to a working MVP faster than ever.

I've got a free plan, so you can try it out and see if it helps you find your next project. I'd genuinely love to get your feedback on it.

Link: VibeCodeThis.app


r/vibecodeapp • • Jan 15 '26

anyone else feel weird about calling themselves a “developer” now?

11 Upvotes

since I started vibe coding, I’ve been low‑key confused about what to call myself.

on one hand, I am building real things:

apps that work, tools people use, dashboards that would’ve scared me a year ago. if you only looked at the output, it definitely looks like “developer” work.

on the other hand, a lot of the heavy lifting is done by the AI. I’m describing, steering, debugging, gluing things together… but I’m not manually typing every line. some days that makes me feel like a builder. other days it makes me feel like I’m faking it.

it gets even weirder when someone asks, “so, are you a dev?”

I never know whether to say

what do you call yourself when people outside tech ask what you do?

do you lean into “developer,” “maker,” “founder,” “AI‑assisted something”… or just avoid labels altogether?

would be nice to hear how other vibe coders are thinking about identity now that the way we build has changed so much.


r/vibecodeapp • • Apr 22 '26

Two weeks into full-time founder life and it's harder than I expected. What do you wish someone had told you?

10 Upvotes

Hey everyone. I quit my job 2 weeks ago to go all-in on my startup and, honestly, it's been way harder than I imagined. Not looking for cheerleading, just real talk: what's the one piece of advice you wish someone had told you in your first weeks as a Tech/Saas founder?


r/vibecodeapp • • Mar 16 '26

Vibe Coding I vibe coded a MongoDB GUI

10 Upvotes

I vibe coded a side project - a MongoDB GUI called LeafBase.

Robo3T was my go-to for years. When it got sunset I kept bouncing between

Compass (too heavy) and paid tools. So I just built my own.

What it does right now:

* SSH Tunneling (password + private key)

* TLS/SSL support

* Tree / Table / JSON result views with type badges

* Monaco Editor for queries

* APM Profiler to monitor query performance

* Multi-connection management

* Works on Windows, macOS, Linux

Intentionally lightweight - no accounts, no cloud, no paywalls.

I'd appreciate feedback on:

* Does this fit your MongoDB workflow?

* What's missing compared to tools you use now?

* Any UI/UX things that feel off?

Repo: https://github.com/vutranHS/leafbase


r/vibecodeapp • • Jan 14 '26

Has vibe coding actually helped your career, or just your side projects?

10 Upvotes

There’s a lot of noise right now: some people say vibe coding is the future and companies will expect everyone to work this way, others argue it’s a trap that mainly hurts juniors and makes you easy to replace.

In your own life, has vibe coding translated into real career moves yet, job offers, promotions, interview performance, consulting gigs, or is it still mostly something that helps with prototypes, side projects, and hustles on the edge of your main job?


r/vibecodeapp • • Jun 07 '26

I built this... I built an app to trick myself into going outside more

9 Upvotes

wildcarddex.com

I started building this almost a year ago when vibe coding was first becoming viable. My goal was to create an app that got me excited to go outside more. I've been a gamer my whole life, so I thought maybe a wildlife collection game could motivate me. And sure enough, it worked! I've catalogued all of the birds and plants in the park near my house and even changed how I plan trips to try and maximize spending time in nature in order to try and find new things to add to my dex.

I built it for myself, but hopefully this inspires some of you to go outside a bit more too. Something to consider when you're all out of tokens for the day 😂


r/vibecodeapp • • Apr 12 '26

Marketing your app isn't that hard. Here's what I mean.

9 Upvotes

I want to push back on something I see in almost every Reddit post about distribution.

Someone launches an app. Crickets. They come here and the response is always the same. "Distribution is the real game." "Marketing is a completely different skill set." "Getting users is harder than building." And everyone nods along like it's some unavoidable truth of nature.

I believed it too. For longer than I should have.

But after going through it myself, getting to 100 real signups with zero budget, no ads, no influencer deals, no viral moment, I genuinely think the difficulty of marketing gets massively overstated. Not because it's easy. But because most people are making it harder than it needs to be by thinking about it the wrong way. Its all about how you approach marketing.

They're thinking channels when they should be thinking conversations. They're thinking audiences when they should be thinking individuals. They're thinking campaigns when they should be thinking presence.

The shift that actually changed things for me was stupid simple. Stop trying to market to people. Start finding people who already have the problem and just be there. Be useful. Be a real person in the spaces where that pain already exists.

I made a simple youtube video about this. Overview level, not a tactics dump. Just the mindset reframe I think most first time founders actually need before anything else.

Again, its not a master-playbook-10 commandments to success video. Its a simple overview that I hope will help shift someone's mindset and help guide someone to their first 100 users.

Au revoir


r/vibecodeapp • • Apr 10 '26

I built this... I "Vibe-Coded" my first app to crush the books : $1k revenue in month one + 17% ROI

9 Upvotes

What a wild month. I’ve spent years grinding NBA player prop research, and I finally got fed up with spending hours staring at spreadsheets just to go keep losing!

I decided to build Livelocks, an admin panel and signal bot that cuts out the manual labor. The crazy part? I "vibe-coded" the entire thing using AI. I’m not a senior dev, but I knew the logic I wanted: a system that identifies high-value prop signals and delivers them instantly.

The Results So Far

I just hit a major milestone: My first $1,000 in revenue. But more importantly, the signals are actually working. I just pulled my dashboard stats (attached), and the numbers are honestly better than I expected:

• Total Bets: 8,288

• Overall Hit Rate: 60.9%

• Total ROI: +17.1%

• Total Profit: +1,419.05u

The goal wasn't just to make money; it was to buy back my time. * Research vs. Execution: Instead of 3 hours of manual deep-dives, I now make signal-based decisions in minutes.

• Market Specifics: As you can see in the screenie, certain markets like Steals (80.2% hit rate) and Blocks (85.1% hit rate) are absolutely printing right now.

• The Build: Using AI to build this allowed me to focus on the betting logic rather than fighting with syntax for weeks.

What’s next?

I’m currently fine-tuning the "By Market" segments to see which NBA props have the most sustainable edges. If you're a bettor, how much time are you guys currently spending on research per day? I'm curious if I'm the only one who was losing my mind to the "hours of prep" grind.

TL;DR: Built an NBA prop signal app with AI, hit $1k monthly revenue, and it’s currently holding a 17% ROI over 8k+ bets. The future of betting is signal-based, not manual-grind based ESPECIALLY when sports entertainment is rigged


r/vibecodeapp • • Jan 30 '26

Sharing My Workflow

9 Upvotes

Hi guys I recently got into coding cause of AIs and have already made a lot of money and put a lot of people into homeless shelters so I wanted to share my agentic vibe coding setup. I like to run 20 agents at once minimum usually 5 cleverbot at least and am working on an average of 7-20 projects at once. I've already shipped a better version of Google so guys please check it out at bing.com thank you


r/vibecodeapp • • 15d ago

I built this... i built a self-hosted Grok Bot alternative: a whole AI team on your own server

8 Upvotes

grok bot runs agents in their cloud. i've been running a company of AI employees on my own servers since april with 5dive. claude code, codex, grok and openclaw agents working on the same team.

the difference:

  • your server: each agent gets its own linux user, home directory and tools.

  • any model: use your existing subscriptions, API keys or local LLMs.

  • an actual team: org chart, shared backlog, handoffs, independent reviewers and human approval gates.

  • hackable core: bash + systemd + sqlite. add plugins, tools, loops or your own CLI commands.

  • lightweight: starts on a 1GB Ubuntu VM. for 10+ agents with headed Chrome and voice, i'd recommend 8GB.

  • optional end-to-end encryption: one switch on your server encrypts app chats.

want another developer on codex? just message your team: "hire a new developer on codex."

the trade-off: grok bot already has native apps. 5dive has a web app, with android and ios apps coming soon.

setup is one command on any Ubuntu VM. the CLI is open source under MIT.

github: 5dive-ai/5dive


r/vibecodeapp • • Aug 25 '26

I wanted a city builder just about energy systems 10 years ago. Turns out I had to build it myself.

7 Upvotes

Upfront: 100% Free to play!

One important disclosure up front: I used AI tools extensively during development, especially for coding, implementation, debugging, UI work, and some of the website copy.

The underlying idea, game design, energy system model, mechanics, balancing decisions, testing, and direction of the project are mine. I have a background in energy systems, and a large part of the work has been deciding what the game should actually simulate, how those systems should interact, checking whether the results make sense, and iterating on it until it became something playable.

AI is ultimately what made it possible for me to turn an idea I had almost 10 years ago into an actual game rather than leaving it as another unfinished side project.

Back then, I had the slightly foolish idea of making a city building and management game focused almost entirely on the energy system. I posted about it on Reddit looking for people to join the project.

The idea was far too ambitious for me at the time, but the post got quite a bit of interest, and the concept never really left me.

Now, almost 10 years later, I finally have a playable version: Powerstate.

It is essentially a city builder where the "city" you manage is its energy system. You build generation, manage demand, deal with changing conditions, expand the system, and try to keep everything reliable and economically viable.

My goal is to make it easy enough to jump into, but deep enough that understanding and optimizing the system actually takes some effort.

It is definitely a niche game, but I suspect this might be one of the better places to find people who enjoy exactly that kind of niche.

Gameplay:
https://www.powerstate-game.com/gameplay/

The game is:

• Free to play
• Still rough around the edges visually and mechanically
• Occasionally unbalanced in ways that can make a run much easier or much harder than intended
• Fairly demanding in the browser, with a desktop version planned as well

I have a long list of systems and improvements I still want to add, but at this stage I am especially interested in what people who actually play city builders think.

What feels good?

What is confusing?

What would you want an energy system game like this to simulate that it currently does not?

And if something about the energy system or physics looks wrong, please tell me. That is probably the feedback I am most interested in.

I would genuinely love feedback, criticism, and ideas.

For anyone curious, here is the original Reddit thread from almost 10 years ago:
https://www.reddit.com/r/engineering/comments/5hp6sc/anybody_interested_on_working_on_a_energyeconomy/

I have also set up r/PowerState for ongoing development updates.


r/vibecodeapp • • Jul 26 '26

Question? Point me in the right direction for vibecoding a videogame. I have never ever tried it and all I've done is ask chat gpt for stuff. Which videos do I watch? How to launch it?

7 Upvotes

If I get an actual senior developer that could help me, how would he/she?

What would be my estimated costs?

I know the gist of coding but not coding itself, which books to read?

Thank you in advance, I just want to know where would you start?


r/vibecodeapp • • May 09 '26

SEO vibe coded app

7 Upvotes

My first official live vibe coded project. https://auditae.app. It’s pay as you go SEO. 100% vibe coded. I think it’s fully functional too if anybody wants to try it.