How seharbashir/groomify works
Project type and purpose
• This is a React Native mobile application (“Groomify”) that connects salon owners and clients.
• Users can browse services (haircuts, facials, massage, etc.), book appointments, rate services; salons can manage services, view appointments, and collect feedback.
• It integrates with a chatbot, Firebase for configuration/auth, and a custom Groomify backend API.
File structure
• Top-level files:
• index.js & App.js: app entry points
• app.json: React Native configuration
• firebaseConfig.js & config/config.js: environment and Firebase settings
• package.json / package-lock.json: dependencies
• Directories:
• assets/: animations & images used by UI
• components/: all React components, subdivided into common, salons, users
• services/: wrappers for external HTTP APIs (ChatbotAPI.js, GroomifyAPI.js)
• hooks/: custom React hooks (useChatbot.js)
• utils/: shared utilities (network, email, chat rendering)
• constants/: application-wide constants for chat flows
• config/: potential toggles and environment abstractions
• No backend code here—only API clients. Deployment is purely mobile (iOS/Android), calling external services.
README for additional insights
• README is minimal but project name “Groomify” indicates salon-booking focus.
• docs/ contains CHATBOT_INTEGRATION.md and IMAGE_PICKER_FIX_GUIDE.md, pointing to specialized subsystems (chatbot, image picker).
Detail
• Within UI, group screens by domain (users vs. salons).
• Flows:
• “User taps BookService → GroomifyAPI POST /bookings”
• “Chat message → useChatbot → ChatbotAPI → Dialogflow”
• “Login → Firebase Auth → returns token”
• Avoid over-splitting; capture each logical module and its dependencies to reflect the structure in the file tree.