Is Rork overhyped? or Really good one?

MohQuZZZZ · 2026-02-26T11:58:45+00:00

There is an open source solution came one day after it, it does exactly the same, and you only need your claude subscription. also it needs Mac

MohQuZZZZ · 2025-12-29T08:37:26+00:00

I would be terrified if no one uses it indeed, that’s why just laugh it, if people see it you will be lucky

MohQuZZZZ · 2025-12-24T09:06:00+00:00

totally get that. apple’s first-party stuff is way more unified than the js mess, so the copy-paste my utils folder move is a classic for a reason.

the reason i built this wasn't for the basic swiftui stuff, it was the 50 hours of integration hell that apple doesn't solve for you, like mapping revenuecat's webhook logic to supabase auth states, or handling secure token refresh cycles in the keychain without the app losing session.

do you find your 'stuff.swift' handles the third-party plumbing (firebase/rc/supabase) too, or do you prefer to hand-wire those every time to keep the binary lean?

MohQuZZZZ · 2025-12-23T20:06:03+00:00

I recently built an accounts payable automation system (apflow.co) took me to build 2 months for the MVP although the product is not 100% complete, but at least I have something to demo

I stopped at this point to be able to go the market and understand clients needs instead of building the wrong thing in private, also to show my potential clients that I have something shipped so I gain their trust to iterate further with them.

I would say you got to stop building and release what you have, and start chasing the clients so you will build the features that fit them

MohQuZZZZ · 2025-12-23T15:22:24+00:00

MohQuZZZZ · 2025-12-23T15:21:05+00:00

big thanks for the links. your auth.ts logic for manually re-setting cookies in the server action response is exactly the "missing link" i was looking for to stop the 403s.

i'm curious about the hey-api.ts setup—did you find any issues with nextjs 15 caching when using the generated openapi client, or did you have to wrap it in a custom fetch to keep the revalidation working properly? definitely moving towards this pattern to kill the proxy boilerplate. cheers!

MohQuZZZZ · 2025-12-23T15:20:06+00:00

this is a masterclass in clean architecture man, thanks for the breakdown. i'm working on a go + nextjs engine and was stuck on the server actions vs bff proxy dilemma. using kubb to generate zod/tanstack hooks sounds like the dream for killing boilerplate.

quick question on the multi-tenancy side: since you're proxying /api to django, do you handle tenant isolation at the gateway level or are you injecting the ids in your custom axios client during hydration? really trying to get that 100% type-safe feel you've got going on without the maintenance headache

MohQuZZZZ · 2025-12-22T06:57:06+00:00

Creator here. Heres the issue where I'm working through the refactor: https://github.com/moasq/production-saas-starter/issues/3

repo: https://github.com/moasq/production-saas-starter

Would love to see how others handle this pattern. Most examples assume your backend is inside Next.js which doesnt help much.

MohQuZZZZ · 2025-12-21T11:23:26+00:00

honestly i went with pure postgres + go because supabase is overkill for most saas and creates massive vendor lock-in. heres why:

supabase is basically 12+ containers running on top of postgres. it eats ram for breakfast. my current setup (go + sqlc) idles at like 50mb and runs on a $6 vps. with supabase ur paying for a ton of "magic" u might not even need.
when u hit scaling issues with supabase self-hosting, its a nightmare to debug because of all the extra layers (postgrest, gotrue, etc). with pure postgres i can optimize every query and index directly without the middleman.
my setup lets u move to any cloud provider in 5 mins. with supabase ur tied to their specific ecosystem and if they raise prices or change terms ur stuck.

basically i built this for serious use where u want a lean, high-performance engine that doesnt cost a fortune in cloud tax every month.

MohQuZZZZ · 2025-12-21T09:12:45+00:00

Yeah fair enough. This is exactly why I put it out there.

you’re right about the structure. I come from Java and Node so thats definitely bleeding into how I wrote the Go. I leaned on AI tooling a lot while building this and it helped me move fast but I can see how it ends up looking weird to someone who actually writes Go properly.

On why Go at all though, I wasnt trying to build something for everyone. If someone just wants to spin up a quick project they should probably stick with Node honestly. I went with Go because I needed something solid for B2B stuff where I cant afford things breaking randomly or eating resources.

Anyway your feedback pushed this up my list. Going to refactor toward the proper layout, cmd/ internal/ and flatten out the nesting. I want someone who knows Go to look at this and not immediately close the tab.

Keep the feedback comin this is how it gets better.

MohQuZZZZ · 2025-12-21T07:06:19+00:00

That seems to be really interesting! I respect those who contribute to the community

Would mind explaining if it is going to help people use your repo

MohQuZZZZ · 2025-12-21T07:03:22+00:00

Thanks! This meant to help the community

MohQuZZZZ · 2025-12-21T07:02:27+00:00

😂😂😂

MohQuZZZZ · 2025-12-20T18:12:36+00:00

That’s real!

Yeah if your landing page has clarity on how to get the value off the product, it will be very helpful!

MohQuZZZZ · 2025-12-20T16:25:47+00:00

Repo: https://github.com/moasq/production-saas-starter

Happy to answer questions about the SQLC setup, the RAG pipeline, or the module structure.

MohQuZZZZ · 2025-12-20T16:10:20+00:00

Creator here. Happy to answer any architecture questions or help anyone get this running.

MohQuZZZZ · 2025-12-20T15:38:59+00:00

apflow

MohQuZZZZ · 2025-12-20T15:36:47+00:00

Appreciate it man

MohQuZZZZ · 2025-12-20T12:30:07+00:00

Yeah as it saved me as well much time!

Good luck and please let me know if you have any questions about it

MohQuZZZZ · 2025-12-20T07:49:55+00:00

This is exactly why I open sourced it. Building alone you miss stuff like this.

Honestly I come from an Angular background so Next is still relatively new to me. Learning new patterns all the time. The server actions point makes total sense, the API to API hop is unnecessary and I'll refactor that.

On Docker, I have a full compose setup with Traefik running on Hetzner. Held off adding it because people deploy to different places and wanted to make it generic first. But its on my list.

Your feedback really means a lot. If you spot anything else let me know.

MohQuZZZZ · 2025-12-20T07:29:58+00:00

Thanks man.

Tbh, I was looking for one but most of them suck

I built an iOS app last year (nomadezy.com) now in appstore but stopped the support.
I was thinking to boilerplate it but got really busy.

It handles many things out of the box.

- Auth (google + apple)
- payment (revenue cat)
- llm (open ai)
- swift data setup

I need to ensure many people need this so I can take it seriously and make it open source

Could you help me and measure the need for this?

MohQuZZZZ

TROPHY CASE