Mobile Game Development (6 cr)

Objectives (course unit)

The goal is that after student has finished the course, student is able to implement a game running in a mobile device.

Content (course unit)

Object oriented programming,
programming environment,
game objects,
animation,
persistant storage,
collision detection.

Prerequisites (course unit)

Opintojakson Johdatus ohjelmointiin suorittaminen tai vastaavat tiedot.

Assessment criteria, satisfactory (1-2) (course unit)

Student is able to compile and run a mobile game.
Student is able to implement small mobile game that contains game objects.
Stydent is able to implement mobile game that receives user input.

Assessment criteria, good (3-4) (course unit)

Student is able to implement mobile game that contains persistant storage.
Student is able to implement localized mobile game.

Assessment criteria, excellent (5) (course unit)

Student is able to implement mobile game that uses physics engine.
Student is able to publish mobile game.

Location and time

- Follows the game project's schedule (available on Moodle)

Exam schedules

No exam. The course is completed by doing exercises and the mobile game project.

Assessment methods and criteria

The course is graded by exercises (30%) and by the mobile game project (70%). Exercises are mandatory and points can be earned only by being present. 50% of the exercises must be completed to be able to pass the course.

Exercise grading:
[ 0%, 50%[ => 0
[50%, 60%[ => 1
[60%, 70%[ => 2
[70%, 80%[ => 3
[80%, 90%[ => 4
[90%, 100%] => 5

The game project is graded by the code (50%) and by peer review (50%). That's why it is important that the code is available on a public Git repository.

Project's general requirements:

- 2D/3D Game targeted for Android
- Tested in the actual device
- Uploaded to Google Play before the deadline
- Add a link to the game in google play to google sheets.
- Add a public GitHub repository to google sheets

Assessment scale

0-5

Teaching methods

- Lectures (on-premises and remote)
- Exercises (on-premises)
- UX-part (on-premises)

Learning materials

- YouTube playlist. Available on Moodle
- Unity's documentation
- Unity Learn

Student workload

3rd period:
- Lessons once a week
- Exercises once a week
- UX lessons every other week
4th period:
- Working on the game project
- Exercises & project guiding once a week
- UX lessons every other week

Content scheduling

3rd period:
- Lessons once a week
- Exercises once a week
- UX lessons every other week
4th period:
- Working on the game project
- Exercises & project guiding once a week
- UX lessons every other week

Completion alternatives

- Can be agreed with the teacher case by case

Practical training and working life cooperation

Spring's mobile game project is done in cooperation with a customer.

International connections

- UX part is held in English

Further information

Opintojaksolle erillinen hakumenettely.