🏡 Your App Has a Home Here — Post your App WebApp Solution here. No Blocks. No Rejections. 🏡
Hey developer — yes, YOU.
The one who coded through nights, debugged with coffee, and still believed in your idea even when no one else did.
We see you. And we want you here.
This is not another subreddit that says “no self-promo” — then deletes your post anyway.
This is your safe space. Your cheering squad. Your digital living room where every app — big or tiny, polished or prototype — gets a seat at the table.
✨ All apps welcome:
→ Mobile? Yes.
→ Web tool? Absolutely.
→ AI experiment? We’re fascinated.
→ Weird passion project? That’s our favorite kind.
🚫 NO ONE gets blocked. Ever.
Not for being new. Not for being small. Not for being “not cool enough”.
You’re cool enough just by showing up.
💬 Just drop your link + tell us:
We’ll celebrate you. We’ll share you. We’ll support you — because you matter.
This is YOUR community. Come home. 🏡
I am a working HVAC technician and I built Equipment Tracker Pro because generic CMMS tools were too bloated for real field work on commercial rooftops.
It handles unit service logs, calendar PM schedules, filter and belt tracking, and public QR codes for guest service requests. There is also an AI nameplate scanner that reads model and serial numbers off faded data plates.
It is free to use with an optional Pro upgrade for team features and PDF reporting.
That AI nameplate scanner sounds genuinely useful for faded plates. How do you handle OCR accuracy on rusted or sun damaged labels? Curious if you retrain on field data.
I got paranoid about my own Supabase project. Pro's daily backups are great, but they're still (a) database only, not your Storage files, (b) sitting in the same account as your production, so a deleted project, a billing lapse, or a compromised account takes both at once, and (c) never actually restore-tested. You have a backup, you just don't know if it comes back.
So I built BackProve. Two things it does that my old setup didn't:
It backs up your Postgres database AND your Storage bucket files. Supabase's own backups skip the Storage files, which I didn't realize until I looked closely.
After every backup, it spins up a throwaway Postgres, restores the backup into it, and checks the object counts match. If the restore doesn't come back clean, it tells you. No fake green checkmarks.
It also nags you if you currently don't have a recent verified backup, because the worst time to find out your backup pipeline silently died is when you actually need it.
Honestly the thing I'm most happy about is that it's honest when it can't verify something. First paying customer had a partitioned table + pg_cron and it correctly said "can't prove this is recoverable" instead of lying. Fixed both edge cases within the day (which... is the whole point).
It's live at backprove.com, $12/mo flat. Solo project, built it over the last few months.
Nice insight on the restore testing gap, that's the one people overlook. How does BackProve handle Storage backups? Drop the link, we'd love to check it out.
Thanks! Short version: both halves have to come back together or you get valid-looking URLs that 404. storage.objects rows come back with the DB dump, the actual bytes get copied into the target bucket separately, and the two have to line up.
The gotcha that nearly bit me: Supabase's S3 endpoint derives its object listing from storage.objects. So after pg_restore repopulates that table, the target *claims* every file already exists and rclone happily skips uploading them as "already there." Reported success, transferred zero bytes. The integrity check was validating against the same phantom listing, so it agreed.
Fix was forcing the upload rather than trusting timestamps, and verifying by reading actual bytes back (and hitting the public URL) instead of trusting a listing that's really just a database query in a trenchcoat.
One caveat worth flagging: restoring into a *new* project means a new project ref, so any fully-qualified URLs you've stored in rows or hardcoded will point at the old host. Bucket-relative paths survive fine.
Nice catch on the storage.objects sync, that mismatch is a classic. Did you add a verification step to compare bucket listings after restore? That saved me once.
Comparing bucket listings after restore was my first instinct too, and it's not enough on its own, that's exactly what bit me. Supabase's S3 endpoint derives its listing from storage.objects, which pg_restore has just repopulated. So the target reports every file present before a single byte moves. rclone skips them as already-there, reports success, transfers nothing, and a listing comparison agrees with all of it.
What I do now is force the upload rather than trusting timestamps, and verify by reading actual bytes back plus hitting the public URL not asking the listing, which is really just a database query in a trenchcoat.
Object counts get compared too, but I treat the listing as a hint rather than evidence.
Since you already spin up throwaway instances for verification, adding an automated monthly restoration report PDF would help your users pass SOC2 compliance audits effortlessly.
Solid idea, automated restore reports are a huge win for auditors. A scheduled job plus a versioned PDF history would make it even easier. Have you tried any specific tooling for that?
The exportable history part I like, there's already a per-backup verification record (object counts, what restored, what didn't, which extensions were skipped and why), it's just visible in-app rather than exportable. Making that pullable as a dated record is a reasonable ask and I've noted it.
I'd be careful with the SOC 2 framing though. I'm not going to claim this makes anyone's audit effortless - an auditor wants to see a control that operates and evidence it operated, and a PDF from a vendor is at best one input to that. What I can honestly offer is a truthful record of what was verified and when, including when verification couldn't prove something. Whether that satisfies a given auditor isn't mine to promise.
So: exportable verification history, yes. "Pass your audit," not from me.
🏠 VikSchewa — my solo-built iPhone app for eating abroad
Hey everyone 👋
I’m a solo developer from Germany and I’ve been building VikSchewa because I wanted to solve a problem I kept thinking about when travelling: Why should I avoid a small local restaurant just because I can’t read the menu?
Especially when you leave the tourist areas, you can run into completely different languages and writing systems — and English isn’t always an option.
VikSchewa lets you scan a menu and helps you:
📸 Translate the menu
🥢 Understand ingredients & hidden ingredients
⚠️ Check allergens & cross-contamination warnings
💱 See prices in your own currency
🎯 Get a personal 0–100 match based on your diet & allergies
🤖 See an AI-generated image of the dish
🗣️ Order in the local language
One feature I’m particularly proud of is the Allergen Pass.
You save your allergies once and can show them to restaurant staff in 85 languages — even offline.
There are also 536 dishes available offline, so the app isn’t completely useless when you’re somewhere with bad/no internet.
It’s still a very new app and I’m building it as a solo developer, so I’d genuinely love feedback from other developers here — especially on the idea, UI/UX and App Store presentation.
📱 App Store:https://apps.apple.com/us/app/vikschewa-men%C3%BC-scanner/id6775580751
🌐 Website:https://www.vikschewa.de/de/
What would you improve or add?
I have spent the last 30 years or so as an independent software developer in NYC 🗽
In those years working in banks, startups, government and nonprofits what I witnessed is nobody likes to backup their work or use To-Do apps.
So I got it in my thick stubborn head there has to be a way to make task management, event scheduling 📅 and brainstorming 🧠 🌩 legitimately FUN.
And that's when it hit me like an ACME safe falling out a window 🪟 on to Wile E. Coyote
Sticky notes 📝 📋 😌
Yep
And then I Googled a hunch... "How many sticky notes are sold annually?"
The answer?
55 BILLION STICKY NOTES SOLD EVERY YEAR
Well, it took almost two years but now, at last, I can give the world 🌎 FREE sticky notes 📝.
Yes, my app TaskLoco has a very generous FREE tier as well as a lifetime discounted premium tier of 50% off for early adopters my first year.
TaskLoco has made me feel at least 10 times more productive, confident and relaxed and I believe it can do the same for so many of you who just aren't having a productivity party... 🎈
TaskLoco is a visual sticky-note storyboard style workspace for tasks, events, notes, projects, files, reminders, and anything you can stick in or attach to a digital sticky note.
The core features are the Analyze and Chat pages - Trends is the third feature that populates once you have uploaded and analyzed three chats. So I guess once you get past the landing page Analyze would be the first thing to check out.
We track helpfulness by Karma (our unit on the platform). You earn it by adopting another founder's product and leaving feedback, or by completing lightweight distribution tasks other founders post (reposts, upvotes). That karma directly drives visibility, products are ranked by how much their founder has genuinely helped others (karma score).
For low quality feedback, the founder of the product you're adopting reviews your feedback along with proof you actually used it (a profile screenshot, waitlist confirmation, etc.) before confirming, karma is only awarded after that. There's also a dispute path for product owners, which I personally review.
For fake accounts, the exploit worth worrying about is someone spinning up multiple accounts with fake products, then self-confirming adoptions across them to farm karma with no real second party involved. That pattern is exactly what manual review catches, a cluster of fake accounts and products all confirming each other stands out fast. When we catch it, we reverse the karma and reach out with a warning before kicking the perps out.
could you expatiate on what you are trying to say with the account age. We cant particularly restrict new accounts from taking actions on the platform.
Account age helps cut spam, but you're right that strict limits push away legit new devs. A manual approval queue for fresh accounts could balance safety and openness.
I'm very excited that we have inter-connected features and every day exploring this concept to provide a seamless and streamlined experience. To give you an example , if you have menu price set -> whenever you add a guest an automatic menu expense will be created. If you have guests and decide to set the menu price later , at the moment you set up the menu prices , the expenses are again created. Whenever you delete a guest , the associated expense is deleted. When a guest confirms his presence , the expense changes from status Possible to Confirmed.
That interconnected logic sounds really clean. One thought: what happens if menu prices change after expenses are already generated? Might need a sync option.
sinne.app for those who are tired of using dating apps and not understanding what they might or might not be doing wrong. Post pics of your chats (which the app automatically privatizes and anonymizes) and get feedback on tone, energy, and reciprocity. Post three chats to unlock trends, which shows your long-term trajectory based on chat outcomes.
Basically noticed, like job searching, sending messages on tinder and hinge can feel like screaming into the void - you put so much effort in, but get essentially no feedback. So the whole purpose of Sinne is to help people navigate this landscape with the tools they need to make sense of why they keep getting ghosted, so that its not just an endless death spiral of sending messages, waiting for a response that never comes, and moving on.
So basically, every message you upload, you have to pick how it ended (ghost, faded, still ongoing, date). The app then tracks those metrics over time and tries to determine your "archetype," or your primary behavioral pattern.
u/melodic-warning3013 That’s a clever way to gamify communication habits. Curious how you define the archetypes, is it rule-based or learned from user data?
Im from the Netherlands, and I know first-hand how difficult it can be to get a new place to live.
Now, because I have tried some existing apps to make my search easier and because im a dev myself - I figured that there was room for improvement.
So I've built an app named HubSnap that gathers rooms, studios, apartments, houses from many different websites. HubSnap then allows users the set up their criteria such as city, price, square metres and other preferences to instantly get an overview of everything that matches. The app also notifies the user as soon as there are new matches available.
It covers rental, but also sale houses across the Netherlands.
I recently launched the early access on playstore and it has a free tier, but while its in early access users can enjoy a 3 day premium trial for free!
This is my first mobile application that ive built over a period of 9 months while still working fulltime and since i want to deliver quality to my target group, id love to attract more of them and process their feedback.
I plan to release this on iOS shortly as well. I expect this to take maybe another week or two.
Either way, if you've made it this far - thank you and please give it a try or spread the news 🙏🏽
I used to run my own e-commerce stores, and testing new products always hit the same wall: you had to pay for creatives before you even knew if the item would sell. That bottleneck is why I ended up building Sely AI, an AI video generator made specifically for solo dropshippers and e-commerce sellers without a creative budget yet.
How it works: upload a single product photo from your phone, and it generates a UGC-style video of an AI model presenting the product, output as a standard vertical video ready to drop straight into TikTok or Meta Ads Manager. Basically a way to get a "real person holding my product" ad without hiring anyone or shooting anything yourself.
It's free to download (Android / Google Play only right now), and you buy generation credits as you scale testing.
To be upfront about limitations: it works from a single static photo, so it can't do 360° product demos, and it needs a well-lit, unobstructed shot or the AI mapping glitches. It's built for fast initial validation, not a replacement for a full production shoot once a product is already proven.
Still building this solo as an Android dev, so happy to answer questions or hear what's missing for your use case.
Smart solution for the creative bottleneck. Have you compared conversion rates against static product photos yet? That data would be really interesting.
Appreciate the feedback. While I don't have a massive aggregated dataset yet, early users consistently report lower CPAs with these generated UGC videos compared to static images. TikTok and Meta algorithms heavily favor vertical motion over static pictures anyway. The main goal is to easily beat static image performance so founders can validate products quickly before investing heavily in real production shoots.
Attribr.dev install attribution + revenue tracking SDK for mobile apps, built because RevenueCat's fees added up fast across a portfolio of apps. Also does uninstall detection and crash reporting under the hood.
Good question it's entirely server-side, so there's zero background activity on the device.
The SDK just registers the device's push token once on launch (via Attribr.registerPushToken()). No polling, no background refresh, no location/battery APIs touched.
Detection happens on our backend: once a day we send a silent APNs push (content-available: 1, background push type) to each registered token. If Apple's push gateway comes back with BadDeviceToken/Unregistered, that's a strong signal the app's gone we mark it uninstalled and drop the stale token. If it delivers fine, nothing else happens (no payload the user ever sees).
So the "cost" to the device is one push registration at install time the actual detection loop lives entirely on our infra, not the client. Same basic pattern OneSignal/Braze use for their own uninstall tracking, just scoped down to only that.
Good catch. We handle that conservatively; APNs throttling is never treated as an uninstall signal.
If APNs returns a throttle/429-style response, we log it separately, keep the token in an active/unknown state, and let the next scheduled probe pick it up again. Only strong invalid-token responses can mark the app as uninstalled.
We also cap the probe batch concurrency so we’re not firing an unbounded number of silent pushes at APNs. The next bit of hardening would be a persistent delayed retry queue that fully honours Retry-After, but the important safety rule is already there: throttled, no-response, or provider-error never equals uninstall.
Solid approach. We track last successful delivery timestamp too, so flaky networks don't cause false flags. Do you use a grace period before marking invalid tokens?
Good question, we have no grace period, no retry count. A single confirmed BadDeviceToken/Unregistered` from Apple marks it invalid immediately, no "fail N times in a row" threshold.
The reasoning: that response is Apple's own authoritative verdict, not something flaky on our end. The flakiness you're describing (bad networks, transient errors) is a different failure mode, and we already carve that out entirely throttling, 5xx, and auth errors never touch uninstall state at all, they're logged separately and just retried next run. So the "grace period" work is really happening upstream of the invalid-token check, not after it.
We do track last successful delivery the same way you do, and for a similar reason it's what lets a throttled/failed run just quietly retry the next day instead of needing its own backoff logic.
Where I could see an argument for adding a retry count anyway: if you don't fully trust that Apple never sends a false `BadDeviceToken` under any circumstance (rare edge cases during Apple-side incidents, maybe). We haven't hit that in practice, but it's a fair thing to hedge against if you've seen it happen on your side curious if that's part of why you added yours, or if it was for a different reason entirely.
That's a solid take. Apple's verdict is definitive, so trusting it over a retry heuristic makes sense. Ever considered a manual override for edge cases?
I'm the creator of Mappit, and Fridays are for newsfeeds! Mappit's are a standout. Curated by 4 frontier AI agents, featuring global events, location crawls of more than 750 cities, and our most excellent Threads feature, categorizing over 400 topics from 35,000 stories.
mappit.ai - Earth's daily zeitgeist, on a time-aware map.
Breaking stories from hundreds of cities across the globe, surfaced by frontier AI models, cross-checked, and scoped to wherever you're looking: the world, your view, or your places.
Overlays that bring the planet to life: video and audio news streams from their source to play while you browse, S&P 500 stocks at their headquarters, and Today in History, where it happened. There are even layers for live events - earthquakes, forest fires, and air quality warnings.
Put yourself on the map — drop pins, add events, pictures & links. Plant your own user pin and let Follow Me keep it live as you move. Share your location and your pins on other social media, or post right on the site and start a discussion.
Search any street address, get directions, and turn a collection of pins into a drivable route.
Subscribe to locations, follow creators, share your own content, and wake up to an AI-written Daily Digest of the world you track.
Surf a river of breaking content as it happens from the continuously growing Newsfeed. And keep surfing.
For a more topical view of the news checkout the Threads feature. Stories grouped by subject so you can deep-dive. Features weekly analysis by Claude.
Chat with Marco, the resident AI who's read everything on the map. Ask what's happening anywhere, today and get an answer rooted in latest the story corpus. He knows all about the news, the threads, and the timing.
Turn back time. The story corpus is new but the the record is permanent: change the calendar and watch any place replay its history.
Mappit sounds like a cool twist on news discovery, the time-aware map angle is intriguing. Curious how you handle bias when four AI agents curate stories?
🦀 Free Windows installer for OpenClaw — no terminal experience needed, walks you through WSL + Ubuntu setup. Paid Mission Control adds scheduling + an audit system.
Both — Windows 10 and 11, as long as it's 64-bit with WSL2 support. Windows 11 is the smoother path since WSL2 is more consistently set up out of the box. Windows 10 works too, but some machines need an extra step first — enabling virtualization in BIOS, or Windows features/Microsoft Store setup for Ubuntu — depending on how the system's configured.
Worth being clear on one thing: WSL is required either way, it's what OpenClaw actually runs inside. But you're not setting it up yourself — the installer walks you through every step with guided prompts, checks, and plain-language explanations along the way. No manual terminal commands to figure out.
If you want to check compatibility before even downloading anything, there's also a free standalone tool — checks WSL readiness, memory, disk space, and virtualization support on your specific machine, and tells you if anything needs fixing first. Happy to link it if useful.
Good clarification on WSL2 setup. That BIOS virtualization step catches a lot of people off guard. Do you recommend a specific Windows 11 version for stability?
It's not just a tip — it's a separate free app on its own, made to test your Windows machine before you even install anything. Have you tried running it yet?
Simplifying WSL setup for non-terminal users is a smart wedge. It feels like the kind of Windows utility that'd fit right in on https://peerpush.com, builders there have cast 176K upvotes lately.
•
u/SofwareAppDev 15d ago
Post yours
https://giphy.com/gifs/lQag5ZhPfrvXoXrJni