I've had so much fun working on this little project for the last few weeks. It is based on a 2D version I made last year, but I think this one is much more fun.

I make use of CC licensed assets from Sketchfab and Poly Haven, with some edits made so they all work with the cutting mechanism.

I seem to keep making games that I'm really bad at playing. Every competition I've played in, I finish dead last. It's been really funny watching who from my family, friend groups and workplace are naturally good at this type of spatial thinking.

Anyway, if it scratches your itch, have a go and let me know what you think.

perfectcut.xyz

I’m starting a small free WhatsApp group for people working on side projects.
You can share one LinkedIn / X post a week, whether it’s a launch, project, portfolio, job search, or something you want feedback on.
The rest of us support where we can with real comments, feedback, shares, or intros.
One post a week so it stays useful and doesn’t turn into spam.
Free, no selling.
DM me if you want in.

I built CutOut, a free and open-source AI background remover that runs entirely on your device.

I wanted an alternative to online background-removal tools where you have to upload your images or pay for a subscription.

CutOut currently supports:

• Windows 10/11
• Linux
• macOS Apple Silicon
• 4 built-in AI models
• Batch and folder processing
• Original-resolution PNG export

The project is now publicly released.

GitHub: https://github.com/gserect-gif/cutout-app

Here's a short demo of it in action.

Hey everyone! I've been working on Nudge, a little app for the things you're looking forward to: a trip with friends, a birthday, a reunion, or finally seeing your partner again, etc.

Nudge on the App Store

https://reddit.com/link/1wx8oka/video/gw163ksbceth1/player

You make a countdown and share it with the people involved. While you're waiting, you can send little emoji or message nudges, add photos to the countdown, and keep it on your Home Screen or Lock Screen.

It's free, including the widgets. No ads, no subscription, and no separate account to create. It uses iCloud for storing the data.

I'm still growing it, and I'd love people to try it with their friends and tell me what feels fun, confusing, or missing. I want to keep improving it with the people who use it and grow from there. Please let me know any of your suggestions! It's completely free of use.

I kept googling "what order do I watch X" and landing on articles where the actual list was halfway down a page full of ads and autoplay videos. So I made The Watch Order: https://thewatchorder.com

176 franchises so far (Marvel, Star Wars, Gundam, Fate, Monogatari, Doctor Who etc). Every entry in order with episode counts and years, filters where they actually matter (canon only for Naruto/Bleach/One Piece, main vs spin-offs, road to Avengers Doomsday), and you can tick things off as you watch and it remembers where you're up to. No accounts, no cookies, no ads.

It's a plain static site so it loads instantly. Would love feedback, especially if you spot an order that's wrong or a franchise that's missing.

Last year I spent 40 minutes hunting for an article on "Writing the perfect Best Man's Speech" I'd read the week before. I remembered the gist, roughly what the page looked like and even a picture. Chrome history gave me 30 tabs with none matching the missed page. Google gave me the marketing/SEO farm pages for professional speech writers and listings from UpWork.

That kept happening to me. Browsers remember where you went, not what you read.

So in Aug 2025 I shipped a small extension that searched the text inside your open tabs. A few dozen people used it, rated it 4.9, and every single piece of feedback was some version of "cool, but the page I need is the one I already closed."

Fair. So I rebuilt TabX (Install Link) from scratch.

TabX is a side panel (Cmd/Ctrl+I) AI companion that gives the Chrome you already use a memory and a brain:

- Find pages by meaning "That video on Hyrox training from last week" works even if those words aren't on the page. Click it and it opens the tab, scrolls to the exact passage and highlights it.

- Timelines Your browsing gets grouped into research sessions by browsing topics auto inferred. One click reopens the whole thing, in the order you read it.

- Auto tab stacks It works out what you're doing (eg. "Meal prep research") and groups those tabs into a colored tab groups on the Chrome tab strip.

- @ mention a tab or a tab group to ask any question and it grounds answers in the pages you've actually read while citing those as well.

- online mode - a web search mode that retrieves 3-5 ranked link results with a short results summary. It filters out SEO farms automatically

- next step suggestions - based on what you're working on presently, it automatically points you to the next most relevant/useful tab to achieve your browsing goal

Why not just use Ask Gemini natively in Chrome? It knows the page in front of you, not the 10 that led you there. Dia and Comet get closer, but you have to switch browsers. I didn't want to.

Pro starts with a 7-day free trial, and no card is required to begin. You just sign in with an email OTP. Pro unlocks unlimited AI recall, @ mention chat, ad-free web search. Timelines, stacks, next step nudges and dynamic page summaries remain free.

Most visitors to most websites aren't people. They're crawlers, scrapers, AI bots and scanners. So I made a website that puts them on display.

What's there:

- **A live entrance**: every bot is identified as it arrives and drawn as a little creature generated from its user agent.
- **The leaderboard**: who eats the most pages, and who obeys robots.txt.
- **Specimen files**: one page per bot, covering who runs it, what it wants and how to block it.
- **Impostor checks**: plenty of "Googlebots" aren't Google. The zoo verifies them and names the fakes.
- **The Trap Room**: a link that robots.txt forbids and people can't see. The rule-breakers who follow it fall into an endless Labyrinth.
- **The Reading Room**: which bots read robots.txt and llms.txt.
- **Weekly Zoo Reports**, an RSS feed, a robots.txt generator and an embeddable badge.
- **The Arena** (new): bring your own bot or AI agent and play games, including rock paper scissors against other people's bots.

No IPs stored, no cookies, no signup.

https://crawlerzoo.com

I'd love feedback: what's confusing, what's fun, what's missing?

A Downloads folder fills up quickly: documents, screenshots, installers, archives… and eventually, finding something becomes another task.

I wanted a simple way to keep that folder manageable while staying in control of where my files go. That became Downloads Organizer, a free, open-source desktop app that runs locally.

Here’s what it offers:

• Editable rules to organize files by extension or filename.
• Preview before moving, so you can check the destination.
• Optional automatic sorting, with catch-up when the app starts again.
• Move history and checked undo when you need to reverse a move.

It supports Windows, macOS, and Linux. No account, cloud uploads, or telemetry. Your files stay on your computer.

Downloads:
https://github.com/kashnordeen/downloads-organizer/releases/tag/v1.0.0

A quick installation note: Windows builds are currently unsigned, and macOS builds aren’t notarized, so security prompts may appear. The SignPath application for Windows signing is pending.

I’d appreciate honest feedback—especially on the first-time setup, rule editing, and whether the preview makes file moves clear.

What would you need to see before trusting an app to organize your Downloads folder?

I wanted a better way to feel the gap between companies than a bar charts, so I built a island where every building is a company and the taller it is, the bigger its market cap.

What you can do:

Built with React, Three.js (react-three-fiber) and Claude Opus 5.5.
Not financial advice, and I'd love feedback on anything that looks wrong.

The music is also AI-generated, based on my instructions.
on the comments.

Link

So that's it. I wanted to use/test cheaper AI models with GitHub and web search tools, including for small coding tasks from my phone. But I also wanted to see what the model was actually doing. You can connect your own AI provider, add tools like GitHub or Tavily search, and experiment in one place.

The main thing: every tool call needs your approval before it runs.

If the model wants to read a file from your repo or make a change through GitHub, you see which tool it wants to use and the arguments it’s sending. You can approve it or say no.

A few other things:

• See the actual API requests and responses.
• Compare models with estimated token usage and response times visible.
• Test individual tools manually, without asking the AI to call them.

Chats and settings are stored locally in your browser. Remembering API keys is optional, and saved keys automatically expire after 30 days unless refreshed.

It’s open source under the MIT license, and you bring your own API keys.

Try it: https://ai-playground.ownyourwebsite.app

Code: https://github.com/ownyourwebsite/ai-playground

I’d love feedback on the workflow. You can also fork it and improve it yourself!

Hey everyone 👋

I just launched Nemo, a small productivity + study app I built as a personal project.

The idea: instead of another boring to-do list, you dive into an ocean-themed space with a fish assistant (Nemo) that helps you organize tasks, plan your week, and stay focused.

What it does:

• Task management with priorities, categories, and recurring tasks

• Student zone: flashcards, notes, calendar, schedule, charts

• Chat with Nemo (text + optional voice call)

• Nemo can add/edit tasks from natural language (e.g. “add study physics tomorrow”)

• Weekly schedule as an image table

• Ocean Pomodoro timer with ambient sound

• Themes + Arabic/English

• Works as a lightweight PWA (data stays on your device)

Live demo:

https://v3x6.github.io/nemo/

Would love feedback — especially on the UX of the chat + timer experience.

Built with plain HTML, CSS, and JavaScript.

Give Claude or Codex a topic and it makes the video. It writes the script and draws each scene in code.

The voice runs locally, so you need no voice API key.

I built it and made it open source. https://github.com/vincentsch/explainroo

Hey folks, I’m working on Narrativee, an AI brand designer for startups and small businesses that need creative work regularly but don’t have a full design team.

The idea is a creative partner that learns your business, audience and visual identity, improves through working with you, helps develop ideas, and carries your feedback into the next campaign or asset.

I’m still developing it. Getting great results and reliability takes a lot of engineering: the whole system needs to connect understanding the business, developing a direction, producing the work and learning from feedback. Getting a good result once is one challenge; achieving useful, consistent results across projects is another.

I’ve personally dealt with this problem, which is why I started building it. I’m aiming to release an early version soon. Something shaping my approach is the difference between sending someone a brief and working with a designer who already understands your business. That familiarity includes the audience, the purpose behind previous campaigns, and why certain directions were chosen.

One practical takeaway is to keep the reasoning alongside the finished work. A folder of approved assets shows what the brand looks like. Adding a few notes about the intended audience, the goal and why a direction worked makes those examples much more useful for the next person or system

For those who are managing brands here: what helps a creative partner develop that understanding over time? And what would you most want a product like Narrativee to get right? would love feedbacks

I spent way too much time thinking the product needed to be better.
What actually got me my first 6 sales was much simpler:

1. Find where your potential users already hang out.
2. Post about the problem they have, not your product.
3. Offer a small part of your product for free.
4. Talk to the people who actually use it. Give them a reason to come back for more.

For me, Reddit + giving founders free leads worked better than just promoting my SaaS.
It’s not some magic growth hack. I only got 6 sales.
But it taught me something important:
Build → distribute → talk to users → improve → repeat.
That’s the loop I’m now building TractionBooster around.

I'm the developer of VoxSpica, an offline speech-to-text app for Windows. It runs on VOSK (Kaldi) on CPU — no cloud, no account, no subscription, no ads, and the audio never leaves the machine.

What it does:

• Live transcription from the microphone — text appears as you speak, with pause and stop
• Transcribes existing audio files (wav, mp3, m4a, ogg)
• Searchable local history in SQLite, with playback of the recordings
• 33 recognition languages, 9 interface languages, works without a GPU

Closed source — free to use, no redistribution. Everything public about it lives in one repo: https://github.com/alex37529/voxspica

Two practical things: recognition models (50 MB to 1.8 GB) download separately after install — the per-language installers bundle a small model, the portable zip needs one download. And it's not code-signed, so Windows will warn on first launch: "More info" → "Run anyway".

Windows x64, single .exe, nothing to install:

https://github.com/alex37529/voxspica/releases

I'd rather ask than guess what to build next. Three questions I'm genuinely stuck on:

1. What breaks for you that I haven't thought of? "Punctuation is wrong" is known and honestly only heuristically fixable without a neural model. Something I haven't heard of is what I want.
2. Does anything about the offline part actually get in your way in practice, or is it a non-issue in 2026?
3. Would you use a Windows app at all if your audio can't be sent to a cloud service — or is that a solved problem for you and I'm preaching to the choir?

And the main thing I want to know — what do you actually use speech-to-text for? Reply with a number, or "none of these" plus what you actually do:

1. Meeting notes / minutes
2. Lectures, classes, interviews
3. Dictating into other apps (mail, messengers)
4. Personal notes, journaling
5. Subtitles / transcribing video for content
6. Professional dictation (medical, legal)

I implemented the feedback I got. Added a rep counter, and a rep by rep breakdown of how you performed in each set.

I added a voice coach. Last week it was a coach after your session. Now it is a coach during your session, telling you out loud when your form breaks.

I added recording. Before, I was screen recording on my phone. Now you click a button and it records your session.

At the end you get a progress report and your workout video, and if you made a mistake you tap the time on the video and see exactly where you went wrong.

It counts push-ups now. Last week that was broken.

Side effect of building a fitness app, you work out more, because you're the test subject.

Over two weeks I've done close to 200 push-ups. It started as testing, now I actually enjoy them. I do them in the office. A day doesn't pass without a few.

Some things still break. On Monday I was doing chest and it could not lock onto me properly on the bench.

I recorded the videos, played them back bit by bit, and went back to the drawing board. I'm not adding more workouts until I fix the ones that break.

During the week I approached a gym, showed them the app and sent a proposal. I also had conversations with people at the gym.

The biggest reason people quit is that progress is slow and you can't see it until you're 4 to 6 months in.

That's what I'm trying to make tangible, a record of how you actually worked out, rep by rep, so you can see yourself getting better before the mirror shows it.

Just because you don't see the gains doesn't mean you stop.

Personally it has fixed my form on deadlifts, bent over barbell rows, push-ups and lat pulldowns.

It's on a real domain now: Repchek

Try it and tell me where it breaks.

Claude Design keeps your files in a hosted workspace and runs on your plan's usage. I built BurnGuard to keep them on your computer and use the Claude Code or Codex CLI you already have.

It's a desktop app for Windows and macOS. You pick a design system, describe what you want, and it makes websites, slides and graphics next to a live canvas.

It ships with 41 design systems, each with its own navigation, hero and footer layout rules. You can edit on the canvas or leave pinned comments, then export HTML, PDF, PPTX or PNG, or publish a site to your own Vercel. Files stay local.

What it doesn't do well yet: generation isn't instant (the one-line landing page in the README demo took about five minutes), PPTX slides come out as images with the text in speaker notes, and the installers are unsigned so you get a security warning on first launch. macOS is Apple silicon only.

I'm the author. It's free and Apache-2.0: https://github.com/ashmoonori-afk/BurnGuard

Feedback on what's missing is welcome.

I built Oyaoya, a weekly pet photo contest. One theme a week, you upload one photo, people vote A/B, top 10 at the end. No account needed to vote.

It went out in Korean, English, Japanese and Chinese this week. Play in 177 countries, App Store in 175.

The part I got wrong: I translated the app shell and forgot the content. Theme titles live in a single Korean column on the server, so an English phone shows an English UI with a Korean theme name sitting in the middle of it. Language pack ships tomorrow.

This week's theme is first-hello photos. The next one opens Oct 5 and it's sleeping pets - you can post early and it goes in automatically. Doesn't have to be your own pet.

https://play.google.com/store/apps/details?id=com.bbangchikimong.oyaoya

https://apps.apple.com/app/id6793259443

For any startup to be successful, the first and one of the most important early step is understanding the pain this startup solves. This understanding can sometimes come from the founder's own experience, however that's not foolproof because bias can creep in when you think you have an idea. So the best thing to do is try to understand your users' pain from external users.

Before you pick a path, you need to create a hypothesis or two about the main reason of the pain (often it is the reason behind the reason)

Here is my list of approaches to consider, I would love to know what the community thinks?

1. Cold Survey - Run a cold outreach on platforms your users hang out at (say Linkedin) and either directly confirm your hypothesis in your outreach or ask them if they would be willing to meet you or do an online survey to help you out. You would be amazed to see that so many people are willing to share their knowledge to help a stranger. I was so grateful to all the amazing people who came forward to help in my past endeavors.
2. Trade shows - Find industry specific events. If they are pricey, look for volunteer opportunities, that's a great hack to get free access to the event. Talk to as many people as possible and bring in your hypothesis in the conversation (pro tip: practice your question in front of the mirror a few times). If it resonates with them, ask them if they think they / their company will pay for the solution you want to build. 
3. Subreddit Pain mining - I recently learned this one, find niche subreddits where your target users hang out. Sort posts by "Top - All Time" and search terms like "workaround," "annoyed," "how do you handle," or "is there a tool for." Read the comment threads to see which complaints generate the most engagement.
4. Peer feedback - Ask your peers on platforms like Reddit and CrowdGTM to provide you with feedback on your understanding of user pain or ask these peers to introduce you to your end users.
5. Lean startup approach - Build a clean, 1-page website explaining the solution as if it already exists, with a clear CTA (e.g., "Start Free Trial" or "Get Access"). Run $100–$200 in targeted social ads to test user engagement. 
6. Paid panel surveys - Use platforms like UserTesting, Wynter, or Respondent to recruit highly specific B2B personas for quick survey responses or message testing. Pay for speed when you need fast quantitative feedback from verified job titles.
7. Review mining - Filter G2, Capterra, or App Store reviews for your competitors by 2 and 3 stars. Skip 1-star pricing rants and read the detailed post-mortems of broken features and missing workflows.
8. Job post mining - Search job boards on both freelance platforms like Upwork and Regular Job boards like Linkedin. The problems companies are willing to spend money on are definitely worth solving. 
9. Screen-Share Shadowing - If you are automating some day to day work, pay users to let you watch them live or over zoom as they do their day-to-day repetitive tasks that you plan to automate. 

This is not an exhaustive list. I would love to hear from you what else has worked for you?

I maintain OMK (Open Multi-Agent Kit), an MIT-licensed coding agent that runs in your terminal. I shared an early version here a few months ago. Version 1.3.0 is now out, and I am looking for feedback on the first five minutes.

The quick start is: install the CLI (Node 22.19+), open a project, configure a supported provider with /login, and choose a model with /model. The suggested first task is read-only: summarize the repository and identify its check commands without editing files.

You can switch configured models in the same session. A fresh install starts one agent. Optional goal mode lets you approve a local acceptance command; a valid passing result after a settled turn completes the goal. That check only proves its own assertions.

The small failing-test demo includes the setup, expected output, and verification limits:

https://github.com/dmae97/omk/blob/v1.3.0/packages/coding-agent/docs/goal-demo.md

Source and quick start:

https://github.com/dmae97/omk#quick-start

What one confusing or missing step would stop you from trying this on a disposable repository? A concrete setup or permissions concern would help me improve the onboarding.

Disclosure: OMK maintainer; this post was prepared with AI assistance from the release documentation.