Summary

RNHT already has a substantial product surface and many integrations, but local setup still depends on developers knowing which Supabase, Stripe, Firebase, and Capacitor environment values need to exist. A checked-in env template plus startup validation would make onboarding much smoother.

Why this matters

Right now the repo looks rich and production-minded, but the local developer experience is still too implicit for new contributors or future maintainers.

Proposed scope

• add an env example file that covers the core local variables
• group variables by integration area such as auth, payments, analytics, and mobile
• add runtime validation for required variables in development
• fail fast with readable errors when critical configuration is missing
• document the local setup path in the README or deploy checklist

Acceptance criteria

• a new contributor can discover the required local environment variables without reading source files
• missing critical configuration produces actionable startup errors
• docs explain the minimum setup needed for local development

Notes

This is a developer-experience issue, but it is high leverage because RNHT spans web, mobile, auth, and payments in one codebase.