App Features

This is pretty obvious but we need the ability to add/delete/update resources to a list. It would also be nice to be able to have resource categories -- let's say Stackoverflow, Android documentation, etc.

@jen16 certainly if you want to start on the API go ahead, but do we also have the optino to create a mock data set for testing purposes. This is what I typically do leaving connectivity for later. That's just a preference on my part, but I wanted to mention it.

I totally agree we need to talk about features, but what is our Minimum Viable Product? What are the bare-bones features of this app that make it functional. It's a good idea to start from there, get it to work and then build up features from there.

And yay! We got our channel! Woohooo!!!!! :laughing: :clap:

@jen16 to build upon your thought about creating the Google Sheets API, there are two things to think about with this.

1) In order to hook into the Google Sheets one has to get a SHA1 fingerprint and then a Signing-certificate Fingerprint (see resource attached). Do note that there is a limit on the number of times per day that any one certificate can be used - i.e. access the sheet on without having to pay. If this gets a lot of downloads and use, we'll need to see if someone will build a back-end and API. For now I think Google sheets works because it does what we need without having to stray too far away from learning/implementing Android. But I'm totally open to other suggestions as my technical knowledge is narrow - mostly having to do with Android.

2) At Google I/O 2017, the Android team came out with code architecture recommendations as well as new Architecture Components (and they're awesome!). One of their suggestions is to create a Repository which serves as an intra-app API for any and all data sources - be they retrieved from an online source, persisted in an app db, another app's Content Provider, etc. By using a repository we can easily use mock data for now OR you could go ahead and get the connection to the sheet working. Honestly your expertise is far greater than mine, so I defer to you.
Assuming all of us are going to use this app/project in our portfolio though, I think it might be a good idea to implement the structure that Google is pushing. I have attached the Architecture Guide, and there is a great visual representation about halfway down the page along with great code examples.