Expo Go Login Requirement: Impact on White-Label Food Delivery Marketplaces
What Changed
Expo Go has introduced a new requirement for users to be logged in to both the Expo CLI and the Expo Go app to run projects in development mode. This change is currently applicable to the latest version of Expo Go for iOS and will extend to Android in the future. For more details, refer to the official Expo changelog: https://expo.dev/changelog/expo-go-57-login.
Who is Affected
This update primarily affects developers working on the customer, driver, and restaurant apps within the Good Food Pro ecosystem. Specifically, it impacts those using Expo Go for development purposes. The admin web and backend systems remain unaffected by this change. Key workflows that are touched include:
- Developer Workflow: Developers will need to ensure they are logged into the same Expo account on both the CLI and the Expo Go app to successfully run their projects.
- Testing and QA: Quality assurance processes that rely on Expo Go for testing will need to adapt to this login requirement.
Marketplace Impact
The introduction of a login requirement in Expo Go can have several implications for a white-label food delivery marketplace like Good Food Pro. Here's a detailed breakdown:
Live Courier Tracking
During development, ensuring seamless live tracking of couriers is crucial. This update means that any developer or tester working on live tracking features must be logged in on both the terminal and the Expo Go app. Failure to do so could lead to delays in testing and validating real-time tracking functionalities, potentially impacting the efficiency of the development cycle.
EAS Build and White-Label Binaries
While EAS Build processes are not directly affected by this update, developers must ensure their development environment is correctly set up with the necessary logins. This ensures that any debugging or last-minute changes made using Expo Go are accurately reflected in the final builds. For more on EAS Build, visit our EAS Build guide.
Maps and Polylines
Developing and testing map-related features such as route plotting and polylines will require developers to be logged in. Any oversight in this requirement could lead to incomplete testing of critical navigation features, affecting the user experience for both drivers and customers.
Onboarding and User Experience
While the login requirement is a development-time constraint, it indirectly impacts the speed and efficiency of onboarding new developers or testers. Ensuring that all team members are aware of and comply with this requirement is essential to avoid bottlenecks in the development process.
Action Checklist
- Ensure all developers and testers have active Expo accounts and are familiar with the login process.
- Update internal documentation to reflect the new login requirement for Expo Go.
- Conduct a team briefing to highlight the importance of logging into both the CLI and the Expo Go app.
- Verify that all development devices, especially iOS, are running the latest version of Expo Go.
- Monitor the Expo changelog for updates on the Android version of this requirement.
When to Ignore
If your development workflow does not utilize Expo Go for testing or if you primarily rely on simulators and development builds, this update may not significantly impact your operations. Additionally, if your team is already well-versed in managing multiple accounts and login states, the transition should be seamless.
For more insights into optimizing your food delivery marketplace, explore our Good Food Pro resources and consider scheduling a demo to see our platform in action.