Note: This card includes a lot of features which probably should be weaned down for the sake of MVP. Those decisions have not been made yet, and will likely be reflected in the issues linked below.
Due to my limited experience with PWA, this user story does not take into account setting device permissions.
[ ] A user should have the option to Broadcast or Amplify and have consistent access to a menu (#9) which includes privacy and audio settings
Broadcast:
[ ] When Broadcast is selected, the user will fill out a form about the event. This could include, but is not limited to title, host/organization, mission statement, description of the event, time, location, related links and their labels, password(for access to the event; if one is not provided, one should be generated).
[ ] Once the Broadcaster has submitted the above information, they should see a page with settings which includes start broadcasting, share (#10), event details
[ ] When the Broadcaster selects start they are taken to a page which allows them to mute/unmute, send a brief text alert, end the event and be shown their audio input level. When broadcasting, these tools persist throughout the app in a tool-bar.
[ ] When the Broadcaster ends the event, they are asked to confirm this decision and reminded that ending the event will end it for all Amplifiers as well
[ ] Extension: Broadcasters can select co-emcees and pass Broadcasting power to other groups. Co-emcees become the Broadcaster automatically if the Broadcaster is disconnected without ending the meeting. If there is any text messaging built into the app, the co-emcee receives those messages from the Amplifiers.
Amplify:
[ ] When Amplify is selected, the user will need to provide a meeting ID and a password. If QR codes are implemented, they will also be presented with the option of taking a photo of a QR code
[ ] Once they've successfully joined the event, they can hear audio from the broadcaster
[ ] The user will have the options to mute their connection to the event, leave the event, share (#10) the event, and see the incoming audio level. These tools will remain active in a toolbar on other parts of the app as well.
[ ] When they decide to leave the event, the user will be required to confirm that they are leaving.
Note: This card includes a lot of features which probably should be weaned down for the sake of MVP. Those decisions have not been made yet, and will likely be reflected in the issues linked below.
Due to my limited experience with PWA, this user story does not take into account setting device permissions.
BroadcastorAmplifyand have consistent access to a menu (#9) which includesprivacyandaudio settingsBroadcast:
Broadcastis selected, the user will fill out a form about the event. This could include, but is not limited totitle,host/organization,mission statement,description of the event,time,location,related links and their labels,password(for access to the event; if one is not provided, one should be generated).start broadcasting,share(#10),event detailsstartthey are taken to a page which allows them tomute/unmute, send a brieftext alert,endthe event and be shown their audio input level. When broadcasting, these tools persist throughout the app in a tool-bar.endsthe event, they are asked to confirm this decision and reminded that ending the event will end it for allAmplifiersas wellAmplifiers.Amplify:
Amplifyis selected, the user will need to provide ameeting IDand apassword. If QR codes are implemented, they will also be presented with the option of taking a photo of a QR codemutetheir connection to the event,leavethe event,share(#10) the event, and see the incoming audio level. These tools will remain active in a toolbar on other parts of the app as well.