# Week 8

## Everyone
(15/11) discussed possible implementations of App1 and App2.

## WebRTC
(15/11)Attempt to finish milestone M2
(17/11) Finished M2

## Sensors

## QR

## REST
(15/11) First attempt at implementing user interface for milestone M2
(20/11) Implemented M2 with UI + tests

## App1 (WebRTC + sensors)
Implement a game played by using the sensors in a smartphone. For example, the sensors can be used to move around a pawn.
The app will have the ability to communicate with other player/players and share data about the game through WebRTC.
Other users on the web page that don't want to play can spectate the players. This will require a button to participate.
The game still has to be determined.
Tests can be run to see if the following works:
A connection is made with other players who want to participate in the game.
The data is send and received successful through the established connection.
The game responds to the correct movement of the player.

Read and approved by: William De Deyn,...

# App2 (QR + REST)
A choose your own advendure type game that can be played through the browser.
Each level/puzzle can be loaded on a different URL and finishing a level/puzzle provides a new URL as to progress the game. Puzzles can be anything from soduko to a simple word pun. These puzzles could also be generated based on a seed, as to introduce replayability by changing the seed. A leaderboard can be made to compare stats between players.
To be able to return to a previous URL, QR-codes will be used. This provides both save points to a player as well as a way to share interesting puzzles with friends.
Tests can be run to see if the following works:
QR-code generation and reading brings us to the right page
Puzzles are solvable
Giving a correct solution provides a working new URL
Speedrun leaderboard correctly displays/updates statistics

Read and approved by: Tim Borremans,...