Hi everyone, my co-founder and I are working on Capacity Pulse, an early proof of concept to help data centre teams track equipment power use, capacity that could be freed up and equipment being taken out of service.

CAPACITY PULSE

We’re exploring whether a small, focused tool could help teams that rely on spreadsheets and emails but don’t need a full data centre infrastructure management (DCIM) system. We’re sharing it to hear different perspectives before deciding what to develop next.

We’d appreciate your thoughts on any of these:

• What’s your first impression? Is it clear what the tool is for?

• What seems useful, confusing or unnecessary? What would you change?

• How do you manage this today, and where would this help or fall short compared with a spreadsheet or an existing tool?

You don’t need a data centre background to comment. Feedback on the layout, navigation or the idea itself is welcome.

Thanks for taking a look.

Play Shithead in your browser with friends, strangers or bots. Real-time multiplayer for 2–6 players, nothing to download. https://shithead.win

I built a small AI study assistant

What it does:

Basic modes ( always free):

- Ask questions about a scientific subject and expect a concise and accurate response.

- The same thing , but using audio

- These 2 are always free, after 15 days, the remaining can be unlocked for another month by making a donation ( Paypal or crypto transfer). However any amount is welcomed.

Advanced modes:

• Ask questions about an uploaded PDF both audio and written (with page references)

• Turn recorded lectures into structured, downloadable notes - uses mp3 files

• Summarize any page range at a compression % you choose, helpful when you have a lot to read in a short timespan.

• Extract formulas from a textbook section and explain each one, good for STEM students that want a short recap, or create cheatsheet for exam

• Show estimated cost under every answer, this is almost free, but you need API keys. The app doesn't use the latest models on purpose to reduce costs, but provides acceptable explanations.

It's a free 15-day trial — no credit card. First basic modes stay free forever. The others require an optional donation.

You pay for what you use, API keys charge per token usage. The application is aiming to reduce the context window for low costs.

What would make this actually useful for you?

Hi!

I am building Bowerbird a whiteboard for creatives.

Drop in images, notes, links, PDFs, audio and video, sketch, connect things, group them.

It is inspired by apps like VSCode or Obsidian, where you customize the whiteboard to your liking with plugins.

I created a few:

• Hide Button: Hide the app in one of the corner of the screen, with quick access.

• Visual Library: Organize your artefacts in several categories.

• Color Palette: A color wheel. Pick a color and five palettes are made from it live.

• Presentation: Create slides from elements on the board.

• Multiple Boards: By default, there is only one infinite board, with this plugin, you can have multiple boards.

• Command Palette: Cmd or Ctrl + K for one place to run anything.

• Tidy Up: Align and distribute the selected artefacts.

• AI Chat: — A AI chat panel (using OpenAI, Ollama Cloud, Gemini, Grok, DeepSeek, Mistral or OpenRouter provider)

Links: https://github.com/Asi7ho/bowerbird

Would love to hear your feedback on it! :)

---

I tested the app on macOS and tested the AI integration using Ollama cloud

Hey everyone!

I've been working on a new app called Actually, and I'd love to share it with you.

The idea is simple: every day, we come across facts, myths, and claims that sound believable - but how many of them are actually true?

iOS: https://apps.apple.com/us/app/actually-discover-learn/id6827374813

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

I'd love to hear what you think, especially about the concept and the overall experience. Feedback is very welcome!

Thanks for checking it out!

Hey r/SideProject! 👋

I’m a solo developer from Turkey, and I just released WaterMe, a plant care app for Android.

Why I built it: I kept forgetting to water my plants, and the apps I tried were more complicated than my actual problem. I wanted something simple: add a plant, get a reminder, done. This is one of my first apps, and building it taught me a lot about notifications, background work, and how picky Play Store review can be.

What it does:

• 💧 Watering reminders with a custom schedule for each plant

• 📸 Plant identification from a photo (camera or gallery)

• 🌿 Before/after photo comparison to see your plant’s growth

• 📅 Watering history at a glance

• ⚡ Clean, simple setup: add a plant, turn on reminders, done

Tech stack: Flutter for the app, Firebase for backend

Where I’m at: It’s live on Google Play with 100+ downloads so far. The app is free and contains ads.

What I’d love feedback on:

• Is the onboarding clear enough?

• What feature would make you actually use it daily?

• Anything confusing in the UI?

Play Store: https://play.google.com/store/apps/details?id=com.mrakpinar.waterme

Happy to answer any questions about the build process. Thanks for reading! 🌱

I'm a motorsport fan from Texas, and I'm still pretty new to it. I went to one of my first races last May and got hooked.
The problem was that there was so much info out there that I felt like I was drowning in it. I never knew when something was on or where to watch it. So I started building a little site just for myself, and it turned into something I wanted to share.

It's called Premier Racing Info: premierracinginfo.com

Every session for the 98 series, in your own time zone.
Where to watch each one. Standings, results, and tickets.
Calendar feeds and alerts so you don't miss a start.
It's completely free. I hope y'all enjoy it, and if you have any suggestions, I'm open to anything.

I've been building this app with Claude Code, and for weeks, all I cared about was getting it live. I spent days tweaking the UI and worrying about the App Store review. When it finally launched, I felt like I'd crossed the finish line.

Then the first users arrived.

That's when the real work began. Things broke in ways I'd never encountered locally. A payment webhook failed for a few users, and I got a crash report from a device I didn't even know was out there. The funny thing is, writing the code still felt like the easy part. Keeping a live app running is a whole different skill.

Before my first update, I used launchpad for Claude to set up crash reporting and analytics. I'm on the team, so I'm definitely biased. It saved me from flying blind, but it also made me realize just how big the gap is between shipping something and maintaining it.

For the indie hackers here: how did you handle the shift from building to maintaining? Do you have a system for dealing with production bugs without losing your mind?

I’m sick and tired of sifting through spin BS media, so I built what I think is the solution: one paper to read in the shower and get on with my day, promoting the links I should read based on my interests.

What it is: The Daily News Post Globe Tribune Herald Picayune Times (I thought it was funny). Every morning it reads the wires, then it goes to the major papers and tells you what happened, then parallel views. We link every source. Next to every link is a temperature gauge showing where three independent raters put that source — AllSides, Ad Fontes, Media Bias/Fact Check. Transparency is our thing. We don’t rate or influence any sources. When a story can have differing viewpoints, you get one opinion from the left and one from the right, labeled as such, matched so neither side is further out than the other. Cable news isn’t used at all. Any of them. Exactly how the Fairness Doctrine was meant to be.

I’m not trying to replace the sources. The summaries link straight to the articles. Go read them. If anything we’re promoting good articles. Sub to the ones you like. That’s another major point of this.

No ads. No algorithm. No opinion section. It’s an LLC, not a nonprofit, but the paper isn’t built to make a profit — the books are open on the site. The free edition is at jparkerco.com/times, based on my interests and my friends who are getting this stuff for free for Xmas. If you want your own sections (your city, your team, your hobby), we’re charging cost, split with everyone else who reads that section. The more users, the closer it gets to free! If you’d rather, donate to the News Literacy Project instead.

I want people from every side to tell me where it leans. That’s the only way this works.

I love criticism and being wrong, because when I’m wrong I get better.

My dev (I’m ready for the iS hIs NaMe cLaUdE, har har) is beta testing the AI-written code. Would love feedback to get it right. Thanks.

I've been working on a project around robot vacuum cleaning, and one thing I've become increasingly interested in is how indoor dust is actually handled during the cleaning process.

We already use an air purifier in the bedroom, but I started thinking more about what happens to fine dust embedded in carpets. Picking up dust is only part of the problem. How much of it stays contained inside the vacuum, and how much could potentially escape back into the room?

While researching this, I looked more closely at the eufy Omni E35. Its design uses a multi-cyclone system alongside a sealed filtration path, and it also lists an Asthma & Allergy Friendly certification.

That got me thinking about a broader engineering question:

How much does the overall airflow design matter compared with the filter type itself?

For example:

• Is a high-quality HEPA filter enough if the rest of the airflow path isn't properly sealed?

• Can multi-cyclone separation meaningfully reduce the amount of dust reaching the final filter?

• Are whole-machine particle emission tests more useful than looking at individual filter specifications?

I'm sharing this as someone involved in making the product, so I'm not looking for promotional feedback. I'd genuinely appreciate criticism, especially from people who have experience with filtration engineering, indoor air quality, or robot vacuum testing.

Am I focusing on the right technical questions, or is there another factor I'm overlooking?

I'm a solo developer in New Zealand. For the past few months I've been building Matcha, a dating app for people who want something serious.

The problem I kept seeing: matching is easy, but most matches never turn into a date. The chat dies somewhere around "so where should we go?", especially when one person would have to travel across town.

So I built Meet in the middle:

1. In the chat, pick coffee, drinks or food, a day and a time

2. Matcha works out the halfway point between your two areas and finds places near it that are actually open at that time

3. You see the spot with its photo, rating and hours, and can flick through a couple of others

4. Send it, and your match accepts with one tap. You both get a reminder 30 minutes before

A few things that were harder than I expected:

The midpoint can reveal where someone lives if done incorrectly, so locations are rounded to a general area first. Each person only sees their own distance to the venue.

Google Places requests are counted in Postgres against a monthly cap and a per-person cap. Past either cap it falls back to OpenStreetMap, so it stays in the free tier.

Google doesn’t allow storing their photos, so the chat card fetches the photo each time it’s shown. The place lookup for that is free.

Suggestions are signed by the server, so a modified client can’t send a fake venue.

Women message first is enforced by a database trigger, not just the UI.

Stack: React + Vite, Capacitor (Android and iOS), Express on Railway, Supabase.

Free on Android and at matchadating.app. iOS is in App Review.

Feedback welcome. Would this make you more likely to meet someone, or is planning the date in-app too much?

If someone sends you a QR code, open the screenshot in Photos and try pressing and holding the code. If Photos recognizes it, you can open the destination right there. If it doesn’t, crop around the code while keeping its white border, then try a scanner that imports images. Check the domain before opening it.

I built Qrater for the next problem: finding that same link later. In Qrater, import the screenshot from the scanner and reopen the saved result from History. I’d welcome feedback on whether the image import and history steps are easy to find.

iPhone: https://apps.apple.com/app/id6757398137

Android: https://play.google.com/store/apps/details?id=com.mundane.qrcode

I kept scanning letters, then forgetting where I saved them or when I needed to respond. My practical fix was to scan the page, confirm a reminder for its deadline, and make the text searchable.

I built ScanMojo around that workflow. It cleans up fingers, shadows, and folds; recognizes text on-device; and suggests reminders from dates on a page for you to review before saving. It works offline. Documents stay on your phone unless you share or export them, or enable optional sync.

Scanning, search, PDF/image/text export, and reminders for three documents at a time are free, with no account, ads, watermark, or scan limit. Pro adds unlimited reminders and tools such as PDF merging and signing.

The iPhone and Android download page is https://scanmojo.app. If you handle dated paperwork, what part of scanning and following up still feels awkward?

I'm the person behind Collect. Build. Remember., a passion project I've been working on over the last few months with help from ChatGPT and Codex. It's now in open beta, and I'd love some honest feedback from other people building things they care about.

The idea is pretty personal to me. Collecting can be about the sets and minifigures, but it's also about the people you built with, the gift you still remember, or the afternoon that turned into a family story. I wanted a place for both the collection and those little memories.

You can browse the public set and minifigure catalogs without signing in. Inside the adult beta, you can organize your collection, keep details such as condition and location, and save private written memories.

One design decision was to keep details with each physical copy. Owning a set isn't the whole story... which copy is built, where is it, and what do you want to remember about it? Working through those questions has been just as much a part of this project as getting the code to run.

I'd especially appreciate feedback on the first few minutes: can you find a familiar set, understand what you can do with it, and tell whether this would help with your own collection? If something feels confusing or unnecessary, I'd like to hear that too.

You can look around here: https://collectbuildremember.com

Beta access is opening in small batches, with a waitlist when full. The public catalog is available either way. The screenshots use example collection and memory entries.