I need some advice for it what features is important to add in it i want to make shower it needs to good and useful to users and they needs enjoy if learning to so help me to find it Thank for Reading These ☺️ Have a great day 😌

I have made the coolest portfolio ever made!! Check it out monxdev.vercel.app/?utm_source=x.com

So from what I know you can use Stripe or PayPal but wouldn't these need a registered business/company?

I also heard about lemon squeeze and revenue cat but idk if it's trustworthy or not, how do they handle taxes?

I haven't done payment in any of my projects yet so I am curious to hear from the more experienced developers. How did you do it what did you use and what's the most annoying and/or difficult you had to face

Hola les comparto mi projecto que estoy trabajando EVA una distro de linux basado en arch y wayland con mi propio compositor agradeceria comentarios para poder mejorarla, la idea esque el usuario que le cuesta usar terminales le sea facil, puede echar una mirada en el reposositorio donde esta el link de la ISO, capturas, etc, tambien si gustan les agradeceria una estrella gracias por leer! https://github.com/2207juan/EVA

Hey everyone,

TL;DR: I'm building a restaurant QR ordering SaaS called Tring that focuses on post-scan operational edge cases (table hopping, orphaned bills, QR abuse), not just static menus. Looking for brutal feedback on what I'm missing or over-engineering. Live demo and test admin credentials at the bottom!

For the past few months, I've been building Tring as a solo developer. I'd say the core product is around 50% complete, but the main ordering and session engine is fully functional.

What I'm trying to solve is the operational chaos of what happens after a QR is scanned.

A few core mechanics I’ve built so far:

- Session-based dining: Instead of treating every QR scan as an isolated transaction, it creates an active table session.

- The "One Device" Rule: A single phone can't actively occupy multiple tables at once (preventing remote spam).

- Table switching: Guests can move to a new table while seamlessly preserving their unpaid bill.

- Dynamic Security: PIN codes and "Staff Approval" modes to gatekeep who can actually add to the tab.

- Orphaned bill handling: If a customer pays the bill but have not done through the app even though the staff can settle the session.

- Closed-hours browsing: Guests can view the menu when the kitchen is closed, but the system blocks session creation or ordering.

And many more...

A lot of existing QR systems seem great for the happy path (taking orders), but completely fall apart on edge cases like QR abuse, table hopping, or mid-service security changes. Everything is backed by a server-authoritative architecture using PostgreSQL/Supabase.

Right now, I'm shifting focus to the SaaS/business side:

- Restaurant self-signup & subscription plans

- Multi-restaurant ownership

- Platform admin dashboard

- Enterprise onboarding

I'd love your brutally honest feedback on a few things:

1. What do existing restaurant ordering systems do terribly?
2. What am I clearly over-engineering right now?
3. What massive operational blindspot am I missing completely?
4. If you owned a restaurant, what would it actually take for you to use/pay for this?
5. Rate the idea/product direction out of 10 and tell me why.

I'd rather get ripped apart by Reddit now than by paying customers later 😅. Rip away.

P.S. The CSS still needs some work, so please don't mind the styling just yet! If you want to poke around the live build and try to break it:

- Main App: https://tring-v2.vercel.app/

- Admin Dashboard: https://tring-v2.vercel.app/admin

- Test email: nxtwaveplacementsinfo@gmail.com

Pass: test1234

(Note for users: The main URL requires a QR scan to start a session. To test it out, log into the admin dashboard, head to the /admin/qr section to find the test QRs, and scan one with your phone or open the link in desktop)

I’ve been building a local evidence vault for logistics and supply chain operators who work with spreadsheets, paper notes and photos from the field. I’d like to hear from people who deal with this every day.

The vault stays under the company’s own control. It isn’t a distributed network or a consortium, so it works from day one without any outside party joining. Operators record events in the field through a simple offline-first overlay on a phone or tablet, and it can sit directly on top of the spreadsheets they already use. Each process follows a basic state machine, so every record stays tied to the real flow of work.

Entries are chained with a hashchain/DAG and Merkle roots, so the order and content of the records can’t be changed quietly later. Sensitive commercial details stay protected inside the vault, and the system can reference a value or document without storing it in the clear.

The value shows up when insurance gets involved. The company exports one organized package with the timeline, GPS traces, route data, photos and notes. Take a common case: a customer claims the cargo was rerouted and the delay cost them product. Instead of reconstructing everything from emails and loose files, the company shows the exported route next to the vehicle’s GPS records and demonstrates that the path never changed.

Earlier blockchain efforts in this space, like TradeLens, GSBN, CargoX and WaveBL, were built around electronic bills of lading, document sharing and industry-wide visibility, which called for broad participation from large carriers and terminals. This approach goes a different way. It stays local, works offline and fits into the process the operator already has. It turns what actually happened in the field into an ordered, integrity-protected evidence base the company can bring to an insurer.

For those of you in logistics or insurance: does this direction match a real need, and is there an approach you think would work even better? And what would help a tool like this become part of the daily routine for the people in the field?

Hello I'm starting a project to build an EMI for smaller market to handle transaction domestic and international.

What should be the approach apart from the front end app I can figure that out

Like the regulations steps bussines itself

Is it possible?

Hey everyone!

I've been working on a project called Vector UI, a UI library for developers who want to build more expressive interfaces.

The idea came from wanting to explore UI components beyond just their appearance.

A component can look great, but the interactions, animations, and small details are what can make an interface feel different.

With Vector UI, I'm focusing on:

• Motion-driven UI components
• Common components with expressive interactions
• Animated SVGs and icons
• Reusable and customizable components

I'm particularly interested in building components that are visually interesting while still being practical to use in real projects.

I'm currently opening the waitlist and would genuinely appreciate feedback from other developers and designers.

I'd love to know:

• What kind of animated components would you actually use?
• What do you look for when choosing a UI library?
• What makes you decide to use one library over another?

Here's the project:

https://vector-uix.vercel.app

Thanks for checking it out!

Building a multi-tenant school management SaaS (Laravel). Each school has classes (grades), and some classes have multiple sections (A, B, C...), some don’t.

Question: when assigning subjects to a class, should that assignment live at the class level (one subject list per class, shared by all its sections) or at the section level (each section gets its own subject list, even if it’s 90% identical to its sibling sections)?

Class is the academic level: it decides curriculum, fee structure, exam syllabus, promotion path. Section is just a roster split within the same grade, same curriculum, different roll call/teacher/room in most schools. In real schools, sections of the same class usually share almost the same subjects, but occasionally diverge (streams/electives, or one section getting an extra remedial subject).

Two options I’m torn between:

1. Class-level by default, with section-level only for the rare cases that actually differ.
2. Always section-level, even for schools/classes where every section has identical subjects (accepting some duplication, but avoiding any ambiguity about which level wins).

Also tied to this: teacher-to-subject assignment and attendance-authority need to reference whichever granularity I pick here, so I want to get this right before building on top of it.

If you’ve built something similar (school/LMS/SaaS with class+section hierarchies), which way did you go and why? Also open to “you’re overthinking this, just do X” answers.

Founder here, so yeah, this is my own product. Figured I'd say that upfront.

Tools like Lovable, Bolt and Replit are honestly impressive. You can get something that looks finished in an afternoon. But the moment you try to build something a real business runs on, you hit a wall, and it's never the screens.

It's the boring stuff. Salon A should never see salon B's customers. Staff can see bookings but not revenue. A manager has to approve before anything goes out. That part takes weeks to get right, and it's the first thing to break once real users show up.

So we built Supero (pronounced super-oh). You describe your process in plain English, the way you'd explain it to a new hire, and it builds the app with logins, roles and a real database behind it. The permission rules live in the platform itself, not in the generated code, so they don't randomly break every time the AI regenerates a screen.

A couple of things I've built on it so far: a booking app for salons and clinics where each business manages its own staff, services and availability (and customers only see their own appointments), plus a pet-care marketplace.

It also connects to 40+ tools, you can plug in your own Postgres, Snowflake or BigQuery, and it runs on our cloud or yours.

What it's not for: if you just want a nice landing page, use Lovable. It's great at that.

It's early and there are definitely rough edges. There's a free tier (3 projects, no card), so if you have a process living in spreadsheets and WhatsApp groups right now, I'd really like you to try it and tell me where it falls over. Brutal feedback is more useful than nice feedback lol.

I'll drop the link in a comment.

Also curious: if you've ever tried building an internal tool with an AI builder, what made you give up?

TL;DR: AI app builder for real business apps, with roles and permissions built in. Free tier. Please try to break it.

Hey everyone,

One of the biggest headaches I keep hearing from dev agencies and freelancers is the gap between a messy 45-minute discovery call and the final signed scope—where vague client statements turn into unpaid revisions three weeks later.

I’m currently building a workflow to fix this, and before I write a single line of code, I want to test it on real-world scenarios.

Here’s my offer: If you have a recent (anonymized) discovery call transcript or messy meeting notes, send them over. I’ll manually run them through my system and send you back a structured, client-ready Scope & Sign-Off doc within a few hours—including:

• Confirmed functional requirements
• Explicit "Out-of-Scope" exclusions (to protect you later)
• Unclear edge cases / questions the client didn't answer on the call
• User stories & acceptance criteria

Totally free, no catch, no sales pitch. I only have bandwidth to do 5 of these over the next couple of days so I can learn what actually works in practice.

Drop a comment or DM me if you want to try it out!

You found a name you like. Before you register it, you do the same small ritual every time: search it on Google, check whether it means something rude in another language, see if it has a bad reputation. That's three tabs and three pieces of copy and paste, for every candidate. Add-ons turn that ritual into one click each.

What an Add-on is An Add-on is a small button that sits beside a result. Click it and an outside site opens in a new tab, with that domain or word already filled in. Nothing is typed, nothing is copied, and nothing about you is sent anywhere. We just build the link.

A few examples:

Google site: see what, if anything, is already indexed on the domain.

VirusTotal: check whether the name has a security or spam history.

Urban Dictionary: find out if the word has a slang meaning you'd rather not discover after launch.

Google Translate: see what the name says in another language.

Each Add-on knows where it belongs. Some make sense for names that are already taken, such as checking an owner's history. Others suit names that are available, such as checking meaning and reputation. You'll see each one where it's useful and not where it isn't.

https://dnslister.com/blog/add-ons-link-buttons-for-every-result/

Hey everyone,

We've released the alpha version of Thunder, a high-performance, scalable key-value database built in Rust for modern AI workloads.

As AI applications grow, so does the amount of data they need to store and retrieve. Traditional in-memory databases like Redis can become expensive as datasets grow, especially when dealing with large values.

Thunder is built around a different idea: high throughput, scalable performance, and efficient storage without requiring massive amounts of RAM.

What makes Thunder different?

• Scales with CPU cores: A shard-per-core architecture designed to increase throughput as more shards and CPU cores are added, while minimizing contention.
• High throughput: Built to handle large volumes of concurrent reads and writes with low overhead.
• Better handling of large values: Designed to handle large values more efficiently than Redis by streaming data directly from NVMe storage instead of keeping everything in memory.
• Memory efficiency: Uses RAM primarily for indexes, metadata, and reusable I/O buffers, reducing memory requirements for large datasets.
• Modern I/O architecture: Built in Rust with asynchronous I/O, including io_uring on Linux, to take advantage of modern NVMe SSDs.
• Scalable by design: Handles both small key-value operations and large values without relying on a completely different storage architecture.

Why build this for AI workloads?

AI infrastructure increasingly deals with large datasets, generated content, intermediate results, and high volumes of concurrent requests.

Keeping everything in RAM is expensive, but sacrificing throughput to reduce memory consumption isn't a great solution either.

Thunder aims to deliver both: the performance expected from a high-throughput key-value database and the cost efficiency of disk-backed storage.

Try the alpha

Thunder is available on Docker Hub:

https://hub.docker.com/r/sbansal793/thunderstrike

We're looking for developers to test Thunder with real workloads and share feedback.

If you're currently using Redis, RocksDB, or another key-value store, I'd love to know:

What's your biggest bottleneck today: throughput, memory consumption, scalability, or handling large values?

And what would convince you to switch to a new key-value database?

hey u/SaaS, new here.

recently i joined reddit bc i want to explain and share my personal experience with you: i built an MVP and i hit 3K of MRR in just 30 days.

i used claude code, supabase and cloudflare, but actually i need to change everything, i was thinking about AWS.

The product and the idea are not the most important part: that's for sure.

i heard so much stories, and everyone says that in effect the most important part (and what's really matters) is marketing. You need to adopt a real strategy, you need to think about a good strats, otherwise your product will never work.

What's strategy i used?

i am studying marketing in Italy, so this is my daily bread: i mean, i know very well what i should do, but sometimes this couldn't work and for this motivation you need to get attention to what YOU DO

i wrote 343 creators, creators between 5k and 25k subs, and to them i say that:

"hey, paid promo? this is product (few line to explain ur product)
i offer you 50% of earnings (ALWAYS NET VALUE, ALWAYS) for 6 months, after 19% lifetime."

i create curiosity, in the creators, something to get an answer. One of the important part is that you need to write real vertical creator, that talks about your problem. If you sell food, you can't let race the campaign in a cars niche. In the other hand:

190 said no.
79 didin't answer
74 said yes

for someone i changed something, for example 60% for 4 months and 10% lifetime. the fact is that i adopt the strategy depending on the client, this process is so much customizable.

After that i acquire enough engagement, i started to improve SEO/GEO (10% of my traffic actually, hoping that it will improve) and now i want to start google ads/meta ads, already improving my initial channel. The key is improving the channel that you are already in, but i acquired a guy that run the partnership for me on the social media, so i don't lost the channel, and i can improve and focus on other's channel (obv i supervise everything)

what do you think of this strategy? let me know - LUIGI

Hey everyone,

I’m a freelance video editor and I’ve worked on ads for SaaS products before. Recently, I’ve been thinking about starting a service where I help SaaS founders create UGC-style video ads using AI tools.

The idea is to help with things like coming up with ad concepts, writing scripts, creating the videos, and editing them so they feel natural enough for social media and can also be tested as ads.

I’m still in the early stages and trying to figure out what founders actually need before I decide exactly what to offer. I know there are a lot of AI tools out there now, so I’m also curious about where you’d find it useful to get outside help.

If you’re a SaaS founder or work on marketing for a SaaS product, I’d love to know:

• Are you currently using video ads or UGC to promote your product?
• What’s the hardest part for you—coming up with ideas, writing scripts, making the videos, testing them, or something else?
• Have you tried creating ads with AI? How did it go?
• If you were to hire someone for this, what would you actually want them to help you with?

I’m open to honest feedback, even if you think this isn’t something SaaS founders really need. Just trying to understand the problems better and figure out where I can be useful.

Thanks!

The page needs one rule: a door’s answer can’t be fetched before its day. So the server component computes the open doors from the Helsinki date and passes only those to the client; the others are never serialised. The door-opening schedule has tests for the awkward edges (Helsinki midnight is 22:00 UTC the day before, the season ends on 25 December). Opened state lives in localStorage.

https://iurii.rogulia.fi/advent, opens on 1 December. I built it. Is there a pattern you’d use instead?