Unit 5 - Introduction

Lesson 5.1 - Clicky Mouse

Lesson 5.2 - Keeping Score

Lesson 5.3 - Game Over

Lesson 5.4 - What’s the Difficulty?

Challenge 5 - Whack-a-Food

Lab 5 - Swap out your Assets

Quiz 5

Introduction to user feedback and testing

Learn how to implement a User Interface - or UI - into your projects, such as a title screen and score display.

In this Mission, you will program a game to test the player’s reflexes, where the goal is to click and destroy objects randomly tossed in the air before they can fall off the screen. In creating this prototype, you will learn how to implement a User Interface - or UI - into your projects. You will add a title screen with a difficulty select menu that will control how challenging the gameplay is, you will add a score display that will track how many points the player has earned, and you will add a Game Over screen, which will allow the player to restart and try again. In learning these skills, you will be able to create a fully “playable” experience that the user can enjoy from start to finish without having to restart the application to try it again.

User Interface

Unity Junior Programmer

Kickstart your programming career with Unity's Junior Programmer Pathway. Learn coding fundamentals, C#, and game development to create your first interactive projects. Start learning for free!

Junior Programmer Pathway - Learn Coding & Game Development | Unity Learn

We recommend that you have basic knowledge of Unity or complete 

Ready to code? This guided learning Pathway will take you from zero to job-ready!

Welcome to Junior Programmer! Designed for anyone interested in learning to code or obtaining an entry-level Unity role, this pathway assumes a basic knowledge of Unity and has no math prerequisites. Junior Programmer prepares you to get Unity Certified so that you can demonstrate your job-readiness to employers.

Junior Programmer

Course Introduction

Install Unity Software

Unit 1 - Introduction

Lesson 1.1 - Start your 3D Engines 

Lesson 1.2 - Pedal to the Metal

Lesson 1.3 - High Speed Chase

Lesson 1.4 - Step into the Driver's Seat

Challenge 1 - Plane Programming

Lab 1 - Project Design Document

Introduction to project management and teamwork

Quiz 1

Learn how to create new C# scripts, call basic functions, and use variables to modify the results of those functions.

In this first mission in the Junior Programmer pathway, you will program a car moving side-to-side on a floating road, trying to avoid (or hit) obstacles in the way. In addition to becoming familiar with the Unity editor and workflow, you will learn how to create new C# scripts and do some simple programming. By the end of the Unit, you will be able to call basic functions, then declare and tweak new variables to modify the results of those functions.

Player Control

Unit 2 - Introduction

Lesson 2.1 - Player Positioning

Lesson 2.2 - Food Flight

Lesson 2.3 - Random Animal Stampede

Lesson 2.4 - Collision Decisions

Challenge 2 - Play Fetch

Lab 2 - New Project with Primitives

Quiz 2

Mod the Cube

Quiz: Create with Code 1

Gain familiarity with some of the most important programming and Unity concepts, including if-then statements, random value generation, arrays, collision detection, prefabs, and instantiation.

In this Mission, you will program a top-down game with the objective of throwing food to hungry animals - who are stampeding towards you - before they can run past you. In order to do this, you will become much more familiar with some of the most important programming and Unity concepts, including if-then statements, random value generation, arrays, collision detection, prefabs, and instantiation. In completing this Unit, you will learn how to program a basic game with the ability to launch projectiles and maneuver the player to keep the game alive.

Basic Gameplay

Unit 3 - Introduction

Lesson 3.1 - Jump Force

Lesson 3.2 - Make the World Whiz By

Lesson 3.3 - Don't Just Stand There

Lesson 3.4 - Particles and Sound Effects

Challenge 3 - Balloons, Bombs, & Booleans

Lab 3 - Player Control

Quiz 3

Learn how to add music, sound effects, and visual particle effects to transform the experience of your project.

In this Mission, you will program a fast-paced endless side-scrolling runner game where the player needs to time jumps over oncoming obstacles to avoid crashing. In creating this prototype, you will learn how to add music and sound effects, completely transforming the experience of your projects. You will also learn how to create dynamic endless repeating backgrounds, which are critical for any side-scrolling games. Finally, you will learn to incorporate particle effects like splatters and explosions, which make your games so much more satisfying to play.

Sound and Effects

Unit 4 - Introduction

Lesson 4.1 - Watch Where You’re Going

Lesson 4.2 - Follow the Player

Lesson 4.3 - PowerUp and CountDown

Lesson 4.4 - For-Loops For Waves

Challenge 4 - Soccer Scripting

Lab 4 - Basic Gameplay

Quiz 4

Learn how to implement new gameplay mechanics including powerups and increasing difficulty.

In this Mission, you will program an arcade-style Sumo battle with the objective of knocking increasingly difficult waves of enemies off of a floating island, using power ups to help defeat them. In creating this prototype, you will learn how to implement new gameplay mechanics into your projects, which are new rules or systems that make the game more interesting to play. On one hand, you will learn to program a powerup, which give the player a temporary advantage. On the other hand, you will learn to program increasingly difficult enemy waves, which make survival more challenging for the player. A good balance of powerups and increasing difficulty make for a much more interesting gameplay experience.

Gameplay Mechanics

Next Steps - Introduction

Lesson 6.1 - Project Optimization

Lesson 6.2 - Research and Troubleshooting

Lesson 6.3 - Sharing your Projects

ECS Survival Guide

Career research and preparation

Introduction to portfolios

Debug the App

Counting Prototype

Quiz: Create with Code 2

Prepare to continue developing your Unity and C# skills independently, including learning how to complete your personal project.

In this Mission, you'll prepare to continue developing your Unity and C# skills independently, including learning how to complete your personal project and how to prepare for the Unity Certified User: Programming exam, which you can take through your school program, if available.

Publishing Your Project

Introduction to real-time 3D experience design

Set up version control

Explore the sample project

Principles of object-oriented programming

Create a scene flow

Implement data persistence between scenes

Implement data persistence between sessions

Quiz: Manage scene flow and data

Submission: Data persistence in a new repo

Learn about data persistence and an introduction to the core pillars of object-oriented programming.

In this mission, you’ll learn about data persistence, or how to manage the loading and unloading of data between both scenes and sessions. Along the way, you will be introduced to the core pillars of object-oriented programming, which will help you structure your code throughout the mission. There will only be one practical example throughout the mission, which will build on the new functionality you create with each tutorial. At the end of this mission, you’ll take everything you learned and apply it to a new project by building a persistent score system for a small game.

Manage Scene Flow and Data

Abstraction in object-oriented programming

Inheritance and polymorphism in object-oriented programming

Encapsulation in object-oriented programming

Profile code to identify issues

Job preparation: Junior Programmer

Quiz: Apply object-oriented principles

Submission: Programming theory in action

Deep-dive into the pillars of object-oriented programming and their application, then learn how to profile and optimize code.

In this mission, you’ll refactor the inventory project you completed in the previous mission using the pillars of object-oriented programming as a guide. You’ll deep dive into the inner workings of each pillar individually, so you can better understand its value in developing applications. Next, you’ll learn how to profile your code to identify any optimization bottlenecks that would slow down the final build of your application. To close out this mission, you’ll develop a small application for your portfolio that uses fully optimized code built on OOP principles. 

When you complete this mission you will complete the Junior Programmer pathway - CONGRATULATIONS!

Apply Object-Oriented Principles

de40d5c3-33b7-498a-8d92-03b0ee70d219:49e1d4f0fd32

Overview

What is user testing and feedback?

Why conduct structured user testing?

The phases of user testing

Planning for user testing

Preparing yourself to run the session

Facilitating the session

After the session

Exercise: Mini product evaluation

Summary and next steps

Communicate clearly and express themselves creatively for a variety of purposes using the platforms, tools, styles, formats and digital media appropriate to their goals, collaborating with others and working effectively in teams both locally and globally.

Communication & Collaboration

Ellen Flaherty

Senior Learning Architect - Unity

Use a variety of technologies within a design process to identify and solve problems by creating new, useful or imaginative solutions. 

Level 1 Design process

How user testing can be integrated into your design and development process.

Tips for running feedback sessions and getting actionable feedback from your target users.

Designed for post-secondary and K-12 educators at accredited academic institutions teaching Unity in the classroom, the Unity Educator plan provides you with free access to the same real-time 3D development tools used by professionals to support your students.

Included in this plan are Unity Pro, cloud-based collaboration, cloud build, free Unity assets, and much more!

Junior Programmer Pathway Facilitator Kit.zip

Junior Programmer Pathway Facilitator Kit (Google Drive)

Unity Educator Hub

The Unity Junior Programmer Pathway Facilitator Kit includes everything you need to successfully bring this Pathway into your learning context including a syllabus, complete lesson plans, standards alignment, teacher preparation guide, and more. 

Demonstrate curiosity by asking questions to focus and clarify

Get clarification that your understanding is correct

Seeking out, listening to and interpreting feedback 

2.1 Demonstrate curiosity by asking questions to focus and clarify

2.2 Give full attention

2.3 Get clarification that your understanding is correct

2.4 Seeking out, listening to and interpreting feedback 

2.5 Critiquing designs 

2.6 Giving feedback on a project 

2.7 Taking notes on critique

Participating in listening, constructive feedback cycles, and peer review

Distinguish open-ended and closed-ended questions

Explain how to facilitate a simple user testing session

Construct a plan for a mini product evaluation

Define user testing and its purpose

Explain the four phases of user testing

Coordinate a user feedback and testing session

Veronica Brown

Junior Programmer: Create with Code 2

VR Curricular Framework Resources

AR Curricular Framework Resources 

Game Design Curricular Framework Resources  

Architecture, Engineering and Construction Curricular Framework Resources

Unity for Artists Curricular Framework Resources

AI, ML Curricular Framework Resources 

When you create a real-time 3D experience (or any other experience, product, or service), it should address defined user needs based on research with your target users.

User testing and feedback is an opportunity to “reality-check” your project — against the user personas you created during pre-production, and ideally with real people who review your designs, prototypes, and the real-time 3D experience throughout the development cycle. 

The purpose of user testing is to gather qualitative and quantitative information about how well your design and its current implementation is meeting the user needs that the experience is designed to address. In other words: testing the product as an experience. 

The output of user testing is actionable feedback that you can evaluate and use to improve the experience you are creating. 

User testing isn’t a once-and-done activity. User testing must be embedded throughout the phases of production. It will ensure a high-quality final product that meets the needs of your target audience. Engaging in the user feedback process will also help you develop your skills in scoping, designing, and implementing solutions that address particular user needs.  

Although it’s possible to get valuable information from informal feedback, user testing isn’t just putting your product in front of someone and asking what they think. It’s a structured process designed to get as much specific and useful information from the tester as possible. A coordinated approach to user testing will also enable you to collect data from a range of users, so that you can compare their responses and get a better data set to support evaluation and improvement decisions. 

Ideally, you should conduct several user tests at various stages of project design and development, whether you’re working on a professional project or a solo project to help you learn. 

You might be tempted to think, “It’s not ready yet — I’ll show this to people and get their feedback when it’s done!”  This is a natural feeling, but by the time your project is in a polished state, it’s likely you won’t be able to make big changes that the feedback might bring to light. Instead, test early and often! The more you test and refine along the way, the better your end product will be. 

The user testing process typically follows this high level structure: 

Before you prepare the questions to get feedback from users, you should determine:

What you want to learn about your project


What you will show the users to elicit feedback (for example, wireframes, design mock-ups, or a prototype)


You can then assess your questions and testing session plan against these objectives, to ensure that they will help you get the information you need about your project.

Next, you’ll need to prepare the questions that will guide the user’s feedback. Depending on the type of feedback you’re looking for, you might ask open-ended questions, closed-ended questions, or a combination of both.

Open-ended questions give the user freedom to explain their answers. Examples include: 

How well do you think the design/prototype/product addresses [a user need]?

What were the moments in testing where you felt confused, and why?

Although these questions can work in a survey or questionnaire, it can be more useful to ask them through a conversation. This allows you to ask follow-up questions and gain a deeper understanding of the tester’s thoughts 

Closed-ended questions have predetermined answers, like those found in surveys. These might include: 

A series of statements which the user will grade their response to, for example rating confidence on a scale from 1 to 5

These questions work well in a survey or questionnaire format; you don’t need to ask them yourself.

It can be helpful to use both types of questions, not only to get a variety of information, but also because some testers may find it easier to give honest critical feedback via a survey rather than to a person talking to them directly.

When you’ve defined the test questions, there are logistics to consider. You should:

Determine how to find testers from your target audience.

Create an agenda for the testing session(s).

Plan to record the session (if applicable).

Choose a leader and note-takers for the session, if working in a team.

User testing can be challenging to run effectively — once you’ve planned the session, you need to get ready to facilitate it. You can do this by preparing using the following tips.

If you conduct your tests in person (in person or virtually), you may find it’s extremely difficult to sit there and not say anything while the users try your experience or review your designs. You may also want to interject and tell them how to do things, if they’re struggling! There is a balance to be struck here — if your testers are struggling with something so basic that they can’t test your product, wait at least 30 seconds, make a note of it and then tell them what to do so you can get more information. On the other hand, if they can work through the problem, their solution will be valuable information for improving your design. 

Don’t explain or justify your design choices 

If you gather qualitative feedback — for example, by having a conversation with the tester — again you may be tempted to explain things or justify the current implementation of your project. This can feel good, because it may “fix” the tester’s understanding — but it will not fix what you’re testing! 

The user insights that come up during testing may immediately send you into problem-solving mode, thinking about how to correct any issues raised. Your tester may also start to focus on this, exploring potential solutions they think of rather than focusing on their experience. 

It isn’t that these suggestions for solutions don’t have value, but the purpose of the testing session is to gain insights about their experience and to get deep information about their issues. Prepare yourself to remain in an observational role instead, actively listening to what the tester is telling you. You can also prepare to gently steer testers back to the problem they were explaining or the next question. If you don’t feel confident doing this, try practicing with a fellow creator!

There are different ways a testing session might be structured, but facilitators typically use the following broad structure:

Make introductions if testing as a group. 

Explain the recording policy (if applicable) and confirm the tester's consent to this.

Provide the materials for testing, and observe the testers as they use or review them.

Provide summaries of participant answers for clarification purposes. 

Here are some useful tips and tricks to support you in facilitating user testing sessions.


Remind yourself that you are not your product, and every product gets better with feedback — but only if you’re paying attention to what your users are telling you.
 

Frame the experience for participants. As each tester comes in, talk with them and explain what a user test is. Emphasize that you want all feedback, and negative feedback can actually be more helpful than positive feedback. Ask them to talk or “narrate” as much as possible while using the product or reviewing the materials, so that you can get a deeper understanding of their thought processes.


When the testing begins, make sure that you stop talking and record your observations in detail. Things that seem clear in the moment can easily get fuzzy if you only rely on your memory. What does the user struggle with? Is there any feature they’re not using as intended? Are they doing things that don’t seem to make sense?


If the user stops talking for a while, gently remind them to turn on the interior monologue again, but otherwise pretend you’re behind a one-way mirror.


If you conduct a conversation with a group of testers, make sure to include them all. Gently prompt quieter testers for their thoughts, to make sure their insights are included. 

Immediately after the testing session, you should:

Make sure the session was recorded (if applicable).

Write down any additional notes or observations. 

Introduction to user feedback and testing

1. Overview

2. What is user testing and feedback?

3. Why conduct structured user testing?

4. The phases of user testing

5. Planning for user testing

6. Preparing yourself to run the session

7. Facilitating the session

8. After the session

9. Exercise: Mini product evaluation

10. Summary and next steps

Complete this tutorial