How distrad/ign_tattoo works
Based on our analysis of both the file tree and README, IgnTattoo is a full-stack mobile social platform for tattoo artists and designers. The project is divided into two main parts:
• A backend built with Node.js and Express.js (in the “backend-ign-tattoo-app” directory) that serves as the REST API and handles business logic.
• A mobile frontend built with React Native using Expo (in the “frontend-Ign-Tattoo-App” directory) that offers the client-side experience.
Main Components
a. Mobile Frontend (React Native/Expo):
• Contains screens like authentication, profile management, appointment scheduling, messaging, and collaborative project views.
• Uses Expo for building and OTA updates, along with libraries for animations (Reanimated/GestureHandler) and styling (NativeWind).
b. Backend API (Node.js/Express.js):
• Implements RESTful endpoints for authentication, user management, appointments, and designer projects.
• Manages assets (e.g., image uploads) and handles the business logic.
c. Database (PostgreSQL):
• Stores user data, appointment details, and designer project information.
• Represents relational data concerning users, appointments, and projects, as outlined in the README.
d. DevOps / External Services:
• GitHub Actions, Expo Application Services, and optionally Docker for containerization.
• These may be represented as supporting components or labels showing CI/CD, deployment processes, and OTA updates.
Relationships and Interactions
• The Mobile Frontend interacts with the Backend API over HTTP(s) using REST calls.
– Indicate data flows for user authentication, data fetching (e.g., portfolio images, project details), and appointment management.
• The Backend communicates with the PostgreSQL database for persistent storage.
• DevOps components (GitHub Actions, Docker) are connected with both the frontend and backend deployment processes.
Architectural Patterns & Design Principles
• Clearly demarcate the separation of concerns: the frontend is solely responsible for user interaction while the backend manages data and business logic.
• RESTful API endpoints and the relational database model clearly.
• If desired, use distinct grouping for authentication flows (using JWT) as these cross-cut both frontend and backend.
• Frontend: React Native (Expo), NativeWind, Reanimated, Image Pickers.
• Backend: Node.js, Express.js.
• Database: PostgreSQL.
• Other: GitHub Actions for CI/CD, possibly Docker for containerization.
• Where push notifications or OTA update services (Expo Application Services) come into play.