Design Docs Review #1

[jliversi]

Great start on your design docs, here are my notes so far:
MVP LIST

• "Login required to access key features". What are the key features? Be specific here about what exactly a logged in user can do that a logged out user cannot.
• For friends, does "adding by email" indicate a mailer and an email sent out? Or just that if the user with the email exists on the site, they will be added as a friend?
• Will there be a friends index page for viewing friends? Be explicit with what will be built at each MVP.

SCHEMA

• Can a user ONLY be in one group? If a group can contain multiple users, and a user can be in multiple groups, than you should remove the group_id from users table and instead have a joins table between groups and users.
• Do you need a history table? Or can this just be the generated from bills being associated with a user or group?
• Bills need a description column
• You don't need a group_id on comments because you can get the group through the bill_id.