History log of /expo/ios/Tests/Environment/EXClientTestCase.h (Results 1 – 2 of 2)
Revision Date Author Comments
# dc898499 10-Dec-2020 James Ide <[email protected]>

[ios] Expo Client -> Expo Go (#10847)

The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To h

[ios] Expo Client -> Expo Go (#10847)

The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To head off confusion with default development clients, this commit renames the app store development client known as "Expo Client" to "Expo Go".

"Expo Go" is the name for the App Store and Play Store development clients that are published under the Expo team's accounts and currently have support for multiple SDK versions. Expo Go is the fastest way to get started. But we've seen billion-dollar companies use the managed workflow for production apps, so names like "Expo Lite" or "Expo Start" wrongly communicate that the app is just for demos or getting started. "Expo Go" implies it's a good way to get started and also not the entire workflow, but also a workflow that can hold its own.

In this commit I focused just on iOS (native). Android (native) and Home need to come later. I also changed "experience" to "project" in a few places to start cleaning up our terminology.

Tested by running the app and verifying it shows up as "Expo Go" on the home screen in a simulator.

show more ...


# 6bc76542 12-Jun-2018 Ben Roth <[email protected]>

Split XCTest cases into superclasses by runtime environment

fbshipit-source-id: 42bf9f9