How omar290904/jaladope works
Project type and purpose
• This is a full-stack mobile application built with Expo (React Native) using the expo-router “app” folder convention for screen-based routing.
• A simple Node.js/Express API (“API/api.js”) and a local “db” folder implement your backend data layer.
• The mobile client handles authentication, tabbed navigation, QR features, and user-specific shortcuts.
File structure
• Top-level “app” folder: expo-router screens organized into two route groups:
• (auth): authentication flows
• (tabs): main tabbed UI (add, chat, courses, profile, qr)
• _layout.js files define shared layouts per group and the root navigation container
• “components”: reusable UI pieces (ShortCuts, TabBar)
• “views”: screen subcomponents and modals (Home shortcuts, QR scanner, QR display)
• “context”: React Context providers for AuthContext (login state, tokens) and UIContext (theme, loading states)
• “service/auth.service.js”: client-side service for calling backend auth endpoints
• “API/api.js”: Express server entrypoint defining REST endpoints
• “db/user/user.js”: data model or file for user persistence
• “assets” and “themes”: fonts, images, and theming definitions
Detail without overcomplicating
• Grouping (e.g., group all “app/(tabs)” screens under a “Tabs” container)
• Don’t omit the Context or Service layer—they are critical glue