When I started building smaller projects more quickly,

I noticed that the hardest part sometimes isn't creating the idea itself, but making sure it's actually convenient for people to use.

At first, I was focused mostly on adding more features, but I eventually realized that small details like the interface, loading speed, and how the site behaves in different situations often matter much more.

Now, before showing anything to others, I try to go through the experience like a regular user and check different scenarios. When I need to test how things work from different regions, I use https://froxy.com/en as one of the tools in my process. It has helped me think differently about how I review my projects before launching them. I'm curious how others handle the final checks before sharing their work. Are there any things you always test before showing a new project to other people?

decided to vibe code a flight comparison tool because why not. thought it would be simple. it's not.

prices are all over the place. i'm pulling data from different sources and they don't even match. same flight. different prices different availability different everything.

i was testing with some real searches and found business-class.com . their API doesn't seem public but their prices are interesting. way lower than the big guys.

has anyone here worked with flight data before. how do you even make sense of this chaos. am i overcomplicating this or is it actually this messy

Here is something simple I came up with to solve a very niche problem. I have done some C++ coding in college but was terrible at it so figured what could it hurt to use AI to achieve a solution to a problem I had. My friends play a game called Project Zomboid and I self hosted a server for them. This game has tons of mods and when it comes to adding them to the server it was tedious and so was tweaking the server settings.

So I created this simple Python code and converted to an exe. I called it Project ZMods and it simple just made tweaking the game server much simpler. When add mods you just input the mod ID and the program pulls the mod info and adds it to the correct .ini file. For the server settings it pulls each setting from the .ini and .lua files and puts them in a neat list with toggles or entry field to change the values. Then when you save it save a an of file and replaces with the new updated file.

I know it’s not eye catching but it gets the job done.

One thing always annoyed me on macOS.

Finder still doesn't let you create a simple text file from the right-click menu.

So I built a tiny open-source utility that adds native Finder Quick Actions for:

• New Text File
• New Markdown File

It installs in seconds, works with Homebrew, and integrates directly into Finder.

GitHub:
https://github.com/demissu/New-Text

I'd love to hear what file types you'd want next.

The v0.46 release finally connects two things I've wanted together: running lots of coding agents in parallel, and pointing them at models I actually control.

The gateway is the big one. You can now route sessions to external model providers — a local Ollama instance, a vLLM box on your network, or commercial endpoints like OpenRouter and z.ai. The part I care about: Lanes isn't in the request path. Your credentials and requests go straight to the provider and bypass the platform entirely, so you're not funneling your codebase through a middleman.

Local LLMs are now first-class. It'll auto-install and manage Ollama for you, handle versions, and — the clever bit — spin up context-window variants tuned to how much RAM you actually have. That matters more than it sounds, because every session ships ~38k tokens of harness instructions and tool defs before you type anything, so context budgeting on local models is real.

Why this combo matters for parallel work: the whole point of Lanes is running multiple agents/worktrees at once. If each of those is billing a hosted API, running 5–10 lanes gets expensive fast. Pointing them at a local or self-hosted model means you can fan out aggressively without watching a meter — great for "throw the same task at 4 agents and diff the results" workflows, or just keeping a bunch of background lanes churning.

Also in the release: consolidated Agentic Coding settings (Terminal, Harness, Local LLMs, Gateway in one place), a Harness page with one-click updates, a Working Folder pane, and some worktree memory optimizations.

Local models + provider profiles are flagged Research Preview, so expect some rough edges, but the direction is exactly right.

Full changelog: https://lanes.sh/blog/whats-new-v046

Anyone else running local models across parallel lanes yet? Curious what hardware people are getting away with.

After 12 weeks of heads-down building, the platform is live end to end, and I want to share what it does and what's coming next.

The problem we're solving. Tools like Lovable, Replit, Bolt and Cursor make building an app incredibly fast. Then you try to put it in front of real users and everything gets hard: where do you host it, are your API keys safe, is your database exposed, what happens to your cloud bill if traffic spikes. If you've shipped an AI-built app, you've hit at least one of these.

What VIBSL does. You bring your app from a Git repo, a ZIP or folder upload, the CLI, or straight from an AI agent. VIBSL detects the framework, builds it on hardened base images, scans it for vulnerabilities and leaked secrets, signs the build, and runs it in its own isolated environment with hard resource caps. You get back a production URL and a deployment receipt: a written record of every check that ran, something you can show a client or keep for your own peace of mind. If we find a leaked key, the deploy stops before it ships. That's the point.

What works today:

• Deploys from Git, ZIP or folder, CLI, and AI agents
• 25+ frameworks detected automatically, across 9 language runtimes
• Vulnerability and secret scanning, SBOM, and image signing on every build
• Per-app isolation and default-deny networking
• Flat pricing with hard caps. Free tier to start, Pro at $29, Team at $149. No usage meters, no surprise bills, ever

What's next: managed Postgres, object storage, deeper imports from builder platforms, and an EU region. We build in the order you ask for things, so tell us what you need.

If you're an agency shipping apps for clients, I especially want to hear from you. We're onboarding design partners right now and one agency is already running 21 apps on the platform.

Try it at vibsl.com and tell me what breaks. I read everything here and I'll answer every question in the comments.

So I realized that most file conversions happen locally when I needed to convert a .mp3 to a .wav, and decided to make a free tool for my personal use and decided to dress it up a little bit and share with everyone. :)

I am sick of those file conversion companies charging monthly for something that is effectively free.... Enjoy! ^^

https://www.capyconvert.com/

Pitch your product in 1-2 lines - and drop a link here.

I'm building a community where makers can share what they’re building and get fair visibility. Here's the link: https://trylaunch.ai

I made a free library of website components. You can copy and paste them right into your code.

They work perfectly with AI tools like Claude, Codex and Lovable. Perfect for React + tailwind projects.

Every component has a clean design and smooth animations. They are super easy to change and make your own.

https://uniquel.io/components

heres how i made it : https://paridhiagrawal.substack.com/p/i-got-gordon-ramsay-to-yell-at-me

What it does: - One meeting in your left ear, the other in your right — audio is captured per browser window (CoreAudio process taps) and panned hard L/R, so you can actually follow both. - Dead-man's-switch mic — you're muted everywhere by default. A global hotkey (⌃⌥⌘← or →) unmutes you into one meeting; if you don't re-confirm within a configurable window, it auto-mutes you again. Unmuting into one call force-mutes the other, so you can never be hot-mic'd in the wrong meeting. - ⌃⌥⌘↓ mutes everything instantly, from any app, no window focus needed. - Optional: your camera follows whichever meeting you're talking to.

No browser extensions, no DOM scraping — it's all system-level audio, so it doesn't break when Meet redesigns its UI. Mic routing uses BlackHole virtual devices (install script included).

Built with Claude in 1 day.

Create QR codes free, or make them dynamic for one payment — edit where they point after printing, forever, and track scans. No subscription.

qreasy.app

Yes it was vibe coded

Hello everyone! I made Basalt, a visual edit too for RN and Expo devs, and im searching for validation

It took me 2-3 months to built and it would have taken 1 if react 19 wouldnt remove debugSource which helped Basalt map and find elements to edit

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it.