Library name | Description |
---|---|
react native with expo | Mobile Framework |
supabase client | Supabase SDK |
TanStack query v5 for React | Manage Async State |
React Hook Form | Manage Form State |
Zod | Runtime Validation |
RNUI and React Native Reanimated | React Native UI Components |
Day.js | Parse, validate, manipulate, and display dates and times |
In the per feature separation there is no clear structure because it depends on business domain.
Don't use the generic folders like utils or components, each folder is a separate feature.
"move files around until it feels right" with this rules:
- Each module should correspond to a specific functionality or business domain
- Each module can have shared folder with shared files across module and child modules
-
Features at the same folder level are not allowed to import each other.
-
The shared folder is an exception to the first rule and modules can import files from shared folder at the same level.
-
Child features are not allowed to import the parent feature but parent can import children.
Same rules like in features folder
Copy .env.example and rename to .env
You can message me (contact info) for environment variables if you want test the app
npm install
npm run gen:types
npm run start