I built tryproduck.com/audit, it walks your app like someone opening it for the first time and sends back every bug and confusing bit it hits. Over 650 startups have run it so far.
Solo dev here. I kept owning things and forgetting where I put them, so I built Store & Forget.
The whole point is zero effort to catalog: you don't type or tag anything. Snap a photo and it auto-fills what the item is (the photo scan uses a cloud AI service). Later you find it by searching names, descriptions, or which box or room it's in, or tap "Smart Find" to search by meaning.
Local-first: everything sits in an on-device database, no account, no sign-up. Optional backup to your own Google Drive.
It's free, Android only. Would love feedback from other builders.
https://play.google.com/store/apps/details?id=dev.koalalab.storeandforget
Introducing the business, since that's what the tag is for.
What it is: FlexScan (https://flexscan.app). A web app. You upload one to three photos, front, side, back. It grades each muscle group A+ to D, shows you a muscle map of where you're strong and weak, then builds a 7-day training plan and a meal plan around the weakest groups. There's a chat coach that can see your own grades and your training log.
Where it operates: not regional. It runs in a browser, so anywhere with a phone and a connection. Nothing to install and no app store listing, though you can add it to your home screen and it behaves like an installed app.
What it costs: the first scan is free and doesn't ask for a card. You do have to confirm an email address. After that it's $9.99 a month or $79.99 a year for repeat scans, then-vs-now progress and the coach. Cancel anytime.
Who runs it: one person, me. I don't write code. It was built using AI coding agents while I did the specifying, the testing and the rejecting. I have no background in the fitness industry, which is the first thing anyone should hold against it.
The numbers, four days in, pulled out of the database this morning rather than from memory:
The number I got wrong. A few days ago I posted my launch numbers and said three of my signups were one person farming free scans with throwaway email addresses. It made a good story. My first real "user" was an abuser. Then I actually queried the table instead of trusting my recollection: those three accounts had run zero scans between them and one had never even confirmed its email. They were mine. I made them on launch night testing the signup flow and forgot. There was no farmer.
If you're going to post honest numbers about your own business, query them first. The interesting-sounding version of your own data is the one you'll remember.
Three things that broke since launch. All mine, all fixed:
The rate limit I added to stop the free-scan farming that, per the above, was not happening, ran before the code that works out who is signed in. So it counted requests per IP address for everybody, and anyone sharing wifi or a phone carrier with an abuser was locked out of scanning for 24 hours. That included paying accounts. It was live about eight hours. My tests all passed, because they only ever checked that going over the limit returns an error, never who was being stopped.
Double clicking the checkout button created two charges. The guard meant to swallow the second one was comparing a function against a rebound copy of itself, so it never recognised the duplicate.
A cache size limit in the service worker evicted the app's own core files, so the installed version cold-started to an offline screen on a perfectly good connection.
One design decision I'll defend. The grader has to answer "not visible" when it can't see a muscle group, instead of guessing a score. Those groups are excluded from the weak-point ranking so they can never become your training priority by accident, and you can self-grade them yourself if you want them counted. And if a response comes back with nothing gradeable in it, the free scan goes back on the account rather than being spent on a blank answer. That costs me the API call. It's worth it, because the whole product is "train this, it's your weak point", and an invented weak point sends someone to the gym to fix a problem they might not have.
For the avoidance of doubt: it's a coaching opinion, not medical advice, and the results page says so. Photos are processed in memory and never stored.
What I'm bad at is distribution. Building it was the easy half. If you run a small independent business and you've found something that actually produced your first handful of paying customers without an ad budget, I'd rather hear that than compliments about the product.
Happy to answer anything about the build, the running costs or the numbers.
I built Sitemapper after getting tired of checking a sitemap, then checking pages, then checking robots, then trying to remember what changed after the last deploy.
It does that in one pass. Give it a public site and it reads robots.txt, discovers XML sitemaps, checks live pages, and keeps a snapshot so later runs can tell you what actually changed.
The part I care about most is not an SEO score. It is catching boring regressions like a page turning noindex, a canonical moving, a URL disappearing, or the sitemap suddenly shrinking.
Free first scan, no account: https://sitemapper.oortstack.com/
If you try it on something weird or messy, I would like to know where it falls over.
Doing this again because the last post did so well. I built an agent that runs a quick SEO visibility audit for SaaS websites.
Drop your site and I’ll reply/send over a link to the audit.
It looks at things like:
This is part of Tavyn: an email-native SEO agent for SaaS founders. It finds organic visibility gaps, asks tailored questions for each blog via email to have your voice in the blog, and submits blogs to your GitHub as PRs.
Drop your SaaS link and I’ll run the audit.
been running a small consulting side gig for about 18 months. first year i used basic flat business cards from a big box print shop, like 250 for 25 bucks. they did the job but honestly the card would hit someones hand and go straight into a pocket or a bin. nothing made them want to hold onto it.
as a solopreneur you only get one shot with most people you meet. if the card doesnt do something, if it doesnt make them actually look at it for a second, its dead on arrival. so last quarter i upgraded to metallic foil printed cards. paid like 40 bucks for 250 with foil on the logo.
tracked it informally, from the foil batch 4 of 50 people i handed them to actually emailed me within a month. from the old basic batch the ratio was like 1 in 50.
not saying foil is magic. but the card becomes a conversation starter and people dont throw it away. for anyone running solo where every connection counts, the extra 15 bucks per batch is nothing.
ill update when i finish the next batch.
I’ve had this pattern more than once, and I’m trying to be more honest about it now. Building is comfortable for me. I studied engineering, I like product problems, and it is very easy to convince myself that one more feature, one cleaner onboarding flow, or one better landing page is still progress.
The first SaaS I built failed mostly because of that. I was spending my energy making the product feel better while the real problem was that not enough people knew it existed or cared enough to switch. It sounds obvious when I write it, but in the moment product work feels productive and sales work feels messy.
For indie founders who are more builder than salesperson, how do you force the balance back toward distribution without turning every week into guilt and fake discipline? Do you set hard rules, like no product work before outreach, or is there a better way to structure it?
I’ve been building Makemetryon, a SaaS that helps ecommerce stores add interactive product experiences without building the whole system themselves.
It includes:
Still early, but the platform is live and I’m looking for honest feedback from other builders.
Hi everyone,
Over the past few months, I've been building an Android app called Petals because I wanted a notes app that truly respects privacy.
Most note-taking apps today encourage cloud sync, accounts, subscriptions, or AI features. I wanted something much simpler:
The goal wasn't to compete with feature-heavy apps like Google Keep or Obsidian. Instead, I wanted a lightweight personal journal and notes app that opens instantly and keeps your data private.
Some features I'm planning next:
I'd genuinely appreciate feedback from Android users:
If you'd like to try it, here's the Play Store link:
https://play.google.com/store/apps/details?id=petals.careernotes.com
Thanks for taking the time to read this. Any criticism or suggestions are welcome—I'm actively improving the app.
I started my apparel project with the usual mindset: more designs meant more chances to make a sale.
So I kept adding ideas.
After a while, I had too many products to properly test. Some had different fits, some used different garment qualities, and the branding wasn't always consistent. The store looked busy, but I wasn't actually learning much about what customers wanted.
I decided to slow down and focus on a smaller group of products. Instead of immediately adding another design, I started ordering samples, checking the actual garments, testing different branding details, and paying attention to how everything felt together.
That changed the process quite a bit. I could spot quality issues earlier, make better decisions about customization, and avoid committing to large quantities before knowing whether something actually worked.
The biggest lesson for me has been that building a small product business isn't necessarily about having the biggest catalog. Sometimes it's about finding a few products you can make really consistently and confidently.
I'm curious how other indie founders approach this. Did you grow faster by expanding your product range, or by getting a smaller number of products really dialed in first?
So I built this directory for people to showcase their products. I wanna make it different for builders in a way that their product stays in public for a longer period of time rather than just a launch day. I've always come across this situation where waiting for months for the launch day still gets you ghosted. This is an approach to go beyond that and always have the products in front of the right people.
Also, builders who're truely in for making their product stand out, i've made a builder tier for them that really helps them stand out from the regular products. Pricing honestly feels like a deal.
I've also implemented analytics for people to see how they're doing on the platform.
For normal users to navigate through the platform, I've implemented semantic search. just give it a proper description on the search bar and look at it come up with the best products.
Currently with just a few products covering every category. I'm on a quest to grow this platform more and more.
I'd love for your to be genuinely unhinged on the UI/UX, Navigation, Pricing, Features, Everything.
lessgooooooo.
I’ve been in a bit of a slump lately and I’m trying to figure out what direction to take.
I love building startups and digital products. Taking an idea from nothing to something real is probably the part I enjoy the most - figuring out the product, UX, tech, positioning, and actually shipping it.
Right now, I’m building a startup for hotels and short-term rental operators around digital content. I think there’s something there, and I’ve built a product I’m proud of.
But I keep running into the same realization:
I don’t think I enjoy sales. And more importantly, I’m not sure I have the motivation to become great at sales.
I can spend 10 hours obsessing over a product problem and genuinely enjoy it. But the thought of spending those same 10 hours cold emailing, doing outreach, following up with leads, booking calls, and trying to close customers drains me.
That’s making me question what I should actually be doing as an entrepreneur (If i can call myself that?). Maybe I’m not someone who should build a traditional startup and try to scale it into a large company.
Maybe I should build smaller products that can grow through self-service, SEO, content, distribution, etc.
Maybe I should find a co-founder who genuinely loves sales and distribution.
Maybe I should build products, get some initial traction, and sell them to other entrepreneurs.
Or maybe avoiding sales is exactly the problem I need to force myself to solve.
I honestly don’t know.
For those of you who are much better at building than selling: What path did you take. Appreciate any advice.
Hello everyone,
I am nearly finished with a project of mine, it helps run due-diligence on online businesses with a focus on revenue durability, website and repository health. I have my own ideas and research on what a buyer NEEDS to know, but please share what issues or data is most important for evaluating any business on the internet. Thank you all!
I build landing pages. Right now I'm building three of them for free, and after that they're $150.
That's the whole offer. Details below if you want them.
Not mockups, not tutorials. These are live and in production:
silkline.co.in — a door-to-door imports platform I built for a client. Freight, customs, GST and last-mile delivery consolidated onto a single invoice. React, Tailwind and Supabase, with a working waitlist and an admin dashboard behind it.
papervault.in — a document vault for Indian paperwork. This one's mine. ₹99/mo, real paying users, and I handle everything from the schema to the support emails.
Everything else is at kynokeys.com.
I want better portfolio pieces than my own projects, and I want to get sharper at the conversion side of things. Three slots, no cost, no catch.
What you get
What I ask for
That second part is the real payment. I'm confident about the building. I'm still learning what converts, and I'd rather learn that on something real than on an invented project.
What I need from you is rough: what it does, who it's for, and any logo or images you already have. Don't have them? That's normal at this stage. I'll work with what exists.
Pre-launch and early-stage founders get priority, because that's where a good page changes the most.
Flat rate, not hourly. You know the number before I start and I'm not billing you for my thinking time.
$150 covers: a responsive single-page site built to spec, deployed live on your domain, two rounds of revisions, and the source handed over so you're never locked to me. React and Tailwind by default, or plain HTML and CSS if you'd rather keep it simple to maintain yourself.
Timeline: five working days from the point I have your content.
Multi-page sites, backends, or anything involving auth or payments gets quoted separately. I'll scope it honestly before you commit to anything.
Free advice, take it or leave it:
If any of this is useful to you, comment or send me a message. If I'm not the right person for what you need, I'll tell you that instead of taking the work.
kynokeys.com
reputation management gets sold like a marketing tactic, but a lot of it is operations in public.
if reviews keep saying late technician, unclear pricing, slow replies, rude front desk, missing refund, the growth problem is not review volume. it is the repeated experience.
same idea exists with apps as something like appfollow or other similar ones seem to be able to surface repeated app-review themes as far as I've tried..
but the useful part is to ask yourself, who owns this pattern and by when?
couple examples to clarify: replying matters. collecting reviews matters? but perhaps neither fixes a repeated complaint theme by itself and public reputation improves fastest when the business stops creating the same review
For most of my life I tried to be someone else. I'd find someone I admired, decide they were better than me, and copy them. That mindset pushed me into a business I never enjoyed and only started because I looked up to one specific guy. It failed. I felt completely lost.
Around that time I was obsessively tracking my sleep with a Whoop, trying to optimize it. I kept getting good recovery scores. And I was still exhausted, yawning through entire afternoons, dead by 2pm. That's when it clicked: the score doesn't do anything. It just confirms you slept well or badly. Cool. Now what? Knowing isn't fixing.
So I built the thing I actually wanted. It takes the data your wearable already collects sleep, recovery, heart rate, and turns it into a daily protocol instead of another number. It tells you what supplements to take based on your metrics, predicts your most productive hours and gives you the exact time window when you should do deep focus tasks and light focus tasks, it tells you how much caffeine you have in your system left based on your first coffee taken and notifies you when you should take the next caffeinated drink for maximum productivity, it even tells you when to nap so your energy lasts the whole day instead of crashing and much more...
It's on the App Store as RizeAI https://apps.apple.com/us/app/rizeai-maximize-your-energy/id6762402079. i built by myself, it's early stage right now, and I want honest feedback, what's confusing, what's missing, what you'd never use. Tear it apart.
Maker here, full disclosure.
Paxio is a parental control app for Android — daily screen time limits, real-time app blocking, on-device DNS content filtering (not routed through a third-party server), and bedtime scheduling. Free tier covers all four controls for one child, no paywall on the core features.
What I'm looking for: people willing to actually install it on a real device and try to break it — permission flow, device-role setup (same phone shared with a kid vs. a separate dedicated device), the actual enforcement behavior. Bug reports and "this is confusing" feedback are what I actually need, not praise.
A bit on how it works under the hood, if that's useful context for testing: content filtering is VPN-based DNS filtering (so it can flag/block categories without routing traffic through an external server), app blocking uses Accessibility Service to catch a blocked app in real time, and there's a PIN-gated settings layer so a kid can't just flip things back off.
As a thank-you, early testers during this period get 3 months of the full paid feature set free once that tier ships — not live yet, but it's a real commitment, not a vague "maybe someday."
https://play.google.com/store/apps/details?id=com.paxio
Happy to answer anything about the implementation or take feature requests — this is early enough that real input still shapes what gets built next. Bug reports/feedback also welcome directly at support@paxio.in if you'd rather not post it here.
I'm building QAL, an early-stage blockchain infrastructure project focused on commitment integrity rather than token issuance.
What I'm building: an exact private artifact can be sealed locally; QAL anchors its fingerprint/commitment record to Solana. The original artifact can remain private/off-chain. Later the commitment can be independently verified and its lifecycle can show active, revoked, superseded, or disputed.
Who it's for: initially developers and teams that make claims/disclosures/promises where a mutable webpage, screenshot, or PDF isn't a strong enough historical record. One concrete vertical I'm testing is crypto/memecoin teams making wallet, mint, treasury, LP, or incident commitments.
Stage: pre-alpha / protocol hardening. I have an interactive educational demo and verifier, but I'm not presenting it as audited production infrastructure yet.
Demo: https://bestmemecoins.app/
What I want feedback on: does the commitment-history layer add enough beyond 'publish a hash somewhere,' and which use case has enough pain to justify integrating it?
I built an app named Gravitas out of pure personal frustration. I was the kid who hated any kind of social situation, dates were a nightmare, meeting new people felt like a test I was going to fail. Gravitas is my attempt at building an app I wish someone else had handed to me
It's split into 4 tracks. Dating, Work, Social, Mind. You do a short assessment first that scores you and it points you at what to work on based on that. Each track has 10 modules including AI-conversation practice scenarios with instant feedback.
One week free trial then it's a subscription.
App Store link: https://apps.apple.com/us/app/gravitas-charisma-aura-app/id6767658034
Website: https://gravitas.social/
Tear it apart. Be as brutal as you want
Hey everyone!
I wanted to share my developer journey over the last month and get some real feedback on whether I should keep pushing this project or pivot to something new.
### đź’ˇ The Story & Why I Built It
A local contractor I know was complaining about how every invoicing app on the store forces you to create cloud accounts, pay $10–$15/month subscriptions, and upload sensitive client/financial data just to issue a basic bill.
He just wanted something fast, private, and offline to generate a clean PDF on his phone in 30 seconds. So, I spent the entire last month coding a strictly local-first billing tool for Android.
### 🛑 Where I Am Now
I finished the app and published it. It handles local PDF generation, custom company logos, digital signatures, multi-currency formatting, automatic tax calculations, and dark/light modes—all working 100% offline with zero account setup needed.
Building the app was the fun part. But as a solo dev, getting initial traction in a store dominated by huge cloud platforms is a massive uphill climb.
### âť“ My Question to the Community:
I'm at a crossroads. Do you think a privacy-first, zero-subscription utility app is a project worth scaling long-term, or do most users only care about cloud sync? Should I keep updating this, or unpublish it and take what I learned to a new niche?
I'd love your honest thoughts and advice!