Looking for React 18 + Supabase Dev — 7 Week Paid Contract

Hey Chance,

I run a small dev team building SaaS MVPs. Recent project: huaspeed dot cc — full-stack VPN accelerator (Node.js, Express, WireGuard tunnels, Stripe payments, production deployment).

Your 4 questions:

1. Supabase migration?
   Not Supabase-specific, but we've done production database migrations and auth rewrites. The patterns translate: dump → recreate → re-validate permissions → cut over. Aware of the RLS policy gotcha (breaks silently on ownership change). Would budget buffer for thorough policy testing.

2. Cloudflare R2 / similar?
   Yes — S3-compatible storage setup, CDN-routed subdomains. Our approach: grep codebase for hardcoded URLs → build signed-URL pipeline → migrate with a script. The real work is the frontend URL hunt, not the R2 config.

3. Capacitor experience?
   No direct Capacitor experience — being upfront. But the scope here is wrapping an existing web app + store submission. We've handled iOS provisioning/certificates and review processes before. Would allocate extra time for Apple ATS/quirk handling.

4. Week 1-2 hour estimate?
   ~110 hours for my team. Breakdown:

• Supabase migration + RLS re-validation: 35h
• R2 + frontend pipeline swap: 20h
• Twilio SMS OTP: 10h
• Google OAuth: 8h
• Apple OAuth: 8h
• Testing + buffer: 30h

Anyone quoting under 100h for this is being optimistic — the Supabase migration alone needs real testing time.

Why us?
We ship products end-to-end, not just code. Huaspeed dot cc has real users, real payments, real infrastructure. We work from specs, communicate clearly, and deliver without hand-holding.

Available immediately. Prefer fixed price per phase, happy to discuss on a call this week.

— Cyber Free Bird
songwanxindeyouxiang1 at huaspeed dot cc

Is it still relevant?

Hey Chance, we have built and shipped with supabase for over a year now. We have setup very similar object storage utilizing supabase native S2 buckets, One of our devs has worked with cloudflare R2 before. Not fully with capacitor. We are a team of developers with capabilities ranging in different specialities. We work on a phase by phase rate would love to hop on a call and discuss more. You can visit our site at thundebirdlabs,co here to learn more (wont let me post links but the , is a . for .co), along with this my email is nick@thunderbird-labs . co m (once again ignore my weird spelling you can guess what im trying to write lol)

Great scope definition — rare to see a job post this well-structured.
Respecting the "no agencies" note, not applying, but wanted to drop
a few notes for anyone else reading this looking to do similar
Supabase hardening work.

Common gotchas I've seen on projects with this exact stack:

1. Supabase migration: RLS policies don't migrate cleanly when
   project ownership changes. Budget 8-12 hours just for policy
   re-validation — separate from the SQL migration itself. The
   SECURITY DEFINER functions often break silently.

2. Cloudflare R2 + Supabase storage swap: The real work isn't the
   R2 setup, it's hunting down hardcoded storage URLs scattered
   through the frontend. Do a full codebase grep before touching
   anything — pre-signed URL handling is where most teams lose
   a day.

3. search_path injection fix: Don't patch one function — audit
   every SECURITY DEFINER function in the project. Missing even
   one leaves the whole attack surface open.

4. Capacitor iOS submission: Apple's ATS and bitcode requirements
   hit Capacitor apps hard. TestFlight 2 weeks before final
   submission, minimum. Google Play is usually smoother but throws
   curveballs on permission declarations for media access.

5. On the 80-hour estimate for Week 1-2: that's optimistic unless
   you've done a Supabase migration before. Realistic range is
   100-120 hrs if it's your first one. Worth building in that
   buffer upfront.

The "600-1000 line component refactor" in weeks 3-5 is where most
devs underestimate. Splitting without breaking existing behavior
takes meaningful test coverage — if the codebase doesn't have it
already, add 20-30% buffer there too.

Best of luck with the hire — whoever lands this has a clean spec
to work from, which is half the battle.

— Jillur

Hi — I’m interested in the role.

1. I haven’t shipped a dedicated Supabase project yet, but I’m very comfortable with backend-as-a-service systems like Firebase. The patterns (auth, database modeling, real-time data, serverless workflows) are familiar, and I can ramp up on Supabase quickly since the concepts translate directly.

2. Yes — I’ve used Vercel, Netlify, Firebase, and similar modern deployment stacks in production-style projects. I’m comfortable with CI/CD workflows, environment configs, and shipping fast.

3. My initial estimate is ~80 hours for the first phase, but I’d need to review the existing codebase to give a more precise breakdown. I usually prefer to evaluate architecture first before committing to time estimates.

I work fast, communicate clearly, and focus on shipping working features rather than overengineering.

Happy to jump in immediately. Looking forward to hearing from you.