Set Up Mobile Development Environment & Configure Expo Go

[PESolut]

Integrate the mobile frontend codebase into the existing project structure, ensuring dependencies are set up correctly and Expo Go is configured for testing on both local devices and workstations.

Tasks:

• [x] Import the code from the old codebase
• [x] change backend WF so it only triggers upon changes that change the backend dir
• [x] Set up all project dependencies and ensure the mobile frontend runs correctly in the development environment.
• [x] Configure Expo Go for iOS devices, enabling local testing on a physical device.
• [x] Configure frontend to 'speak' to the deployed backend
• [ ] Document steps for technical users to replicate the environment setup and configuration process.

Why This Matters:

Expo Go streamlines testing and development of our React Native app by allowing instant feedback on changes across devices without building separate native versions. It also ensures cross-platform compatibility, speeding up development while utilizing features like push notifications and camera access.

Acceptance Criteria

1. A developer is able to build the mobile app via Expo Go and see dispensaries, login, and test user flow at the current state.
   • Developer should confirm the following flows:
     • [x] Dispensary listings load successfully.
     • [ ] #18
2. Documentation is reviewed for clarity and completeness.
3. Ensure new backend WF only triggers upon changes in the backend and not within anywhere else in the monorepo

[PESolut]

Import the code from the old codebase:

This task involves cloning the old repository onto the workstation and integrating it into the monorepo.

EDIT: oct21 738

its important to change the wf so that the backend wf is only triggered when changes happen on the backend; if im thinking correctly It is essential to modify the workflow so that the backend workflow is only triggered when changes are made specifically to the backend code. In most cases, minor changes (e.g., adjustments to a button on the login screen) do not necessitate a rebuild of the backend. Implementing this change will optimize our build process and improve efficiency.

[PESolut]

README drafts for frontend

# Demo Options

This section outlines the different methods available for demonstrating the mobile frontend of our application. These options cater to various audiences, ensuring an effective showcase of our app's capabilities.

## Option A: Hosted Expo Go Server with QR Code Access for Expo Go

We host the Expo Go server on an EC2 instance, allowing consistent access to the latest build of the app. This setup enables a CI/CD workflow that automatically deploys new code changes, ensuring that demos always showcase the most recent features. This method is ideal for formal presentations where a stable and controlled environment is essential

For tech-savvy users, we provide a QR code that links to the latest version of the app via Expo Go. This option allows users to quickly access the app on their devices by scanning the QR code, enabling them to interact with the app in real time. This approach is convenient for informal demos or when users prefer to explore the app themselves.

## Option B: Video Demo for Non-Technical Users

To accommodate non-technical audiences, we create a polished video demo that highlights the key features and user flows of the app. This video can be easily shared and viewed without requiring any downloads or installations. It provides a clear and engaging way to showcase how the app works, making it accessible to everyone.