Hello team,

This is a summary of the updates completed in today’s working session across Flutter mobile, Nest API, and admin panel.

1) Mobile app (Flutter) updates completed

• Implemented and stabilized authentication flow: onboarding, register, login, profile view and profile edit connected to staging API.
• Added i18n (English/Spanish) and runtime language switching.
• Added dark mode support with persistence and fixed theme-related runtime crash during settings transitions.
• Updated app shell navigation to approved order: Home, Near, Create, Community, Settings.
• Implemented News as main feed after login and created Near tab integration path for location-based filtering.
• Refined Settings UI to match approved design structure (profile block + grouped settings rows).

2) GPS and near-by news behavior

• Settings now supports obtaining location directly from device GPS (permission-based), without manual latitude/longitude input.
• User coordinates are saved in profile and used by Near flow.
• Near endpoint behavior now aligns with user geolocation + project geolocation relationship.

3) API (NestJS + Prisma) updates completed

• Added profile geolocation fields (latitude, longitude) and integrated profile update validation.
• Added /api/v1/news/near endpoint to return nearby published news based on user coordinates.
• Updated logic so nearby calculation is based on project coordinates, not free-text location parsing.
• Added optional geolocation fields to projects (Project.latitude, Project.longitude).
• Added login event tracking for successful auth sessions (IP, user-agent, timestamp).
• Maintained token refresh handling to reduce forced re-login on profile actions and session continuity tasks.

4) Admin panel updates completed

• Users list now surfaces more operational info: latest IP and total login count.
• User profile modal now includes login history entries (time, IP, user-agent).
• User profile modal includes editable GPS fields (latitude, longitude).
• Project admin create/edit forms now include optional latitude/longitude fields with validation.

5) Documentation and planning artifacts

• Updated frontend documentation links and included Flutter progress documentation pages.
• Prepared this consolidated status mail for stakeholders to track what has already been delivered in this session.

6) Immediate next focus

• Continue improving Near UX with optional region presets in addition to GPS.
• Validate project geolocation coverage in data to maximize near-by relevance.
• Keep tightening admin observability for user activity and moderation workflows.

Regards,
Robert Rascheri