How muhammadhasaanwaseem/fyp-react-native-social-media-application-name-rabbit- works
Project Overview & Identification of Main Components
• This project is a full-stack, React Native social media application built with Expo Router. Its core functionalities include authentication (with Supabase and Twilio Verify), posting (media, text, audio, video, GIF support), real-time notifications, messaging, and AI-based chatbot integration.
• The file tree clearly separates “app” (or “screens”) for different functional areas (auth, onboarding, tabs, etc.), custom UI components (in components/ui), utility libraries (in lib, hooks), and providers that abstract business logic and external integrations.
Main Architectural Elements
a. Frontend/UI Layer:
• Mobile UI Delivery: The React Native “app” and “screens” directories contain the implementation for various screens (splash, authentication, onboarding, tabs such as home, profile, search, etc.).
• Reusable UI Components: The “components/ui” folder is a collection of custom-designed UI elements using the Gluestack UI library, designed with both mobile and web variations.
• Assets: Static media (images, logos, fonts) are provided in the “assets” folder.
b. Business Logic & State Management:
• Providers: “providers/AuthProviders.tsx”, “providers/PostProvider.tsx”, and “providers/VideoPlayerProvider.tsx” encapsulate cross-functional logic (authentication flow, post management, video handling).
• Hooks: Custom hooks (in the “hooks” directory) manage data fetching and real-time interactions (e.g., use-posts, use-followers, etc.).
• Libraries: “lib” directory includes code for sharing profiles, Supabase integration, storage handling, and defining custom types.
c. Backend / Data Layer:
• Database & ORM: Prisma (located in the “prisma” folder) serves as the database schema and migration tool.
• Authentication & Real-Time Data: Supabase is used to handle authentication (in the README you see the SQL commands to set permissions) and store data.
• External Services Integration: Integration with Twilio Verify for phone-based authentication and OpenRouter API for the DeepSeek Llama R1 chatbot.
Relationships & Data Flow
• Bidirectional data flow where needed (e.g., real-time notifications from Supabase sent back to the UI).
• Dependencies of external services such as Twilio Verify (for authentication) and the chatbot API.
Incorporate Key Architectural Patterns
• MVC / MVVM can be implicitly depicted by separating the UI (view layer) from the business logic.
• Component-based architecture: Emphasize the reusability of UI components.
• Service abstraction: Use providers to abstract API calls and external service interactions.
Relevant Technologies, Frameworks, and Libraries
• React Native with Expo Router (for mobile navigation).
• Prisma for ORM and database migrations.
• Supabase for backend services.
• Gluestack UI for component styling.
• TanStack Query for data caching.
• Twilio Verify and OpenRouter API for authentication and chatbot integration.