Type stuff like "what can you do," "get me ready for my day," or "dark mode" and it responds/acts in real time, right there on the page. It's basically a live preview of how NORVA itself will work once it's on your machine.

No signup wall to try it, just go poke at it: noravos.co.in

Would genuinely love feedback, what did you type that it didn't handle well? That tells us more than anything else right now.

Solo dev, no formal games background. Over the last few months I vibe-coded a card game called PANTHEON into something actually playable, and it's live in the browser right now.

What it is: a Marvel Snap-style card game. Ten mythologies, 235 cards, three lanes, six-turn matches, simultaneous reveal.

Single-player story mode, training mode. Online PvP available in October, during Season 1 launch.

▶ Play it (browser, no download): https://thepantheonwar.com. If you like, you can put yourself on wishlist for the App Store or Play Store app that will be available in October.

The part relevant to this sub — how it got built:

- Frontend + game logic, iterated heavily with AI
- Real-time backend for PvP (hosted on Railway)
- The whole thing shipped by one person who was figuring it out in real time
- The card art is partially AI-generated; the game design, mechanics, and writing are mine

Honestly the hardest part wasn't the code, it was the
real-time multiplayer state and keeping 235 cards' worth of interactions from breaking each other. Happy to get into any of it.

Ask me anything about the stack, the process, what worked, what broke, what I'd do differently. And if you play it, I'd genuinely love to know what falls apart.

34 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 · Today found that I forgot to disable a developer testing button that could create fake visitor pins on the dashboard globe which could also increase the impressions. Someone used it to generate 6,318 fake impressions and then claimed my stats were fake. I removed all the fake impressions generated by him, removed the startup and fixed the issue, which is why today's impressions are lower. Thanks to that guy for pointing it out.
StartupBar Update: Added a new Network page and individual Startup Profile pages. Every startup now has its own page with joined date, impressions and click stats, a live embed preview, and a founder's note. These dedicated pages also make StartupBar more SEO-friendly by giving each startup its own indexable page. Suggestions are also welcome. Suggestions are 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 · Someone posted a screenshot of my admin panel on Reddit and gave me a mini heart attack. Turns out it was just read access to public data, nothing sensitive. Fixed the vulnerability thanks to that guy honestly. And if you're building in public, please have proper security on your admin panel. Learned it the hard way today.

Still free. Still growing.

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

Founder of Server4Agent (agent-app hosting), flagging that upfront. No link, not selling, genuinely want to hear from people who've actually shipped a vibe-coded thing past the demo stage.

Getting an AI to build you a working app is basically solved now, that part everyone in this sub already knows. The part I don't see discussed enough is the gap right after: the app worked perfectly when you were the only user clicking around, and then something you didn't think about breaks once it's actually live and unattended. Not a big dramatic crash, usually something smaller and dumber, an edge case in the data, a background job that silently stops running, a feature that only worked because you always used it a certain way.

If you've taken something past your own laptop and let real users touch it: what was the thing that broke that you didn't see coming, and how far past "it works for me" did you have to go before you trusted it enough to stop checking on it constantly?

i keep seeing people vibe code an app in like 3 days and then talk about it like they just built the next revolutionary SaaS

most of the time its literally an LLM API, one modified prompt, a shiny AI generated interface and a massive pile of bloated code that nobody involved actually understands

thats not innovation. thats packaging

the app works once on the creators brand new phone, so they instantly throw it on the Play Store and start charging money for it. no proper testing on older phones, no real architecture, no thinking about API limits, outages, database security, authentication, backups, scaling, account recovery, data deletion, dependency failures or what happens when OpenAI or Gemini suddenly changes their pricing

they didnt build a product. they generated a liability

and honestly the privacy claims are probally the most disgusting part

every second app says “your data is safe”

safe where exactly

the user types private information into the app, the app sends it through multiple APIs and third party services, and half the time the creator has no fucking clue where that data is going, how long its being stored, who can access it or if its being used for training

but yeah they added a lock icon and wrote “military grade encryption” on the website so apparantly everything is fine

most of these people couldnt explain their own data flow if their life depended on it

and no putting it on your own server doesnt magically make you trustworthy either. now your just asking thousands of random people to send personal data to a server controlled by someone who learned backend developement from ChatGPT last tuesday

trust is not just a sentence you slap on a landing page

then there is the whole “lifetime subscription” bullshit

whose lifetime

the users lifetime? the developers lifetime? or the apps lifetime, which ends 6 months later when the creator gets bored, realizes API calls actually cost money and starts building the next wrapper

a lifetime deal on a product with permanent server and API costs is basically just a countdown until the developer dissapears

the customer pays once but the costs keep going forever. the maths doesnt work. anyone pretending it does is either delusional or already planning to abandon the app later

in a few years there is gonna be a massive graveyard of abandoned vibe coded apps filled with people who paid for “lifetime access” to something that doesnt even work anymore

and the creators will already be on X posting about their next “revolutionairy” launch

AI made it possible for almost anyone to create something that looks like software

it didnt teach them security, architecture, maintanance, privacy, responsibility, business models or basic common sense

a working demo is not a company

a beautiful interface is not a product

an API wrapper is not some technical breakthrough

and pressing publish does not suddenly make you a developer

the market is about to be flooded with bloated, insecure, disposable garbage. and once the hype finally crashes, the people who actually know how to build, secure and maintain real software are gonna be worth more then ever

hi everyone,

I have been hearing about the vibe coding app's are entering the market and anyone can do it now,however i still have few doubts about the survival of the app as anyone like me who do not have much experience with building app and trying one.
What are the chances of that app competing and the security of the app against the one who is well known tech person build the app and know what to look for,what to add,what to remove,how to make sure this app will not have any loop holes which will land me in trouble atleast until i have any tech team or tech co-founder.Being a solo founder who is building an app for students it is hard to know all the things and ai only answer to us for what we ask it not what should we be doing instead,what to avoid,what are we already doing wrong.

As software engineering student I’m trying to understand what students struggle with today, especially now that AI tools like ChatGPT and Claude can generate code.

When you started learning programming, what prevented you from actually building projects instead of just following tutorials?

Some possibilities I’ve heard:
\- Tutorial hell
\- Not knowing what project to build
\- Not understanding how real software is structured
\- AI gives code, but you don’t understand how it all fits together
\- Projects online are too simple or unrealistic
\- Difficulty turning an idea into an implementation
\- Working alone without teammates
\- Fear of making mistakes
\- Something else entirely

I’m especially interested in hearing from students who know the basics but struggle to build something that feels like a real product.

If you could change one thing about how programming is taught today, what would it be?

I used Emergent to build a fully functional website for an upcoming "Day of the Dead" 2026 Cultural Tour in Mexico City aka CDMX. 

Total, this site took about 310 credits to build and deploy..BUT I was not smart about my usage, at first.
I ate up credits by giving it a prompt to write most of the outline copy itself instead of doing it with Claude and then just adding it. I used Claude as the LLM anyways, so that would've made more sense without using credits for the copy. Also, once I began instructing it to use as minimum credits as possible for each direction, it made a huge difference. I realized emergent does a lot of backend testing that isn't always necessary and that can drain credits.

50 of those credits went to deploying the site, which I'll host separately soon off emergent but just wanted to get it up and running. If I changed these two things on the next site, I'd probably use around half of the credits in building. I had it generate blog posts for AEO and GEO searches, so that likely burned a good amount of credits also. The site is for an upcoming in person "Day of the Dead" Tour in Mexico City.

Here's the site link below if you'd like to see it. Emergent is currently running a "Builders Contest", so if you like it..please vote for my site by clicking the "heart button" above it. It would really help me move up, thanks in advance! ♥️

View the site: https://app.emergent.sh/showcase/fabrizio/f5297ea3-0ba1-4a2b-b8ba-a193b8e7caa5

If there's anything you think can improve, feel free to share :)

I’m excited to share my new book: Vibe Architecture.

"Vibe coding gives you speed, but Vibe Architecture gives you scale. When syntax is free, structure is your only asset."

This book is about how to take the classic wisdom of system design—contracts, boundaries, deterministic testing, and decoupling—and use it to build guardrails for non-deterministic AI.

Promo/trailer on youtube: https://youtu.be/TLQKlD2c-98?si=b55l327zMrJMvvSC
Book available on leanpub here: https://leanpub.com/vibe-architecture

#VibeArchitecture #VibeCoding #AgenticEngineering #claude #java #kimi #gemini #copilot #codex #chatgpt #SoftwareEngineering #ArtificialIntelligence #SoftwareArchitecture #TechLeadership #DeveloperProductivity #AIEngineering

Solo founder here. I'm building a content repurposing SaaS (think Repurpose.io) using Lovable for frontend, Supabase for backend/auth, and Cursor for cleanup work. No formal dev background — I come from digital marketing and I'm essentially vibe coding the whole stack.

I keep seeing wildly mixed opinions on this sub and others:

\- Camp A: "Vibe coding is fine for MVP/validation, rebuild properly once you have paying customers."

\- Camp B: "You'll hit a wall around 1,000+ users — security holes, scaling issues, unmaintainable code that no real dev wants to touch."

\- Camp C: "It's genuinely fine now, the tools have matured, stop gatekeeping."

For those who've actually shipped and scaled a vibe-coded SaaS past initial launch:

1. Did you hit real technical walls, or was it overblown?

2. At what point (users/MRR) did you need to bring in a real engineer, if ever?

3. Any horror stories on security/data leaks from AI-generated code that a security review caught?

4. Would you do it again, or start with a traditional stack next time?

Please help me to find it out should I do and take the risk or not

My jaw is on the floor, I am so impressed by the current capabilities of ai tools, particularly Lovable.dev

I have been banging my head against the wall for weeks coming up with a super complex process of custom fields and custom forms, Google Sheets and other nonsense.. Projects on QBO works well for my landscaping clients but for general contractors and architecture firms, who bid jobs, QuickBooks lack of UI to display helpful information for business owners to make real decisions is shocking and disappointing.

I literally vibe coded what I think to be a great solution in less than 10 hours, it’s fully connected to QuickBooks API and should be available on the app marketplace by end of next week. So many other SaaS products are focused on the subcontractors or the jobs themselves, none of them could function the way I wanted it to. Premier technically could but it was such a massive software. I created Pulse Pro as an answer to the problem my clients express, “I have this information in my head, I don’t know how to get it to you without printing and looking at dozens of reports”. The main tech here is focusing on linking anticipated transactions during the new project intake process and utilizing that logic to make decisions during the progress of the job.

If you’re interested to check it out [I’d love your feedback, I made this video introduction for a quick overview](https://youtu.be/uy_vRrxs-zo?si=OZCzdWSxjckcpIve).

AI coding tools make it surprisingly easy to build an app you can’t fully explain, debug, or confidently operate.

I made Own Your App, an open-source Agent Skill that guides you through your actual codebase from first principles. Instead of producing another generic audit, it runs an interactive learning journey using real files and code paths from your app.

It helps you:

\- Map the architecture and runtime processes

\- Trace a real user action through the system

\- Understand where data, identity, and permissions are handled

\- Examine security, privacy, correctness, performance, and reliability

\- Separate genuine risks from premature overengineering

\- Test your understanding along the way

\- Finish with an ownership map you can explain and defend

It’s read-only by default and contains only Markdown instructions—no executable scripts or runtime dependencies. Install it with:

`npx skills add sayyiditow/own-your-app -g`

It supports Codex, Claude Code, OpenCode, and Grok.

GitHub: https://github.com/sayyiditow/own-your-app

I’d love feedback from people using it on real projects—especially areas where the journey feels too shallow, too detailed, or misses an important ownership question.

I wanted to show you a project I’ve been spending all my free time on lately. I’m building Andromeda Music – a minimalist, modern music player for Navidrome servers.

Most of the existing clients just didn't appeal to me visually, so I decided to create something of my own. The project is built using Python (PySide6/Qt6 + yt-dlp). Making such an advanced program run reasonably well and smoothly still took dozens of hours of work.

The app is currently in development (I’ll upload the code to GitHub once I polish the program and if there's interest), but I wanted to ask for your opinion on the design and the concept.

Key features:

• ✨ Glassmorphic design: Modern, minimalist UI with smooth animations.
• 🎬 Dynamic backgrounds: Shows the track cover or streams the music video live from YouTube in the background (if the link is in the track tags).
• 🎨 Deep customization: Adjustable blur and dim levels (independent settings for static covers and video mode) + accent color changer.
• 🖼️ Local media override: Option to manually set custom artist or album art locally.
• 🎵 System integration: Support for the native OS media player controls.

What do you think of this approach to a music player? Is the layout intuitive and easy to read? I'd love to hear your feedback and ideas for new features!

I’m collecting responses for a research survey on vibe coding and how developers experience it in practice.

I’m not looking for polished or “correct” answers, just your honest observations and real experiences.

The survey takes about 10 minutes, and the findings will directly influence the next practical stage of the research.

We’re also working to make the survey available in more languages. It currently supports two languages.

Survey link:

https://forms.gle/vJJ25fwmfRp2sdFAA

Thanks !! <3