What are you building, and what does your stack look like?
by•
I am a Computer Science student doing research into how solopreneurs and small startups create new apps and what their stack looks like. Particularly, I'm interested in how you handle things like authentication, billing, and permissions/authorization in your apps.
Let me know what you're working on below and how you're going about it -- I'd love to connect for some quick calls to learn about your product and talk about your process in building it!
1.2K views
Replies
Building vibepreneur.com — a platform that validates micro-SaaS niches before you build. Stack: Next.js, Supabase, Claude for research synthesis, Airtable for content pipeline. Auth via Supabase, payments via Stripe. The interesting part of our stack is the validation pipeline: we use a mix of Reddit signal analysis, Product Hunt launch data, and real buyer intent patterns to score niches. The insight we kept hitting: most solopreneurs pick markets too broad and get crushed by incumbents, or too niche and find no buyers. We're building the gap between idea and first paying customer. Always happy to trade notes with other indie builders on what's working for auth and billing — the boilerplate stuff eats more time than it should.
I just launched Amplitron, a free open-source guitar amp simulator!
Tech stack:
• C++17 with PortAudio for low-latency audio I/O (~1.3ms latency with 64-sample buffer at 48kHz)
• Dear ImGui for the visual pedalboard UI (drag-and-drop interface)
• Cross-platform: Windows, macOS, Linux
• 9 custom DSP effects: Noise Gate, Compressor, Overdrive, Distortion, EQ, Chorus, Delay, Reverb, Cabinet Sim
• CI/CD with automatic builds/tests on all 3 platforms
• Thread-safe audio pipeline using try_lock to prevent UI blocking
It's all open source on GitHub. Built it because commercial amp sims are expensive for casual home practice. Would love to hear from other audio devs interested in contributing!
https://www.producthunt.com/products/amplitron
https://github.com/sudip-mondal-...
I'm building lightPDF, a high-performance, minimalist document viewer for the desktop.
The main goal is to create a fast, lightweight, and privacy-respecting alternative to bloated applications like Adobe Acrobat. It's an "offline-first" app, meaning it processes all your files locally on your machine without sending them to the cloud.
Here’s a breakdown of the technology stack I'm using to achieve this:
Application Framework: Tauri is the core of the project. It allows me to build a native desktop application using web technologies for the user interface and a Rust backend for performance-critical logic, resulting in a much smaller and more efficient app than something built with Electron.
Frontend: The user interface is built with React and bundled using Vite. This allows for a modern, responsive, and interactive UI.
Styling: I'm using Tailwind CSS to rapidly design and style the user interface, keeping it clean and consistent.
Backend: The backend logic is written in Rust. This provides memory safety, speed, and the ability to interface directly with low-level libraries, which is perfect for a high-performance application.
Core Rendering Engine: For the most demanding task—rendering documents—the Rust backend integrates with PDFium, Google's native C++ library that powers the PDF rendering in Chrome. This is the key to achieving "extreme performance" when opening large PDFs or comic book archives.
Its already in a beta stage and the idea is to try and keep it lightweight and free. The plan is to keep exe installer below 15mb(dll itself is around 6 mb) msi below 10 and overall HD usage below 20mb's.
Building thevibepreneur.com — a platform that validates micro-SaaS niches with real buyer proof before you write a single line of code. The model: paid niche reports (5 free, then paid). Each report bundles niche research + vibe coding blueprint + vibe marketing blueprint. Stack is intentionally thin because the product is research + curation, not software: Next.js + Tailwind on Vercel, Airtable for the content pipeline, Brevo for email, Stripe for payments. Auth via Supabase. The interesting part is the research process itself — F5Bot monitoring Reddit/HN for keyword signals, Product Hunt API for launch velocity, GSC for organic demand data. Synthesize that into a report that tells you whether a niche has buyer intent before you build. The biggest lesson: 'niche validation' as a category is massively underserved. Most people either build blind or spend months validating manually. There's a real market for compressed, pre-validated niche intelligence.