How mattiasaan/grademate works
Project type and purpose
• This is a React Native mobile application (built with Expo/EAS) named GRADEMATE.
• Its primary purpose is to let students record grades, compute averages (using Galileo Galilei school rules), and display subject details on a mobile device.
File structure
• Top-level files and folders:
• App.js & index.js – application entry points
• Screens/ – UI components for each screen (WelcomePage, HomeScreen, AggiungiVoti, DettagliMateria)
• app.json & eas.json – Expo configuration & build settings
• package.json & package-lock.json – dependency definitions
• No dedicated backend folder: all data storage and business logic live in the mobile client, likely using local storage (AsyncStorage or SQLite).
Extract insights from the README
• Sole focus on local grade management and average calculation
• No external APIs or backend services mentioned
• Core feature: grade entry and average computation
Main components
a. Mobile Client – React Native application
• UI Layer: Screens folder (WelcomePage, HomeScreen, AggiungiVoti, DettagliMateria)
• Business Logic Layer: functions in App.js (grade aggregation, average formulas)
• Data Layer: local storage module (e.g., AsyncStorage or SQLite abstraction)
b. Development & Build Pipeline
• Code repository (Git)
• Local development (Metro bundler)
• Expo Application Services (EAS Build) for iOS/Android binary generation
c. External Services (optional)
• If in future you integrate a cloud backup or authentication, these would sit outside the mobile client
Relationships and interactions
• UI → Business Logic: user taps “Add Grade,” UI calls logic functions in App.js
• Business Logic ↔ Data Layer: logic reads/writes grades to AsyncStorage or SQLite
• Development Workflow:
• Developer machine pushes code to Git
• EAS Build pulls from Git, runs build pipeline → generates mobile binaries
• Metro serves JS bundle to running simulator/device
Architectural patterns & design principles
• Component-based architecture (one React component per screen)
• Layered separation: UI layer vs. business logic vs. data storage
• Single codebase for both Android and iOS via React Native / Expo
• Configuration-as-code for build (eas.json, app.json)
• Arrowheads showing data-flow direction (user action → function call → storage)
• Annotations for technology choices (React Native, Expo, EAS)