Students will produce a networked game that will leverage sensors on the phone to create a unique gaming experience. The focus of the game will be to make it physical through real-world gestures, motion and knowledge of other players real-world location. To do this students will need to integrate knowledge of graphics, networking, sensors, and user interface design alongside a skill set of tool usage. The final project will involve milestones with opportunities to get ungraded peer review feedback from fellow learners so that they can iterate and improve their game program. The final networked game that the students produce would be something they could showcase in job application materials, in an interview, or offer in the iTunes store.
Schedule
Loading...
En provenance du cours de University of California, Irvine
iOS Project: Transreality Game
8 notes
University of California, Irvine
8 notes
Cours 6 sur 6 dans Specialization iOS Development for Creative Entrepreneurs
À partir de la leçon
The Project and the Plan
In this module we go through the project that you will be working on for this capstone class. We look at the details of what the requirements are and talk a little bit about how to go about finding some of the assets that you might want to use. The first week is all about planning and designing.
Rencontrer les enseignants
Don PattersonAssociate Professor
Informatics and Computer Science
Sam KaufmanPartner at Gradient
[MUSIC]
Okay, since this is an eight week long class and
each of the weeks is going to build on each other,
what I want to do in this video is just walk through the schedule a little bit and
give you an expectation about what is going to happen over the next few weeks.
Basically, what we're looking at is we're looking at eight weeks of
development time.
The final week, however,
is going to be spent doing a review of everyone's projects, so really,
you only have the first seven weeks in order to do development of this game.
This is going to be an incremental process, and
it's going to be an iterative process.
Each week, you're going to have a deliverable due, except for
the end of the eighth week.
You'll have seven deliverables due that are going to build on each other.
Those deliverables are weekly, and they're graded.
In between, you can get feedback from your cohort peers through the discussion forum
if you'd like.
And each week, we'll also have some materials for you to evaluate, to review,
in some cases, but most of the time is going to be spent, you working on your
code, as opposed to watching a lot of new, or learning new material.
Week 1 is frontloaded with a lot of the material.
What it's going to be focused on is doing up-front design of your game.
In this week, we're really going to ask you to read all the requirements of
the game that's going to be due seven weeks into the future and
think through a plan of what you want your game to be like.
And as you think through that plan, think about it both creatively.
What do you want your game to be like?
How do you want to play it?
How do you want to include that physicality in your game?
What assets do you want to use?
What kind of theme do you want to use?
And then come up with a plan of how your game is going to meet each of those
constraints that we put into the requirements for the final deliverable.
How are you going to meet each one of those and
still come up with a game that you think is fun, and creative, and different?
For Week 1, what your deliverable is going to be is not going to be code,
it's going to be a video presentation.
Imagine this like a PowerPoint slide deck with a voice over,
put together into a video that you're going to upload to YouTube.
And then you're going to submit the URL for your video as your deliverable.
And we'll give you a little bit more information about it in the rubric.
But basically, you're going to be putting forward your design of your game and
sort of specifying how you're going to meet the requirements for
the rest of your peers to evaluate.
Week 2, we're going to ask you to do the basic scaffold
implementation of your game.
And what we want you to do in this week is to make sure you build the view
controllers to move from each of the different stages of your game, the launch,
the main entry, the game view, the preferences screen, and
possibly a placeholder for the game over screen, or the game lost, game won screen.
This is going to involve turning in a deliverable, which in this case, will now
be a video of your code, like many of the projects that we've done up to this point.
It's going to be showing the scaffolding being navigated, meaning, showing you
moving through the scaffolding, touching each of the pages that you've created.
And we also want you to show off some assets that you've found, so
some art assets that you place onto one of your UI kit controllers.
It doesn't have to do anything, doesn't have to move,
it can just be in the UI image view if you want.
But just sort of a palette of the things that you've collected,
the sounds that you've collected that you're going to include in your game,
kind of moving from the game designer concept stage
to a little bit more of a fleshing out of what it's going to look like.
Also in Week 2, you'll be responsible for
reviewing the development, the designs and the concepts from Week 1 of your cohort.
In Week 3, you'll start and throughout the week, you'll be reviewing Week 2.
Week 2's turn in.
And while you're reviewing Week 2, you'll be working on Week 3's turn in,
which is a gameplay view.
This is where you build out your first level,
the first example of the place where the game is actually played,
as opposed to the intro screens or the preferences screen.
We'll ask you to develop at least one of those.
We want you to implement some touch interaction according to your game
design plan.
And we also want you to implement some sensor interaction.
To support that, Sam has written a Cocoapod for us.
And what this Cocoapod does is it presents an overlay on your
screen of what sensors the device is currently experiencing.
The reason why we would ask you to use this is because when you record your game
being played,
there's no way to know that the device is being moved physically at all.
The recording shows the screen just sort of like still, and
you don't know that it's actually, if you record it through Quicktime,
you don't know that the device is actually moving.
And so this little bar will show a reading of the sensors coming in to
demonstrate that the device is actually moving.
So that will be a Cocoapod that you will include, and
you can subclass your game view from it.
We'll give you instructions on it.
At this stage, we're just asking you to have some game play view with
some interaction and some sensor input.
Ugly and buggy and glitchy is okay, as long as you've got something that
demonstrates those components, and if you were planning on having multiple levels.
Having one level is okay as well.
The deliverable in Week 3 will be a video demonstrating your game play screen.
Week 4, we're going to ask you to level up.
And we want you to add to your game the sound effects that are going to meet
the requirements of the final game.
We want you to add the special effect or
the particle system somewhere in that game play.
This will also be an opportunity to iterate on your level your game play
design and your code, add more levels if you're planning on having more than one.
And then finally, your deliverable will be a video demonstration of what's new,
including the things that are required, the sound effects and
the special effects, and anything else that you've added since week 3.
In Week 5, we're asking you to fill out the game completion screens, so
whatever is appropriate for your game design.
If you have a game won or a game lost or a game completion screen,
we'll ask you to do that and flesh it out in terms of what you want it to look like
and any other screens that you might have based on your game play.
You might have additional about screens or, I can't even imagine, there's so much
creativity in these classes, it's hard to imagine what you might come up with.
But if there's any other screens that you need, we'll ask you to add those.
And also in Week 5, we'll ask you to add the achievements, so
whatever you're tracking within your gameplay,
we want to see that kept track of, and we want to see those achievements awarded.
And then of course, this will also be an opportunity to iterate on the gameplay and
improve your code.
Week 5 will be a video demonstration of what's new, and with each of these weeks,
you're also going to be reviewing the previous week.
Week 6 is going to be the week in which you have the opportunity to make sure that
your preference screen, the selections on your preference screen are actually
affecting the rest of the game.
So if you choose to turn the sound off in your preferences screen,
we want to see that the sound's actually turned off.
If you choose to clear the achievements,
we want to see that the achievements are cleared.
And if you have any other preferences that you want to add specific to your game,
we'd like to see those as well.
The other thing we're asking you to do in Week 6 is to have someone near you
do a local play test of your game, meaning to play the game in some way that
you might find that someone that you might find to play it.
And we want you to turn in a video deliverable of your game again.
We also want you to turn in a short description of what the experience
was of the play tester who played your game.
Most of the time when you do this, you will find that the play tester will
immediately recognize various sorts of bugs in either your game mechanics or
in the actual code.
That for whatever reason as a developer, and you're working on these things,
you just become very blind to some things, that when you just bring
out the first person, the first couple of people to play test,
they immediately recognize some things that you need to fix.
And the lightbulb goes on in your head, and you're like, yeah,
that's obvious, I should have addressed that.
Let me go back and
make sure that works, to make sure that you've got a basic playable game.
Okay, Week 7 is going to be your final presentation prep.
This is your last opportunity to put the finishing touches on your game.
Any little gloss, any bugs you want to fill out, any reach goals that you had for
yourself, this is the week to do it.
This is also the week where you need to plan your presentation of your final game.
Because this presentation has gotta demonstrate
all of the different requirements that we've asked for.
And you need to record that game sequence.
So you can't use all of the week for development because you do have to
record a game sequence in which you're meeting the requirements of the game.
The final deliverable in this case is going to be a video of your game, but
you should think of this as a game trailer.
Probably familiar with movie trailers, and you're probably also familiar with the way
in which movie trailer as a genre has been adopted by the game industry.
So that you'll watch a video of a game trailer kind of showing you
the exciting parts of a game, or maybe a little bit of the back story.
So we're asking you in Week 7 to put together a game trailer,
demonstrating selling, marketing, and
showing that you've met the requirements of this assignment.
Finally, in Week 8, this is a week to kick back and enjoy the fruits of your labor.
You will have an opportunity to look through all the other projects that have
been turned in and
just enjoy what the rest of your cohort has been able to achieve.
All right, so that's what we're looking forward to for
the schedule over the next eight weeks.
Hope you're excited, got a lot of work,
got a lot of opportunity to really do some cool things.
Thanks.
[MUSIC]
Explorer notre catalogue
Rejoignez-nous gratuitement et obtenez des recommendations, des mises à jour et des offres personnalisées.
Coursera propose un accès universel à la meilleure formation au monde,
en partenariat avec des universités et des organisations du plus haut niveau, pour proposer des cours en ligne.
© 2018 Coursera Inc. Tous droits réservés.
