How giselearaujos/fiap-enterprise-challange-social-life-ring works
Project type and purpose
• From the README and folder names, this is a full-stack “Task Management” / social-engagement app with three distinct deliverables:
• A React Native / Expo mobile client (in mobile-app/)
• A static web client (HTML/CSS in web-app/) that could evolve into a ReactJS front end
• A Node.js + Express + TypeScript REST API backed by MongoDB (in web-api/)
• The business goal is to let users create, view and manage “tasks” (or social-impact actions) across mobile and web.
File structure
• Top-level folders:
• mobile-app/ – React Native + Expo, using Next-style app router (app/+*.tsx), custom components, screens, and a tasks-manager API service.
• web-api/ – Express server with controllers (health, tasks), a database layer (connection, entities), HTTP routing, and error handling.
• web-app/ – Static front-end (index.html + style.css + image assets).
• Notice architectural patterns:
• mobile-app/src/services calls the REST API
• web-api/src/controllers implements the API endpoints
• web-api/src/database encapsulates the MongoDB connection and entity definitions
• Config & infra files: Dockerfile for the API, Postman collections, tsconfig.json in each module, .prettierrc, .vscode, babel.config.js.
README for additional insights
• Technology stack: Node.js, Express, TypeScript, MongoDB on the back end; ReactJS on the web front end; React Native + Expo on mobile.
• The API is RESTful and documented/testable via Postman.
a. Clients
– Mobile App (React Native + Expo)
– Web App (HTML/CSS or ReactJS)
b. API Layer
– Express Server
– Controllers (health, tasks)
– Routing & HTTP middleware (web-api/src/http)
– Business logic / Entity layer (web-api/src/entities)
c. Data Persistence
– MongoDB cluster (database connection in web-api/src/database)
d. External/Support Tools
– Postman (for API testing)
– Docker (for containerizing the API)
– CI/CD or hosting (optional, not in tree)
Relationships and interactions
• Web App → API Server (HTTPS/JSON)
• API Server → MongoDB (native driver over TLS)
• Postman interacting with the API for testing.
Architectural patterns & design principles
• REST API pattern (separate controllers, shared error handler, centralized routing)
• 3-tier separation: Presentation (clients), Application (Express controllers + services), Data (MongoDB + entities)
• Client-side service layer (tasks-manager-api.ts) abstracts HTTP calls
• Modular folder structure (controllers, http, database, entities)