How faontane-git/diakonia works
• A web system (located in the “diakonia-admin-web” folder), which is a React application.
• A mobile system (located in the “diakonia-app” folder), which is a React Native/Expo application.
b. Mobile App: Represent the “diakonia-app” application. Note it is structured as a React Native application with Expo (as indicated by the “expo” folders and instructions in the README). Include details such as screens for login, registration, and various “Ventanas” like Asistencia, Seguimiento, and VerRegistro. Also, highlight its use of Expo for development and testing.
Separate supporting layers/components
• Static Assets & Public Files: For the Web Client, include a small subcomponent for “Public Assets” (HTML files, manifest, robots.txt), which are served to the browser.
• Third-party Services & Libraries: Optionally indicate any external libraries or services (for instance, Expo for mobile development, QR Code scanning functionalities in mobile, chart libraries in the web, etc.). While the file tree doesn’t list every dependency, you may annotate that common libraries (React, Firebase, React Navigation in the mobile app, etc.) play a role.
Interactions and data flow
– The Web Client and Firebase (for API calls, authentication, and data retrieval).
– The Mobile App and Firebase (for real-time data synchronization, authentication, and related services).
• Within each client, illustrate how presentation components (screens or pages) interact with shared service layers or contexts (for example, AuthContext in the web and its mobile equivalent).