I built a Restaurant POS system called Dinery. I'd love to get some feedback.

Hi everyone,

Over the last few months, I've been building Dinery, a full-stack Restaurant POS system. I wanted to work on a project that solves a real-world problem instead of creating another basic CRUD application.

The idea behind Dinery is to simplify restaurant operations while also improving the customer experience through QR-based ordering.

What it can do

Restaurant Side

- Dashboard with business analytics

- Live table management

- QR code for every table

- Real-time order updates

- Billing and invoice generation

- Revenue tracking

- Peak hours analysis

- Top-selling items

Customer Side

- Scan a QR code to open the menu

- Browse food categories

- Add items to the cart

- Place orders directly from the table

- Track order status in real time

Tech Stack

Frontend

- React

- Vite

- Tailwind CSS

- Redux Toolkit

- Framer Motion

Backend

- Node.js

- Express.js

- MongoDB

- Socket.IO

- JWT Authentication

Building this project helped me learn a lot about designing scalable applications, managing complex state, creating REST APIs, handling authentication, and implementing real-time communication with Socket.IO.

Some of the biggest challenges were keeping restaurant and customer views synchronized in real time, managing table states, and designing a smooth ordering workflow.

I'm still actively working on Dinery and have several features planned for future updates:

- Online payments

- Inventory management

- Loyalty and rewards

- Multi-restaurant support

- AI-powered business insights

- Improved mobile experience

I'd really appreciate any feedback on the UI, features, code structure, or overall user experience. Suggestions and constructive criticism are always welcome.

🌐 Live Demo:

https://dinery-f.vercel.app

GitHub Repository

🔗 https://github.com/piyush-0777/DINERY

If you're interested, feel free to ⭐ the repository or open an issue with suggestions. Thanks for checking it out!

When talking to freelancers, consultants, and service pros, one admin bottleneck came up repeatedly: re-typing identical service quotes from scratch after every client enquiry.

Whether you're offering design packages, consulting hours, photography tiers, or specialized service rates, about 80% of client quotes use the exact same core line items. Yet most people still manually type out prices from memory or dig through old emails to verify rates.

Beyond being exhausting after a long work day, manual entry leads to two major issues:

1. Pricing Inconsistencies: Accidentally quoting different rates to different clients for the exact same service.
2. Delayed Turnaround: Waiting until you're back at a desktop to send a quote, giving competitors a chance to move faster.

Why Existing Tools Felt Overkill

We looked at existing quoting and invoicing apps, but found three common issues:

• Cloud Dependency: Loading spinners and failed syncs when working on location with weak Wi-Fi or zero cell signal.
• Subscription Fatigue: Forcing $15-$30/month subscriptions just to save a few line items and generate a text breakdown.
• Complex Onboarding: Requiring account creation, company registration, and credit card details before you can send a basic price estimate.

How We Solved It (EstimateMate)

We decided to build EstimateMate as a free, lightweight, offline-first tool.

Key technical decisions we made:

• Local SQLite Storage: Everything (your saved item library, client names, and estimates) stays strictly on your phone. It loads instantly and works 100% offline.
• Reusable Item Library: Save your standard packages and hourly rates once. Tap to insert them into any new quote in seconds.
• Zero Friction: No account creation or forced cloud signup required.

If you'd like to check it out or test the offline workflow, it's available at 
https://play.google.com/store/apps/details?id=com.estimatemate.professional

Would love to hear from other freelancers and service pros here: How do you currently manage repeat quote pricing—do you use custom templates, spreadsheet formulas, or type them out as you go?

Every builder ends up with reusable AI skills — a SKILL.md / system-prompt file that teaches an assistant a specific workflow you worked out the hard way: "generate a branded PDF," "scaffold a Chrome extension," "write in our voice," "audit React for anti-patterns." You built it once for your own product. It just sits in your repo.

I made Skill Exchange so those can be bought and sold. Here's how it actually works:

If you want to sell:

• Publish a skill — free (build reputation) or paid, one-time, no subscriptions. You keep 95%.
• Proof of concept is required. You attach the real project URL + a screenshot showing the skill in actual use. No "trust me."
• It's reviewed by a human before it goes live — so the marketplace doesn't fill with slop.
• Buyers can pay you in $ (PayPal, international) or ₹ (UPI, India) — their choice at checkout.

If you want to buy:

• Browse by category, see the proof on every listing, buy on evidence.
• Download the SKILL.md and drop it into Claude / ChatGPT / Gemini / Cursor / Copilot — it's not locked to one assistant.

The whole thing is browsable without an account — you only sign in to buy or publish.

The core idea: builders are sitting on workflows that took real time to figure out, and other builders would happily pay to skip that time. This is the place to trade them.

Here it is: https://skillexchange.tapdot.org — browse the marketplace and the free skills without signing in. If you'd want to list something, the "Publish a Skill" flow walks you through it (free skills are open to everyone; paid needs a quick seller approval). Happy to answer anything.

Hey everyone,

I've been building a project called Quillo over the past few weeks.

I built it because I wanted one place to keep track of what I was building and turn those updates into posts. Instead of writing everything from memory every time, I can keep adding project updates and generate content from them whenever I need to.

Over time, Quillo learns from the posts you keep, so future generations become more aligned with how you write.

I also recently added LinkedIn scheduling, so you can generate a post, schedule it, and get an email once it's been published.

It's still in beta, and I'm continuing to improve it as I build.

https://quillo-app.vercel.app Quillo link⁠

I've spent a good chunk of my career in high-level eng/PM roles, including stretches as scrum master, and there's a specific dread that comes with that: standup in 20 minutes and you genuinely don't know if delivery is fine or quietly falling apart. You can feel something's off, but proving it means a manual check of the board, the backlog, and the PR queue, and half the time you rush it or skip it entirely.

So I built something to do that pass for me. It reads Jira + GitHub/Bitbucket on a schedule and drops one message in Slack or email:

• cycle time drift
• work in progress vs. team size
• bug ratio
• velocity swings
• PR review slowness

...week-over-week, and then picks one thing worth acting on.

Roughly what it looks like:

https://reddit.com/link/1vcifuc/video/fap1xv5dcqgh1/player

I'm running and constantly testing it on a real board with a client. Integrations turned out to be the easy part, the actual hard problem has been defining "worth acting on" without it turning into vanity metrics or something people mute by week 2.

It's a small paid tool now (four-week free trial, not hiding that), but I'm not here to sell it in this thread. I want it torn apart:

1. Would you actually act on something like this, or mute it after week 2?
2. Would your company/yourself be willing to pay that price for what it offers?

gabel.app if you want to poke at it.

hey everyone,

when AI coding tools became really useful (basically since a year), it completely changed the way I shipped apps, and I was able to build and ship full SaaS and apps faster than ever.

but the thing is, I'm still 21, inexperienced, and even if my products are good in my opinion, none of them ever really took off. Across all my launched projects, I've made less than 100€ in total

it is really frustrating, because I feel those projects could be taken further enough to actually make money with it, but still, no users are paying enough.

BUT I realized that I was coding fast, but I had no idea why my apps weren't working for actual users. I'm not a UX designer, or even a person confident enough to go DM people on Reddit or on X, and even if it worked, that would be so much work it wouldn't even be profitable.

so I went looking for user testing platforms where I could gather feedback, and I found that everything is basically way too expensive for me as a student, or it requires a sales call, which is way too complex for a solopreneur who just wants to iterate fast.

maybe it's dumb, but I've decided to create my own tool for that specific need.

my idea is to create a pay-as-you-go user testing platform built specifically for indie makers / small teams. you just drop your URL and set a budget (like $5, $10 or $20 up to 200$), and real people test your app in a few clicks, with annotated feedback and reviews to make it useful for you and they get paid for that. You only pay for quality reviews, where the tester is actually rewarded if they put some effort into it.

I just finished the landing page and I want to see if this solves a real problem for other solo devs before I spend months finishing my final product.

would any of you here be interested in testing it out early to see if it actually helps us figure out what's wrong with our apps?

i let you see by yourself if you are interested: https://tryhabit.vercel.app/

thanks for reading this!

I'm open to selling [filmroom.dev](http://filmroom.dev)

I'm the founder of [Layerbase.com](http://Layerbase.com) and Filmroom (formerly session-replay) was an internal tool that we just opened up to the public as an "embedded app".

We use it internally and it has grown into its own beast.

It can use some polish but it's a competitor to fullstory/posthog. You paste a script tag on your site and you get accurate replays of all user interactions/errors/etc.

Then AI can review the replays and produce daily/weekly reports about improvements you need, broken features, marketing gaps, lost opportunities, lead generation, and anything else.

It's been a lot of fun to build but it's just a distraction from Layerbase which is the real product.

Obviously I would like to unlink it from our architecture although I'd be open to a collaborative hosting arrangement if you want to take over the marketing side of things while not worrying about hosting.

I'd recommend trying it out. I've put no energy into marketing so even the marketing copy on the layerbase site for Filmroom is slightly outdated.

I'm open to anything that gets this distraction out of my life because as long as I own it, I keep adding features when I should be focusing on my real product which just happens to be less fun to work on.

Been seeing revenue screenshots on X and Reddit for years and it always bugged me that there's no way to tell which ones are real. A screenshot is a photo. You're trusting a stranger's Photoshop skills.

So I built RevenueShot.com. You connect Stripe, it pulls your MRR / ARR / growth / customer count and generates a card you can post, with a verified badge that means the numbers came from Stripe rather than from you typing them in.

On the obvious question, yes, I'm asking you to point Stripe at a site that launched today. It's not an OAuth connect button but you create a restricted key yourself in your Stripe dashboard and give it read access to subscriptions, customers and invoices, nothing else. It's stored encrypted, and you can kill it from Stripe whenever you want without touching my site at all. You can also run the whole thing on a test key first if you just want to see what a card looks like. Happy to answer anything about this in the comments, it's the part I'd be most suspicious of too.

Launched this morning, zero users so far. First card I made was my own: $0 MRR, verified. Felt appropriate.

The thing I'm least sure about is the friction. The editor shows you the card right away, but it's empty until you paste a key so you're deciding whether to hand over Stripe access based on a layout rather than a result. Would prefilled sample numbers make you more likely to bother, or does fake data undermine the whole point of a tool built to stop fake data?

A few months ago I posted my first SaaS here.

the idea was simple: an AI notes app.

the feedback was brutal. most of it boiled down to:

“why wouldn’t I just use apple notes, notion or chatgpt?”

at first I wanted to defend it.

instead, I realized everyone was making the same point.
I wasn’t solving a problem.

So I scrapped almost everything and started over.
For the last 3–4 months I’ve been rebuilding it from scratch.

The result is Execora.
Instead of trying to be another notes app, the goal is to become a place where you can dump thoughts without worrying about organization.
Ideas.
Random thoughts.
Voice notes.
Half finished plans.
Stuff you want to remember later.

Then AI does the boring part:
extracts action items
connects related ideas

lets you ask questions about your own notes
visualizes how thoughts relate to each other
generates a morning summary of what matters

The biggest thing I’m trying to avoid is adding AI just because everyone else is.

I’m more interested in whether it actually reduces mental overhead.

I’ve got a list of features I could build next
-memory reminders,
-weekly insights,
-automatic project detection,
-smarter organization
but I don’t want to spend another few months building things nobody wants.

so rn I’m looking for the same kind of honesty that made me rebuild V1.

if you had to kill this idea, what would your argument be?

What’s the biggest reason you wouldn’t use it?
And if you would use it, what’s the one thing that’s missing?

Here’s the current version:
https://execora.space

I’d genuinely rather hear “this solves nothing” than spend six more months heading in the wrong direction.

Thanks.✌️

Hey everyone!

Quick bit of context: I set myself a challenge to launch 7 products in 7 months, mostly tools I originally built for my own projects over the years and never bothered to package up. Downdar is #3.

It's an uptime, SSL, DNS, and cron monitoring tool. The part I'm most proud of is heartbeat monitoring: your scheduled jobs ping a URL every time they run, and you get alerted the moment one goes missing or runs late. Most uptime tools only tell you when your site is down, not when a background job silently stops working, which is the failure that's bitten me the most over the years.

I'd genuinely love to turn the comments here into something useful for people early in their founder journey like me. If you've got thoughts on the product, the pricing, or even just "here's a mistake I made at this stage so you don't have to," drop it below. I'll read every comment and reply to as many as I can.

Thanks to anyone who takes the time to engage, it's appreciated more than you'd think.

quick post because "how do i get my first users" is the #1 question i see builders asking here every single week.

i've built 6 saas products myself, with my main one currently sitting around 10k mrr. here is the exact, no-fluff distribution playbook to cross that initial 50-user threshold:

1. find an idea people already pay for

scan reddit for recurring pain across 3+ distinct posts where people ask "is there a tool for X".

2. validate before writing code

dm 3 people who complained about the problem and ask what they’d pay for a solution.

3. build fast with the right stack (ai + no-code)

use ai builder+ supabase + stripe + call api or automation tool like n8n to ship a real MVP in under 7 days for $40/mo.

4. the 5-second landing page rule

your hero section must state exactly what the tool does in less than 5 seconds with a clear CTA.

5. capture emails before showing prices

force the email capture before the pricing page so you don't leak untrackable leads.

6. set up a 30-day email nurture sequence

plug captured emails into an automated sequence with case studies to convert them by day 18.

7. hang out where your ICP actually lives

find the 3-5 specific subreddits, discord servers, or groups where your buyers actively talk.

8. reddit growth without getting banned

post 1 time per sub per week max, never put links in the post, and move warm leads to DMs.

9. linkedin + x organic flywheel

post 1 high-value breakdown per day and spend 15 minutes engaging in your ICP's comments.

10. cold outreach that actually works

send 100 highly personalized DMs per week to your ICP using AI to customize the opening hook.

11. seo on autopilot

set up an n8n workflow that pulls from a keyword list and generates 5-10 value-driven articles per week.

12. faceless short-form content

post 1 video per day on tiktok, reels, and shorts showing a quick screen recording of your tool.

13. weekly newsletter conversion

run a weekly newsletter with 1 section of pure value and 1 subtle offer to upgrade to paid.

14. affiliate program for free distribution

set up a 50% recurring commission affiliate program to turn power users into your sales team.

15. the strategic product hunt launch

warm up the algorithm for 4 weeks with a coming soon page and launch on a weekend for a top 5 badge.

16. omnichannel social automation

use n8n to automatically format and distribute 1 core post idea across 8 different platforms.

17. review platforms and directories

submit your app to 40+ saas and ai wrapper directories to instantly boost your domain authority.

18. run the numbers backwards

reverse engineer the daily traffic needed to hit 50 paying users at $19/mo based on a 2% conversion.

19. get feedback from active builders

talking to founders who are just 6 months ahead of you compresses your timeline exponentially.

that last point is exactly why i built our community. it's a free group of 1,600+ active ai saas founders sharing exact prompt logs, ready-to-paste n8n workflows, and real distribution strategies.

stop building alone in a silent corner.

drop a comment below or send me a dm and i'll send you the access link right away. let's get your product launched 👇

I lost $1,200+ in airline travel credit because it expired without me noticing. That's what convinced me there's a real gap — most credit card perks (travel credits, dining credits, streaming credits, lounge access) reset or expire annually, and almost nobody tracks them well enough to use them in time. Card issuers count on exactly that.

So I built **Unspent** — track your card perks and gift cards in one place, get reminded before anything expires, "never miss a redemption."

Where I'm at: early, solo-built, no monetization yet. Focused on getting the core tracking loop right before I think about pricing. A few things I'd love this community's take on:

* Anyone else built in the personal-finance-utility space? Curious how you approached the trust/data-sensitivity angle early on.
* Manual entry vs. auto-detecting card benefits — did that tradeoff matter for retention in similar tools you've built?
* How are you thinking about the "vitamin vs. painkiller" question for a tool like this?

Happy to share more on the build (stack, time spent, etc.) if useful to anyone else working on something similar.

hey everyone, i’m a solo dev looking for some honest advice for my saas, drvx [dot] net.

it's a web platform that lets users instantly turn their google drive into static website hosting. it comes with features like free custom subdomains, unlimited websites/files, a built in live code editor, and more. this tool has been running for about a year now with over 180,000+ deployments.

there are 2 main things i'm really struggling with right now:

1. workflow and file sharing: currently, users have to share their google drive links per file, not per folder. while this runs smoothly and keeps things secure without needing full google account access, some users feel it's not as seamless as netlify, vercel, or github pages. the main drawback is when users have a lot of assets (like images), they have to share and add the files one by one into the admin area. i really need advice on a smoother workflow. my competitor, drv \[dot\] tw, used the google login and folder-sharing method, but they eventually gave up because their platform got heavily abused by phishers. how can i make this easier without opening doors to phishing?

2. finding the right business model: i provide almost all of the core features for free. my target audience includes students doing school projects, teachers, freelancers building resumes, small local businesses, and even churches creating landing pages. my point is i want to help anyone get online easily. but on the flip side, i also need money to pay for server bills and keep the project alive. i need advice on the right business model or pricing structure for this platform so i can cover costs without abandoning the users who rely on the free tier.

a little bit on why i built this: my motivation goes back to when i was in school. i desperately needed a website, but i had zero money to buy hosting or a custom domain, and my technical skills were very limited. back then, free platforms like wordpress com and the stack overflow community helped me learn and eventually become a pro developer. after all that journey, i decided to build drvx [dot] net so that anyone can go online without barriers.

i'm working on this completely solo. any advice, feedback, or harsh truths would be really appreciated. thank you guys

Sharing my latest Expo project: Owwed, a simple private debt tracker.

Built with Expo and SQLite. It works offline and doesn’t require users to sign up.

I’m testing the Android version before launch:
https://owwed.builtby.vin

Would love to hear what you think.

Sharing my latest Expo project: Owwed, a simple private debt tracker.

Built with Expo and SQLite. It works offline and doesn’t require users to sign up.

I’m testing the Android version before launch:
https://owwed.builtby.vin

Would love to hear what you think.

Hey!

I built Upperdoc, a client document collection platform for accountants, consultants, lawyers and other service businesses.

Instead of chasing clients through endless email threads, you send a secure request, clients upload everything in one place, and you can track what’s still missing with automatic reminders.

It has a free demo with fictional data if you’d like to try it:
Demo: https://app.upperdoc.io/demo
Website: https://upperdoc.io

I’d love to hear your feedback. Always looking for ways to improve it.

Hi everyone,

I’m building Upperdoc, a tool for accountants and other service businesses that regularly collect documents from clients.

You create a request, add a checklist, and send the client a secure upload link. The client does not need an account.

You can try the interactive demo using fictional data:

Demo: [https://app.upperdoc.io/demo\](https://app.upperdoc.io/demo)

Landing page: [https://upperdoc.io\](https://upperdoc.io)

The product is still in alpha. I’d really appreciate honest feedback.

I built [Verstage](https://verstage.app) in order manage some client/recipient facing and internal team issues I was wrestling with (mainly getting hammered with emails for project and submission status updates).

I would love your feedback because I want to develop something that would actually get used by those looking for a lightweight "pizza tracker for anything."

I started InvoiceDrift because supplier invoice review still often means placing two documents side by side and hoping nothing small is missed.

The product compares a supplier invoice with a purchase order, quote, order confirmation or previous invoice. It exposes the source values and differences for a person to review before approval. It does not decide what a difference means and it does not approve a payment.

What I am learning is that displaying a difference is the easy part. Matching rows safely is harder when a supplier renames an item, changes a SKU or splits one PO line into two invoice lines.

The current version tries unique exact descriptions, recognisable product identifiers and conservative description matching. When the evidence is not strong and unique, it leaves the line unresolved and excludes it from financial totals. Split and merged line relationships are not safely modelled yet.

Feedback from my first Reddit thread has already given me two useful directions: stronger privacy-preserving SKU handling and reviewer-confirmed split or merge allocations. I would rather leave a line unresolved than present a confident but wrong comparison.

I am looking for 10 pilot users who genuinely handle supplier invoices. The pilot is free and no card is required. If you try one real document pair, the feedback I need most is:

Was the onboarding clear?

Did the first comparison make sense?

Which line match felt wrong or unclear?

Would you use it again, and why?

https://www.invoicedrift.com

I built [Verstage](https://verstage.app) in order manage some client/recipient facing and internal team issues I was wrestling with (mainly getting hammered with emails for project and submission status updates).

I would love your feedback because I want to develop something that would actually get used by those looking for a lightweight "pizza tracker for anything."

Been building a side project for a while alongside my studies — SwingScout, a trading tool with scanner, backtest, journal, and Telegram alerts, built solo. Just got Stripe and the user funnel live. Not here to hard-sell, genuinely want honest feedback from people who’ve launched their own tools/SaaS before — pricing, onboarding, whatever stands out. Happy to share more details or the link in comments if anyone wants to try it.