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.
Status
READY
Description
I saw that there are references to expo.dev on Shorebird's docs and we'd like to remove them, to avoid any confusion about how our service works. We heard from a few people drawing comparisons and it took us awhile to explain how we're different.
Overall, we are trying to center our updates product around developer workflows, and provide the most value there. Also, I want to make sure users don't think that Expo's updates allow more than we offer, like that we only allow updating an app's JS bundle for critical bug fixes in production and we don't support accessing any native APIs or functionality.
Shorebird is a great project and an awesome tool for Flutter developers, I'm just trying to make sure users don't get confused along the way.