kennethlng / nmbo-app Goto Github PK

The button routes the user to a checklist page with no title.

Probably due to header tag pointing user to wrong site

• Header account button should show display name
• Project task writes should keep track of display name of users that created new tasks and completed tasks.
• project_users documents should keep track of display names of members.
• Think about how display names or avatars (emojis) can be embedded as part of a task. E.g. user who completed task has avatar/emoji filled in the bubble.

A checklist is considered "updated" when:

• A new task is added
• A task is completed

All user_project docs for a given checklist should include an updated_on field.

This special time stamp field is for notifying the user when there are important changes to a checklist. This is similar to a chat app. In chat apps, you only get a notification when a user has sent a new message. You don't notifications for other less important things, such as a user changing their name, or a message has been deleted.

User accounts are anonymous by default. On user creation, the user account should be assigned a randomized placeholder display name, similar to Google Docs' "anonymous animals". Future features, such as assigning tasks and viewing checklist members, will require being able to identify who is a part of the checklist.

• Update display name
• Update email
• Update password
• Verify email
• Forgot password

Options:

• Show my checklists only
• Sort by title
• Sort by last opened
• Sort by last created
• Sort by last updated

If a user changes the title, the title tag in the header isn't updated in real-time. So when the user shares the checklist it shows the old checklist title in the link preview.

Menu:

• Leave checklist
• Delete checklist

Checklists "disappear" in 7 days.

All checklists have a special modified_on timestamp. This timestamp is a special relevance metric.

Only checklists that have been modified within the last 7 days appear on the home feed.

In a chat app or file management app (e.g. Google Drive, Dropbox), messages and files are typically ordered by last modified. You almost never scroll down past the initial feed because you only care about what's on the top. In fact, in a messaging app, you either only open the app when somebody messages you, or you want to message somebody that you already message quite frequently, so their name is already at the top. For people you don't message frequently, you either start a new message, scroll down, or perform a search for the message.

The recent checklists feed can be designed in 2 different ways:

1. Like Stories, they will sit horizontally at the top. The rest of the page can be used for adding/editing a checklist.
2. Like Facebook or IG, they will sit vertically in the body of the page.

Closed checklists are archived or deleted.

• Each checklist should have a sub collection for tracking each user action, such adding a new task, deleting a task, and completing a task. Each record includes the user (id and displayName) that performed the task and the time stamp of the action.
• Each checklist should keep track of key data, such as total number of tasks, number of completed tasks.
• When users visit checklists, they want to see who added certain tasks, who completed certain tasks, etc.

When users visit a checklist page for the first time, the checklist tasks don't load. You get a FirebaseError for permissions denied.