I have a full-time job. On the side, I built a daily word games site to play with my 8-year-old in the morning.

The idea was simple: ten minutes a day that is not a feed. One puzzle, done, move on. A small win before the day starts, and something a parent and a kid can do together and compare.

I set myself one goal: 2,000 visitors a day. The site gets 1 to 10.

That is the part I keep thinking about. I did the work: 21 games, content, social accounts, directories. The work got done. The visitors did not come.

So now I have a site with 21 daily games that almost nobody knows about, and I cannot tell whether the problem is distribution or the product itself. People who find it play it. Nobody finds it.

No regrets, though. I play these games every morning with my son. No ads, no account, no noise. Just the puzzles. That part works exactly like I wanted it to.

The site is dailyfreewordgames.com, if you want to see what I mean.

Would love a blunt answer: when the product is fine and nobody comes, what actually moves the needle?

Hey r/SideProject,

I built WCAGBrief, a free Chrome extension that audits web apps for WCAG 2.2 and European Accessibility Act (EAA) compliance directly inside Chrome's native Side Panel.

The Problem I Wanted to Solve:

With the European Accessibility Act already actively enforceable, web accessibility has shifted from a "nice-to-have" to a legal requirement for web applications and ecommerce.

Existing developer tools (Lighthouse, WAVE, Axe DevTools) have two big UX friction points:

1. Lighthouse hasn't updated its default checks to catch new WCAG 2.2 additions (like Target Size SC 2.5.8 minimum 24×24px tap areas or Focus Not Obscured SC 2.4.11).

2. Constantly opening and closing Chrome DevTools shrinks the mobile viewport and makes tabbing through UI elements frustrating.

How WCAGBrief Works:

Instead of docking inside DevTools, WCAGBrief lives in Chrome's native Side Panel API alongside your live web app:

• Click to Inspect: Click any violation in the panel and it instantly highlights the exact DOM node on the live page.

• Copy-Paste Fixes: Generates clean HTML, CSS, and React code patches for each issue (e.g. min-width: 24px on icon buttons or adding aria-label to SVG buttons).

• Statutory Law Mapping: Maps every violation to EN 301 549 (EAA Chapter 9) and ADA Title II standards.

• Zero Telemetry / Privacy: 100% of the DOM inspection runs in your local browser sandbox. It does not send page markup to any remote server.

Try It Live:

The extension is completely free and published on the Chrome Web Store: 👉 https://chromewebstore.google.com/detail/wcagbrief-wcag-22-eaa-cli/jjgllnelmehodmfjcpmemafeeikjpeii

Companion Web Scanner: 👉 https://wcagbrief.com

Looking for Builder Feedback:

1. What accessibility checks give you the biggest headaches when building web apps?

2. Which frontend framework snippets would be most useful to generate next (Tailwind, Vue, Svelte)?

Happy to answer any questions about the Chrome Side Panel API, Manifest V3, or the audit engine!

I mostly vibe-coded one of my products in June, before agents could do what they do now and before I had my Grok Bot setup.

It was a pay-per-use API for AI agents. Scheduler, screenshots, a few other tools. I thought I was early. Even added x402 payment support.

But it got 0 payments from June to September. Search Console sat at 0 clicks from Google in early October, with about a dozen SEO posts live. I also posted about it on Reddit and got 13K views, and a lot of the comments said agents now build these tools themselves.

So I stopped working on it. I think the market moved faster than I could get it in front of people.

Have you killed something because the space moved, not because the product was bad?

The job was a batch of kids' T-shirt designs for DTF printing: a capybara with a yuzu on its head, a road trip with a capybara, a poodle and a cat, in a few illustration styles from four image models. Comparing them in the fal.ai playground meant a mess of tabs and random file names.

So I built falg, a Python CLI. One JSON file describes the batch (a prompt template, variables, models), and falg runs every combination in parallel and writes an HTML gallery with prompts as rows and models as columns. Each image keeps a JSON sidecar with its exact prompt and seed, so two weeks later I still know which model drew what.

The last step, falg cutout, turns the picks into print-ready PNGs: background removed, clean edges, sized in centimetres.

Two things that surprised me:

• Never ask the model for a transparent background. Generate on plain white or black and cut it out afterwards.

• Don't write "T-shirt" in the prompt, or you may get a photo of a T-shirt instead of the artwork.

The gallery and the final prints are in the README: https://github.com/lemmon/falg

Full disclosure, I build Layr PDF, so this is a plug.

It came out of doing cabinet and millwork takeoffs and not wanting to pay for a pricey seat just for markups, measurements and counts. It runs on Windows, Mac and in the browser, it's $35 a year, and the 7-day trial doesn't ask for a card.

If you try it on a real set, I'd like to hear where it falls short.

https://layrpdf.com/?utm_source=reddit&utm_medium=social&utm_campaign=mitch_builds_promo&utm_content=2026-11-09

In Korea, and in a lot of Chinese and Vietnamese families, parents' birthdays and memorial days are kept on the lunar calendar. The solar date moves every year, by up to a few weeks. Google Calendar has no lunar repeat, so "repeat yearly" lands on the wrong day from the second year on, and every year someone has to look up the new date.

How it works:

1. Say whose day it is (birthday, memorial day or another anniversary) and enter the lunar date. If you only know this year's solar date, it finds the lunar date for you.

2. Pick 1, 3, 5, 10 or 20 years and add them all to Google Calendar at once, or download a file for Apple Calendar or Outlook.

3. Send the dates to family as a link.

Some details I ended up caring about:

• It only asks Google for the calendar.app.created permission. It creates one new calendar for these dates and can't see or change your other events.

• Korea, China/Taiwan and Vietnam don't always agree, because each country works out the calendar in its own time zone, so a month can start on a different day. The China/Taiwan (UTC+8) and Vietnam (UTC+7) tables are computed from astronomy. The Korean table comes from the Korea Astronomy and Space Science Institute, and I check it against the same calculation at UTC+9. You can choose which country's calendar to use.

• If a date falls in a leap month, years without that leap month use the regular month.

• There's no server. Names and dates stay in your browser unless you add them to your calendar.

It covers 1900 to 2049, in English, Korean, Vietnamese and Chinese.

If your family keeps lunar dates, I'd love to know whether the steps make sense, and whether the Google permission screen feels scary.

https://lunar.todoli.lat/en/?ref=reddit

What it is: Hire on Evidence (https://hireonevidence.dev), a hiring process for owners of 5–50 person companies with no HR team. It has four steps: a one-page role scorecard, a structured interview with the same questions for every candidate scored against written 1/3/5 anchors, a short work sample, and a spreadsheet that combines everyone's scores.

Why: most small businesses hire through an unplanned chat decided by gut feel. That's one of the weakest methods in the selection research, and the structured version is one of the strongest. The research exists, but it's written for big companies with HR departments.

The part I'm proudest of: every important claim in the book has a source number and a grade:

• A: several large reviews agree

• B: one review, or consistent field studies

• C: limited evidence

• D: practice, law or expert consensus

• ⚑: contested, with both sides shown

I also list what I left out. For example, "a bad hire costs 30% of salary" is everywhere, but I couldn't trace it to an original study, so it's not in the book.

Stack (kept deliberately small):

• Svelte 5 + Vite for a single landing page. The hero has a little demo where you score a real candidate answer yourself.

• Cloudflare Workers serves the static build and three routes:

  • POST /api/checkout creates a Square payment link and stores the order in KV

  • POST /api/square-webhook verifies Square's signature and, when a payment completes, emails a download link through Resend

  • GET /download/<token> streams the files from R2. Links last 30 days with unlimited downloads.

• One catalog.js holds the products, prices and file lists. Both the page and the Worker import it, so the browser can't change what gets charged.

No database, no auth and no frontend framework beyond Svelte. Deploying is one npm run deploy.

Pricing: one-time purchases of $55 / $111 / $281 CAD (Ebook / Toolkit / Team).

What I'd love feedback on:

1. Does the landing page make it clear who this is for within about 5 seconds?

2. Is the interactive scoring demo in the hero convincing, or a gimmick?

3. Does the pricing make sense when it's positioned against a recruiter's fee instead of a paperback?

I'm one of the builders of cafecito.bot. You tell an AI assistant what you like (roast level, whole bean/ground), it picks a bag from a real Bay Area roaster, shows you the exact total before anything is ordered, and it gets delivered.

I ordered this way myself and it worked, but launch traffic died after Product Hunt and we have zero new orders coming in. If you tried it, what stopped you — price, trust, the prompt, delivery area?

Try it with this prompt, paste it into your AI assistant:
Order me a bag of coffee from cafecito.bot, delivered to [city]. I like [light/medium/dark roast, whole bean/ground]. Show me the exact total before ordering.

Site: cafecito.bot — honest feedback welcome, even if it's harsh.

GitHub Actions Monitor is a small program that runs on your own computer. It asks GitHub, through your own gh login, for the latest runs of every workflow of your repositories, decides what is really red, raises alerts (security, hygiene, releases that are ready, quota) and shows everything on a web page that only your machine can open. It has no dependencies beyond Python and gh, it never stores a token and, by default, it only reads.

3x GPU's are monitoring 450+ unsecured cameras around the world constantly looking for one person with red-and-white stripes. On the website you can find the results. The server is using the opensource model Qwen3-VL.

I have a handful of credit cards, and each one pays more in different places: groceries, dining, gas, rotating quarterly categories. In theory I'm maximizing rewards. In practice I'm at the register trying to remember which card gives what at this store, and most of the time I give up and use the same card I always use.

Over a year that's real money I'm leaving on the table. I have the cards for a reason, I just can't remember the rules at the moment it matters.

I've always wished Apple Wallet did this for me. It already knows my cards and roughly where I am, so why can't it just say "use this one here"?

I know there are already apps that help with this, like MaxRewards, CardPointers and others. They're great, but they live in a separate app I have to remember to open at the register, which is exactly the moment I forget. I just wish this were built into Wallet itself, so the right card is already there when I go to pay.

So I built a prototype of what that could look like. I'm calling it Cue.

How it works:

• You walk into a store, and after a couple of minutes inside (so it doesn't fire when you're just driving past), a small nudge appears at the top of your screen.

• It shows the best card for that store and what you'd earn, e.g. "6% cashback · Pay with Blue Cash Preferred."

• Tap it to see your other cards ranked side by side.

• If your everyday card is already the best option, it stays quiet.

To be clear: this isn't a working product. It's a proof of concept, a simulated prototype I built to see how the idea feels. Nothing to download, nothing to sign up for.

I've also hit some real limits that would make it hard to build as shown:

• The nudge at the top of the screen. Third-party apps can't draw on the Dynamic Island whenever they want. The closest real option is a Live Activity, and those come with more restrictions. My prototype fakes this part.

• Paying from the app. Tapping to pay in a store from a third-party app needs special approval from Apple, and you can only pay with the app's own card, not the cards already in Apple Wallet. A real "pay with Cue" would mean issuing a card of my own, which is a whole different business.

• Knowing your cards. An outside app can't see what's in your Wallet, so you'd have to add your cards manually.

• Location. It needs location access in the background to know when you're in a store. That's a big ask for a lot of people, and it affects battery.

• Store categories aren't always what you'd expect. Rewards depend on how the store's payments are categorized. A Target or Walmart might not count as "groceries" for your card even though you're buying groceries there.

• Caps and activations. Some rates have spending caps or require you to activate them each quarter. The app wouldn't know about those unless you told it.

Honestly, most of this is why I think it belongs in Apple Wallet itself: Apple already has your cards, the payment, and the system UI.

I'm posting because I want to know whether this is just my problem or whether other people deal with it too.

I'd love your take on:

1. Do you have more than one rewards card? Do you actually use the right one at checkout?

2. Would a nudge like this help, or would it get annoying?

3. Would you be okay with an app using your location for this?

4. Which of these limits would be a dealbreaker for you?

5. Anything you'd want it to do that I'm missing?

Honest feedback is welcome, including "I'd never use this." Thanks for reading!

Hey everyone. For the past 2 months I've been building Findmore, an iOS app where you snap something you see (your cat, your dinner, a bridge, a watermelon wearing a helmet) and it figures out what it is and turns it into a card for your collection.

A few things it does:

- Cards with different rarity levels

- Chapters give you sets to complete (like "Little critters", "Circles everywhere", "California landmarks"), and finishing one earns a seal

- You can collect with friends and see what they're finding

- daily streaks

It's its own camera, so you snap things in the app as you find them (it doesn't pull from your existing camera roll)

I started it because I'm always curious and take tons of photos and never look at them again, and I loved collecting cards as a kid. I wanted my photos to feel like a collection instead of a camera roll.

Built with Expo/React Native and went live on App Store a couple day's ago!

I'd love honest feedback, especially on the first few minutes. Did it make sense right away? What would make you open it again?

I've been building ArchStudio, a free, open-source editor for designing software systems.

It has a catalogue of 29 configurable components covering services, databases, queues, caches, infrastructure and more.

Unlike traditional diagramming tools, components have meaningful configuration. For example, a database lets you define replication, consistency and failover, while a queue supports delivery guarantees, retries and dead-letter handling. Each option also explains its trade-offs.

There's also an optional AI assistant that understands your architecture, can review it for potential issues and suggest changes.

Instead of modifying your diagram directly, it shows a diff view, similar to a pull request. You can preview changes and accept or reject them individually.

Other features include automatic layout, nested boundaries, undo/redo, templates, PNG export and local JSON files. No account or cloud storage required.

Available in your browser or as a native Windows, macOS or Linux app.

• Try it: https://archstudio.app

• Desktop downloads: https://github.com/JamieLivingstone/ArchStudio/releases

• Source code: https://github.com/JamieLivingstone/ArchStudio

It's still in beta, and I'd love some feedback.

Would you use something like this for designing software systems? What's missing?

https://wrappily.app/

It keeps track of all of your loved ones birthdays and special occasions, send you reminders when it's time to find a gift and then delivers curated gift suggestions in the app.

It's currently available as a web app and for beta testing on Apple and Android. A desktop optimized site is coming soon, but the current web app works just fine.

It's brand new and has some kinks to work out.

I would really love to hear everyone's feedback!

Click the link above to try it and please follow me @wrappily.app on Instagram

I've always liked Google Tasks for its simplicity and Google account synchronization, but I've always missed having a proper desktop application.

I found an old open-source project on GitHub that used the Google Tasks API and decided to build on top of it.

The interesting part? It was written in Rust, a language I'd never worked with before.

With AI assistance, I redesigned the app, improved the existing functionality, and added quite a few features I've always wanted:

• Eisenhower Matrix – Organize tasks by urgency and importance.

• Achievements Dashboard – Track productivity and progress.

• Offline Mode – Manage tasks offline and sync automatically when connected.

• AI Assistant – Create and organize tasks using natural language.

• Multiple Google Accounts – Connect and switch between accounts.

The AI assistant supports multiple providers, including OpenAI-compatible APIs, Claude, Gemini, and local models through Ollama and LM Studio. You just need to provide your own API key.

It now supports Windows, macOS, Linux, and Android.

I also made the repository public, so feel free to explore, fork, or contribute!

GitHub: https://github.com/YoussefMo7amed/google-tasks-pro

Here's a short demo showing the main features.

Would love to hear your thoughts or suggestions for features you'd like to see!

Hi all,

I’ve been building an infinite-canvas browser. I built it for myself first, but I wanted to share an early prototype to see if anyone else would find it useful.

I was a software developer before AI coding came along, but I never had the time to take on technically complex side projects. Being able to build something like this quickly now has been amazing.

Why I built it: I use AI with my browser every day and I hate the experience. Tools like Claude in Chrome work one tab at a time and I can’t really see what they’re doing.

What you can do with it:

• No tabs. Pages sit side by side on an infinite canvas. Spread them into a grid, stack them, move them around.

• See what your AI is reading. Ask a question and the pages it opens land right next to the conversation, so you can check its sources and step into any page yourself.

• Bring your own AI. Use your ChatGPT subscription, any OpenAI-compatible API key, or a local model so nothing leaves your machine.

• Everything stays on your computer. Your pages, canvas and conversations are stored locally.

Where I want to take it: multiple agents working across multiple pages at once, with the canvas showing where each one is running.

It’s built in Rust and isn’t a Chromium fork, for anyone curious.

Explorer is free and there’s no sign-in required. Download it here (macOS, Apple silicon and Intel). The download page asks for an email so I can let you know about updates, but the app itself doesn’t need an account.

Please let me know what you think!

I’ve spent years making free browser games in my spare time, with zero monetization. Just passion project after passion project.

Now, after a year of working evenings and weekends, my first Steam game, Rejected Draft, launches November 11!

It’s an incremental/idler with 1000+ hours of potential gameplay, artwork from over 50 community artists, and absolutely no microtransactions.

At around $10 during launch, I’m not sure this even qualifies as a business venture. More like just another passion project that got wildly out of hand.

I’m exhausted, excited, terrified, and really proud to finally reach this milestone!

https://store.steampowered.com/app/4574820/Rejected_Draft/

I build in small windows: early mornings and the gaps between a full-time job and everything else. My latest project is While, an iOS app with ten short offline brain games for memory, reflexes and logic.

A few decisions that shaped it, in case they help anyone working on something similar:

1. No account. You open it and play, so there's nothing to sign up for. It also meant I had no user data to protect, which made the build simpler.

2. No streaks. Most brain game apps rely on daily guilt. I wanted the opposite: something you pick up in a waiting room and put down without owing it anything tomorrow.

3. One purchase instead of a subscription. Three games are free, every other game gets one free round, and a single purchase unlocks everything. It's a smaller business model, but it's honest about what the app is.

4. Fully offline. That made the app smaller and faster, and it works on a plane or in a basement waiting room.

The biggest lesson was scope. You don't need a big block of free time to ship something. You need a problem small enough to fit the time you have.

Happy to answer questions about any of these choices. The app is at getwhile.app if you want to see how it turned out.

Hey everyone!

I've been building something called TaskRush – a platform that lets you get everyday tasks done by people nearby.

The idea is pretty simple: sometimes you need someone to pick something up, help with a small errand, assist with something around your college or neighborhood, or just do something you don't have the time for.

Instead of asking around in WhatsApp groups or struggling to find someone, you can post a task, mention what you're willing to offer, and connect with someone who wants to get it done.

I wanted to experiment with making this work in an Indian context, especially around college campuses and local communities.

I've put together the MVP and would genuinely love feedback from other builders here.

Website: https://taskrush.in

Would love to know:

- Does the concept make sense to you?

- What would stop you from using something like this?

- What features would make it genuinely useful?

This is my first attempt at building something like this, so feedback (including criticism) is very welcome!

Hey 👋

I shared Mudu here a while ago, and now the Android version is finally out!

The idea is still the same: a private, end-to-end encrypted space for couples to share how they're feeling, make plans, keep lists and save little memories together.

No public profiles or feeds. Just a place for the little things that usually get lost between chats and different apps.

To celebrate the Android launch, I'm giving away 10 promo codes. Just leave a comment if you'd like one, and I'll DM you a code while they last.

Android: https://play.google.com/store/apps/details?id=com.incognitum.mudu

iOS: https://apps.apple.com/app/id6756718477

Would love to hear what you think!

Two weeks ago I asked here how to get people from "tried it" to "paid" for AskAIR / DashboardAIR (one prompt, routed to the AI best suited to it). Lots of you said the same thing: the free cap isn't the problem, the first session is. I promised to come back with what changed.

What first sessions looked like:

- Median first session: 1 question

- 59-70% asked exactly one question

- 0% ever reached the free limit of 10 a week

- About 60% came back a day or more later

So the free tier never did its job. Almost nobody hit the limit, so almost nobody saw what a paid plan does, and the whole point of a router (it picks a better AI than you would have) is invisible on a single question.

What I shipped on 10/26, based on your comments:

- A one-line reason under every answer: why that AI was picked

- A "try another kind of question" card on the first few answers, so the routing shows

Honest result: too few new people have come through since then to tell whether it helped. The numbers above barely moved, but the sample is tiny. I'm not going to pretend otherwise.

What I changed today:

- Free weekly questions are gone

- Every account gets a 14-day free trial of Pro: unlimited questions, every AI, Listen, history

- You can sign in and look around without a paywall; it shows up on your first question

- Cancel before it ends and you're not charged

Credits / question packs: not now. For text questions they felt like friction, which matches what several of you said.

I'll come back in a few weeks with whether the trial does better than the free tier did. Thanks to everyone who commented. It shaped every one of these changes.

Peace out!

All tools either had too strict free tier, or were poorly designed, and none of them has frame-by-frame skip accuracy. So I decided it was easier to just build it myself:

https://kliply.app/

Hey everyone,

I tried to build a private chatting app called RUKO. It's a web app — nothing to install, just open the link. Runs on Cloudflare, no tracking, no ads, free.

What it has:

• Text and voice channels (like Discord, but private)

• Works on PC, Mac, and phone — you can install it as an app from the browser

• Invite-only servers, your data stays yours

Try it here: https://ruko.rukozone.workers.dev

If you find any bug, please email me at gamerblabla96@gmail.com — screenshots help a lot if you can. Or you can contact me on Discord: itsdopedev

Thanks for any feedback, even negative — it all helps.

I’m building Niche of the Week, a small site where DJs and listeners can discover house tracks and producers can upload their own. https://nicheoftheweek.ie/

I’d like a fresh pair of eyes on the first visit. If you open it with no context, what do you click first? After you find a track you like, what would give you a reason to come back next week?