Software doesn’t have to be boring or utilitarian. Games can be “serious” and useful.
Make a thing that blurs the boundary between software and videogame.
I’m going to show some examples.
Join my team on this Miro board
Teams of 2-4 are formed, split in breakout rooms.
Start a miro board for each team and designate a note taker.
20 min discussion:
Why is this subject interesting to you?
How serious vs ironic and real vs fictional do you want this artifact to be?
How do you want to affect the user? (emotionally, intellectually…)
30 minutes of individual research:
Collect both game and non-game references relating to your subject.
Add them to the mood board.
10 minutes: discuss your findings and see if there are converging inspirations and elements that could work for the goals you defined before.
Together, start sketching out a low fidelity wireframe of your application.
Focus on layout, and break down the progression like in a storyboard if there are different pages or sections:
Watch some videos about UX and app or website wireframing
1/3 of you are going to become UX designers anyway so you should start figuring our this stuff.
You can sketch out your wireframe on your team Miro board or on Figma.
If your project doesn’t involve interfaces, make a mock screenshot using whatever technique you consider appropriate.
Prof checks with each team
Homework for Feb 25
- I will set the deliverables for each team since the projects can be quite diverging
- The team should pick at least 3 things to play among the ones listed in Homeplay II OR among important refences you choose. Have an asynchronous discussion on your discord channel about what you liked and disliked, and what parts could be an inspiration for your project. Try go in detail, even if you didn’t like a game as a whole, it probably still has something to offer. I might send you some project specific references as well.
- Go through the team checklist and make sure you are able to work together by next Friday.
Prepare the material for a short presentation of the concept. Teams start working.
Prof checks with each team. Scope and priorities established. Makes a list of technical needs.
Afternoon: technical tutorials if needed.
Setting minimum goals for next week.