Oh My Spikes

Developed by Soumya Kakarlapudi and Mahir Yasar

Beta Version Final Version

.aia File Type CSE#4_Kakarlapudi_Yasar_Oh_My_Spikes_ CSE#4_Kakarlapudi_Yasar
(Source Code) Beta.aia _Oh_My_SpikesV2.aia

.apk File Type CSE#4_Kakarlapudi_Yasar_Oh_My_Spikes_ CSE#4_Kakarlapudi_Yasar

(Packaged App) Beta.apk _Oh_My_Spikes_V2.apk
 Table of Contents:
1. Game Title Page
2. Table of Contents
3. Game Ideas, Brainstorm, Flowcharts
4. Feedback and Tiers of Progression
5. Beta Walk and Gallery Walk Instructions and Comments
6. Conclusions
7. Daily Log
Top 3 Game Ideas
- Quiz me
- Space Invaders
- Oh my Spikes
Brainstorm
- Having the moving sprites that are the spikes, animate. (up and down to make the game
more difficult)
- Have 3 different levels that progress in the game’s difficulty level
- Add more obstacles throughout the game other than spikes
- Have a scoreboard with coins or some kind of object that a player picks up to get a higher
score
- Different modes (easy, medium, hard)
- Timing system (Try to beat the best time that you have)
Game Designs

Levels : 1, 2, 3 Modes: Easy, Medium, Difficult

Flowchart Flowchart

We decided to use the version with levels so that the player can progress as they
complete more and more screens.

Feedback (Pair Share):

- Fixing the glitch at the bottom of the screen
 - Have a level progression (1-10)
- change controls the bird moves in.
- RNG the spike’s position and movements
- Add a timer where the players has to finish in a certain amount of time (tier 2)
- Make the scoreboard more visible
- More challenging (each level is unique with variety of spike’s movements and the bird’s
ability)

Tier 1:
- levels 1-5
- Vary different obstacles
- Animate the obstacles
- Make the scoreboard more visible
- Adjust the setting of the spikes
- Adding spikes
Tier 2:
- add a timer to the game
- Have different collectibles to earn points
Tier 3:
- make more levels
Beta Walk Instructions and Comments

Instructions:
1. Tap the play screen to begin the game.
2. Tap the bird to fly. Avoid the spikes through each screen, and for every screen that you
pass through, you get one point on the scoreboard.
3. If you hit a spike, the bird shall die, and you have to start the game over again. When you
die, your score will be displayed.

Pro: Features Liked Con: Aspects that were confusing, buggy, or etc.

● I like the bird sprite.
● I like the bird’s mechanics, it flies
smoothly and move up when you tap.
● The ball is a good feature
● It’s a fun game to play
● The ability to control the bird by just
tapping the screen is cool
● If you don’t tap at all and the bird falls, the
score rapidly increases.
● Spikes are only near the top.121
● The ball in the middle moves too fast;
maybe make the ball slower so that it’s
harder to go past it
● too much gravity
● Game glitches a lot
● I don’t even know how to play

Gallery Walk Instructions and Comments

Instructions:
1. Tap the play button to play the game.
2. When you tap the screen, the bird will fly.
3. Avoid the spikes, and avoid the ball, as they will kill you, and reset your score to 0.
4. As you pass through each screen, the score will increase by 1.
5. As your score increases, the ball will go faster, and the birder will fly faster, increasing the
difficulty as your score increases.

Pro: Features Liked Con: Aspects that were confusing, buggy, or etc.

● The app isn’t glitchy ● Not many obstacles

● Good aesthetics ● Spikes won’t go to the bottom of the
● Good idea screen
● Red ball won’t kill you below the bottom
half of the screen
● No level progression
● Top left or right hand corner of the screen
gives you infinite points if you get to it and
keep tapping
● It is kind of hard to fly since you can keep
on flying really fast,
● The goal is not really clear on the game,
so it is unclear what you are aiming for.
● What is the pink ball that goes around,
because it sometimes kills you, and
sometimes it doesn’t.
● It is unclear that hitting the floor will make
 you die, because if you hit the walls, then
you don’t die.
● There’s no level progression
● You need to make it way harder, the red
ball is almost impossible to bump into
● Provide ingame instructions
● The red ball would suddenly move very
slow to is very easy to win those level
● Game is easy to exploit and very glitchy
● I set the high score in two minutes. The
game has a glitch that makes the score
run to infinity and beyond!
● Make a realistic best score.
Conclusion

Mahir Yasar: The development process consisted of taking the tutorial code, then adding our
ideas to it. Personally, the App Inventor project itself was slightly more confusing than the Scratch
project, as this time, there were no conflicting broadcasts that could get contradict each other, but
each sprite and image had its own code associated with it. That made the project more
complicated that the previous one. On my end, I spent a considerable amount of time working on
the spikes position on the y-axis, but the difficult part on that is that the positions were incredibly
finicky, as each time it was testing using the app companion, the game ran successfully, but the
app version kept receiving bad arguments, which was odd. In fact, the other group in the class that
was developing a version of Oh My Spikes told me that they scrapped the game’s systems of RNG
spike positions altogether, as it simply wasn’t very practical for an app. When it comes to the
comments, most of the criticisms are legitimate. Although most problems stated were addressed
on the version that didn’t work correctly, it was fair criticism for the game that we did display. To
explain this, an explanation is handy. For example, half of the comments are based on the glitch
on the bottom right/left of the screen, but spikes were added at (0, 840) which made it virtually
impossible to slip to the bottom of the screen to trigger the glitch. Another example includes the
confusion concerning the ball and level progression, because the level progression includes the
ball and bird speed becoming faster as the score increases, but in our fault, that kind of
progression isn’t very clear, and in combination of the glitch making the score jump to the 10,000s,
the ball speed was incredibly fast, and the bird was impossible to control. Overall, most of the
criticism is warranted, but the developing process was generally more confusing in this project.

Soumya Kakarlapudi: For this project, my partner and I took the original code that there was
provided and added our own personal changes such as obstacles, level progression, and more. I
found that this project was generally a lot more harder than the last one, because I still haven’t
learned everything MIT App Inventor drag and drop code consisted of. It was difficult to figure out
the glitches of the app had because I have never experienced the type of code before. Although, I
think that the ball that we added and the display of the scoreboard was an improved addition to the
game because it transformed the game’s abilities and improved it much more. Based off the
criticism and feedback we got back from the beta walk and gallery walk there was definitely a lot
more negative criticism then positive because of how our app still consisted of the glitches that we
couldn’t fix or get to on the day of the gallery walk. Most of the feedback that we got definitely was
valid and there probably could have been a better way to functioning our app. I mainly focused on
the scoreboard placement and the level progression with the ball, and when the score get higher
the game got more difficult. In addition to the glitches of the app, we couldn’t quite install the app
on the tablet because the QR code couldn’t build the game for us as there was an in logical
argument that was added. Due to this, our app didn’t function as well as we would have wanted it
to.
Date At Class At Home

9/19/17 We created some ideas and We both started interpreting

choose our game, which is “Oh
My Spikes.” Additionally, we
started working on the design
Tuesday notebook brainstorms and this
log.
the code of Oh My Spikes as
well as drawing some
flowcharts.

9/20/17 We finalized our version of the We both worked through the

game to the modes and tutorials to understand what
Wednesday finished creating the the code did in the game.
flowcharts. We also have
started to look at the code and
see ways that we could
improve upon the code.

9/21/17 We did the tutorial for the N/A

game and understood the
Thursday levels of difficulty that we need
to add. We tried to find ways
to improve the code with
adding more obstacles and
creating modes.

9/22/17 We did peer feedback based on Using the peer feedback, we

our game and flowchart. will improve upon our game
Friday based on what they have
enlisted us with.

9/25/17 We found a way to include Mahir figured out the errors

more sprites with the png file that enlist in our game and
Monday and we also figure out the Soumya tried to fix the glitch
animation of sprites so now we at the bottom of the screen.
have a moving obstacle

9/26/17 Today we patched the glitch of At home, Mahir tested the

the bird getting infinite score,
Tuesday as well as moving up the
scoreboard to a site of
visibility.
game as it was. However, it
wasn’t very prudent as App
Inventor on a phone isn’t
nearly the same experience as
on a tablet.

9/27/17 We worked on combining our At home, we both wrote

code together for the beta walk instructions for Oh My Spikes.
Wednesday tomorrow.

9/28/17 Today, we had our beta walk. N/A

Thursday

9/29/17 Today, we uploaded our .aia N/A

Friday and .apk files to Google Drive.

9/30/17 N/A Today, Soumya added some

code for the ball’s visibility.
Saturday

10/2/17 N/A Today, Mahir adjusted the

spike’s image files to become
Monday larger, whilst adding a 5th
spike.

10/3/17 Today, we added 2 more At home, we both added 2

spikes, worked with the ball’s more spikes to cover up the
Tuesday visibility settings so that if you glitch.
die, the ball disappears.

10/4/17 Today, we tested into the game At home, we both tried to work
and tried compiling it into a out the error in downloading
Wednesday QR code to install it. We also our app.
combined both of our code
into one.

10/5/17 Today, we had our project log. At home, we both worked on

the project log.
Thursday

10/6/17 N/A Mahir worked on missing

information, and Soumya
Friday worked on organization and
order in the project log. Both
of us worked on the
conclusion.