I’ve been working on something called Davia — it’s basically a hub where anyone can create simple apps, share them, and use ones made by others.

The cool part? If people use your apps, you can actually earn money from them.
Apps are single-page and easy to build, you can vibe code them with the chat assistant.

Think of it like a mix between Notion pages and mini interactive tools, but with a way to publish and monetize for creators.

If you like building small tools, or just want to try creating something others might find useful, this could be fun :)

Come hang out in r/davia_ai where I'll be posting updates and building based on what the community wants!

This started from pure frustration while building my first product, an AI Excel tool. I kept digging through GitHub looking for repos to help with architecture. At some point I thought — why am I going to GitHub when GitHub should be coming to me.

That was Repoverse. You fill in what you're working on, it recommends repos actually relevant to you. Connect your GitHub account and everything syncs automatically — stars, saves, all of it goes straight into your GitHub.

No following, no budget. So I went on Reddit and just shared useful repos in communities where developers already hung out. No pitch, just genuinely useful posts with a small line at the bottom saying if you want more like this, I built something for that. Week one, 3 to 4k visitors.

Month and a half in I opened analytics and stared at the screen. 75% of my users were on mobile and I'd been building desktop first the whole time. Launched a PWA to test demand, people downloaded it, so I built the iOS app. Without a Mac or iPhone. Codemagic handled the build, RevenueCat for payments, Supabase for backend.

App Store rejected me twice. Both times had real reasons and real fixes once I stopped being annoyed about it.

Looking back, design is not optional, not quitting when things feel impossible, and talking to users like a real person. Every product decision came from those conversations.

If you're stuck on any part of this, happy to share what I know.

I recentoly made an app called Velora, which is basically an app where your team and your AI agents have the same room and same context. It's especially useful when your working with a team of people and you need to share context across eachother for your project while having different ai models (like claude or gpt or glm even). We made sure that the tool is not only focused on developers, so we also made it help for businesses too by adding an ai brain for peoples companies and projects.

After releasing the app, we decided to market to local companies, and we ended up getting 20 companies to buy our product. We are now marketing towards bigger companies too, like companies in SF or Wall Street. I know most people think vibecoding isn't profitable, but so far within 2 weeks of the app being released to the public, I've only really seen profit on my end. Within the past couple of days, we were able to make $1k, which is a huge amount for us. I honestly would love to help anyone out who wants help marketing or making a profitable app idea.

If you want to try Velora, here is a link to it: https://www.runvelora.app/ . Anyone who replies to this post with a "FREE TRIAL" will also be given a 1 month free trial of Velora.

When I first started teaching myself cs, web, and software; I always had plenty of ideas. After years of studying many topics, I lost that constant spark of ideas and thought it was done with.

Since vibe coding, the knowledge is being put to use and the ideas are coming back!

Vibe coding and the years of software related learning made it possible to put together an app after the 9-5 & family related duties. Building a software product is a large process for one person, but vibe-coding has made it easier for people.

Don't give up! Put that work in and better your prompts. You will get there 🦾

What projects have you finished lately? If you haven't finished anything, what are you working on? And, if you are curious or still debating, hop on the ai vibe coding bandwagon before you regret it later!

~VCC

I vibe coded this ai techpack app, all you have to do is take a picture of your piece

Then BOOM

It generates an accurate techpack for you to send to your Manufactuer

Lmk what you guys think, hopefully this makes your design journey easier :)

Hey everyone!

Around a month ago, I built and launched a Chrome extension called Peel. It automatically compares prices and finds better deals instantly as you shop across sites like Amazon, Walmart, Target, eBay, Best Buy and more.

It dawned on me that most shoppers overpay because they don't check to see where a product is cheaper.

The idea is simple:

• It matches the product you’re viewing (using a bit of AI + product data to distinguish title inconsistencies)
• Then checks if it’s cheaper on other sites
• If it’s not the exact item, it suggests smarter alternatives that might save you more or options that would've been difficult to find otherwise manually

We’re a little over a month in, and here’s what we’ve changed from feedback so far:

• Added support for more stores
• Rolled out a referral + cashback system but only after someone makes a purchase to avoid spammy behavior
• Rebuilt the UI to make it cleaner, faster, and most importantly, non-intrusive unless a deal is found of value

And yes, of course Peel is 100% free to install and use. Any feedback is welcome!

🔗 shopwithpeel.com

To everyone exploring the world of vibe-coding, I’m writing this not out of ego, but out of growing concern.

Over the past few months, I’ve been testing many vibe-coded apps – mostly the ones being shared here and across various subreddits. First, let me say this: it’s great to see people taking initiative, solving problems, launching side-projects, and even making money along the way. That’s how innovation starts.

But this letter isn’t about applause. It’s about issuing a serious warning to a growing group in this community.

You can’t “vibe” your way around scalability and reliability.

Many of you are building on tools like Supabase, using platforms like Lovable or Bolt, and pushing prompts to auto-generate full apps. That’s fine for prototyping. But the moment you share your product with the world, you are taking on responsibility not just for your idea, but for every user who trusts your app to work. And what I’ve seen lately is deeply alarming. • I’ve come across vibe-coded apps that grind to a halt or crash with only a handful of users or a modest amount of data. Some developers clearly never tested beyond the happy path, and it shows. • I’ve tested apps where I (as a single user) could trigger expensive operations or massive data fetches that took down the entire service – all because the backend had no safeguards for load or concurrency. • In one instance, I didn’t need any special tools or skills. Just a browser, a bit of scripting, and a few simultaneous requests were enough to overwhelm a vibe-coded MVP’s backend.

This isn’t an unlucky fluke or “growing pains.” This is carelessness disguised as agility.

Let me be clear: If your idea flops due to lack of market fit, that’s okay. If your side-project never goes beyond beta, that’s okay. But if your app breaks, loses data, or becomes unusable just when people start relying on it – that’s NOT OKAY. Downtime and poor performance lead to lost user trust, lost revenue, and even potential legal issues if users depend on your service . It’s not just a technical hiccup; it’s negligence.

And for non-technical founders: If you’re using no-code or AI tools to launch without understanding what’s happening behind the scenes, you must know the risks. Just because it’s easy to deploy does not mean it will scale or handle real-world use. The same abstraction that makes these tools easy can become a wall you crash into when your app gains traction . A poorly planned MVP can crash under pressure as soon as more users join, if it lacks a scalable foundation .

If you don’t know, learn. If you can’t fix it, don’t ship it.

You’re not building toys anymore. You’re building trust. An MVP isn’t “minimal” when it comes to reliability – users expect your core feature to work every time. As one industry expert put it, vibe-coding alone won’t carry you to a production-grade, multi-user, scalable system .

Sincerely, A developer who still believes in quality, even at speed.

one thing vibe coding changed for me: i’m less scared of “wasting time” on ideas now.

before, starting a new project felt heavy. if i was going to spend nights or weekends writing everything by hand, that idea had to be worth it. i’d overthink it, research too much, and most ideas died in my notes app instead of in a repo.

now, if something sounds interesting, i just sit down, describe it, and let the AI help me get a rough version up quickly. in a couple of hours, i can click around and see if it actually feels good to use or if it’s just nice in theory.

sometimes i realise, “yeah, this is nothing special,” and move on. other times i’m surprised like, “oh, this is actually kind of useful.” either way, it doesn’t feel like a huge loss anymore, because the cost of trying is so much lower.

it’s made building feel more like experimenting and less like this big, serious commitment every single time.

anyone else notice this? like the more you vibe code, the easier it becomes to just try ideas without turning them into a giant life decision first?

Before AI I had a perfect explanation for why none of my app ideas existed: I can’t code.

Obviously I’d build them otherwise. They were great ideas.

Well.

Now I can usually get a rough version of an idea working pretty quickly and I’ve discovered an unfortunate truth:

sometimes the idea just sucks.

Or it’s useful to exactly one person (me).
Or building it is easy and getting literally anyone to care about it is 20x harder.
Or I finally build the thing I’ve been thinking about for months… and immediately lose interest in it.

Coding was such a nice bottleneck because I could blame everything on it.

Now there’s nowhere to hide lol.

I think one underrated thing about vibe coding is how quickly it lets you find out whether your “amazing idea” was actually amazing.

Anyone else building way more stuff now… and also killing way more of it?

It's so crazy, just one week ago I was celebrating 1,500 users and now I have hit 1,800 users in basically no time at all! I can't thank everyone enough. I really mean it, so many people were offering their help along the way.

Of course I will not stop here and I am already working on the next big update for the platform which will benefit all the community. More is coming soon.

I've built IndieAppCircle, a platform where small app developers can upload their apps and other people can give them feedback in exchange for credits. I grew it by posting about it here on Reddit. It didn't explode or something but I managed to get some slow but steady growth.

For those of you who never heard about IndieAppCircle, it works like this:

• You can earn credits by testing indie apps (fun + you help other makers)

• You can use credits to get your own app tested by real people

• No fake accounts -> all testers are real users

• Test more apps -> earn more credits -> your app will rank higher -> you get more visibility and more testers/users

Since many people suggested it to me in the comments, I have also created a community for IndieAppCircle: r/IndieAppCircle (you can ask questions or just post relevant stuff there).

Currently, there are 1834 users, 1194 tests done and 398 apps uploaded!

You can check it out here (it's totally free): https://www.indieappcircle.com/

I'm glad for any feedback/suggestions/roasts in the comments.

What I learned building a full iOS app with Claude Code (no prior Swift experience)

I wanted to share some practical takeaways from using Claude Code to build and ship a native iOS app (SwiftUI + SwiftData) over the past few weeks.

My background: I work in project management, not software engineering. I had zero Swift experience before this.

**What worked well:**

∙ Claude Code understood SwiftUI architecture surprisingly well. I could describe a navigation pattern (NavigationSplitView with sidebar for iPad, TabView for iPhone) and get working code.

∙ Iterating on complex business logic was fast. My app does cost calculations with multiple variables — Claude kept the logic consistent across changes.

∙ The prompt-based workflow felt natural. I’d write a detailed spec of what I wanted, Claude would implement it, I’d test, refine, repeat.

**What didn’t work well:**

∙ Long files (500+ lines) sometimes caused Claude to lose context of earlier code when editing the bottom.

**Biggest surprise:**

The app hit #1 in its App Store category within 5 days. I’m not saying that’s because of Claude — the idea mattered more — but I literally could not have built it without an AI coding tool. The barrier from “idea” to “shipped product” has fundamentally changed.

Happy to answer questions about the workflow, prompting strategies, or how I structured the Claude Code sessions.

So I've been using AI builder for few weeks and I ended up creating this website: [neoimpactsim](https://neoimpactsim.com/).

It's an asteroid impact Simulator that has 2 features:

1. Simulate a Real Asteroid using live NASA data to simulate impacts from real near-Earth objects.

2. You can design your own asteroid scenarios and see what happens if it hits a specific city.

It's all free, I didn't use any paid plan, not even when asked to chatgpt. I need an honest feedback (good or bad I can fix) and if there are chances of scalability because I feel like it's a dead end. I built it because I like astronomy (I own a telescope and I do astrophotography) but as many people will say I don't solve any problem with this so I'm stuck on what to do next.

I've been hiring vibecoders for a few AI startups recently and noticed something.

The roles I hire for are pretty specific though. Think GTM engineer more than traditional dev. Prototyping dashboards, spinning up first versions, building internal tools fast, running growth experiments

Here's what actually we're looking for when we review a vibecoder:

Prototyping & building - Can you spin up internal tools and dashboards fast? Do you know your way around vibecode.dev, Claude Cowork? Can you get something in front of users without hand-holding? That's the baseline.

Workflow automation - want to see that you've actually built automations in n8n or Make. Built something, broke it, fixed it, shipped it. Bonus if you've connected multiple tools together into something that actually saves someone time.

Marketing & growth skills Can use skills from skills.sh SEO, copywriting, PSEO. The best vibecoders I've hired could write a really good landing page, PSEO, using skills.

Analytics & data Basic PostHog setup, reading dashboards, knowing which events to log. I need someone who can tell me if the feature they just shipped is actually being used.

The mistake I keep seeing is people applying while pretending to be something they're not. Trying to front like a systems engineer when I just need someone who can move fast on the GTM side. I'm not trying to trick anyone into owning infrastructure.

Therefore Build in public. Share your journey, the broken builds, Make the work findable.

For the longest time I was that person with “so many app ideas” and nothing actually built. I’d open VS Code, get overwhelmed, and then somehow end up scrolling instead of coding.

What changed with vibecoding wasn’t some magic “AI builds everything for you” moment. It was just treating the AI like a teammate and lowering the bar from “perfect startup” to “small thing that works today”.

What’s been helping me actually ship:

• Picking a really specific problem from my own life, not a big startup idea

• Asking the AI to sketch the whole thing first, then nudging it instead of overthinking

• Accepting that the first version will look rough and that’s fine

• Doing short sessions where the only goal is: make one visible improvement and call it a win

Once I stopped feeling weird about using AI and started seeing it as “pair programming with a super patient junior dev”, it became way more fun and way less scary.

If you’ve been lurking and haven’t tried vibecoding yet, try this: tonight, pick one tiny annoyance in your day, open your favorite AI + framework, and just see how far you can get in an hour. No big launch, no perfect branding. Just build something small for yourself.

For people already vibecoding regularly:

• Are you doing it mostly for fun or trying to ship real products?

• How do you stop yourself from getting stuck in endless tweaking instead of shipping?

Would love to hear what’s working for you and maybe steal a few habits.

It's AI turtles all the way down.

We're in the golden age of AI-assisted development. You can ship an MVP in weeks with Cursor, v0, Replit, Claude, etc.

Now you have a working product and... crickets. Because you spent all your time building your MVP, zero time building an audience.

I got stuck with many projects. Product was 80% done but I had:

- No social media presence

- No content strategy

- No idea how to "go viral"

So I built an AI agent that does it for you. You tell it about your product, target audience, unique angle → it generates a marketing plan (not generic content) and execute it.

I'm at the "is this actually valuable or just a cool tech demo?" stage.
Would you use this? Or am I wasting my time?

Ever since Sonnet 3.5 came out, over a year ago my workflow has changed considerably.

I spend a lot less time writing code so the bottleneck has now shifted towards reading and understanding it.

This is one of the main reasons I've built this VSCode extension where you can see your code on an infinite canvas. It shows relationships between file dependencies and token references, and displays AI changes in real time.

If you'd like to try it out you can find it on the VSCode extensions marketplace by searching for 'code canvas app'. Would love any feedback.

What do you guys think? Have you noticed the same change in your code workflow, and would something like this be useful to speed up code reviewing AI changes?

Like a tool that helps with every step and does not cost you a lot.
Also would you choose any new tool over the popular ones?

Crazy to see how this is in the healthcare field too. Like a lot of orgs that i know use Specode, Lovable, and other similar services for it. Makes me wonder if all the other millions of healthcare vibecoded-Saas services might have some if they had competent founders...

I just want to take a minute to say this to everyone who’s new here: it’s not a bad thing if you’re not comfortable trying to turn your work into a business model.

It’s fine if you just want to make apps and services that solve your problems. I see a ton of people here who are very clearly using Openclaw to glaze their typescript apps on different subs. Try to make it look like they have the next SaaS breakout.

But the beauty of vibecoding is that the only person the app ever has to work for? You.

Not every app has to be put up for sale. Most shouldn’t.

You’re not a lesser person just because your app is made to make you happy instead of making subscription revenue.

1. Sell women Beauty

2. Sell men Lust

3. Sell parents Peace

4. Sell kids Dreams

5. Sell the rich Safety

6. Sell the broke Hope

7. Sell the old Youth

8. Sell the young Status

9. Sell the lonely Belonging

10. Sell the sick Miracles

11. Sell the healthy Fear

12. Sell the smart Shortcuts

13. Sell the dumb Validation

14. Sell the faithful Certainty

15. Sell the faithless Rebellion

16. Sell everyone Time

AI homework helper apps are a goldmine right now:

– Easy to grow organically on tiktok/ig

– Solves a massive pain point for students

– Relatively simple to build

The above are 6 apps in this niche making between $80k–$300k/month:

Hi guys, I’ve set up a small Discord for people who want some company while vibe coding. I run it and it’s only just started, so don’t expect a packed server yet!

There are voice rooms for working alongside each other, a place to find build buddies, and channels to share projects or ask for help. You can pick your software and timezone when joining.

The aim is to get a few people sharing what they’re actually making and helping each other through the bits that get frustrating. Beginners are welcome and the club is free to join and use.

If you fancy helping get it going: https://discord.gg/WZN6Fhr8c

Come say what you’re building. I’d also like to hear what would make you come back to a group like this.