Design Docs Review #1

[jliversi]

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

• For handling "recent activity", this is probably best implemented during transaction history or just as its own bonus MVP.
• For friending, you can neglect the emails real Splitwise sends out, at least to start. Instead, restrict it to the functionality of adding friends already on the platform.
• As to that previous note, the "invite pending" only happens when you enter an email that isn't associated with a splitwise account. Because you won't use emails (at least to start), there shouldn't be any "pending" element, at least not to friending.

SCHEMA

• Can remove invite_confirmed boolean on friendships table, as if you have two user ids, they're both on the platform and there is no invite confirmation.
• If eventually implementing email invites, that will likely need to be it's own table (with a inviter_id and an email address) as these operate pretty differently from in-platform invites.
• Expense detail should include a notes column in addition to the description

[philipk8]

Ok, thank you. All makes sense to me. Will update files accordingly.