Backend link: http://instagram-collection-backend.herokuapp.com/api/v1 Client link: http://instagram-collection-client.herokuapp.com Client repo: https://github.com/anthonyn60/instagram-collection-client
Dependencies: Rails 5.0.1, Rails 2.3.1, Postgres
Use this link for setting up dependencies: http://railsapps.github.io/installrubyonrails-mac.html
(On OSX) For Postgres, just use Postgres.app available for Mac. Link here: http://postgresapp.com/
If you're using Postgres.app, then set up the PATH variable like this: http://postgresapp.com/documentation/cli-tools.html
Run rake db:setup, then rails s. In the browser, go to http://localhost:3000/api/v1.
The front-end client is an Angular application which consumes the backend web service. I did this both for modularity as well as creating a my own feedback loop for the API itself. Putting both front-end and back-end together wouldn't allow for this.
The front-end is a single-page application which features the same menu and several templates for viewing past collections, adding a collection, and viewing posts for a collection. To ensure responsiveness and a good experience on mobile, I used the Materialize library.
I decided to add viewing past collections because that way, if I wanted to come back and view posts in previously created collections I could with ease.
I also let the user name the collection to add context to the tag time. For example, if I were to look for tags between July 28 and August 1 with the tag Red Hot Chili Peppers, I would be looking for their concerts at Osheaga and Lollapolooza. The collection makes more sense with a name added.
In the future, I would let users log in using their Instagram account and allow users to save collections to their account. This way, people are able to log in and create collages to share. I'd create a UserCollections table so Collections can be added to Users (without duplicates).
I would also look at improving to a better client web server.