Reading guide

In this reading guide I'm going over what CTOUCH is and what their vision, mission and core values are. What the problem is and design challenge is we want to solve. For each devlog entry I've given a brief introduction on what that specific entry is all about. Lastly, I've made a short reflection of how I've grown after this project was finished.

CTOUCH

Who is CTOUCH?

CTOUCH is a company that loves dynamic, innovative large format touch displays. This is how they provide you with the best interactive touch screen experience (and the software and hardware you need to achieve it). They look beyond now and deliver refined and future-oriented quality products.

Their vision

CTOUCH brings a lasting smile through the best interactive experience for collaboration and knowledge sharing.

We encourage you to use your full potential.

Their mission

We want to be always and everywhere where people work together and learn.

In every office, classroom, hospital, design studio, whenever there is a moment to collaborate, CTOUCH is there.

Their core values

We work smarter together. We provide a personal touch. We are proud of what we do. We take the responsibility.

The problem

CTOUCH would like to see users become aware of the energy consumption of the screen. 60% of CO2 emissions are produced during the manufacturing process. 40% of the emissions are currently caused by the end users. How can we actively encourage them to be aware of the power consumption of the screen? Can we encourage them to use the screen more efficiently?

The design challenge

Design an application to enable children aged 8 and below who use a CTOUCH Riva in primary schools to improve the energy efficiency of how the screens are used.

Our game idea

The same sort of idea as the aquarium, however, there is a correlation between the energy savings and the landscape. While energy is being saved, animals come to your landscape to roam. When energy savings are bad, bad things will happen. Bad things could be deforestation, hunters, roads, etc. The basic mechanics of the aquarium can be reused for this project. The shop could contain special animals you can buy with coins (just like in the aquarium game). Some special animals only appear when certain milestones are reached.

Devlogs

For each devlog I've made I'll put in a short introduction to what this devlog entry is about.

• Devlog 1: We wanted to have a cinematic overview of the world that flies over the world to display your progress and changes to the world. To read more about it click here.

• Devlog 2: Our idea was to implement a language localization for the game. That way this game could also be used in other countries in the EU besides the Netherlands. To read more about it click here.

• Devlog 3: The game also needs a proper UI design, fitting for the target group it's going to be used by. The other requirement is that the design should be designed for Android, this created an extra challenge to the design process. To read more about it click here.

• Devlog 4: For creating your custom animal, you first need to select which animal you want to customize to your own liking. They also needed to be made in such a way that it would be easy enough for children to understand how to use it. To read more about it click here.

• Devlog 5: Our end users need to understand how they should use the game and where they can find all the elements we put into the game. For this I've made a user manual that helps the end user to understand our game. To read more about it click here.

Reflection

The project was a fun and interesting way of creating a game. I've got a change to experiment with elements in Unity I never worked with before, which was a nice change of paste.

Although I joined a bit later in the project due to my health issues, it was easy enough for me to join and the group guided me through what the project was about and what they're concept idea was. We've discussed about the open tasks and what task(s) would fit my skills. This was quite helpful so I felt much more at ease taking on this project.

Looking back at my previous project I've made solo, I've made some improvement in creating devlogs. In my previous project I used Trello as my devlog entries. My teachers told me that wouldn't be a good idea to use it again for this project, since the way I've set it up before wasn't the correct method. My teammate told me about Git Book and the method he used to create his devlogs. I've used this as a base for my own devlogs and I must say the devlogs have really been improved.