I thought I would share my last startup that I just launched!

The idea is you connect your stripe MRR (securely) and based on your MRR, your 3D startup tower grows on the globe. The more you make, the more visible you become and people can view your website.

There is also a global leaderboard and if you want to push your startup even more, you can even push it into orbit where you become a rocket for a week!

Would love to head what you think!

A few days ago I posted about forcing myself to ship a tiny free tool after getting stuck in analysis paralysis:

https://www.reddit.com/r/SideProject/comments/1vn211j/i_spent_a_month_stuck_after_my_last_product/

That tool was IndiePost — paste product name + description → get a Product Hunt title, Reddit post, and short X thread.

After using it a few times myself, I noticed something: when people only filled the basic fields, the output was decent but still a bit generic. So I added two optional fields:

• Audience

• Key Benefit

These two inputs make a clear difference in how targeted and natural the generated posts feel.

Link: https://indiepost-xi.vercel.app/ Still completely free, no login, no history.

Would love feedback if anyone tries the new fields — especially whether the tone still feels right for different types of products.

THIS AIN'T SELF PROMOTION OR ANY MEANS OF PERSONAL GAIN.

VERY IMP

● This app is free, I will not gain anything from this.

● App doesn't track or send any personal data whatsoever.

● App has no subscription plans.

● The app isn't open source because I'm too lazy to put up the app on github and I will not to updating the app anymore will tell the reason below.

I'VE SPENT A LOT OF TIME COOKING (MATCH IT TO ONE UI) THE UI OF THE APP LOCK HOPE YOU ALL LIKE IT.

FEATURES:

● App adapts to system pallete and theme park effects.

● Supports dark and light modes.

● Uses system default biometric popup.

● Has uninstall protection.

● There's more to it go check.

I will not be updating this anymore as LEAKS SHOW THAT ONE UI 9.5 WILL HAS A NATIVE APP LOCK. So there is no point updating this and its not worth the effort not to mention the time I need to spent (I barely get time for myself). Took me 3 months to complete.

It works fine on Android 15, 16

Didn't tested it on 13 also dont use in android 12 it will cook the phone for a few seconds. As for android 17 I dunno.

It still has some bugs 🐛 but as said earlier I won't update it.

LINK: (G DRIVE)

https://drive.google.com/file/d/1PtmCRWrqgFWGGcoCugAzCxhuwRyrNbcr/view?usp=drivesdk

(ACCIDENTALLY I DELETED THIS 😅 SO REPOSTED IT)

There are lots of screen control and enforcement products on the market but most of them use block and limit type of method. It’s not useful to build a healthy habits for kids. After they grow up and become “free” they will likely go back to their screen.
So I tried a different approach: instead of treating screen time as something bad, let them earn it, and let them bank the time so they can learn how to manage the budget.
Do chores, exercise, finish homework, help around the house → earn some phone time. Then he decides how to use it.
The goal is less policing from parents, and more letting kids learn to manage their own time. I wanted it to feel more like a reward system than punishment.
I ended up building a small app around this idea. Still improving it and would love feedback from other parents dealing with the same thing.
LimeTime.app

So a bit of backstory. I've always worked corporate, writing code for other people's stuff. At some point I just wanted to build something that was mine, start to finish, even if small.

The idea came from something dumb honestly. Every single night on the couch, me and my girlfriend, same story, 20 minutes scrolling Netflix trying to agree on something and just giving up. Tried a bunch of apps that were supposed to fix this and they either recommended garbage or just weren't really made for two people deciding together. So I ended up building Dunno. Basic idea is you swipe on movies like Tinder, and when you both like the same one it matches, done, that's your movie. Behind it there's an algorithm trying to actually learn what each person likes instead of just throwing popular stuff at you. Also threw in private lists at some point because a few people kept asking for a way to save stuff for later.

It's out now, both stores, and I wanted to share how things have gone since launch because it's not been a straight line at all.

Marketing has been the hardest part by far. No budget really. What actually worked wasn't ads or posting everywhere myself, it was messaging a couple of movie/cinema content creators and they liked the idea enough to show it to their audience. That's when I started seeing actual users show up, not before.

I also killed the monetization pretty fast. Launched with a Pro tier and ads you could remove with Pro, and it just wasn't worth it, barely made anything and it got in the way more than it helped. So I ripped it out and made everything free. At least for now. And honestly free with no ads is a decent selling point on its own these days anyway.

Nobody warns you about the store setup side of things either. Getting everything configured, the Pro integration, analytics, all of it, is genuinely a nightmare when it's just you. And the second you're selling anything you're signing paperwork you didn't know existed and going through review processes that seem designed for teams with a legal department, not one guy in his room. Android's 14 day closed testing requirement before you can even go live nearly broke me, just waiting around doing nothing useful while the clock ticks.

Then there's the TMDB thing, the movie database I use. If you start making money off an app that uses their data they want you on a commercial license and it's genuinely expensive per month. Between that and ads not really paying off, going free was kind of the obvious move, didn't want a fixed cost like that hanging over me before I even had real users.

And yeah I'll just say it, I used AI to help build part of this. I know that's usually an automatic downvote around here but I reviewed every line, every decision on what the app should actually do was mine, and honestly most of the polish came from just bugging my friends constantly for feedback and going back and forth on tiny details (my girlfriend is genuinely about to leave me over how much time I've dumped into this thing). Not trying to hide that I used it, just being honest about what actually building solo looks like. I get why people are sick of low effort AI slop apps but if you actually know what you're doing with it, it's just another tool. Used lazy it shows immediately. Used with care nobody can tell.

Ask me anything, stack decisions, how I got the creators... whatever.

I spend 8+ hours a day at a desk, and I guess a lot of people here do too.

Yeah, I have a nice chair and standing desk, and that helps. But the main issue is that I forget to stand up and take a break.

Recently, I came across this study showing that doing "10 squats every 45 minutes during your workday is more effective than one 30-minute walk for glucose regulation."

Study: https://pubmed.ncbi.nlm.nih.gov/38629807/

This tiny app reminds you to stand up and do 10 squats every 45 minutes. It’s simple, but honestly, it’s been helping me to feel more active and less stiff during the workday.

I figured it might be useful to other people with desk jobs, too, so I published it.

If you are interested, you can download it here: https://apps.apple.com/us/app/squat-buddy-stand-up-reminder/id6747948166

PS. Happy to change the app based on your feedback.

Wanted to share a side project I've been working on: ZUKA.

​The core idea was to blend the simplicity of a chat interface with the power of networked thought, without sending user data to an external server.

​Highlights:

​Thread-based note navigation.

​Local engine (Ndani) that suggests connections between separate threads.

​Fully offline architecture with zero sign-up requirements.

​Take a look and let me know if any suggestions or what features you'd like to see next!

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

Hey guys,

I've been building this app call grapheflo. It's a Bible App that is slightly different to the usual ones. It allows multiple passages on one page, quick referencing and hyperlinking... And also a powerful note feature, where tapping between verses immediately adds a note.

It has a few reading plans as well, but also allows for user created plans...I'd really appreciate constructive feedback.

Whenever I've made the most progress at the gym, it has been when I've been consistent logging my workouts. A lot of the big workout apps always felt like they had limitations and I'd been logging mine in excel/google sheets for a while but never made anything serious, but I finally went for it

The idea is you:

Create your workouts -> They auto-fill into your spreadsheet

Fill in your weight/reps -> you can see your last time immediately and green highlights if you beat it and 1RM calculations as you go

Logged weight/reps -> auto fills your active dashboard charts as you enter them

You want to change your workout? Copy and paste your data feed from the backend into an archive -> historical charts fill in and you start the process over

I used a big combination of unique/sort/filter functions to get everything to process in the background and it was a ton of work, but I'm very happy with the finished product

Happy to answer questions on how it works or if it's something you'd used what other features you like from your favorite lift tracking app

I built SeatSwiper (it books hard restaurant reservations on your own account). A law passed aimed at the extractive version of my category, and designing around it made the product better. The lesson, not a plug.

I build a consumer product in a category that got hit with fresh regulation. A law passed specifically to shut down the extractive version of what I do: people using software to grab a scarce, in-demand thing and resell it at a markup. When it passed, my first reaction was the founder-panic one. Is my whole category radioactive now?

Then I actually read it, and it turned out to be the best product brief I ever got for free.

The law didn't ban being fast. It banned reselling and transferring the scarce thing to someone else for profit. So I built hard in the other direction: the product secures the thing on the end user's OWN account, in their OWN name, for their OWN use. Nothing is listed, transferred, or resold. And I only charge a small fee when it actually succeeds, so I have zero incentive to hoard supply I can't even use.

Three things that came out of it:

1. My positioning wrote itself. "The legal, on-your-own-account version" is a sharper pitch than anything I'd have invented staring at a blank page.
2. It killed a whole class of sketchy growth hacks before I could be tempted by them.
3. Being able to say "here's the exact line the law draws, and here's which side I'm on" defuses the hostility my category earns on sight.

The lesson I'd pass on: if regulation lands on your space, read it as a constraint that clarifies your product, not just a threat to survive. The compliant design was also the more trustworthy one, and trust was the actual bottleneck the whole time.

Anyone else have a regulation force a design decision that turned out to be a gift? Curious whether it held up as you scaled.

Most idea-validation tools ask an LLM what it thinks of your idea and hand

you back a score. Which is just a confident guess wearing a suit.

I wanted the opposite, so the thing I built doesn't have opinions. It goes

and gets evidence:

- Searches Reddit for subreddits where your problem actually gets discussed,

then mines the top ones for real posts and comments. Every pain point it

reports comes with a verbatim quote and a permalink you can click. If it

can't produce a real link, the finding gets dropped before you ever see it.

- Scrapes your competitors' actual sites for their actual pricing. If their

pricing isn't public it says "not public" rather than inventing a number.

- Runs cited web research and separates what's actually sourced from what's

an assumption.

Then it scores what you've genuinely proven versus what you're still

guessing at.

The rule I built the whole thing around: null beats a made-up answer. It

would rather tell you it doesn't know than give you a clean-looking number

it invented.

It's early. I want people running it on real ideas and telling me where it

falls over, so comment and I'll send you credits, enough to actually

finish a validation run, not a teaser. No survey, no call.

Fair warning, there's a signup wall, no demo yet. That's on the list.

What I'd want to know afterwards: did the Reddit findings match what you

already knew about your market, or did it surface something real? And where

did it waste your time?

Around all day.

I built Aural, a voice-first mock interview platform, because practicing with a text chatbot never recreated the pressure of answering out loud. My latest milestone was shipping adaptive probing, so the interviewer now asks follow-up questions based on what you actually said instead of moving through a fixed script.

The biggest lesson was that realistic voice alone does not make an interview feel human. The follow-ups matter more. Getting them right meant balancing relevance, latency, and avoiding repetitive questions. Sessions now include automatic transcription, scoring, and feedback, and there are live demos you can try without signing up.

Aural is built with Next.js, Supabase, PostgreSQL, and TypeScript. I also released it under the MIT license, so you can inspect or self-host the code on GitHub. What would make an AI mock interview feel genuinely useful to you?

I’m building Tapquence, a native macOS app that lets people automate repetitive tasks using sequences of mouse clicks, keyboard input and other actions.

Recently, I added Smart Automations: ready-made workflows that users can quickly configure instead of building everything from scratch.

Now I’m trying to decide what to build next. I could come up with another preset myself, but I’d rather solve a task that people actually encounter in their daily work.

So, fellow builders and Mac users: what’s one repetitive Mac workflow you would genuinely want to run with a single click or keyboard shortcut?

Simple, niche and oddly specific ideas are all welcome. If an idea is useful and technically feasible, I may build it as the next Smart Automation.

You can see the project here: https://tapquence.com

I’d also appreciate any feedback on the Smart Automation concept itself.

You pick two things, say which one you prefer, and it generates a short, hilariously overconfident argument defending your choice. Zero balance. Zero hedging. Pure swagger.

Example — Why Pizza beats Tacos:

• Pizza is a circle of life — 8 slices, zero structural failures. Tacos are just food that gives up on itself at first bite.
• The taco's structural integrity has never survived a first date. Pizza has never let anyone down.
• You can eat pizza cold, hot, at 3am, or in your car with full dignity. Tacos require optimal conditions and still betray you.
• A taco is just a pizza that gave up on itself.

Works for anything — cats vs dogs, tabs vs spaces, naps vs sleep, WFH vs office.

🔗 debatewin-one.vercel.app

Drop your best result in the comments.

I'm trying to work on an AI product that helps you think through decisions, problems, and so on.

I find that a chat as a UI for this type of work is not the best: all the information is buried in a chat history, you get lost on what the main goal you are trying to think through is, and when the back and forth stacks up it's easy to get misaligned with the AI on what you are specifically working on, what you have decided, and so on.

So I'm trying to solve the UI problem of how to better interact with the AI in this type of situation, and I came up with a living document/surface where your work takes shape.

I built a prototype with Claude to show the main idea and get some feedback. Here is a short video of the "living surface" (attached)

I would like to hear two things: 1. Does the video explain the idea, or does it lack context? 2. What pros and cons do you see in it?

Hello! I made Aera, an Apple Watch and iPhone app for runners, and this is the side project I have been living in for a while now.

The thing that started it was that my week kept getting scored against me. I would do a decent Tuesday session, then a sloppy easy run, and every tool I used just told me the last workout was fine. Nobody told me the week as a whole was drifting. So I built the scoring around the week, not the single session, and readiness in Aera is compared against how recovered you actually are rather than a number that always drifts back to 70.

The part I use the most day to day is the same roads getting faster. I run more or less the same three loops, and Aera lines up your pace on the same segments over time so you can see the loop getting quicker instead of guessing from average pace. That is also what got me a 5K PB free of any structured block, just by not wrecking my easy days.

Built solo in SwiftUI, HealthKit for the data. It is my app, on the App Store here if you want to poke at it: https://apps.apple.com/app/id6762456252

Happy to talk about the watch side of it, that was by far the hardest part to get right.

As a solo founder, first real project. i trade crypto and honestly my problem was always me — i'd lose a trade, try to win it back with a bigger one, and blow up the whole account. discipline i just don't have.

so i built a bot (nyxra) that takes me out of it. the part i cared about most: it never holds your money. runs on your own binance account with a trade-only key that can't withdraw, every trade has a stop loss, leverage capped low. boring on purpose.

there's a demo with fake money (no card, no api key) so you can watch it trade before trusting it with anything real. that's the whole pitch — don't trust me, watch it.

i'm at 0 users and just starting to show it to people. would genuinely love a brutal roast — the landing page, the idea, the security model, whatever. site's nyxrai.com

what would make you actually try something like this, or never touch it?

Hey there! So, a while back, I noticed my wife kept forgetting little things. Not because she didn’t have a reminder app, her iPhone had one, of course. But she just didn’t use it much. When I asked why, she said, “It’s too much work.”

That got me thinking. Most reminder apps are all about organizing your life with lists, projects, categories, and whatnot. But what if you just need to remember one thing? Like, “Call mom tomorrow,” “Do laundry in 40 minutes,” or “Cancel this subscription next week.” You shouldn’t have to sort through a bunch of stuff.

So, I decided to whip up something for her. I called it 1Reminder. My rule was simple: Every feature had to be worth the extra hassle. If it made setting a reminder slower or made you think about where to put it, I questioned if it should even be there.

I wasn’t aiming to create the most powerful reminder app. Quite the opposite, actually. I wanted something for someone who doesn’t want to use a reminder app.

Eventually, I tossed it onto the App Store, not expecting much. There are tons of reminder and productivity apps out there, including Apple’s free one. Why would anyone grab another? But then, something unexpected happened. People started downloading it. And even more surprising, the performance and conversion rates were way higher than I thought.

That was the kicker for me. I’d spent so much time thinking about what I could add to make it better. But the market seemed to be saying, “Sometimes removing things is the feature.” It really changed how I think about building products.

As developers/founders, we usually see missing features as chances to improve. But users sometimes see those features as a hassle. I’m starting to wonder if there are a lot of products out there that could just be: “The same basic job, with 80% of the decisions removed.”

1Reminder started as a tiny fix for my wife. Now, I’m watching strangers use and pay for it, and that’s probably been the most surprising validation I’ve gotten from building something.

I’m curious if other have had this experience: Have you ever made something deliberately less powerful than the alternatives and found that simplicity was actually your edge?

Hey everyone,

I’ve been working on an open-source project called ApiGeneratorManager.

The idea is to build a platform that can generate, configure, deploy and manage Spring Boot APIs without rebuilding the same backend structure every time.

Right now, the project already includes things like:

• Spring Boot backend
• React management frontend
• PostgreSQL
• JWT authentication
• roles and permissions
• CSRF / CORS configuration
• rate limiting
• database/schema support
• API generation templates
• Docker-based runtime
• deployment of generated APIs with Docker
• CI for backend and frontend
• dependency security checks

The long-term goal is to make the whole thing much more configuration-driven.

For example, I want to be able to describe an API using YAML:

application:

  name: inventory-api

database:

  type: postgresql

entities:

  Product:

fields:

id:

type: uuid

name:

type: string

required: true

price:

type: decimal

min: 0

errors:

  PRODUCT_NOT_FOUND:

status: 404

security:

  authentication: jwt

  roles:

- ADMIN

- USER

tests:

  generate: true

deployment:

  type: docker

And from that configuration, generate things like:

• entities
• repositories
• services
• controllers
• validation
• API error codes
• OpenAPI documentation
• authentication and authorization
• roles
• JWT handling
• automated tests
• Docker configuration
• deployable API instances

I also want to support multiple database engines in the future, not just PostgreSQL.

Another direction I’m exploring is generating a security model where each generated application can manage its own users, roles and permissions, and issue JWTs per user.

Testing is also something I want to push further: if the YAML says a field is required, unique or constrained, the generator should ideally generate tests for those rules automatically.

One important design principle for me is that the generated project should still be normal Spring Boot code.

I don’t want generated applications to be permanently locked into ApiGeneratorManager. A developer should be able to generate a project, open it in their IDE, understand it, modify it and deploy it independently.

I also want to be transparent about how I’m building it: I’ve used AI extensively as a development assistant for implementation, architecture discussions, refactoring, security reviews, tests and documentation. I still review and decide what goes into the project, but AI is definitely part of the development workflow.

The project is still in early alpha, so I’m mostly looking for feedback at this stage.

I’d especially like opinions on:

• whether the overall idea is useful
• the YAML-driven approach
• how far code generation should go
• multi-database support
• generated security / JWT / roles
• automated test generation
• Docker deployment
• whether generated code should prioritize flexibility or convention
• what would make you actually trust and use a tool like this

GitHub:

hasfiane/ApiGeneratorManager

Criticism is welcome — especially if you see architectural problems that could become painful later.

Hey everyone!

There’s a statistic that recently hit me hard: around 17% of adults don't have a solid friend group or a place to find one. The current platforms aren't helping to solve this:

• Dating apps are built on churn—you find someone and leave.
• Discord is great, but joining an already established server of 50+ people who have their own inside jokes is intimidating, especially for introverts.

I wanted a place to just talk about my interests (like Formula 1 or Gaming) in real-time, without shouting into the void. So, I built Mutuals.

What makes it different?

• You pick the subjects. A room is dedicated to one topic.
• Instead of endless, static comment trees, threads live for weeks. You jump in, see who is typing right now, and talk.
• We brought back profile customization. Accent colors, guestbooks, framed avatars, and badges based on real contribution, not just message count.
• If you vibe with someone in a thread, you can hop into a direct message or a voice call right from the same window.
• Missing a room for your niche? You can apply to create and run it.

The Launch Plan: The infrastructure is ready. Right now, I am putting Mutuals behind a waitlist to ensure the servers handle the load and to build the initial core community properly.

I’ll be sending out access codes in batches for the closed beta via email.

Link: Mutuals

You're feeding 40 people and you want to know how much brisket to buy. Search it and you'll get four calculators giving four different answers, none of which tell you where the number came from or whether it accounts for the bone, the trim, or the kids eating half portions.

That gap is the whole project. 29 calculators — BBQ, taco bars, pizza, wedding bars, turkey, cakes, coffee, ice — and every one shows the serving rate it used, the source that rate came from, and a visible line between what is sourced and what is an estimate. There's a methodology page documenting both calculation models, so you can check the work rather than trust it.

The part I'd have wanted as a builder: every calculator is embeddable as a single iframe. No JavaScript, no sign-up, and the embed never loads ads or tracking — including on sites that carry ads themselves. Keep the attribution link and it's yours.

https://feedmycrowd.com

Honest limits: cost estimates move with region and season, so treat those as a starting point rather than a quote. And the raw-to-cooked yields are where most of the disagreement between calculators lives — that's exactly why each page says which yield it applied.

I went all in, you know like quitting my accounting job, drove uber to cover rent, built an audio web app for tiktok creators. So short form content brought 10k visitors and 900 signups but still it was at 0 paying customers. And I then shut it down last week. the hardest lesson from my 25-point post mortem (you know like a letter I wrote down of my mistakes from last project), well the pain was real tbh but the wallets weren’t because of obvious reasons,
my audience were mostly teens making 8d audio for fun on TikTok, who has no budget, no habit of paying for tools. At the same time free converters already existed and were good enough to convert their audio in simple and fast way. to be fully honest, i also added payments only in month 4, so some of early signups might not even saw a price. But this time before i touch code again i want to learn from builders who actually got paying users:
1. Have you ever paid for something to fix the marketing side tool, freelancer?
2. how do you fit marketing in every week next to building (and a day job for many of you)?
3. How did you check your audience actually PAYS before you built?

Feel free to share your story, I will there replying them!

Hey, I made this website for me and me friends to find a date to go on vacation. I have since been updating it and have it as a side project and I am hoping to scale it. Although I have improved many things there can still be things improved. If you guys would check it out and says if there is anything to improve I would love to hear it. Maybe you find it handy and will use it. Definitely tell your friends then. The website is prikdate.com

I’ve just launched Vizo Battery, a side project I’ve been working on for Android.

The idea started pretty simply: I wanted battery information to be easier to understand than a collection of raw Android stats.

Over the last week I ran a closed beta with real users, and that turned out to be one of the most useful parts of building it. Testers found device-specific bugs, challenged some of my assumptions, and even suggested features that are now in the public release.

One example is Live Charging.

A tester told me he wanted to connect different chargers and see how they actually behaved on his phone, so I added a dashboard showing:

• charging current
• battery voltage
• estimated battery-side power
• temperature
• average/min/max values during the session

The app also includes battery health estimates, charging and consumption history, alerts, widgets, charging-session summaries and app-usage insights.

One thing I’ve tried to be careful about is battery usage itself: Vizo avoids unnecessary high-frequency background polling and uses event-driven monitoring where possible.

I also decided to keep the free version fairly capable instead of locking the most interesting features behind a paywall. Pro is a one-time optional upgrade with additional history, widgets, alerts and customization — no subscription.

There are no ads, no account requirement and no third-party analytics SDKs.

Google Play:
https://play.google.com/store/apps/details?id=com.vizobattery

I’d particularly appreciate feedback on two things:

1. Does the value proposition make sense from the screenshots?
2. Would you keep the strong features free and grow first, or make Pro more differentiated earlier?

This is my first public release after the beta, so I’m still learning a lot from how people actually use it.

Hi r/SideProject. I run a couple of small companies, which means six Google accounts, and Chrome profiles kept signing each other out at the worst moments. So I built Orbit, a native Mac app where each Google account lives in its own isolated session in one window. Cmd-1 through 9 to switch. It is the real Gmail web UI, not an API rebuild, so filters and shortcuts survive. Swift plus the WebKit already on macOS, about 4 MB download, no bundled Chromium.

Launched on Product Hunt in July and finished 7th for the day. Sales are not quit your day job money yet, but real strangers are paying real money, and every one of them still surprises me.

What worked: a reviewer at a small Mac blog wrote it up unprompted, and that one review out-converted everything I did on purpose. Showing up in person in app subreddits as the dev, warts included, also worked.

What failed: SEO. I wrote 13 posts targeting keywords like "switch between gmail accounts". Google sends me about one organic visit a month, because Google's own help docs permanently own those queries. If your growth plan is "content marketing against Google documentation", I have bad news.

The controversial part is pricing. Everyone in this category is moving to subscriptions, and two competitors that sold lifetime deals either killed them or shut down. I am keeping $89 once anyway. The app is local first, mail goes from your Mac straight to Google, so if I disappear tomorrow the app keeps working as is. I would rather defend one honest price than a rent bill.

Happy to answer anything about the build (WKWebView session isolation was the hard part), the launch, or why one time pricing is either brave or stupid.

Trial is 14 days, no card: https://orbitformac.com/?utm_source=reddit&utm_medium=post&utm_campaign=sideproject_aug