Build console to manage Superminds
Goal
- Create management console for users to easily accept and respond to Supermind requests or reject them
What needs to be done
QA
UX/Design
Note: All design links below refer to the web UI.
- The SuperMind (console) is accessible via the
More Menu
within the main navigation. - Users will also be directed here from email and push notifications.
- This SuperMind console is separate from the Boost console.
- This console displays only the incoming requests Requests received
- And outgoing requests Requests sent
- The settings icon contained within the above designs will link directly to the SuperMind settings (within the Settings Area).
Requests Received
- A user may either reply to a request, or choose to reject it.
- A producer has [72 hours] to respond to a request.
- Any expired request will disappear from
Requests Received
- Requests are ordered from new -> old.
- Each request will also display any meta data relevant to the request.
- Offer amount
- Twitter post
- Content type: Text, Video, Image, Remind.
- If the user clicks reject, funds are refunded to the consumer and a notification sent (As detailed within notification)
- Where the user clicks reply, the composer is launched.
- Note: If the is the users first-time replying to a SuperMind request, they will need to read and agree to the relevant terms of user.
- After doing so, they’ll then be directed to the composer.
- If there’s there are specific content requirements, this could be communicated within the placeholder copy. (e.g. video required).
- Workflow for the above detailed here -> Accept request workflow with T&Cs
Personas
Experiments
Acceptance Criteria
-
...
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Michael Bradley