Activity: Motion Project

Now its time to put the concepts together and make your own unique games!

Here are some example cards of some game ideas:

    "name": "Catch the Cents",
    "imageUrl": ""
}, {
    "name": "Text Adventure",
    "imageUrl": ""

Concepts Learned

  • ||sprites:Sprites||
  • Sprite Position (coordinates: x and y)
  • Controller (||controller:dx||) and ||controller:move mySprite with buttons||
  • ||sprites:overlap|| Events / sprite ||sprites:kind||
  • “Spawning” sprites: ||sprites:create|| and ||sprites:on created||
  • ||math:random||
  • Displaying numbers (1, 2, 3) as a string ("123")
  • ||info:score|| and ||info:life||
  • ||info:countdown||
  • ||images:flip|| image
  • ||sprites:stay in screen|| and ||sprites:ghost||
  • ||sprites:set image||
  • sprite ||sprites:say||
  • ||game:splash||

Student Task #1: Initial Ideas

  1. Think of at least 3 ideas for games that use some of the “concepts learned” listed above
  2. On a piece of paper, sketch out what each game will look like
  3. Discuss your ideas with a partner. Talk about:
    • What you like about the ideas
    • What you don’t like about the ideas
    • Any suggestions you have for extending the ideas
  4. With your partner, discuss what features would be necessary to start each game

Student Task #2: Creating a Minimum Viable Product

A Minimum Viable Product, or MVP, is the simplest version of a product. It will consist of placeholder values, and have features missing.

An MVP is a very simple foundation for your product (or project), which allows you to gather feedback and ideas from others without getting lost in the small parts that require some polish later on: making the perfect sprite, creating challenging levels, identifying how players score more points, and so on.

To create your MVP,

  1. Pick one of your ideas that you want to turn into a full game
  2. Identify what crucial functionality is required for the game - identify what makes it unique
  3. Make a list of these key (important) features that you need to implement
  4. Transition into the development cycle to start making your game

For an MVP game, you might want to avoid spending too much time getting bogged down making the perfect image for your sprite; instead, you can always just use some of the provided sprites in the Gallery. This allows you to focus on getting the concept for your game into a functional state and personalize it later on!

Using Gallery

Student Task #3: The Development Cycle

This is the development process we will use to turn an idea for a game into a finished product.

The development cycle works by adding small changes and getting feedback as you develop. When you get to the end of the Learn section, if there are ideas you would still like to implement, return to the Build section and start implementing those ideas.

Repeat this cycle until you are satisfied with the game and the game has at least 8 concepts from the list of Concepts Learned. If more time is available, create an MVP for another one of your original ideas and begin the development cycle on it.

For a guided example of this process, see the example project page.


Implement a list of features

  1. Break down what tasks need to be done for each feature you want to implement
  2. Make a plan for how each one of the tasks will be finished
  3. Complete the tasks needed to implement these features
  4. When the tasks are complete, create a share link to the game


Gather feedback about the game from an outside source

  1. Find someone to test the current game with
  2. Give a 15-30 second description of what your game is supposed to be: describe the features that are not yet implemented to give them an idea of the ‘bigger picture’
  3. Have them play your game
  4. Ask for feedback:
    1. What do they like about the game?
    2. What would they like to be improved?
    3. How would they like it to be improved?


Convert the feedback into a list of features that to implement

  1. Reflect on the feedback you gathered from users testing your game
  2. Identify what features you would like to add based on what the users want
  3. Prioritize what features are most important to implement next

What did we learn?

  1. What did you learn when making an MVP version of the game? What was useful, what was difficult?
  2. Were any items you initially listed as crucial to the game not used? Why? If all were used, explain which ones were most essential to the game versus the less essential elements of the game.

Teacher Material