Design Documents

[trevoruptain]

It looks like you've put a lot of thought into your proposal. Really nice work on the database schema - it might change a bit when you start coding but I can't think of anything to add.

I have just a few suggestions for your state shape:

• [x] Don't forget to add keys for 'ui', 'errors', and 'session' outside of the entities object. Instagram has a really cool transition effect when the page is loading.
• [x] Think about calling it 'bio' instead of 'user'.
• [x] Posts need an 'image_url'
• [x] You won't retrieve a user's followers unless you click the link on their bio, so it might be useful to have a 'followerCount' stored on users

Great work! This looks like a good plan for cloning Instagram so far.

[trevoruptain]

Now that you've finished your proposal, there are a few more things you should do to get it in tip-top shape:

• [ ] Your proposal could use some Markdown formatting. Please see the Sample Proposal (https://github.com/appacademy/bluebird/wiki) and the Markdown Cheatsheet (https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)
• [x] Make sure your MVP list matches up with the Instagram requirements on this page (https://open.appacademy.io/learn/swe-online/full-stack-project/mvp-checklist)
  • [ ] Each frontend route should be mapped to a component, including the Splash page (see https://github.com/appacademy/bluebird/wiki/frontend-routes)
• [x] Include the Root, App, and NavBar in your frontend routes (if you have them)
• [x] Backend routes look good - however, I recommend avoiding camelCase for your routes