As a CONSUMER I want to be able to get demo from HELPER

[mhanratty]

1. Helper tells Consumer about demo and asks them to tap the "Start Demo" button when they see the prompt in the app.
2. "Start Demo" prompt animates down from the header of the app.
3. Consumer taps "Start Demo"
4. "Start Demo" button toggles to "Stop Demo" button.
5. Consumer taps "Stop Demo" button.
6. Start/Stop Demo app disappears up into the header.

Questions/Concerns:

• Start/Stop button is a simple toggle. Shows up in the same place in the UI for Consumers and Helpers (for the win!) Helper "Start Demo" is persistent, for Consumer "Start Demo" only appears after Helper has tapped "Start Demo" (oops...might need to rethink Helper UI 'cause Helper could tap "Start Demo" but Consumer might not tap it back!)
• Need to give Helpers good boilerplate text to introduce demo/screen sharing option to Consumer. @HerminaC any ideas for text?

[mhanratty]

I redesigned the demo flow for the Helper and Consumer so that it reflects more of an invite/accept model.

1. Helper taps "Send Invite" to send an invite to the Consumer to start a demo session.
2. Helper receives message that demo was sent. Consumer receives invite to "Reject" or "Accept" the demo. Consumer taps on "Accept"
3. Helper and Consumer see a message that the demo is live with a button to "End Demo." Helper (after going through demo) taps "End Demo"
4. Helper sees confirmation that demo has ended and a call-to-action to "Send New Invite" if they want to demo again. Consumer sees message that Helper ended the session and an "Ok" button.

[mhanratty]

I showed this at a design review and got the suggestion to instead of using UI to accept the demo or end the demo, using key commands typed into SMS with messages inline like. For example, the user sees in the chat "To accept the demo please type in ACCEPT" and then types in "ACCEPT" in SMS. It's old school but saves us a lot of UI and makes the chat less crowded :)