[MUSIC] All right, in preparation for the third deliverable, this week what we want you to focus on is improving your app's game play. So really focusing on the game scene component in this week. Previously you built a scaffolding tha included a placeholder for the game and now it's time to start to code this up. Start to flesh it out, start to give it some excitement, some energy, some creativity, some gameplay. Time to bring your design to life a little bit. In this week in particular, what we want you to focus on is addressing the touch and sensor interaction requirements. The video that you're going to turn in for this week's deliverable needs to demonstrate that you have implemented the touch interactions and that you're also responding to sensor interactions. Now it's okay at this point if your game play is maybe a little on the ugly side or glitchy if there are little problems with it. But it does have to be stable enough so that you can demonstrate these two interaction modalities, these different kinds of functionality of your game. If you have a physical device, then you can use, you can include sensor functionalities such as acceleration or the magnetometer or the gyroscope but if you don't have the physical device, then you're going to have to use geolocation as an element of your gameplay. And so you'll be able to demonstrate geolocation as a sensor by simulating the phone's movement through a GPX route as we've looked at previously in the course. No of course if you have a physical device, you can use that too, but you have the option with a physical device. Now one of the problems here, in terms of the mechanics of how we're going to run the grading, is that because you're going to be turning in a video, of your game in progress, and if you have a physical device, now of course you can do that with Quicktime, capture a screen recording of a physical device that's attached to your computer while it's running your game, but it's going to be difficult for someone who's viewing the recorded video to know if you're actually moving your device and whether that's causing something in your gameplay to change. So in order to accommodate this, we've written a special CocoaPod that we want you to include in your game. And the tutorial this week describes how to use it. The CocoaPod's called MotionHUD, and that stands for Heads Up Display, and we're requiring you to use that and to include it in your project for this deliverable in particular. And what this CocoaPod is going to do is it's going to put a small visualization on the bottom of the screen that changes as the physical device is moved. So even though the recording will be stable, you won't see any movement, you'll know that the device was moved because the sensors are going to be, the visualization is going to indicate that there's motion in the device. And then if there's a change in the game at the same time you see the motion indicated in the CocoaPods display, you'll be able to evaluate that okay, yes, something in the game is responding to sensor input. So this week's material includes a tutorial on how to use this CocoaPod. Now as always you're welcome to improve any other aspect of your game this week as much as you'd like of course, you can improve everything as you have time and resources available to you. But the focus this week is on improving the game play, getting touch interaction and sensor interaction down. Right. Okay? So finally in order to demonstrate the functionality of the app, we're going to ask you to turn in a recording and we want you to walk through the different steps in order to show us the things that we're talking about. So we want you to record a verbal explanation of how the touch interaction controls the game, and that's important so that when we look at the game, we know what we're looking for and we can tell if we see it or not. We also want you to record a verbal explanation of how the sensors interact with the game. So again, as we look at our head's up display and we look at the game, we can tell whether or not your video displays what you described. We want you to record your application, starting and then running either in a simulator or on a physical device being recorded on something like Quick Times Movie Recording feature. We want you to step through the different screens that are necessary in order to start game play, and we want you to demonstrate game play. We want you to demonstrate the touch interaction and we want you to demonstrate the sensory interaction. And take your time and do a good job on this. And then we want to make sure that when you're doing that, that we can see the motion heads up display CocoaPod indicating motion of the device if sensor motion is the way that you're meeting the physical device motion requirements of this game. Finally, make sure that your video is no longer than five minutes long. Five minutes, you should be more than enough time to demonstrate these things. And on the one hand you want to make sure that you're very clear and you do a good job of describing these different aspects of the requirements that you're meeting for this week. On the other hand, have a little compassion for your fellow reviewers, who don't want to sit through five minutes of you just jumping up and down on a platform. All right. So have fun with it this week. Focus on the touch and the physical interaction. And keep plowing on. Thank you. [MUSIC]
