docs: Remove development client usage for Expo #1271
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I have signed the CLA! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I noticed that the current documentation mentions development clients with Expo, and then in the next sentence, it mentions development builds. Conceptually, both of these are the same for user-facing information. A development build is something that contains
expo-dev-clientlibrary (the library is called development client).Removing usage of development clients makes sure that information is focused on Expo Go and development builds, and for a developer using this library in a project created with Expo, both of those methods work.
Reviewers’ hat-rack 🎩
N/A
Screenshots or videos (if needed)
Checklist