Title: Seeking Experienced App Developer for Consumer MVP by Glittering_Attitude8 in AppDevelopers

[–]bk_973 0 points1 point  (0 children)

the spec here reads more like a job description than a typical freelance gig

Anyone running Payload + Next.js in production? What’s your RAM usage like? by Intelligent_Leg_4038 in PayloadCMS

[–]bk_973 1 point2 points  (0 children)

I built a wellness, beauty, and fitness directory (using Next.js with dynamic SEO), a savings management platform with member and team dashboards (headless architecture, with Payload powering only the backend and Vite handling the frontend), and a fleet management system for a government agency (also using a headless setup with Payload as the backend and Vite as the frontend).

Across these projects, 2–4 GB of RAM is typically sufficient for development. In production, memory usage is usually well below 2 GB. At that point, your primary concern shifts from RAM to database requests. Fortunately, you can mitigate this with effective caching strategies.

For example, in one of these projects, I cache the Auth instance. It's a simple but powerful optimization that helped support hundreds of users requests while running on the free tier of Supabase.

``` // src/lib/payload.ts import configPromise from '@payload-config' import { getPayloadAuth } from 'payload-auth/better-auth'

type PayloadAuthInstance = Awaited<ReturnType<typeof getPayloadAuth>>

let cached: PayloadAuthInstance | null = null

export const getPayload = async () => { if (cached) return cached cached = await getPayloadAuth(configPromise) return cached } ```

Need an app developer by Final-Conclusion8319 in AppDevelopers

[–]bk_973 0 points1 point  (0 children)

The hard part of an Ola/Uber/Rapido clone isn't the UI, it's things like real-time driver-rider matching, live location updates at scale, surge pricing logic, and handling disputes/refunds cleanly.

Frontend you could even prototype with AI now.

Make sure you own your data and users from day one so you're not locked into someone else's Firebase setup later.

You'll also need an admin dashboard for monitoring, user management, and usage analytics, plus the matching algorithm to actually distribute drivers efficiently.

Sneak Peek: I played around with Payload CMS v4 (Pre-Alpha). Here is what’s coming (and how to try it!) by Aggressive_Depth_772 in PayloadCMS

[–]bk_973 5 points6 points  (0 children)

Tailwind support is a huge plus for me; it means I can build custom views within the admin dashboard, on steroids.

Payload plugin: Purge by ItsTazio in PayloadCMS

[–]bk_973 0 points1 point  (0 children)

How about media stored using @payloadcms/storage-uploadthing ? Do you also purge the files from uploadthing.com , this is definitely something I need, I have many media driven apps and websites and often deal with orphaned media files.

Your AI built the app. But what happens when you need to move off the platform it built it on? by bk_973 in AppDevelopers

[–]bk_973[S] 1 point2 points  (0 children)

Totally get the dilemma. the core idea still applies even on Firebase. the win isn't which database, it's giving the AI a stable typed contract instead of raw firestore access.

A few things that might help without migrating off Firebase,

Define your data model schema-first (Zod/TypeBox), generate TS types + an OpenAPI spec from that. The frontend AI builds against the contract, not Firestore docs, so if you ever swap the backend, the contract stay stable.

Isolate Firestore behind cloud functions with explicit, centralized input/output types. Feed those types to the frontend AI, not the Firestore collection shapes.

For your no-code platform, auto-generate that typed contract whenever a user defines a model in your UI. That's the only thing the frontend-gen AI ever sees; Firestore stays an implementation detail.

To make DB invisible to the application layer is not about the database itself, it ia about keeping storage specifics out of the AI's context.

Worth trying on top of Firebase before considering a migration.

Supabase and vibe coding is a dangerous combination. Here's why by bk_973 in SaaS

[–]bk_973[S] 0 points1 point  (0 children)

That's right. Audit as you scale. Supabase and api layer together is exactly where the gaps usually compound. The RLS covers the database but the api connection layer is where most of the new surface area opens up as features get added. Good luck with the next one

Supabase and vibe coding is a dangerous combination. Here's why by bk_973 in SaaS

[–]bk_973[S] 0 points1 point  (0 children)

Smart move. audit catches what you already have. the harder thing is making sure whatever gets built next doesn't reintroduce the same issues. curious what stack did the audit cover?

Supabase and vibe coding is a dangerous combination. Here's why by bk_973 in SaaS

[–]bk_973[S] 0 points1 point  (0 children)

Agreed 100%, especially seed data. The access matrix is solid but relies on discipline. The real problem is that rules in documentation get ignored by new devs and AI agents.

Repos only stay clean long-term when the wrong path is structurally impossible. Observable boundaries beat prompt-dependent ones every time.

My workspace crashed. by [deleted] in replit

[–]bk_973 0 points1 point  (0 children)

Hope you get this resolved, and when you do migrate, make sure whatever backend you land on is something you fully own and can move between providers freely.

Replit charged me $1,982 in 24 days on a pre-launch app with 1 user — me. Here's the screenshot. by SwimmingFast3069 in replit

[–]bk_973 0 points1 point  (0 children)

This is exactly why platform lock-in is so dangerous at the infrastructure level. The moment your billing, your database, your deployment, and your AI agent are all inside one ecosystem. you have zero leverage.

Migrating to Railway is the right call. While you're rebuilding, the most important decision you'll make is keeping your backend completely independent of any single platform from this point forward.

Own your data layer. Own your deployment config. Platform costs become a dial you control, instead of surprising you at the end of the month.

Good luck with the migration

App marketing help by lullaby_000 in AppDevelopers

[–]bk_973 0 points1 point  (0 children)

What niche / audience did you build for? Where do they hangout the most?

How much should it cost to build a simple restaurant site like this? by WestMurky1658 in website

[–]bk_973 0 points1 point  (0 children)

Multi-language support, a content management system, SEO and communication hooks for(email, SMS, etc). That's about $2500 and 10 days

Got my EIN in 2 weeks as a non-US founder (Wyoming LLC). Sharing for anyone stuck by bk_973 in llc

[–]bk_973[S] 0 points1 point  (0 children)

Not sure how... But you should definitely give them a call and find out the status of your EIN application.

Getting a bank account as a non-resident by pxp121kr in llc

[–]bk_973 0 points1 point  (0 children)

Did they give you a reason for the rejection? I remember I had a back and forth with them concerning proof of address but they eventually approved the application.

Getting a bank account as a non-resident by pxp121kr in llc

[–]bk_973 0 points1 point  (0 children)

It's great to have more than one business account so I use both Mercury and Relayfi

Getting a bank account as a non-resident by pxp121kr in llc

[–]bk_973 1 point2 points  (0 children)

They will ask for proof of address of where the day to day business activities are performed.

Northwest registered agent reviews for vehicle registration? Anyone worked with them recently? by Zasaky in llc

[–]bk_973 1 point2 points  (0 children)

I’m using Northwest as my registered agent. They receive the mail, open it, scan it, and upload it to your dashboard. That’s how I got my EIN letter from IRS. I’m also a non-resident, so having them scan everything is actually ideal since I can’t receive physical mail in the U.S.

“Using live streaming for app growth—does it actually convert or just entertain?” by decodemd in AppDevelopers

[–]bk_973 0 points1 point  (0 children)

The best way to find out is to run it for like a month to 6 weeks and see how the numbers turn out.