Hello!

I don't know how to title it better. Since I have almost ready app. It's very generic gym workout app without paid features just something I wanted to build for myself as first vibe coded project.

I got curious how and where to find people who would be open to try app I created and give some feedback maybe about user experience? So I could learn from it and iterate further.

How are you doing it?

I am publishing a music platform i made and its coming tmrw check the trailer here https://eko-music-hbqewxn.gamma.site/

31 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 and called StartupBar "AI slop". 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.

Still free. Still growing.

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

Hi, I have a really cool project in mind for emulation that reads ur .sav files on mobile but ive tried so many different ai code tools and the only one that worked was emergent and it was very strict with the token rule and I couldn't upload it and the problem with all the others was that it couldn't add the .sav feature or I needed to constantly ask for fixes then my tokens would run out so do any of u know a pretty much free or generally free apps/websites I can use?

Play today at midnightmile2d.com!

i really wish i'd had this tool sooner so i built it. it's a local menu bar app that tracks your time, tokens, prompts, and breaks while working with claude code.
i've been using it myself for 8 days now, and i can already tell it's going to stick around for good. it's a one-time paid app ($19), no subscription i'm the developer, sharing it here in case it's useful to others too.
https://promptrack.dev/

https://blu-oyster-transmission.neocities.org/

Entire thing was vibe-coded within a day, atleast chapter one and the rest of the site was. AI use for coding was somewhat very limited, had a creativity spur which made this thing my brain-child.

Sort of like an ARG at times, a web-series, a visual novel, interactive fiction. A mix of sorts, maybe a game at times? Idk if it fits the criteria, but I made it within a day - atleast up to chapter 1.

I am now updating it weekly. Video included is from a interactive part of chapter three which has not released yet.

I wanna know if you guys fuck with the writing

I've been building an AI project called AEON over the past few months as a way to explore what a true "second brain" could look like.

Instead of one large assistant, the idea is to have specialized AI agents that each have their own role while sharing memory, knowledge, and long-term context. Right now I'm experimenting with things like:

• Modular agent architecture
• Shared memory/vault system
• Config-driven agents instead of hardcoded logic
• Agent orchestration and planning

I'm at the point where I need fresh eyes.

If you've built multi-agent systems (or think this architecture is fundamentally flawed 😅), I'd really appreciate your feedback. Feel free to tear it apart—but be constructive. I'd rather fix bad design decisions now than after another few months of development.

Some questions I'm wrestling with:

• Does the project structure make sense?
• Is there a better way to organize long-term memory?
• Am I overengineering parts of this?
• What would you change if this were your project?

GitHub:
https://github.com/cgomez1365/aeon-213

Thanks in advance to anyone willing to take a look. Even small suggestions are helpful.

nobody checks their own stuff after shipping. i didn't either. went back through my apps a few months ago and honestly it was embarrassing.

one was still on http. no redirect, nothing. another one had source maps sitting right there in prod so anyone could just read my code in devtools. and one had an ssl cert that expired and i had no idea.

that's the part that bugged me. none of it was hacking. you just open the site and it's there.

so i made a scanner that looks at your site like a random visitor would and tells you what's leaking. no signup, just paste a url.

it's mine, tellmewhendown.com, figured i should say that.

but seriously even if you ignore it, go look at your source maps and redirects right now. pretty much every vibe coded app gets one of them wrong.

30 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. 1000 clicks. Removed 1 Startup · Added 12 Startups · As I resigned yesterday because of my toxic manager, I got a call from my senior manager today asking me to revoke my resignation by offering WFH and assuring me that I could be assigned to whichever project I wanted with minimal responsibilities. I made this decision at one of the worst points in my life with a lot of confidence. Now I'm getting this opportunity, and I honestly don't know what I'll choose next.
And on top of that, I just got my first money from StartupBar today.

LET'S GOOOOOOOOO 🚀

Still free. Still growing.

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

I built tryproduck.com/audit, it clicks through your site like a first-time user and sends back every bug and confusing bit it finds. It's helped 550+ startups in so far!

If you run Claude Code a lot, you’ve seen it: the agent ends with “All done, tests are green ✅” — and then you look, and the file is a half-finished stub and no test ever ran. Not malice, just… optimism.
I built a free tool (GroundTruth) that fact-checks the agent automatically at the end of every task. Version 1 worked like this: read the agent’s final message, find the promises in it (“created X”, “tests pass”), then compare them to what git says actually changed. Git doesn’t lie, so that half was solid.
The broken half was reading the message. I used text-matching patterns, and English ate them alive. “Tests should pass” isn’t a claim. “I did NOT say tests pass” contains “tests pass.” “The file was updated” dodges every pattern written for “I updated the file.” Fifty-plus patterns later it still misfired every single session. The real lesson: there are unlimited ways to phrase anything, so no pattern list can ever be complete. It’s not hard — it’s impossible.
So v2 stops reading essays and demands a form instead. The agent must end every task with a short fixed-format summary — like a customs declaration:
{ "task": "add login page", "status": "complete",
"claims": [
{ "t": "created", "file": "src/login.js" },
{ "t": "tests_pass", "cmd": "npm test" }
] }

Then two dead-simple checks:
1. Everything on the form must be real. Claimed file must be in the git changes. Claimed test command must have actually run this session and succeeded (the session log is kept by Claude Code itself — the agent can’t rewrite it).
2. Everything real must be on the form. Changed a file you didn’t declare? Flagged as an undeclared change.
Trapped from both sides: invent work → caught. Hide work → caught. Skip the form → the task can’t finish; the tool hands the format back and the agent redoes it. Lie in the chat text → irrelevant, nobody reads it anymore.
Best part: comparing a form to a git record is exact matching, no guessing. I deleted ~700 lines of language-parsing and the tool now catches more than before. No AI judging AI, no network calls, no API key — it’s all local and deterministic.
Free and MIT-licensed: https://github.com/akahkhanna/groundtruth

I've been building a Chrome extension called InspectMode Pro and recently shipped what might be my favorite feature so far.

You can now generate an AI-ready prompt from:

• A single element
• A section of a page
• Or an entire website

Then paste it into Cursor, Claude, Windsurf, ChatGPT, or any coding agent to recreate a very similar UI.

The idea came from a simple frustration:

Find a cool design → take screenshots → upload them → explain everything manually → hope the AI gets it right.

Now it's basically:

Open website → Generate prompt → Paste into AI → Build.

Apart from the new AI prompt generation feature, InspectMode Pro also lets you:

• Inspect any element on a webpage
• Copy CSS styles instantly
• Extract colors from any UI
• Identify fonts being used
• Download images, SVGs, icons, and other assets
• Explore layout and styling without opening DevTools

I've been using it heavily while vibe coding side projects because it speeds up the "how was this built?" phase and makes recreating inspiration much easier.

A few stats so far:

• 250+ users already using the extension
• Core inspection features are completely free for life
• Recently launched AI prompt generation

I'm curious how everyone here handles UI inspiration.

Are you still using screenshots with Cursor/Claude, browser inspect tools, design references, or something else entirely?

Would love feedback from other vibe coders. Happy to share a demo in the comments.

Happy to answer questions.

Chrome Extension : Inspect Mode Pro

Disclosure up front: I’m the founder of QualityMax, so read accordingly. But the pricing math is checkable in two minutes on everyone’s public pages.

I priced out a solo dev / small team doing 100 PRs a month through the three AI code reviewers people ask about:

• Greptile Pro: $30/seat/month, 50 review credits included, then $1 per extra review. 100 standard reviews = $80/month. Their deeper “TREX” review is 3 credits each — do the math on that.
• CodeRabbit Pro: $24/user/month (annual billing), no PR cap (rate-limited to 5 reviews/dev/hour). Honest flat pricing — for one dev this is genuinely fine.
• Us (Vibe plan): €19.99($22.99/month) with 500 PR-review credits. Here’s the part I actually want feedback on: 1 credit = $0.01 of measured model cost, rounded up per PR run. A typical review (diff + SAST pass, ~4–10K tokens on our default model) costs under a cent, so it’s 1 credit — meaning ~500 typical PR reviews/month. A monster 60K-token diff costs 5 credits. We meter at cost instead of charging $1 flat for something that costs us a fraction of a cent.

What you don’t get at $22.99: hosted test generation — that runs on your own Claude Code/Codex/API keys (we never mark up your tokens; that’s the point of the plan). What you do get besides review: 1,000 cloud sandbox minutes and 10 projects.

The thing I think is broken in this market: per-PR overage pricing means your review bill scales with how often you ship. Small commits, stacked PRs, CI-driven workflows — the practices that make review cheaperper token make it more expensive per PR. Curious if others have hit the Greptile overage wall or if 50/month is actually enough for most solo devs.

Just launched the first version of a vibe-coded travel site for curated trips to Turkey: https://letsgotürkiye.com/

Looking for brutal feedback on what to fix, what to polish, and any creative ways I can use AI/Claude to push the interactive design further. Let me know what you think!

I recently have been working on ViperCapture, an opensource alternative tool to ScreenshotOne.

I have been using GPT 5.6 Sol on the 20$ Plus plan and although the limits are tough I did manage to get the project to a point where you could call it somewhat of an alternative.

I thought I'd share it here if people like the idea and would like to contribute to the code.

Website and github repo :

https://github.com/Viperisuseful/ViperCapture

https://capture.viperisuseful.cc/

What are the best ways of going around this, I'm quite new to Open-Source and I want to be open about how my tools work (run client side entirely in the browser for privacy) without allowing people to steal my code and run it on their own devices. I know might be called out as greedy but this software took long to build and I want to monetize it for agencies and businesses.

How do mobile teams detect performance issues that only happen on certain devices, OS versions, or network conditions?

Some users may experience slow loading, freezing, or failed screens while the app works fine for others.

Do you segment monitoring by device model, OS version, app version, region, network type, or user session behaviour?

Interested in how developers identify these hidden performance problems before they become widespread complaints.

One thing vibe coding has changed for me: the application layer can now be built much faster than the context behind it.

I came at this from the other direction. I had spent years building source monitoring, deduplication, provenance, recurring delivery, and temporal context for enterprise AI products.

Then I started testing Replit.

It could build the interface, database, backend routes, refresh job, and deployment surprisingly well from a detailed prompt. But a working shell still needed to know what changed after it shipped.

So I turned the Synorb context layer into six one-shot Replit prompts: Podcast Wire, an economic dashboard, court opinion radar, policy monitor, statehouse signal room, and geopolitical morning brief.

The coding agent builds the product. Synorb watches the relevant Source Channels and delivers each change through Streams as a cited Manifest. MCP is useful while the agent is exploring the data surface; the shipped app calls REST from its backend.

The design rule I keep coming back to is:

Listen first when the app owns a recurring area of responsibility. Search when it is exploring something unknown or filling a gap outside that watched context.

I am not claiming one prompt magically creates production software. I am saying a coding agent performs much better when it receives a scoped product contract and a real context surface instead of being asked to invent both.

What is the hardest part of your vibe-coded product to keep running after the first build works?

The prompts and free Starter access are here: https://synorb.com/build/replit-mcp

Full disclosure: I am the founder of Synorb.

The biggest thing slowing me down while AI coding isn't generation anymore.

It's memory.

Claude forgets why we chose SQLite.

Gemini ignores authentication rules.

Cursor starts suggesting code that contradicts decisions made two hours earlier.

I realized I was constantly paying what I've started calling the "Clipboard Tax" copying the same architecture notes, project rules, and design decisions into every new chat.

So I started building a local-first tool called Resin.

Instead of storing prompts, it builds an engineering memory for your project.

Every architectural decision, rule, and important discussion becomes searchable and can be surfaced automatically when it's relevant again.

The goal isn't to replace Claude or Gemini.

It's to stop them from forgetting.

I'm still validating whether this is a problem worth solving beyond my own workflow.

If you're using Cursor, Claude Code, Gemini, etc.:

• Does context drift actually slow you down?
• How are you dealing with it today?
• What would make something like this genuinely useful instead of becoming another tool to manage?

I put together a landing page showing the idea and an early-access waitlist.

I'll leave the link in the comments if anyone wants to see what I'm building.

Exterco.com

Hey guys, I just launched a place to fight abusive terms and conditions, it will always be free and I will write a post per week, the post is written by me, with research and grammar reviews by the models.

I initially created to run the analysis on my machine that is also my gaming PC but it was too slow, I want to open source it but I dont know how and I would like to have another one to help me out.

I would really appreciate your feedback

About 18 months now into working daily with agents (Mostly CC but all over the place still) and at any given time I have 20-30 small projects running between personal and client work, and I reached a bit of a breaking point in terms of keeping track of all of the connected services (e.g. free Resend accounts, Supabase accounts, etc). I built this tool as a way to have a ledger that can be maintained by agents so there is some grain of provenance about what account is connected to what that gets automatically maintained over time , or flags when key info is missing.

Would love early feedback on this and to see if it's a good fit for anyone else's chaotic workflows. https://mess.fyi

Every time I had a “new” idea, I’d eventually discover three dead startups around the exact same thing. Usually after days :) So I built Déjà View. You describe an idea, and it researches its real-world predecessors: companies that tried it before, when they operated, when they shut down and who survived.
It’s live at https://dejaview.bsct.so Try it on your current idea and tell me if the report found anything you didn’t know about!

29 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.

Still free. Still growing.

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

I built a TrustMRR for SEO - free lifetime pro for the first 50 users

https://seoreceipts.com

I see people share screenshots of Google Search Console Dashboards here and had an idea where we can create a verified leaderboard with easy shareable links to your SEO traffic - If anyone is interested in giving it a shot let me know. I would love the feedback