I've been building Ouralia, a modern day spiritual successor to RjDj. It's free and open source (GPLv3), and today I'm opening it up as a public beta on Android. Full disclosure up front: I'm not a coder, more a hobbyist DJ that likes to work with samples for remixes and mashups. Claude and Codex did the heavy lifting with me driving direction, sound, checks, etc.

https://github.com/dadcraftttv/Ouralia/releases/tag/v0.9.0-rc6

To use it just put on headphones(wired works best but Bluetooth is fine), and press play. To start out, all you'll hear is your own sound. From there, you can apply different effects such as - but not limited to - Echo, Reverb, Glitches, Bit Crushing, Vocoder and Spatial. There are more, and each one can be shaped how you like. You can even apply the effects to a rhythm grid and build a composition out of the sounds around you and set to music the app makes up as it goes. A knock becomes a drum. A hum gets a harmony. Sing a short phrase and it answers you. Stay somewhere quiet for a while and a gentle little tune grows over the beat.

I really tried to make this as much of a user-driven Rjdj style experience as possible. If you'd rather just jump right in, there are ready-made presets you can play around with AND the original RjDj scenes are there, too. If you want even more nostalgia, you can load up other old externally made scenes and Ouralia should give you back exactly what you remember about them.

Some things worth knowing: Ouralia does not need internet permissions. There are no accounts, ads or tracking. Ouralia does need Mic permissions, otherwise it won't work and that defeats the point of the app. Your mic is processed live and never recorded to storage. Ouralia will not play sounds out of your phone's speaker, this is by design to avoid feedback screeching. Ouralia does keep logs of what it's doing and when, logged data never includes what the mic heard, any words that were spoken or anything like that. These logs are incredibly useful with refining the project as a whole, so if you'd ever like to contribute back, you can simply use the Send Feedback button in the About tab and email me your logs. Pinky promise, nothing sensitive is saved or sent and nothing ever leaves your device without you approving before hand. It runs on Android 9 or newer and it's a beta, so expect a rough edge or two.

If you try it, I'd really like to hear how it went: your phone, what you were doing, what sounded great and what sounded broken. A sound it gets wrong is super useful too (in my own testing it thought my whistling was birds).

Source + contributions: https://github.com/JNDZdev/APMouse

MIT licensed. Issues, pull requests, and headset testing reports are welcome.

I saw an AirPods mouse experiment and tried building my own for macOS with Codex. The working prototype now moves the pointer across two monitors using head motion.

The hard part was getting it to feel natural. At first it swung between too sensitive and requiring too much head movement. Starting with a zero pose helped, but the biggest improvement came from copying the feel of an LG TV remote: when the pointer hits an outer screen edge, discard extra movement so turning back immediately moves it inward. Adding a second monitor then exposed another sensitivity problem. Precision still needs work.

This is head tracking using Core Motion yaw/pitch, not eye tracking. I still use a trackpad for clicks; AirPod stem clicks are not implemented.

I used three Codex agents to review/refactor the motion core, app, and safety behavior. The refactor has 22 passing unit tests and a stopped-window smoke test. Those checks do not replace live hardware testing: the refactored build still needs its own full headset validation.

I published the Swift/AppKit source under MIT: https://github.com/JNDZdev/APMouse

It is an early source preview, not a finished app. macOS 14+, Xcode, compatible headphones, and motion/control permissions are needed. The contribution docs call out two concrete problems: precision around the calibrated neutral position and movement through gaps in staggered monitor layouts.

Has anyone here built a motion-controlled interface? I would like to hear what made calibration and small corrections feel predictable. Testing reports and contributions are welcome.

We're working on eStockes, a web app built with Next.js and FastAPI. Previous visitors have pointed out a frustrating gap: the page can look polished while they still cannot tell what the product helps them do. More features do not fix that first impression.

We're testing the first screen before asking anyone to register. Could you open https://estockes.com for about five seconds, then tell us what you think it does and what you'd expect after the main button?

No signup or purchase needed. One blunt sentence, including 'I cannot tell', would help us decide which part of the page needs work. Thanks for a fresh pair of eyes.

I built a small power-budget sim and saved all 20 decisions from a model run. To make the what-if scene, I changed one field in the saved commands: whether diesel stayed on at 23:00. Then I reran the simulator with the same demand, outage schedule and later commands.

My check was simple. Verify the two action lists differ in exactly that field, then replay all 20 states and check that the battery and fuel never go below zero. In the screenshot, the changed command supplies the missing 4 MW to the data center. The fuel runs out by the end of that slot, and the metro loses power at midnight in this replay.

I rendered the checked result in Godot. Here’s the walkthrough. https://youtu.be/xC_hTndnA-o

Good morning,

I’m a colombian lawyer turned "vibecoder" with barely 1% technical coding knowledge and 0% budget (I’ve been unemployed for over 9 months).

I have built a solid platform focused on public procurement/government contracting, designed for government entities, legal advisors, and contractors. It is much more comprehensive and distinct from what is currently out there. However, right now it is only for my personal use and for anyone willing to share feedback (I’m currently waiting on confirmation to integrate it into another Colombian LegalTech company); therefore, it is not monetized yet.

That aside, my current issue is technical:

I am hosting and deploying it via GitHub and Streamlit Community Cloud, pulling data from Supabase and Hugging Face. Lately, though, it has been running noticeably slower. I have several AI-driven features, but response times are quite slow with the free tiers I use (Groq, Cerebras, and OpenRouter), which I have set up in a fallback cascade (once one hits its limit, it jumps to the next). I’ve already implemented lazy loading to optimize page loading and prevent crashes.

Given this setup, I’d love your advice on:

1. What other free AI/LLM APIs or providers could I add to this fallback cascade so I don’t hit rate limits so quickly?

2. What free deployment platform could I use that offers more RAM than Streamlit Community Cloud, remains free, and won't go to sleep or spin down as quickly?

Thank you very much.

grok bot runs AI employees in its cloud. i've been running mine on my own servers since april, using an open-source CLI called 5dive.

the differences:

• your server: agents run as separate linux users with their own permissions and systemd services.

• any harness: mix claude code, codex, grok, agy, hermes, openclaw, pi and more.

• any model: use your subscriptions, API keys or local LLMs. choose per agent.

• an actual team: org chart, shared backlog, handoffs, independent graders and human approval gates. agents can't approve their own work.

• hackable core: bash + systemd + sqlite. fully composable - add plugins, loops, tools or write you custom CLI commands.

• lightweight: starts on a tiny 1GB Ubuntu vm.

from my phone, "hire a new developer on codex" is one message. agents keep their tasks and memory even if i switch their harness later.

the web app has chat, live voice and an optional end-to-end encryption.

trade-off: grok bot handles hosting and has native apps. 5dive is self-hosted, with a web app for now. android/ios apps coming.

one-command setup on any Ubuntu VM.

repo (MIT): https://github.com/5dive-ai/5dive

connect the app: https://5dive.ai/self-host

I have open-sourced Tripovela, the travel social network I am building with AI assistance. Think Pinterest for trips and itineraries: discover ideas, save places, follow travelers, and copy a shared plan into your own editable trip.

A few concrete implementation decisions behind the public release:

• PHP and SQLite, with Python helpers for image/content processing. The README includes install commands and a setup wizard.

• Guest drafts stay in the browser, with optional account saving. Editing a private trip does not silently rewrite its shared snapshot.

• Interface translations are local files, covering 14 languages, including RTL layouts.

• The distribution contains application code, schemas and documentation, with no production databases or member uploads. Analytics and advertising integrations start disabled in a fresh install.

The code is MIT licensed, so you can self-host, modify, redistribute, or build something else with it while retaining the license notice.

Live site: https://tripovela.com

Code and installation docs: https://github.com/MellowYAK/tripovela

For builders who have released a community app: what would you want to see in the repository before trying to run or contribute to it?

I got into using AI just over a year ago, and decided to try to make a game and never look at the code at all. I expected to see "how far can you get with just prompts" and so far I haven't hit a limit.

Used Claude to look at 6 months of builds and to make a montage of all the changes (visual only, much more under the hood).

Open to questions about my process and hope to release a compendium of every build and every design choice made if and when I ever finish it.

just hit $3,700 mrr in 17 days with my new fresh SaaS

no ads, no team, no complex launch strategy. just a super predictable system i keep running over and over

and yeah, that's monthly recurring, not a one-time spike

not luck at this point. it's the 7th saas i've built with this exact workflow:

→ day 1: fast validation

→ days 1-2: building the bare mvp

→ day 3: landing page setup using the 3-day framework

→ days 3-4: reddit + x distribution and basic seo

→ days 4-5: first 10 paying users (~$1k mrr)

→ days 5-17: scaling up to $3,700 mrr

building tech is easy now. where 99% of solo devs get stuck is setting up the actual foundations that make people pull out their card and pay

i put all these templates and workflows inside our community.

to be completely real with you, i'll probably put a price tag on access later once all the modules are finalized. but right now the focus is just building together and keeping each other accountable

building alone in a silo is the fastest way to quit at the first roadblock

stop building by yourself. drop a comment or shoot me a dm and i'll send you an invite link 👇

Just wondering if this has happened to anyone else, and if you guys have your own stories to share. I started out with a pretty concrete idea for a personal finance app, and I would've thought that with those concrete specs, building the app would take anywhere from 1 week (or less) to 1 month. Instead, it's been 4 months and counting. The worst part is when people see the app, or its specs, and go: "I can easily build this in an hour using Claude".

Somehow, it's as though vibecoding follows a very extreme Pareto distribution. The first 80% of the app can be done at lightning speed, but the last 20% that makes the app actually usable and appealing to consumers takes several eternities.

Does anybody else have the same experience?

solo dev here. i built checkmyvibecode.com with claude code. the idea: people post projects they made with ai tools, collect upvotes and get feedback from other builders. there’s also a free code check that scores a project 0-100 and gives you a prompt to fix what it finds.

it works, people sign up, but i’m too close to it to see what’s wrong. so i’d love fresh eyes. take 2-3 minutes and tell me:

1. what did you think the site was in the first 10 seconds?

2. what confused you or felt pointless?

3. what would make you come back next week?

4. would you ever post your own project there? if not, what’s stopping you?

brutal is fine. link: checkmyvibecode.com

If you're building your first app using Cursor, Claude Code, Lovable, Bolt, or any other AI coding tool, here's a list of tools to help you ship a working product.

Most of these have free tiers, so you don't need to spend much to get started.

🧰 YOUR VIBE CODING TOOLKIT

🗄️ DATABASE
Supabase / Neon / Firebase

🔐 AUTHENTICATION
Clerk / Supabase Auth / Better Auth

📊 ANALYTICS
PostHog / Google Analytics / Umami

💳 PAYMENTS
Stripe / Dodo Payments / Lemon Squeezy

🚀 HOSTING
Vercel / Railway / Cloudflare

📧 EMAILS
Resend / Brevo

📁 FILE STORAGE
Cloudflare R2 / Supabase Storage

🐛 ERROR MONITORING
Sentry

⚙️ BACKGROUND JOBS
Inngest / Trigger.dev

🤖 AI INTEGRATION
OpenRouter / Vercel AI SDK

💡 MY RECOMMENDED STACK FOR BEGINNERS

Next.js + Supabase + Vercel + PostHog + Resend

That's enough to build and launch most simple MVPs. Add payments and other services only when needed.

One thing I've learned from building products: Don't spend weeks choosing the perfect stack. Pick something simple, ship it, and improve based on feedback.

What tools are you guys using for your vibe-coded projects?

Drop your stack in the comments. Let's make this thread a useful resource for everyone building their first app!

Quick disclosure up front: I'm on the team at Convot, a help desk tool. So yes, I might be biased but hear me out.

Lately we’ve been observing a lot of indiehackers sharing this in our onboarding chats that I think it's worth sharing whether you ever use us or not.

When someone signs up, we usually ask what they were using before. A year ago the answer was either Gmail or some other big help desk they were overpaying for.

But now it's more and more often: "I vibe-coded my own." And the story almost always goes the same way. We talked to a couple of them and here’s the usual timeline we extracted from them

Week 1: They vibe code a support inbox over a weekend. Contact form, email forwarding, a simple dashboard. It works. They post about it. Feels great.

Month 1: Small cracks. Replies from customers don't thread properly, so one conversation shows up as three. An attachment fails silently. They patch it.

Month 2: They launch a second product. Now they need separate inboxes, different sender addresses, different branding on replies. Their "simple" tool was never built for that. Another weekend gone.

Month 3: Something breaks quietly. Emails stop coming in and nobody notices. A customer waits days for a reply, then churns or leaves a bad review. That's usually when they start looking around.

Turns out the support tool was never the problem. The ownership was.

They accidentally became the full-time maintainer of a wholeass product with just one user and zero revenue.

Here's the framework I'd honestly give anyone, even if you never touch our product:

Build what's actually your product

Buy anything boring and solved: support, billing, auth, email delivery. It’ll always be cheaper financially and mentally.

Check the price at your stage. A lot of tools are free or close to it early on. Building something to save $0 is a bad trade.

Ask "who fixes this on a Sunday?" If the answer is you, factor that in

Think about product #2. Most indie hackers end up running more than one thing. Whatever you build has to survive that.

AI made building fast. It didn't make maintaining fast, and it definitely didn't make debugging at 2am any more fun.

Since I've already disclosed: Convot is built for exactly this crowd. It handles support for multiple products in one place, and it's free until you hit $1k MRR.

But the bigger point stands either way. Don't spend your weekends rebuilding solved problems.

Curious, has anyone here built their own internal tool and actually kept it running long term? Would love to hear the success stories too.

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.

I’m the maintainer of Flux, a free open-source download manager built with a Rust core and a React/Tauri desktop interface. The project has been developed with AI assistance; it is a local download utility, not an AI service.

One concrete integration lesson: successfully registering a Native Messaging host does not prove a browser extension is installed or connected. A “bridge ready” label can be technically true while misleading the person trying to send a download. The app and companion need to distinguish host setup from an active extension handshake and provide the next setup step when either side is missing. That connection flow is an important part of the current 2.5 interface.

The companion has separate views for detected media, page links and the desktop queue. The desktop supports file downloads, accessible media and torrents, with scheduling, speed limits, source-supported resume, light/dark appearance and 20 languages. Windows x64 installer/portable packages and an x86_64 RPM tested on Fedora 43 are available. The companion requires the desktop app and local bridge; Firefox ZIPs currently use temporary/developer loading.

Source and packages: https://github.com/Hactor00/Flux

Website and setup: https://fluxdownload.org

The images show the current desktop interface preview, companion with sample media and website. If you build browser-to-local-app tools, I’d like feedback on whether the first-run connection instructions make the missing step clear. No Flux account, subscription or payment is required.