One question :?:

[MichelDiz]

Hi, I'm following your project. Because I'm interested in learning about Join Monster and GraphQL.
I've come to ask you why you're adding both Schema and SQL within the same React Native project.
When will you generate the APK (or IOS), will not you have to separate the stacks?

Would not it be better to create a Node server? To feed the React Native.

Best Regards

[tslater]

I actually am going to have a server. This is so that I can use relay offline. The app will have a sqlite database to use relay and graphql offline, and sync with the server.

[MichelDiz]

Very interesting. Would this be the best current solution? To use SQL lite as cache?

offline first! xD

[MichelDiz]

Why not use Apollo? there is a project that uses Join-Monster and Apollo.

look this https://dev-blog.apollodata.com/apollo-link-the-modular-graphql-network-stack-3b6d5fcf9244

[gardner]

I just started an example as well https://github.com/gardner/react-native-apollo-client-join-monster

It uses join-monster-demo as a backend. I dockerized it in the case that you prefer that method for easy setup: https://github.com/stems/join-monster-demo/pull/7

There are a lot of moving parts and subtleties. I am still trying to work out like navigation, pagination, and debugging.

[tslater]

This is to build apps that work completely offline, with complex logic. You can use graphql on the client, without the server. I am next going to do relay offline. This repo won't work until i patch an issue with running join monster in react native in join monster.

[gardner]

Sweet. I'll keep an eye in this repo. I am having trouble with Apollo Client on RN as well. The queries sent by RN are different than graphiql.