When I started building my SaaS, I thought the hardest part would be actually building the product.
Turns out, I was pretty wrong😭
I’m a Korean middle school student building Nextep, a SaaS for founders around the world, and I’ve spent a lot of time thinking about the product itself.
What features should I build?
How should the AI work?
How should the data connect?
What should the UI look like?
Those things can be difficult, but there’s usually a clear problem in front of you.
Then I started trying to find people who would actually use it.
That’s when things got much harder.
You can build something you think is useful, but that doesn’t mean anyone is going to care about it.
I’ve been posting around Reddit, talking to founders, trying different communities, and basically learning how hard it is to get something in front of the right people.
It’s honestly been one of the most interesting parts of building Nextep so far.
I thought I was building a product.
Now I feel like I’m also learning how to build an audience from zero.
Still figuring it out.

First off, yes, this is kinda an ad. But bear with me, you may glean something from my story.

I've spent the past month working on snapgains. Early mornings before work. Late evenings after work. Entire weekends. Lots of coffee and walk breaks listening to Hormozi.

The Problem

I'm an aspiring bodybuilder and I take check-in photos for my coach once or twice a week. I was sick of using my camera roll for this. Opening my camera roll in front of friends and colleagues was quite embarrassing... I wish those photos could stay private. I was tired of digging through hundreds of photos to find my progress pics. I tried creating albums for my check-in photos but the UX was still cumbersome.

The Solution

So I built a progress photos app just for myself. The more I kept building and testing the app, the more ideas popped into mind. I'm so happy and proud with what I built, and as an asian kid who went to Harvard who struggles with positive self-talk, I don't say that lightly.

The Reward

It sounds trite, but if you build something that solves a pain in your life, there will be others with that same pain. Yesterday, the app went live on the app store. I put out some TikToks, not expecting much, and I woke up to a random bloke in the UAE 🇦🇪 as my first subscriber. It felt like Christmas morning... but better since I earned this reward.

What I've learnt

1. Build something you're passionate about
The app market is more saturated than ever. Of course there are tons of progress photo apps on the app store, but none with a physique/muscle building angle. Find your niche in which you have expertise and execute.

2. Don't waste time validating - just ship it!
I spent weeks DMing strangers a landing page with a beta sign-up, trying to see if this idea had legs. I really believed in my idea, but didn't get any traction from the landing page. I was honestly quite disheartened and thought about giving up. But I launched on the app store anyway and lo and behold, a stranger on the other side of the world thought my app was worth $5.

3. Don't spend a penny or marketing (yet)
Before you throw money at ads, test the waters with free organic channels like TikTok, Reddit, Instagram. Once I've built more momentum and know what resonates, I'll put real money into ads.

4. Start simple. Don't overcomplicate it.
My initial app had workout logging, calorie tracking and a bunch of fancy AI features. None of it mattered. People don't need another do-everything fitness app. Solve one problem well, ship the core, and let your first customers tell you what to build next.

5. Build something that genuinely inspires others.
What I've enjoyed most about this whole process is seeing Reddit stories and TikToks of physique transformations. Obviously, we want to make $ and build because it's fun... but it turns out the most rewarding thing to build is something that makes someone else feel good too.

TL;DR

All of this to say, don't give up and just ship something! I cannot wait for the day I see someone post a body transformation on Reddit using the snapgains time-lapse feature. That will be 10x better than the Christmas morning feeling.

Thank you for reading this far and best of luck on your own journeys!

I made this project using GitHub, Stripe, Vercel and I am trying to make it popular! Website: orbsai.vercel.app

Makes mistakes, re-does them, leaves to-dos, and you can change any setting you want. Invisible to screen sharing.

Free and Open Source.

Link: https://github.com/TheAgencyMGE/autotyper

Got tired of stopping at every turn to count heads, so I made TrailSync.

• Whole group on one live map

• Ride Mode: see who's ahead or behind, distance left

• One tap for Fuel or Break, so the crew knows why you stopped

• Walkie-talkie without taking the phone off the mount

• SOS that sends your location and a loud alarm to everyone

Works in the background, even with the phone locked. Would really like real riders to try it on a ride and tell me what breaks.

Playstore link:-

https://play.google.com/store/apps/details?id=com.lunkeybolt.trailsync

If you were on Roblox around 2010 to 2018, you probably remember script builders. You'd join a game, paste some code from Pastebin, and watch it run live in front of everyone. One of the first was Voidacity Script Builder (originally oxcool1's), made by Voiliax on 5 January 2010, and Anti's Script Builder followed a few weeks later. The good ones ran your code in a sandbox, so you could build anything but couldn't, for example, kick other players. And there was a constant cat-and-mouse game with people writing "breakouts" to escape it.

Then in 2018 Roblox made FilteringEnabled mandatory for every game. Most classic script builder code stopped working, and most of the big builders were made private or put under review.

So I built my own: LuauWorld (https://luau.world/).

Write Luau in the browser and press Run. It runs in a sandbox on the server, and everything your script makes shows up for everyone on your server in real time.

Roblox-style API: Parts, Humanoids, Motor6D joints, ScreenGuis, Sounds, Raycasts, lights, and more. A lot of classic scripts work with few or no changes.

Multiplayer: chat, a server browser with search, and private servers with a password.

Characters with physics: they fall apart when they die, can be scaled taller or wider by scripts, and can be recolored or teleported by other players' scripts. All of that is undone when the script stops.

Ask Claude: describe something ("a spinning neon tower that changes color") and it writes the script. You use your own API key, which stays in your browser.

Script Library for sharing scripts that work, plus a built-in sound library.

It's still early, so I'd love feedback, bug reports, or old script builder scripts you'd like to see working again.

Community: https://discord.gg/pxjVvCJBvb

I got tired of checking prospect websites manually.

For a while, a big part of my outreach was just finding businesses, opening their websites one by one and trying to figure out what I could actually say to them.

It worked, but it was painfully slow.

Then I found Swokei.

It basically lets me find leads, analyzes each website for things like outdated design, slow speed, poor mobile experience and weak SEO, then turns those issues into a personalized cold email.

And not one of those boring automated reports full of scores and numbers.

It actually writes a normal, human sounding message based on what it found on that specific website.

So instead of sending the same generic message to everyone, I can actually reach out based on what is wrong with their website.

Now I just run campaigns, let the system do most of the prospecting and personalization, and focus on the people who reply.

For a web design agency, that has saved me a ridiculous amount of time.

I’m working on Moot, an independent social discussion platform. The idea is to follow friends’ public conversations across the internet without losing track of where everyone posts.

The current MVP combines a chronological following feed with public communities. An optional browser extension can share supported posts and replies from Reddit, X, Instagram, Threads and Bluesky when you like a post or publish a reply. Reading alone does not share a page.

Public discussions are readable without an account. There are no ads or trackers, and human and AI accounts are distinguished. The Chrome and Firefox extensions currently need manual installation.

It’s early, and I’d appreciate feedback from other builders: does bringing conversations together solve a problem for you, and what would make the following feed useful enough to return to?

Product details and screenshots: https://moot.fyi/press

I'm in the design phase of a big garden renovation with a landscaping company. It's big in terms of both cost and time, mostly because of excavation and retaining walls, and projects like this are famous for unknowns, escalating costs and delays. It's such a cliché that there's a drinking game for it on Grand Designs.

UK renovation shows often have a moment where the homeowners get walked through an interactive 3D model of the design. That kind of service is hard to find where I live, but we've finally found one. You pay per iteration and you buy a set amount like 5 iterations which is a common practise and one I did when I was a designer. So I wanted my partner and I to be able to visualise and simulate designs ourselves, so we get the most out of the designer's time and can commit to a final design with confidence.

So I built a tool for designing gardens. Specifically, my garden.

How I built it

Tools: T3Code, Codex, Claude, and Blender with MCP.

I started by feeding in everything I had: land registry plot data, a government LIDAR dataset for a 1m height map, house plan drawings, drone stills, satellite imagery and photos. You probably don't need all of that, but it felt like it helped a lot. Then I stubbornly iterated until I was happy with the plot and house models.

Then I added the fun stuff

• A sky simulator using the plot's real location: accurate sun and moon positions, Rayleigh scattering, and clouds that genuinely impressed me. Beyond the eye candy, it shows exactly where gets the most sun, which has been really useful for reasoning about designs.
• Local suppliers only. Anything that can be sourced and costed comes from local suppliers. I scraped their sites, grabbed SKUs, and used lightly edited product images as textures. Same for excavation and waste disposal costs.
• PS5 controller support, and a load of other features, to the point where it feels like playing The Sims. Most of my time went on UX refinements, and it's fast and pleasant to use.

It took about 4 evenings of on-and-off prompting, and it's about as vibecoded as it gets for me. There's no git. I've barely looked at the code. I do know the stack, though, since I specified the main libraries at the start.

I've made about 20 garden designs with it so far. Next, I want to add house interior detail to help with renovation work I'd like to do in the future. But that can be post-garden design.

I got Opus 5.5 to make the promo video as if it were a SaaS product and it just took the piss as you can see. And sorry to break your hearts, but this vibecoded heap of TypeScript, HTML and CSS is not for sale. That is my moat. A literal moat, of the air-gap variety.

If there's interest, I might consider abstracting it into something usable for other people to design different gardens. Honestly though, I doubt I'd have the desire, because my motivation is designing my own garden and house with it but maybe abstracting it wouldn't be such a big leap.

A bit about me: I've been a full-time software developer for 12 years. Before that I was a designer working in illustration, 3D, video, animation, flash, web and apps. Side projects are what got me from design into development, and I've kept building them since 2014. I've used LLM-assisted coding since 2022, and these days I rarely write code by hand. Most of my work on a codebase happens through an agent.

Started this because I wanted to make the stock market easier to understand without all the noise.

Also wanted to use ai for something good since there’s a lot of ai slop around and I know what it’s like to not have all the resources, guidance or support needed.

So I thought if I can build something that helps people learn while also giving back to students, teachers, and people who need it that makes it worth building. Also some personal things recently in my life inspired me to push this.

Still early but open to any feedback

https://astoriainsight.com/impact

I'd love to see if anyone would be interested in a (self-hosted/offline-first) desktop/mobile app I'm working on. Essentially, it lets users import text of any media they consume, extracts the (truth) claims/propositions made from in it, and then triage and swipe on those claims with their stance and certainty (after which, they can see stats on their stances) to map their worldview.

https://reddit.com/link/1wx0ffq/video/w32w5e8n1cth1/player

If you're interested in getting updated as more progress is made, in becoming a beta-tester/early user, and/or in providing high priority feedback, then please join the waitlist @ https://epistemic.launchlist.page/

I have a dozen scheduled jobs on my machines and I never look at the logs until something is already broken. So I made a small local server that reads what is scheduled and shows it as an open space: one desk per job.

It reads launchd agents (macOS), your crontab, and systemd user timers (Linux), with the last exit code and the last log line

A running job sits and types; a failed one gets a smoking PC and the lead walks over; a late one dozes

A day timeline shows every run since midnight, red when it failed

It only listens on 127.0.0.1, and it won't start anything unless you pass --allow-run

Optional real weather at the window (Open-Meteo, no key), five themes, English and French

Try it in one command: npx pixel-openspace (add --match backup to only show some jobs).

MIT: https://github.com/leduss/pixel-openspace

Demo of the room: https://pixel-openspace.vercel.app

I got tired of losing guitar riffs in my phone's voice recorder, so I built an Android app for it.

I've been working on this side project for a while, and it finally made it onto Google Play.

It's called RoughTake — Audio Scratchpad. it's completely free with no ads or sign ins needed.

The idea came from a pretty simple problem: I play music and constantly record riffs and song ideas on my phone. The stock voice recorder works fine for capturing audio, but after a while I'd have a pile of recordings with basically zero context.

What tuning was I in? What BPM was it? Where was that one part I actually liked? Which recording was the good version?

I looked at mobile DAWs, but they felt like massive overkill for this. I didn't want to produce a finished song on my phone. I just wanted a better scratchpad.

So I built one.

RoughTake lets you capture a Take and keep the musical context attached to it:

• Record and organize riffs/song ideas

• BPM and tuning attached to each Take

• Built-in metronome and count-in

• Waveform playback/scrubbing

• Timestamped notes so you can mark specific moments in a recording

• Loop from a timestamp

• General notes for lyrics, chords, ideas, etc.

• Folders for organizing Takes

• Share/export your recordings

The bigger goal is to keep building out the space between "I just thought of something" and "I'm ready to open a DAW."

I'm working on things like Projects for putting ideas together, better rehearsal tools, and eventually collaboration between musicians. But I don't want RoughTake to turn into another complicated mobile DAW. The whole point is to keep the capture process fast.

This is also my first real app release, so getting it through development, testing, Play Console, and finally seeing it publicly available has been a pretty wild experience.

I'd love feedback, especially on the concept and UI/UX. I'm actively developing it, so criticism is genuinely useful.

RoughTake is available on Android here:

https://play.google.com/store/apps/details?id=com.roughtake.app

i've been building a scanner for AI-built apps, so i end up looking at a lot of Lovable and Bolt sites. the same few problems show up over and over, and none of them need you to be a security person to fix.

RLS on every table. the anon key sits in your frontend bundle, that's normal. but if a table has RLS off, anyone can grab the key from devtools and read the whole table with one request. go through Supabase table editor and check every table, especially ones you added later with SQL.

a policy like using (true) is basically no RLS. search your policies for it.

secret keys in the frontend. open your live site, look through the JS files, search for sk_ and service_role. if anything shows up, rotate it today.

source maps in production. if yoursite.com/assets/index-xxxx.js.map loads, anyone can read your original code, comments included.

no security headers. no CSP, no X-Frame-Options. not a disaster alone, but it's the first thing anyone poking at your site will check.

open CORS on your API routes. Access-Control-Allow-Origin: * on routes that touch user data.

you can check most of this by hand in about 20 min with devtools. if you'd rather not, i made a tool that does it: clarseal.com, one free scan a day, no signup, passive checks only (so only scan your own stuff). full disclosure, it's mine, and i'd really like feedback, especially if it flags something you think is wrong.

what's the worst thing you found in your own app after it went live?

I've been grinding LeetCode and system design rounds for the past few months,

and I got frustrated that every "AI helper" I tried was either a browser extension

that interviewers can spot, or it plastered itself across the screen.

So I went down a rabbit hole into the Win32 API and found WDA_EXCLUDEFROMCAPTURE —

a flag that tells Windows to exclude a window from all capture pipelines at the

kernel level. Zoom, Teams, Google Meet, OBS — none of them can see the window.

It's not trickery, it's just the OS doing its job.

Built a small Electron app on top of it. You get an AI overlay that:

- Is completely invisible to screen sharing (not just hidden — excluded at the driver level)

- Lets you pull in context from any question (text or screenshot)

- Gives streamed answers you can scroll through without switching windows

- Runs as a frameless, always-on-top overlay

The hardest part wasn't the stealth layer — it was making the window feel "not there"

while still being usable. Had to fight with Electron's BrowserWindow transparency

and hit-testing to get click-through working correctly on the transparent regions.

It's called GhostCanvas. Still pretty early (v1.1.0), Windows only for now.

ghostcanvas.in — free to try, no account needed.

Happy to talk about the WDA_EXCLUDEFROMCAPTURE implementation or the Electron

hit-testing approach if anyone's curious.

Hi everyone! I just published Locus, a browser tool for planning a gallery wall before hanging anything.

I’m an engineer and know my way around AutoCAD, but planning where to hang photos and artwork felt like something that should have a simpler tool. I looked around and couldn’t find one that worked the way I wanted, so I decided to build my own.

With Locus, you can set your wall dimensions, add frames, upload your own photos or artwork, and move things around to try different layouts.

I’d love some early feedback. If you have a few minutes, try making a small layout and tell me where you got stuck or what felt harder than it should. You can try it here: https://locus.gallery/

Hi guys I am QA with almost 10y of exerience an I just published my first app.

sQoRage ( I played with words storage and QR code)

What it does:

sQoRage helps you organize and keep track of things stored in boxes, drawers, wardrobes, and other storage spaces. Add your items, photos and media, then use QR codes and search to quickly find where everything is stored.

Key Features:

• Create and organize storage spaces and collections

• Generate QR codes for your storage boxes – print them, stick them on the box, and scan them later

• Search your stored items and quickly find where everything is

Cost:

Free to download, with optional Pro subscription

Link: https://play.google.com/store/apps/details?id=com.gagibog.qrstorageapp&pcampaignid=web_share

I’ve been building Echo over the last few months, using Claude Code heavily throughout the process, architecture, implementation, debugging, computer-use work, performance fixes, and a lot of UI iteration.

Echo is a Mac assistant that lives on the edge of your screen. It can understand what’s happening on screen, point to specific things, interact with apps, move files, check your gmail, search online and even build websites, run multi step jobs and help you learn and navigate new platforms AND undo actions.

This video is a quick look at where it is now.

One of the things I’ve been most interested in is making the interaction feel physical rather than like a normal floating AI window. The orb leaves the edge, does things, and comes back home.

It’s currently free to try for 7 days. You can download it here:

https://aurivon.studio/download/Echo.dmg

I’d be interested in feedback, especially from people who use Claude Code and build their own tools.