Closed WSINTRA closed 4 years ago
Absolutely, Will! Sounds like a Go. You know Flatiron Peeps love a Good Rails Back End. I've been familiarizing myself with the React Native Typescript so far on the Master Branch., though we may pivot to go straight React Native if it's causing too much a headache. I just discovered Navigation Drawer, so will plan on implementing Stack Navigator and Drawer.
I'll also look into firebase too and weigh up the pros and cons, I think for the sake of learning a new skill I would like to incorporate a noSQL backend,
And of course, GraphQL, I'll be back in 8 hours!
@WSINTRA So Maybe we set up firebase? I just added you to a Firebase project I started in the console at Firebase.com. I will need to Bone up on GraphQL Quickly. Glad we're doing the EdX Course.
So far my understanding of graphQL is this, its not an actual DB but a layer that exists between the backend and frontend, its purpose is to reduce the amount of data a frontend would fetch/pull from a http request. It gets more complex than that but as far as I can tell it is a specification that deals with the problem of fetches pulling more data than needed when grabbing data from the backend which on a mobile device would be a problem. I'll keep researching...
I'm gonna follow this and see how it goes. https://www.howtographql.com/react-apollo/0-introduction/
See PR #4 for details on the implementation. created a server folder, in the main project, when beginning development don't forget to yarn install any dependencies.
backend created in /server PR #4
Can I request we build a backend DB that handles requests for data on products and customers.
Have this thread as a discussion on the design and choice of backend, maybe a rails backend in PostGresql, What models will we need, and what attributes will those models have? etc etc