What are you building, and what does your stack look like?

building speakeasy — an ios app that turns any article url into audio. paste a url, get ai tts in ~30 seconds, saves to icloud

stack: expo + react native for the mobile side, fastapi backend, inworld tts (with openai as fallback), postgres. for auth its just device id stored in keychain — no accounts needed which keeps onboarding super minimal

biggest challenge has been text extraction — different sites block scrapers differently. revenucat for subscriptions has been great tbh, saves a ton of time vs rolling your own

been building a few ios apps under studio.gold 🔨 three live rn: speakeasy (turns any article url into audio), astrologica (ai personalized daily horoscope podcasts based on ur birth chart), and wordplay (daily cryptic crossword puzzles). stack is swift/swiftui native, firebase for auth + analytics, revenuecat for subs/billing which has been a lifesaver honestly. for the ai stuff in speakeasy and astrologica im using openai apis. biggest learning: revenuecat handles like 90% of the billing headaches so i didnt have to build any of that myself. happy to chat more if anyones curious about the indie ios stack 🙌

solo maker building 3 ios apps under the studio.gold umbrella. all native swift/swiftui, mostly vibecoded with claude honestly

1. speakeasy (speakeasy.studio.gold) — paste any article url, converts to audio. stack: swift, AVFoundation for playback, server-side tts pipeline. the core challenge was making voice quality good enough that you'd actually listen for 10+ minutes

2. astrologica (astrologica.app) — ai-generated daily horoscope podcast from your birth chart. stack: swift, openai api for generation, server-side audio rendering. the interesting bit is generating personalised content daily that doesn't feel repetitive

3. wordplay (wordplay.studio.gold) — one cryptic crossword clue per day. stack: swift, custom clue engine. the "only one per day" constraint is deliberate — forces me to make each clue really good rather than generating volume

for auth/billing: revenueCat for subscriptions, supabase for the backend. kept it simple on purpose — no fancy infra, just "does this work and is it cheap to run"

the common design principle: single-serving daily content. no infinite scroll, no engagement loops. each app does one thing then gets out of your way 🛠️

building Murror right now, an app for young people dealing with loneliness and isolation. the problem is real but most solutions either just throw people into group chats or give them a chatbot that feels hollow after a few days. we're trying to go deeper than that.

stack is pretty lean: React Native on the front, Supabase for backend and auth, and we're using some custom AI logic to make the experience feel more adaptive over time. solo design founder so i do most of the product and design work, leaning on AI heavily for engineering.

curious what problems you're solving @ryan_hendrickson, happy to jump on a call too.

Building Murror, an AI app for young people who feel isolated or lonely. The core idea is that a lot of Gen Z struggles with real connection even though they're constantly "connected" online, so we're trying to actually help with that.

Stack is pretty lightweight right now since it's early. React Native for mobile, Supabase for backend and auth, and OpenAI for the AI layer. For billing we're looking at RevenueCat too after seeing it mentioned here a few times.

Happy to swap notes with anyone else building in the consumer / mental health space.

Building Notion Launcher, a macOS desktop app that saves things like screenshots, highlights, and memos to Notion with global keyboard shortcuts. No need to open Notion at all. Currently working on a Windows port too.

Stack: Electron 40 + TypeScript, Swift for native helpers, Supabase for auth and DB. App distribution via Cloudflare R2.

The hardest part so far? I've been on Mac for 15 years. Just navigating Windows is a challenge.

I am going the full private way.

For authentication :

To create an account, a couple of RSA keys are created in the browser, one to sign/verify, one to wrap/unwrap (encrypt/decrypt can happen through hybrid encryption with wrapped AES keys).

All user data are saved in indexed-db (browser database) and exportable as file. User can encrypt both with a password (the keys are encrypted with password, the data with hybrid encryption) and he gets a password prompt to decrypt his key (then its data) upon opening the app.

To identify the user on the server when necessary, user RSA verify public keys is first sent to the server, then subsequent auth can happen through sign by the user/verify by the server.

Permission for the user can be stored along the verify key in the server DB.

Billing through moneropay for absolute privacy for the user.

Additional benefit : even if some attackers get into the server and find the database, there isn't one byte of data they will be able to exploit.

Building thevibepreneur.com — a platform that validates micro-SaaS niches with real buyer proof before you write a line of code. The core problem: most indie hackers build something nobody pays for, not because the idea is bad, but because they validated with surveys instead of money. Stack is intentionally boring: Next.js, Supabase (auth + DB), Vercel for hosting, Stripe for billing. The interesting part is the research engine underneath — we scrape job boards, Reddit pain threads, and competitor reviews to identify niches where buyers are already spending, then package it into a report with a vibe coding blueprint so you can actually ship it. Permissions/auth is Supabase Row Level Security — verbose to set up but rock solid once it's there.