Design User Flows

[mediafinger]

User Flow

Draft how the different flows should work.

User Registration

• [ ] user visits the website and creates an account
• [ ] user receives an email invitation to create an account
  • [ ] the same flow could be usable for a waitlist feature with small adaptions

Onboarding

• [ ] after registration, what will a user see, which actions can they take, how will they be guided?

Joining a team

• [ ] explain that you need to be part of the team to publish content
• [ ] offer to create a team
  • [ ] explain that free users can only be in a one-person "team", but paying users can join them
  • [ ] explain that when paying for a team you can invite other users to invite you
• [ ] explain how to join an exiting team
  • [ ] asking to become a member
  • [ ] receiving an invite

Homepage / Stream / Content Discovery

• users will see an overview page with the latest published content
• updated experiences and journeys should be pushed
• additionally popular and featured content will be displayed
• the overview page will be filterable by tags, teams and users
  • paying users can store this filtering to quickly select it again
• later a search functionality could be added
• users will be able to follow teams, journeys and experiences, to always see all their updates

• [ ] which content will be displayed to users that not follow any or very few teams or journeys?
• [ ] which content will be displayed to users that check the stream often?
• [ ] how will the content be presented?
• [ ] what interactions are possible?

Content Creation

• [ ] how are team members able to create content
• [ ] how will the publishing flow work
• [ ] how are visibility status changes communicated

Interactions

Reactions and Bookmarks

• [ ] decide how users can react to content
  • [ ] positive: 👍 😄 🤔 ⭐ ❤️ 🔖
  • [ ] negative: 😮 😢 😱 😡 👎
• [ ] allow 👎🏼 but only display them to the user (never tell the team, never display them anywhere) and use them for a popularity ranking
• [ ] don't show 🔖 bookmark as reaction, keep them as reference to the user, and use them for a popularity ranking
• [ ] all other reaction could server as "bookmarks" for paying users as well
• [ ] users can chose one reaction for any piece of content - and change this whenever they like
• [ ] reactions are only visible to the user that left it and to the team that created the content
• [ ] do not even display a number of total reactions, but maybe something like: this content is
  • popular (lately)
  • very popular (lately)
  • incredibly popular (lately)
  • massively popular (lately)

Comments

• [ ] content creator can restrict comments, but when they are permitted, users can leave comments on
  • [ ] memories, chronicles, experiences, journeys
  • [ ] comments are only visible to the user that wrote them and the team that create the content
  • [ ] all comments appear on a team board as well
  • [ ] teams can answer to comment, which will add to the thread
  • [ ] the user will be informed about the comment by a notification
  • [ ] no one else will see the interaction
  • [ ] both sides can decide to close the thread whenever they want
  • [ ] limit number of unanswered comments for free users?!

Followings

• [ ] users can follow
  • [ ] teams
  • [ ] journeys
  • [ ] experiences
• [ ] they will receive all updates in the stream
• [ ] the teams will know who follows them
• [ ] the number of total followers will be displayed for each category

Team Board

Visible to everyone in the team - an no one else - includes

• [ ] newly created insights
• [ ] newly created memories, experiences, journeys - and their visibility changes
• [ ] comments and their threads
• [ ] reactions
• [ ] followers
• [ ] vanity metrics (for paying teams)

Direct messages

• always allowed between team members
  • when a user contacts a user for the first time, the other side has to give permission first
• users can block all or any users from contacting them
• no attachments in messages
• links are allowed, but no preview rendered (and maybe a warning added)
• messages support markdown and emojis

• [ ] only for team member under each other
• [ ] only paying users can make the first contact to another user
• [ ] free users can always answer, but not contact (or only message paying teams?)
• [ ] everyone can limit who can contact them

Content moderation

• [ ] users with special roles should be allowed to flag content
  • [ ] decide how flag content is handled: trigger warning? made invisible & asking team to adapt?
• [ ] #44
  • [ ] decide how to handle blocked content, fingerprint, so no re-upload of insights would be possible?
• [ ] comment threads and direct messages can be reported and investigated
  • [ ] consequences?
  • [ ] allow users and teams to block single threads, DMs or all communication with other users
• [ ] wen users or teams have to many incidents they should be
  • [ ] "downgraded" (how?)
  • [ ] warned
  • [ ] (temporarily) blocked from publishing content, writing comments or messages
  • [ ] finally banned from the platform