This being a week before our final presentation, we made sure to have a build in the beginning itself to get feedback from our advisors before handing over the project to our clients.
Other than that, we worked on the following this week:
- Creating a new build
- Updating website
- Promotional video
- Demo Video
- Post mortem report of our game
- Final Presentation
- Archive
- Teacher’s guide
- App Polishing
- Project Hand off
- Adding our game to app store
CREATING A NEW BUILD:
For the new build, we focused on the following things:
- feedback from the showcase
- client requirement
SHOWCASE: Our showcase went really well and everyone were really impressed by our game. One of the major feedbacks we got from the showcase was to implement a better design for re-grouping (carryover) in subtraction.
CLIENT REQUIREMENTs:
- addition of a regrouping mechanic with a cut-off symbol and graphical representation of carry over
- re naming the app to ‘CompuBots’ in the build we handover to them
NEW BUILD:
Working on the above mentioned feedbacks, we started with implemention of a new mechanic for the regrouping exercise in subtraction.
REGROUPING FOR SUBTRACTION:
The following shows the revised mechanic we came up with for the subtraction re grouping exercise
As you see from the pictures, if we take an example of 66-8, Once they tap all the screws on the numbers down, the remaining two red screws on the digit 8 (which are left behind after the screws from 6 in the ones place take over the ones on number 8) can be taken over by the screws which we get by tapping on the 10 slot screw (now moved to the right corner near the 6 in the ones place) from the number 6 in the tens place which automatically shows it being cut off to number 5. By doing this they can count the screws and get an answer, 58 in this case.
REGROUPING FOR ADDITION:
Though not mentioned, we worked on adding a revised mechanic for addition regrouping as well to maintain consistency in the game mechanic.
Addition has a similar game mechanic for regrouping except for one thing, the placement of the carryover number. In this case, we place the carryovr on top of the number to which it is being carried over.
The following shows the pictures depicting the same:
DEMO AND PROMOTIONAL VIDEOS:
We created a demo video from our final build to present it in our final presentation and also worked on the promotional video which has all the team member talking about their experience and role in the game building process. We also had the teached, principal and the client talk about their expectations, involvement and feedback as well.
TEACHER’S GUIDE:
We came up with a teacher’s guide including all the deatils on how the game works. In our teacher’s guide we made sure to include every aspect from how we followed the touch math for our design to explaining the exercises and progress flow in detail.
POST MORTEM REPORT OF OUR GAME:
We worked on the post mortem repot of our game wherein we included all the detailed explanation on our work flow from pre planning-research-game design-development-feedback-playtesting-revised iterations-project handoff.
FINAL PRESENTATION:
Our final presentation included all the points that our director asked us to and also a demo of our game.
ARCHIVE, WEBSITE:
We moved all our work draft, final products to the archive and also made sure that the website is up to date
APP POLISHING:
As mentioned before, we created a new build early this week to get it tested by our advisors. Though we did not get any major feedbacks, we were advised to change few minor things, like the placement of the carry over in the addition re grouping, which we fixed.
PROJECT HAND OVER:
After polishing, we had our final build handed over to our clients which we did by sharing the IPA file to their IT Department.
APP STORE:
We added our app for in the app store so that teachers and kids can use it for free.
