How trosdan/todoapp-frontend works
Project type and purpose
• This is a full-stack ToDo application:
• Frontend: React Single-Page App (SPA)
• Backend: NodeJS functions hosted on Firebase (REST API)
• Persistence & Auth: Firebase Realtime Database and Firebase Auth
File structure
• Top-level: config files (.env.example, .firebaserc, firebase.json), CI workflows, package.json
• public/: static HTML, manifest, images → served by Firebase Hosting
• src/
• App.js, index.js → SPA bootstrap
• components/ → reusable UI (CardTodo, ModalTodo)
• pages/ → route-level views (home, login)
• routes/ → React Router setup
• services/ → API client (api.js), history.js, REST module (services/rest/todo)
• styles/ → global styles (styled-components)
• assets_readme/ → documentation images
README insights
• Hosted entirely on Firebase: Hosting (React) + Functions (Node.js back end)
• Uses environment variables for Firebase config & REACT_APP_BASE_URL → local dev at http://localhost:3333
• No on-premise server; all deployed to Google Cloud via Firebase
Main components & their relationships
A. Browser (User Agent)
• Loads React SPA (index.html + JS/CSS) from Firebase Hosting
• Renders UI components/pages, handles client-side routing (React Router)
• Invokes REST API via Axios (services/api.js)
B. Firebase Hosting (CDN)
• Serves static assets (public/ and build/)
C. React Frontend
• UI Layers: pages → components → styles
• Client-side Router: /login, /home
• Service Layer:
– services/api.js configures base URL
– services/rest/todo calls HTTP endpoints to create, read, update, delete todos
D. Firebase Functions (Node.js Backend)
• Exposes REST endpoints on REACT_APP_BASE_URL (e.g. /todo)
• Implements business logic: authenticate user, validate payload, read/write to DB
E. Firebase Realtime Database
• Stores user todos, authentication state, user profiles
F. Firebase Auth (External Service)
• Manages user sign-in/sign-up flows
G. (Optional) Firebase Storage if used for attachments/images
Architectural patterns & design principles
• Single-Page App (SPA) pattern: client heavy, server provides only APIs & static files
• Layered architecture:
• Presentation (React components)
• Application (React pages + service layer)
• Infrastructure (Firebase Hosting, Functions, DB)
• Separation of concerns: UI vs. API vs. data layer
• Client-side routing decoupled from server routing