Chatter

A chat application

Design Considerations and decisions

Data Structure

Following is the structure for a user document

{
  id: string; // "id for a user",
  number: number; // "user's number",
  name: string; // "user's name"
}

Following is the structure for a message

{
  id: string; // "id for a message",
  message: (string | blob); // "message body",
  type: ENUM<"TEXT">; // "the type of a message"
}

Issues faced

• Setting up Realtime Connection for all users
  • Ability to set up one connection multiple subscriptions
  • State update across chats