HTML and CSS Reference
What Doesn't the App Do?
Equally important—if not more so—than the list of what the app does, is the list of what it doesn't do. This will inform
decisions about whether or not a feature should be included in the app.
This app is intended to be a tool for presenters and attendees of an event that is occurring live and is most likely
going to be used in the same physical space as the other attendees. Therefore, the app should not :
Attempt to replace live discussion.
This means the app does not allow comments or answers within itself; it is solely there
to present questions, not to answer or clarify them. Allowing discussion within the app
could distract from the actual presentation.
Provide any additional information about the session.
The app doesn't tell attendees what the session is about or provide any resources.
That focus is still on the presenter because this app is not meant to take part in the
presentation, only the Q&A.
Provide any organizational tools for the presenter.
The presenter's dashboard is simply a list of questions, ranked by popularity, that can be
marked as “answered.” This is not a tool to help presenters get better at presenting; it's
there to help them field questions from the room.
What Roles Will Users Play?
Now that we know what the app does—asks and answers questions—we can define the different types of users
that will interact with it.
Because this is a pretty simple application, there are only two user roles: Presenter and Attendee.
A presenter will create a room on the app's home view and then share that room with the people in attendance using
a link that will be generated upon the room's creation. He will be provided with a button that ends the session, which
closes it to further questions.
As questions are asked, they will show up on the presenter's screen in real time with one UI element that allows
him to mark the question as answered.
Attendees will join a room by either clicking the link provided by the presenter or by entering the room's ID, which will
be the part of the URL that isn't the domain name (i.e., http://example.com/ 1234 , where 1234 is the room's ID).
Upon joining the room, attendees will see questions that have been asked in this session previously (if any exist)
with an option to vote up that question. Any new questions will appear on the screen in real time.
There will also be a form through which an attendee can ask her own question, which will be added to the list of
questions already upvoted by her.
Finally, there will be a link to email the presenter directly if a question wasn't answered satisfactorily or if the
question isn't appropriate for the whole group.