2 ms·
Damn, between this and sketch + create react native app, it's the week of 1-step-apps. Is there an easy way to eject into a full blown graph.cool app? It seems
by faceyspacey 10y ago
Damn, between this and sketch + create react native app, it's the week of 1-step-apps.
Is there an easy way to eject into a full blown graph.cool app? It seems you can't take any of your schema and use it as a starting point in graph.cool. From a business perspective, wouldn't that be the point? Perhaps I'm missing something though.
- sorenbs 10y agoJust made a comment on the Expo Sketch thread to that effect. Imo Expo + GraphQL is a killer combo. To your question (Graphcool co-founder) - Our vision for graphql-up is twofold: 1) Enable you to easily spin up a fresh GraphQL endpoint in your automated tooling. Think ci test servers. 2) Lower the barrier for people new to GraphQL. I'm especially excited about the second point and looking forward to see how the community will leverage graphql-up to make tutorials and documentation more accessible
- faceyspacey 10y agoI get that. So are there no "graduation" strategies to ur main product that you see as useful? Basically I'm trying to understand how far this takes you and what "up" is missing in comparison to the information you provide to your core product, "cool," to produce schemas. It would be very enticing if you said there is a 1-step solution to graduate your graphql-up server to a full blown graph.cool app. Are there really no useful synergies there? Is it a secret lol?
- sorenbs 10y agoIf you need a full blown API you should just sign up to Graphcool from the start :-) We have a generous free plan, so there is really no downside. I think you are right that it could be useful to be able to import a graphql-up api to graphcool, so that is definitely something we will consider. What we will do for sure is allow you to create a Graphcool project based on a Schema Definition, just like with graphql-up - look for that in the near future.
- faceyspacey 10y agoI'm excited!