{"id":6728,"date":"2020-10-26T11:08:58","date_gmt":"2020-10-26T15:08:58","guid":{"rendered":"https:\/\/courses.ideate.cmu.edu\/60-212\/f2020\/?p=6728"},"modified":"2020-10-28T09:48:33","modified_gmt":"2020-10-28T13:48:33","slug":"tale-mobiletelematic","status":"publish","type":"post","link":"https:\/\/courses.ideate.cmu.edu\/60-212\/f2020\/ayk2andrew-cmu-edu\/10\/26\/tale-mobiletelematic\/","title":{"rendered":"tale-mobiletelematic"},"content":{"rendered":"

S<\/strong>hake2Break\u00a0<\/strong><\/h3>\n

( code<\/a> | app<\/a> )<\/p>\n

Shake2Break is a quick competitive phone shaking game that could be used to solve a minor dispute by deciding the rank\/order of people. (2 players required to play)<\/p>\n

Project Reflection:<\/span><\/p>\n

This project was a nice opportunity for me to learn how to implement client data \/ server data in server.js, as well as how to utilize sensor data from a mobile device. Although I was initially intimidated by the idea of using server.js and mobile sensor data (as I’ve never used nor seen a code for either of them before), I found implementing server.js and manipulating mobile sensor data very interesting and fun to play with. Since it’s my first time using those, I wanted to begin with a project that is simple yet to the point: an active synchronous shaking game. The server requires two players synchronously present to begin the game. Once there are two players, the competition begins, where each player can shake their mobile device back and forth to engage with the accelerometer inside the device, specifically the accelerometer data along the z-axis.<\/p>\n

Demo Video:<\/span><\/p>\n