This repository has been archived by the owner on Dec 26, 2019. It is now read-only.
SPIKE - Using react-native to oauth into doorkeeper with expo #307
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
ghost
assigned 
zspencer
force-pushed
the
zs-try-making-react-native
branch
from
3894d24 to
c7de5ad
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I did a bit of investigation into how to throw together a react-native app and get it published easily, and expo.io seems pretty solid.
I didn't get a chance to poke at apollo or graphql-ruby just yet, but I think they should be pretty straightforward to integrate with expo so we can persist data in the Rails land and build flexible, performant react-native on the front.