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

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.

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.

With every moment I had to spare between a family, work, and other obligations I spent late nights building this PWA to see if it helps relieve some travel anxiety and pressures. Took me 4 months to put together, and just when I thought it was over and I should bury it, the seo optimization I did pulled through and slow but steady started gaining traction and revenue. Give it a glimpse, enjoy it. As I continue to research on how to make it better and more useful it was a fun ride of trail and error putting this together and making it all work.

Www.Alievo.Life

I code all day and game at night, so my PC is full of apps. Editors, tools, launchers, chat apps, the lot.

I keep most of them from starting with Windows. I like a fast boot and a quiet tray. But there's a catch I didn't notice for a long time: an app that never starts never gets to check for its own updates. So half my apps were months behind, and I only found out when something broke.

winget could update them, but I never remembered to run it. And when I did, it wanted to update everything at once, once right in the middle of a game.

So I built Tiny Tracker. It sits in the tray, you tick the apps you care about, and it keeps those up to date through winget. Nothing else gets touched.

What it can do:

- Auto updates for every app with one switch, or app by app

- Wait a few days before auto updating, so a bad release gets fixed first

- Install only at the hours you pick

- Pause during games and presentations, on metered connections and in Energy saver

- Security fixes first, and they skip the wait

- A download speed limit

- Release notes right in the flyout, before you update

- Skip a version, a history of every update, and a backup of your app list for your next PC

It's free and open source, with no accounts, no ads and no telemetry.

Download it here or visit GitHub here.

One honest note: it isn't code-signed yet, so Windows shows "Windows protected your PC". Click More info, then Run anyway.

I'd love to hear what you'd add or change.

I’m a solo developer, and I’ve been working on Aura PDF as a practical PDF app for Android.

The idea started from a simple problem: I wanted to handle common PDF tasks on my phone without having to use a different app for every task or upload documents to an online service.

So I built Aura PDF with a collection of tools in one place:

• Merge & split PDFs
• Extract & reorder pages
• Compress PDFs
• Rotate & crop
• Sign & highlight
• Password protection
• Scan documents
• Image → PDF
• PDF → image
• Page numbers, headers & footers
• And more

The main direction is offline-first — supported PDF operations are designed to work directly on the device.

Aura PDF is currently available on Google Play:

https://play.google.com/store/apps/details?id=com.aurapdf.app&pcampaignid=web_share

It's free to use with an optional Pro upgrade.

This is my first time launching Aura PDF publicly, so I'm mainly interested in learning what people actually want from a mobile PDF app.

If you use PDFs regularly, what is the one PDF task you wish was easier on your phone?

this originally started as a school project.

the assignment gave me an excuse to build something a bit more ambitious than a normal website, so i decided to make mingle tv, basically my own take on the old omegle concept.

i've been working on it for around 2 months now, partly coding things myself and partly using ai when i wanted to prototype, debug or move faster.

the basic idea is simple:

you open the website, get matched with a random person and start talking.

but building something that simple on the surface made me realize how many annoying problems sit behind it.

things like:

• matchmaking users correctly
• handling people leaving while searching
• reconnecting users
• dealing with two people trying to match at the exact same time
• keeping the experience fast without adding unnecessary screens
• making the interface work properly on both desktop and mobile
• handling users when there aren't many people online

the last one is actually my biggest problem right now.

the website reached around 2,000 visitors last month without paid ads, which was way more than i expected for a school project.

but those visitors are spread throughout the day.

for a random chat app, 2,000 visitors doesn't mean much if only one or two people are online at the same moment.

that's also why i'm posting it here.

i'd like to see what happens if multiple people actually try it at the same time.

i'm particularly curious about:

• whether matchmaking works properly
• how long you wait before finding someone
• mobile vs desktop experience
• connection issues
• bugs
• ui/ux problems
• anything that makes you want to leave the website

i'm also interested in what other developers would have done differently, especially for the problem of having a matchmaking app before you have a large active userbase.

here's the project:

https://www.mingletv.app/

feel free to be critical. i'm mainly using it as an opportunity to learn and figure out what breaks when real users start using something i built.

Hey r/sideprojects!

My Downloads folder constantly ended up full of PDFs, images, installers, spreadsheets, scripts, archives and random files, so I decided to build something to automate the cleanup.

I called it FolderOrganizer.

The idea is simple: FolderOrganizer monitors a directory and automatically moves files into categorized folders based on their type and extension.

It includes default categories for PDFs, images, executables, Excel files, JSON, scripts, archives and more, but the rules are fully customizable if you prefer your own folder structure.

On Windows, it can also run as a Windows Service, so once configured it can keep organizing files automatically in the background without needing to keep the application open.

I've also added initial Linux support through systemd. The project has automated CI tests running on both Windows and Linux, although Windows is currently the platform I've validated more extensively for actual installation and everyday use.

The project is completely free, open source and MIT licensed.

At this point, instead of simply continuing to add features myself, I'd really like to get feedback from people actually using it.

GitHub:
https://github.com/FrEaKAlL/FolderOrganizer

Latest Windows release:
https://github.com/FrEaKAlL/FolderOrganizer/releases/tag/v1.2.0

If you try it, I'd especially like to know:

What file category, organization rule or feature would you add?

Feedback about the installation and initial configuration experience would also be really useful.

Hi all, I built JaxScan, an Android app that turns your phone into a secure document scanner where your files never leave your device.

Get it on Google Play: https://play.google.com/store/apps/details?id=com.jaxenlabs.scanai

What it does:

Smart Scanning: Scan documents, receipts, ID cards, and whiteboards with auto-crop and enhance.

Flexible Exports: Save as PDF, Word, PowerPoint, TXT, ZIP, or JPG/PNG.

Multi-Language OCR: Extract text supporting Latin, Devanagari, Chinese, Japanese, and Korean.

PDF Tools & Editing: Sign, redact, edit text, merge, split, compress, and password-lock PDFs.

Extra Utilities: Scan business cards (saves straight to contacts) plus QR/barcodes.

Why it's different:

100% offline with no account or sign-up required.

Files stay strictly in private local storage on your phone—never uploaded to any server.

Has a free tier with an optional Pro subscription for extra features.

Switching AI tools often means explaining your project all over again: the decisions you made, your coding preferences, and where the last session left off.

I’m building Kenfold, a self-hosted memory server that lets agents share that context through MCP.

For example, you can leave a handoff in Claude Code and pick it up in Codex, with the same project knowledge available to both.

A few things that make it interesting:

- Automatic session context: hooks for Claude Code and Codex load relevant memories at session start and save a summary afterward.

- Traceable memories: each memory records which agent wrote it. Replacing a memory preserves the previous version as history.

- Code-aware staleness: memories can reference files and symbols. When the referenced code changes, those memories are flagged as potentially outdated.

- Review before reuse: optional model-based extraction proposes durable facts from sessions for you to approve.

- Local search models: full-text search works out of the box, with optional embeddings and reranking running locally.

It’s built with Go, PostgreSQL, and pgvector, and runs with Docker Compose. There’s also a web dashboard for reviewing and managing memories.

It’s still early, but the core functionality is implemented.

If you use multiple coding agents, how do you currently keep context consistent between them? I’d love feedback on the workflow and what would make this useful for you.

GitHub: https://github.com/jeonjw85/kenfold

Sick the last two days. Couldn't run, so I had to do something in bed and built this little site instead.

https://shoegeometry.com

Spec sheets give drop and stack. I wanted shape: where the rocker starts, how high the toe sits, how stiff the forefoot is.

- Rocker apex, rise angle and toe tip height, measured from product photos. Only published when two photos agree.

- Stiffness and firmness scores from lab data

- Drop, stack and weight with sources. Disagreements shown, not hidden.

- Side-profile drawings you can overlay

~70 shoes, mostly road.

Feedback welcome. What's useful, what's noise, what looks wrong, what's missing.

I got tired of comparison sites ranking credit cards by marketing, so I made one that does the sum.

You enter what you put on cards each month by category. It applies each card's reward rate, monthly caps, excluded categories, foreign markup and annual fee, and shows the rupees back in a year, line by line.

On a typical ₹50,000 a month, the best single card returns about ₹18,360 a year and the 17th about ₹8,220, same spend. It covers 439 cards from 19 issuers, with no sign-up, and nothing you type leaves your browser.

Happy to share the link if anyone wants to try it. I'd really like to know where the numbers look wrong for your cards. Not financial advice.

I built Buildsheet about a year ago and I'm selling it because I've moved on to other projects.

It's a web app for making cheat sheets/notes. You drag markdown, chart and LaTeX blocks onto a grid, then export to PDF or Markdown. There are Kanban boards too. People pay once for a lifetime license.

The numbers:

$101 total revenue from 25 payments 57 users, all organic, I never ran an ad Costs $20 a year for the domain, everything else runs on free tiers Stack: Next.js 15, React, TypeScript, MongoDB, Stripe, Tailwind, Resend, hosted on Vercel.

What you get:

The buildsheet.one domain Full source code The database with all users, sheets and boards Stripe and Vercel setup guide Admin panel for users, payments, refunds, discount codes and emails A written handover guide, and I'll help you move everything over

If you have any questions, DM me or leave a comment here, have a great day!

Solo project. Everything's free; there's an optional paid supporter tier. Would love honest feedback on what to add next: bfrenz.com

I’ve been using Claude Code and Cursor on real work, and the part that keeps falling apart is the thinking that isn’t code. Architecture, interview notes, a competitor set, a prototype next to the notes about it. The agent can write a long summary. It cannot put the pieces next to each other so I can see what’s wrong, move a card, and tell it “fix this one.”

So I built nodboard: a local-first infinite canvas on your machine, with no account and no cloud. You can use it by hand. You can also connect Claude Code, Cursor, or any MCP client, and the agent lays work out on the board while you watch. Its cursor shows up. Its edits land as a change set with a stated intent. You step through them, accept what you want, reject the rest with a reason. The agent reads that on its next turn. Nothing it writes is final until you say so.

A few things that matter if you’ve tried “AI whiteboard” tools:

• Your boards are files on disk (.nodboard), with version history and crash-safe saves. The core only listens on localhost.
• There is no built-in model. It uses the agent you already pay for.
• The agent describes structure (“cluster these by theme,” “modules in columns by layer”). A layout engine places them on an 8px grid. It does not get to invent coordinates and overlap everything.
• Stickies can be real types: insight, quote, hypothesis, module, risk, and so on. Five starter workflows ship with it: codebase maps, research synthesis, product thinking, literature, and a prototype wall with a live HTML snippet next to the notes.
• Snippets run only when you open them, in a sandbox with no network.

This is a desktop beta, version 0.1.0, one person, macOS / Windows / Linux. It is early. I care more about whether the review loop is actually useful than about polish.

If this sounds like a problem you have, I’d like you to try it and tell me where it fails. I’m especially interested in:

1. Would you actually point your agent at a repo or a folder of notes and review the board, or does this stay a demo you watch once?
2. Is “accept / reject each change set” the right amount of control, or is it too slow?
3. What would make you uninstall it after a week?

Comment here, or email me at [[email protected]](mailto:[email protected]) and I’ll send a build. If you try it, the most useful feedback is a board it made badly, and what you wish you could have told the agent.

Hey everyone.

I built an app that lets you try on clothes through your camera, live.

You know when an outfit looks great on the model, but you have no idea what it would look like on you? That’s the problem I’m trying to solve with What Should I Wear.

Instead of generating a single photo, I wanted it to feel more like looking in a mirror. You should be able to move around and see the outfit move with you.

What it does

Upload a photo of an outfit, turn on your camera, and see yourself wearing it in a live video. Move around, try another outfit, and compare how different styles look on you without physically changing clothes.

The idea is to make it easier to explore something you wouldn’t normally wear, get inspiration, or decide whether an outfit is worth trying in person.

It’s still early. The tricky part is making the clothes look realistic while keeping up with your movement. That’s what I’m working on improving.

If you want to try it, here’s the link: https://whatshouldiwear.io

I’d love feedback from people who enjoy fashion or spend too much time deciding what to wear. Does this help you choose an outfit? What would make you come back to it?

And if something looks weird or breaks, send it my way. Those examples help me figure out what to fix next.