auden is an open-source, hackable audience engagement software, supporting multiple features, such as Live quiz and Voting system. Its hackable architecture allows developer to modify and add features to fit the event.

We used auden in Code in the Dark Thailand #3: CNX 2019 to encourage attendees to participate in the event more easily.

Instead of requiring all contestants to register beforehand (which takes quite a courage), a live quiz system allows anyone in the event to compete to become a contestant in each round.

Because this app supports multiple features, when it’s time for voting, attendees can vote on the same webpage without the need to switch between multiple apps (such as Mentimeter, Slido, and Kahoot).

Each feature (called scene) contains 3 user-facing components:

• The Audience component is a mobile UI for audience to engage in the event.
• The Presentation component displays what the audience will see on the big screen.
• The Backstage component allows event staff to manipulate the scene (such as activating a question, displaying scoreboard, etc.)

Play a multiple-choice quiz game with any number of participants, similar to Kahoot.

Create a live poll to gather audience’s opinion, similar to Mentimeter.

It is a webapp, built on top of:

• React!
• TypeScript!
• Grommet!
• Firebase Real-time Database!
• fiery 🔥!
• Hooks and Suspense!

1. Set up Firebase Authentication to allow sign in using Facebook.

2. Sign in using the web app, and obtain the Firebase user ID by running firebase.auth().currentUser.uid in the JavaScript console.

3. Make the user an admin by writing true Firebase Database at /admins/$uid. Admin users can read and write anything.

Everything is organized into “scenes,” which represents a type of situation in an event.

For example, you can have a scene for a quiz, for a survey, for voting, for announcements, and an idle scene when there’s nothing interesting going on.

Each scene has:

• A presentation display, for projecting to a large screen.
• A audience UI to let audience engage with the event from their mobile phone (or desktop).
• A backstage UI to manipulate the scene.

Data is structured in Firebase this way: Namespace → Name → Access pattern. This allows using same Firebase rules across all scene types, eliminating need for us to deploy new rules when adding new scene types.

Available access patterns:

• public-read — Anyone can read but only admins can write. Examples:
  • main → state → public-read → showLeaderboard
  • main → settings → public-read → maxVotes
• personal — Anyone can read, however, each user can write to their own personal slot. Examples:
  • main → poll → personal → $uid → selectedOption
• events — Anyone can read. Each user can publish events. Append-only. Examples:
  • main → chatMessages → events → $eventId
• private — Each user can read and write to their own personal slot. Examples:
  • answers → $questionId → private → $uid → answerId
• inbox — Each user can read data assigned to their own personal slot. Examples:
  • main → role → inbox → $uid
• secret — Only admin can access
  • main → questions → secret

An instance of a scene. It has:

• Data stored in Firebase. How data is used is determined by scene type.

That can be one active screen at a given time.