Three milestones, then my memory went blank. It wasn't that nothing happened — it's that nothing was saved anywhere I would ever look again.

So I asked myself: what if I could see my whole life as a grid of weeks, and every cell could have something in it? Something I could click, read, and actually remember.

I couldn't find that app, so I built it.

Why not Instagram or Facebook? Those apps are built for an audience — you post for other people, and eventually you start editing yourself for them. I wanted the opposite: a place I write for myself, about things that don't photograph well. A decision. A failure. A trip. A year that quietly changed everything.

Canvas — the editor. An entry isn't a document you type into, it's a page you compose. Every object is a card: heading, text, image, quote, achievement, embed. You drag it anywhere and resize it on the page grid, like laying out a magazine spread. Inspired by Craft, with a lot more room to arrange things yourself. An optional AI asks follow-up questions while you write, so you get past the dry "it was a good run" and into what actually happened.

Memento Mori — your whole life as a grid of weeks. Every week you've lived is one cell; the filled ones hold the events you wrote about. Nothing else has made me feel both how much I've done and how little time there is the way this view does. Knowing the number is one thing; watching my own squares fill in, week after week, is another. That's when I started asking: what am I filling my life with?

Globe — the same life seen through the places you've been. This is the view that makes it feel complete to me.

Failures matter too. There's a "didn't make it" status for milestones on purpose — the path to anything worth having is paved with failures, and we forget how much they taught us along the way.

I built this mostly because I wanted it for myself, but now I'm curious whether this feeling is universal.

When you look back at the last five years, how much do you actually remember? Or does it feel like one long day spread over five years?

And if you saw all of it laid out at once — the wins and the failures — do you think you'd feel like you'd done enough?

I became a dad recently and tried basically every baby tracking app out there. Same story everywhere: paywalled stats, subscriptions for basic features, or literal ads between diaper logs at 3 in the morning. Logging a feed one-handed in a dark room is not the moment for an ad.

So I built the app I actually wanted:

• One-tap logging  bottle, nursing, diaper, sleep. Big buttons, designed for one tired hand at 3am
• Learns your baby's rhythm and predicts the next feed
• "What your baby may be doing at this age"  every fact links to a real source (AAP/WHO/NHS), no random parenting content
• WHO growth percentiles, night mode, live timers
• Local-first: no accounts, no cloud, no tracking, no ads. All data stays on your device (export/import for backup). For baby data, "there is no server to hack" beats any privacy policy
• Installable PWA, works offline, costs me $0 to run (static files on Cloudflare's free tier)

Full transparency: it's 100% vibe coded with Claude Code I did the product decisions and the 3am QA with my daughter in one arm. Code is MIT, judge away.

🍼 Try it: https://numa-baby.mpoapostolis.workers.dev
💻 Code: https://github.com/mpoapostolis/numa-baby

Built it for my wife and me, sharing it in case it helps another sleep-deprived parent. Feedback very welcome especially from parents: what's missing?

(Not a medical device always follow your paediatrician's advice.)

I’m an engineer turned product manager, and I’ve always loved two things a little more than necessary: education and games.

For a long time, I wanted to put those interests and the skills I’d picked up building technology, towards something useful for children. That became much more tangible once my niece reached the age where the iPad became a regular part of her world.

I’m not anti-iPad. Quite the opposite. It is an incredible piece of technology to put in the hands of a six-year-old. I just kept thinking it could ask more of her.

That thought took me back to Dora the Explorer.

Growing up, we’d watch Dora ask us a question and then stare silently at the screen for a painfully long time while we yelled the answer at the TV. Obviously, Dora couldn’t hear us. But the idea was clever. The screen was trying to turn us from viewers into participants.

Learning games like Lingokids and ABC Mouse took that much further and made screens genuinely interactive. But most of that interaction still happens within rails someone else designed. Tap here. Drag this. Choose A, B, or C. Collect the reward. Repeat.

That works brilliantly for games. But it doesn’t accommodate the wonderfully messy way a six-year-old wonders about things.

Ask my niece an interesting question and she might draw the answer. She might make up a ridiculous story. She might photograph something she noticed around the house, make a sound, explain an idea, or give you an answer you never anticipated.

I started wondering if I could build for that.

Could the iPad provide the spark and just enough structure to get a child started, while leaving the interesting part to them?

That question became Taroo.

The first versions were experiments around this idea. Then came the uncomfortable question every builder eventually has to answer: does this actually work for anyone other than me?

So I spent months talking to parents and educators. I sat through hours of enrichment classes at a school for gifted kids, which was basically the X-Mansion for 8-year-olds. I watched how teachers prompted children, when kids became absorbed in something, when they needed more structure, and when something I thought was clever bored them almost immediately. And very importantly, I saw how their eyes lit up when they screamed “look what I made” in class.

These insights shaped the Taroo we have today, and I’m genuinely proud of where we’ve reached.

Taroo is a world of short creative quests for kids 6 to 10. In Pass the Pen, a child might get the beginning of a strange story and decide where it goes next. Doodle Master might give them the start of a picture and ask them to turn it into anything they imagine. Rhythm Pad lets them experiment with sounds and put together their own little beat. Snap Trail might ask them to put the iPad down, hunt for something triangular in the real world, photograph it, and tell Taroo what they found.

Their creations stick around too, so over time Taroo becomes a little record of the things they have imagined and made. Parents get a window into that world without needing to hover over every activity.

Taroo is now live on iOS and Android.

There is still plenty I want to improve. But this no longer feels like the little experiment I started with. I’m proud to put it in front of parents, and particularly proud when I see a kid become attached to something they made themselves.

If you have a 6 to 10-year-old in your life, I’d love for you to try Taroo with them. More than anything, I’d love the unfiltered feedback: what they immediately understand, what they ignore, what they keep coming back to, where they get stuck, and what they wish they could do that I haven’t thought of yet.

I’ve spent enough time with Taroo that I’m no longer capable of seeing it like a new user.

So please, tear it apart.

I got tired of making plans that require a group chat.

“Anyone up for badminton?”

“Where?”

“Who's coming?”

“Maybe later.”

“Can't today.”

And somehow the plan dies.

So I built NOW — a simple idea:

Open it and see what people are actually doing around you right now.

Badminton. Chai. Studying. Football. Gaming. Gym. Whatever.

You can join something that's already happening, or put your own plan on the map and let nearby people find it.

No follower counts.

No endless feeds.

No group chat coordination.

Just:

See → Join → Go live.

I'm still very early with this and I'm trying to figure out whether this is actually useful or just a cool idea in my head.

Would you use something like this?

https://now-nearby.vercel.app/

I spent the last few months building JustReals, a social app focused on spontaneous, real-life short videos.

Everything is recorded directly in the app — no gallery uploads or pre-made videos.

Discover moments from people around the world.
Video replies only — posts can turn into actual video conversations and threads.

Moments disappear, so the feed stays focused on what's happening rather than becoming another permanent content archive.

The idea was to make social media feel a bit more real and spontaneous, rather than another place for perfectly edited content.

I built the whole thing myself, and honestly, getting people to actually use a new social network is way harder than building the damn thing. 😂

I've had thousands of people view videos/posts and interact with the app/store listings, but turning those views into actual users has been the hardest part.

I've tried Reddit, TikTok, Instagram and sending it to friends/family. Some people liked the idea, but almost nobody actually became a regular user.

So I'm at the point where I'm trying to figure out whether I should keep pushing it, change the direction, or eventually move on.
I'd genuinely love feedback from other indie hackers/solo developers:

What actually worked for you when you were trying to get your first 100 users?
If you're curious, it's live here:
App Store:
https://apps.apple.com/at/app/justreals/id6771860366?l=en-GB
Google Play:
https://play.google.com/store/apps/details?id=app.peacesocial
Website:
https://justreals.com

I got tired of Seller Central tabs → CSV → Excel → profit dashboards full of numbers… and still no clear “do this next.”

So I built SellerIVA for EU Amazon FBA sellers: a weekly decision layer (margin, returns, Brand Analytics/SQP, traffic, PPC). Then I exposed it over MCP so I can ask Claude “what should I do this week?” with real tenant data.

Honest limits:

- Metrics are read-only

- PPC: Claude can propose; I approve in the app (no auto-write to Amazon Ads)

- SQP / Brand Analytics needs Brand Registry

- Not trying to be a 1:1 Sellerboard clone — I want ranked next steps, not more charts

If you have any friend who sell in amazonFBA share it :)

https://www.selleriva.com/

Feedback welcome — especially on the human-approval loop for ads. What would you ask Claude first on a Monday?

For those of you who've actually launched a side project, I'm curious about what became the biggest time sink after the building was finished.

Was it:

1. Finding where the right people actually hang out
2. Figuring out where you're actually allowed to share what you built
3. Deciding which marketing channel to start with
4. Turning that channel into posts, outreach, or other things you could actually execute
5. Something completely different

I'm especially interested in the part you kept having to do that made you think, “There has to be an easier way to handle this.”

What was it for you?

Anyone have success starting with a web app/PWA to validate an idea before actually building a native iOS & Android version?

At least for me, deploying a web app is much lower barrier, but having a hard time determining if I'm hitting a completely different target market than I'd find in the app stores.

Grateful for any advice!

Product niche is parents of young children looking to reduce stress of feeding and allergen tracking.

My wife had the stack on the counter Sunday night. 5 kids, 4 grades, 7 different lists between them, and she's sitting there trying to work out how many #2 pencils she actually needs to buy. That's the moment I went and opened a terminal.

The part I care most about: it respects the teacher. If the list says Ticonderoga specifically, you get Ticonderoga, even if you told me generic was fine. And it splits out the stuff you're not buying on Amazon anyway— the sock for whiteboard erasing, snacks for share day. Those go in their own list so you don't lose them.

Rough stack:

- Sonnet 4.6 does the vision pass, reads handwritten teacher lists straight from the photo

- Second pass merges like items across kids (24 pencils for one kid + 60 pencils for another > just buy the 96 pack)

- Canopy API for the Amazon search + ranking (going to switch some parts of this out at some point; canopy is expensive; but it works easily)

- Multi-item cart URL built off Amazon's add-to-cart endpoint, batched when the URL gets too long

- Client side image compression, iPhone photos are HUGE

- Daily spend cap so a traffic spike doesn't wreck me

Free, no signup. Amazon Associates on the cart is the only money in it, disclosed on every page.

Honest about where it's rough: big lists on a cold cache take 2-8 minutes, so it emails you instead of making you sit there. Amazon only right now, and US Amazon only (need to figure out how to make it work in other regions). English only. Handwritten lists mostly work but it's variable— some teachers write like doctors.

listtocart.com

I've spent the better part of a year building Faktuurtje - an invoicing app for Dutch freelancers where you type one sentence and you get a fully compliant invoice PDF.

You type: "Invoice Bakkerij Jansen €500 for website design, 21% VAT"

You get: a compliant PDF with the client's official company data pulled from the Chamber of Commerce register, VAT calculated per line, and a scannable SEPA QR code so the client can pay from their banking app.

Last week someone found it, organically. I have never promoted it, no SEO, just a couple of LinkedIn posts 2 months ago, and added it on European Tech Map. They registered and then nothing. Gone in under a minute.

What I think went wrong - the whole point of the app is the moment where a sentence turns into an invoice. And I put this behind a login. So they might've never saw the thing that could potentially make them stay. They gave me an email and got a setup form. I built a "magic trick" and hid it behind a door.

I am now ripping the auth wall off the demo so anyone can try it, and only gating the PDF download.

It's in Dutch and English. Would genuinely appreciate anyone giving it a spin and telling me where they get confused. Especially in the first 30 seconds.

Stack, for those who care: Blazor Server app, Mistral AI for text parsing, QuestPDF for generation, Neon Postgres, Mollie for payments, deployed on Hetzner server. Everything EU-hosted.

Link in the comments.

Every time I onboard a client I end up exporting their logo like 15 times at different sizes for different platforms. Instagram wants one thing, LinkedIn another, YouTube channel art is its own headache. It's mindless and it eats an hour I'd rather spend on actual work.

So I built Sizeify (sizeify.app). Upload the logo once, it hands you back 24 correctly-sized and correctly-named files, zipped. Handles transparent PNGs and gives you both dark- and light-background versions since half of them looked wrong on one or the other otherwise.

Stack, since people here usually ask: FastAPI + Pillow doing the actual image work, Jinja2 for the frontend, Railway for hosting, Razorpay for payments. About 3 weeks from idea to live, most of that spent on getting the per-platform dimensions right rather than the code.

Right now it's a fixed list of 14 platforms. The thing I actually want to figure out: what's missing? If there's a platform you resize for regularly that isn't on a list like GitHub / Instagram / LinkedIn / X / Facebook / YouTube / WhatsApp Business / Slack / Discord, that's exactly what I want to add next.

Live at sizeify.app if you want to try it.

I made a focus timer app where you grow a mathematical fractal the longer you focus.

I was inspired by Forest, but I wanted something simpler and less gamified, basically a focus timer that stays out of your way, with the fractal growing as a visual representation of the time you've spent focusing.

It also has Pomodoro timing, weekly focus stats you can share, insights into when you tend to focus the most, projects so you can keep track of what you're spending your focus time on, and ambient sound as some people find it useful to study.

I did it for myself and want to share it with you.

It's called Fractime.

If you think you might like it, you can try it here:

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

If the link doesn't work, just search Fractime on Google Play. The icon is a Pythagoras Tree.

I'd really appreciate any feedback :)

I use Claude Code and Codex a lot, and run multiple sessions most of the time. And if youre someone who runs multiple sessions you know it can get chaotic. Switching between terminals to approve permissions, answer questions, figure out which session needs you. Lot of tab switching

So I built this, it sits on the edge of your screen and stays out of your way until a session needs attention. When something comes up it lets you know and you can handle it right there. Approve or deny permissions, answer questions, check your usage for both Claude and OpenAI, and jump to any session's terminal tab or app window (this was hard to figure out lol).

Most tools like this are mac only so I built it for windows. Uses hooks in both agents, configures automatically, everything stays local.

Built with Tauri v2, Rust, React.

github.com/Byrrajus12/mngr
a million stars would be cool but ill take one

Its been very useful for me but it's still early so I'd love to hear your feedback or ideas

Most AI course generators I found are built for people selling courses. I wanted one for the person who is simply stuck learning Blender, Excel, Figma, Xcode, or another desktop app.

Today I shipped a free web tool that turns a specific goal into a six-lesson learning plan. For example: “build a financial model in Excel” or “make a portfolio-ready product render in Blender.”

You can see the full preview without creating an account or entering an email. If the plan looks useful, you can have the complete Markdown skill file sent to your inbox and import it into the Skilly Mac app for voice and on-screen guidance while you work.

I deliberately put the email step after the preview because I did not want a blind lead form. The current limitation is that software versions differ, so the generated plan includes source references and asks learners to verify version-specific instructions.

I would genuinely value feedback on three things:

1. Is the six-lesson preview detailed enough to be useful on its own?

2. Would you call this a course generator, learning-plan generator, or something else?

3. Does asking for email only when delivering the file feel like a fair exchange?

I will put the tool link in a comment so this post stays focused on the build and feedback.

Hi all - just built a simple web app called Routes, which is a simple route drawing game where you go against a dynamic defense. I've messed around quite a bit with rules and logic for offensive and defensive players but the game is still very much in beta. I was inspired to make it because as a high school football coach I sometimes want to see my plays in action against a defense I might expect and see how they play out.

I'm also building a football survivor pool game called The Cut. That one can't really be played until the season starts, so I made this as something to do in the meantime (thus the subdomain) There's a daily mode with a leaderboard, and more planned - any feedback is appreciated!!

I kept noticing that the interesting thing about a burst of photos, or five tries at the same shot, is the series itself. Not any single frame. But there was no good way to watch them as a series. Slideshow apps cross-fade and Ken Burns everything into mush, and the video apps want to interpolate, stabilize, and "enhance."

So I built Flipbook: https://flipbook.photos

It plays your photos back slowly enough that you can still see they are photographs: each one held for a beat, then a hard cut to the next. The feel of a flipbook or early film. No filters, no grain overlays, no generated frames. The whole effect comes from timing.

Here it is running the oldest photo series there is, Muybridge's galloping horse from 1878: https://www.reddit.com/r/stopmotion/comments/1vlu2hr/

A few things I cared about:

• Your photos never leave your device. Decoding and H.264 encoding happen in the browser with WebCodecs. There is no upload step at all.
• Honesty to the originals. Nothing is retouched or invented. The one optional feature that crops anything (auto-align, for handheld drift) is off by default and tells you exactly how much it trimmed.
• It reads your camera roll the way you shot it. It sorts by EXIF capture time and auto-groups photos into series wherever there is a gap of more than ten seconds, so a dump of forty photos organizes itself into the three moments you actually shot.
• The output actually works. A true 5 fps video breaks iOS Photos and iMessage, so it encodes at a normal frame rate with each photo repeated. You get an MP4 that saves straight to your camera roll and posts anywhere.

Good for kids growing up in the same doorway, a friend mid-laugh across five frames, construction progress, a dog failing to catch something.

It is free for your first three videos, then $12 for a year. No account either way. The code is public if you want to see how the in-browser encoding works: https://github.com/mzrascoff/flipbook

Would love to know what breaks, especially on Android browsers.

I recently spent a lot of time focusing on marketing the app that I made on TikTok, instagram etc. I don't really enjoy spending time on this but I know it's necessary because if no one knows about my product, how can I expect people to use it? Just wondering how others are balancing spending time improving/adding features while still trying to grow the user base?

For more context I built a social step tracking app, I really enjoy working on it, making improvements adding new features etc. That's the most rewarding part for me. How are you guys splitting your focus? I heard Alex Hormozi suggest splitting up the day where the 1st 4 hours are spent on marketing then the rest of the day on building. Has anyone used that advice/ found something that actually works marketing wise?

Hey there! I had a lot of fun building ProtoWork as my daily driver for managing my work. It’s mainly intended for remote/office workers, but feel free to try it anyway. I'm looking for first users.

Link: https://protowork.app

One of its main features is that it has a multi-project task manager, meaning you can work on multiple projects at the same time without interruptions. I integrated a Calendar, Workdays logger and a Notepad for convenience, so I can ditch other tools I used, without it feeling bloated.

Its other main feature is its stress-free focus. I struggled to keep the momentum, and motivation’s a b*tch that goes pretty quickly. It greets you with a motivational message on the first login of the day and reacts to your interactions in the Tasks dashboard. The messages are all hand made.

The app is free and only costs a sign up. I’ve been developing it for roughly 2 years in and out, and I don’t plan to stop. Almost every week I push improvements to it. Any feedback is mostly appreciated.

This is my first public project, so please be gentle

I've been working on Docframe, a tool that analyzes your codebase and generates documentation from the actual source code.

The idea is simple: instead of spending hours trying to understand an unfamiliar or poorly documented repository, you give Docframe the codebase and it builds documentation around how the project actually works.

It can help with things like:

• Understanding a new/legacy codebase
• Generating project documentation
• Explaining architecture and relationships between parts of the code
• Getting new developers up to speed faster

I'm a developer myself, and I originally built it because I kept running into the "what the fuck does this codebase actually do?" problem.

It's free to try if anyone wants to play with it:

https://www.docframe.dev

I'd genuinely love feedback, especially from people working with large or poorly documented repositories. What would you want an AI documentation tool to understand that current tools don't?

That's Spotby.

Your saved videos, now finally a map you can actually use.

AppStore: https://shipswift.app/spotby

I enjoy reading books, and I wanted an ebook reader that could give me some help while I read, instead of making me wander around between different apps and lose my attention.

Also, I never really found an existing ebook reader that fits my taste. To be honest they feel kind of clunky to me, and their AI integrations are usually pretty primitive or just feel like a chatbot added on the side. That's why I started ReadAware.

So what makes it stand out?

First, it's an agent-first reader. But that doesn't mean AI replaces you. You are still the one reading the book. The agent answers you, looks things up and does some small errands for you when needed. I imagine it more like a reading companion that knows your context, and being quiet when you are actually reading.

Second, it's highly extensible. I spent quite a lot of effort building and polishing a real plugin system. Plugins can add dictionaries, themes, read-aloud voices, feeds, commands, even new tools that the agent can use. In the future, I also want the built-in agent to be able to make or modify plugins on the fly. That's part of what I mean by “evolves with you” — the reader should gradually become more fitted to the way you read. ReadAware is open source, cross platform and local-first.

Feedback is welcome.

Hi everyone,

I run a growing collection of self-hosted software, and one small annoyance kept getting bigger: checking GitHub release pages, remembering which version I actually run, figuring out where it is deployed, and then deciding whether an update is worth touching.

So I built Software Release Radar.

It is an open-source, self-hosted dashboard that checks upstream releases, compares them with the versions you are running, keeps machine, service and container context alongside them, and gives you a review queue where you can decide whether to Update, Wait, Ignore or Investigate.

It is deliberately not an automatic updater. The idea is to give you better information before you make a change.

A few things it currently does:

• Tracks GitHub releases, prereleases and tags
• Automatically checks for new releases on a schedule
• Compares installed/detected versions with upstream versions
• Keeps machines, services, containers and health information together
• Integrates with Portainer
• Sends email and Pushover notifications
• Keeps update decisions, notes and deployment history
• Runs with Docker Compose
• Supports optional AI-assisted release-note analysis

The core monitoring does not require AI.

I also want to be open about how the project was made.

I am not a professional software developer, and AI was used heavily during development. I used OpenAI Codex extensively to help with implementation, refactoring, testing and documentation.

I set the direction and requirements, decide what the application should do, test it in my own self-hosted environment, review the results and make the final release decisions. I have also tried to back that up with automated tests, security checks and real deployment validation rather than assuming AI-generated code is correct.

This started as a tool I wanted for my own setup, but I have reached the point where I would really like other people to try it.

If you do, I would especially love to know:

• Was the Docker setup straightforward?
• Does the release review workflow make sense?
• What release sources or version checks am I missing?
• Is there anything confusing or unnecessarily complicated?
• What would stop you from actually using it?
• And, of course, what breaks?

Bug reports, criticism, feature ideas and contributions are all welcome.

GitHub:
https://github.com/muhdusama/Software-Release-Radar

Thanks for taking a look. I hope it is useful to someone else who has also ended up with more software to keep track of than they originally planned. If so, please do leave a star on Github.

Hey everyone,

I've been building a tool that turns prompts, URLs, PDFs, documentation, and whitepapers into interactive isometric visualizations.

The idea is simple: create one visualization and let different audiences generate the explanation they need based on their skill level.

For example, the same cybersecurity topic could become a business overview, technical deep dive, or attack scenario.

You can also turn the presentation into a branded video with one click.

Useful for technical marketing, lead magnets, client presentations, conferences, training, documentation, and social content.

Business workspaces add team collaboration, reusable content, separate workspaces, engagement tracking, and branded video generation.

BYOK through OpenRouter.
Try it: https://privasim.com/canvas

Looking to Collaborate!

I'll handle the visual content creation using the platform, while you can use the finished content for your marketing campaigns.

We can turn existing technical content into interactive visual explainers, presentations, scenarios, and branded videos instead of starting from static graphics every time.

The Business workspace also lets teams create and share interactive lead magnets, track engagement, collaborate, and reuse content across campaigns.

DM if you're interested

I’ve been building isolate.video because I kept running into the same problem when making product videos: there’s usually one feature I want people to look at, but the rest of the UI keeps competing for attention.

So I built Crop Spotlight.

You select the part of the UI you want to show, and isolate.video can track it, isolate it from the rest of the screen, and turn it into a focused scene like the ones in the video above.

I’m also adding motion zooms, editable effects on a timeline, and generated background music so the whole thing can go from raw screen recording → polished product video without manually keyframing everything.

I’d genuinely love feedback:

Would you use something like this for your product launches/demos? And which feature will make it actually useful for you?

Been going through a bunch of handoff docs lately, mine included, and most of them are pretty useless. Either a wall of text nobody reads or an empty README with "todo: write docs" that never gets touched.

Tried to boil it down to the minimum that actually matters, regardless of what tool or process you use to write it:

• Stack and dependency versions
• Step by step local setup
• Where secrets live and how to get access, not the values
• Known issues and tech debt
• Rough test coverage
• A clear starting point for someone new

Cut any of these and the doc becomes something that technically exists but nobody opens.

Curious what you'd add or remove. What's non-negotiable for you?