While Local Storage is great, it’s not ideal: it only stores data on the computer from which the user is accessing the page. This approach does not allow for the app to ‘remember’ anything when the same user tries to access it again from a different device. For that, you’re going to need a real backend.
Where you go from here will depend in part on what you’ve learned so far. If you are on the full-stack Ruby on Rails path, hooray: you already have all of the tools you need to build your own full-fledged web app from scratch!
If not, never fear: you can learn how to build a back-end later using Node.js … or you may decide to learn Ruby on Rails after all. For now, you can outsource your backend functionality to a Backend-as-a-Service (BaaS) company like Firebase or Apigee.
For those of you who are on the full-stack Ruby on Rails path, the next step is obvious: you get to build your own backend with Rails! In preparation, reread the Rails lesson on building an API to refresh how to set up a Rails backend that can handle JSON requests.
If you skipped Ruby and/or Ruby on Rails or are on a different path, you’re not quite ready to build an entire web app from scratch. The good news: you don’t have to! We will provide you with resources that guide you through setting up your backend on Firebase.
content_forstuff at the bottom.
This section contains helpful links to other content. It isn’t required, so consider it supplemental for if you need to dive deeper into something.