In the last few weeks in EDTECH564 we have been working on a final portfolio for the class. The process had me looking back through the materials from the course and reflecting on what we have done. The website I created moves through our time analyzing and synthesizing augmented reality, virtual reality, and mobile apps. It then moves into the apps we created in App Inventor. Finally you can see my unit proposal and final thoughts as well. Overall, the project was fun to do and felt good reviewing what we have done. Check out the web site…
For the last few weeks in EDTECH534 we have been working on our final apps. I chose to create an app for use in my Video Game Design course as a tournament activity. For each game there is a different way to control the player so I envision this app also being used for students to analyze player controls.
The app itself is composed of 3 apps created with tutorials over the duration of the semester. Each of these three apps (Space Bouncer, Tap-a-Mole, and Cheasy Chase) have been heavily customized from the original tutorials. The final game, Cookie Crunch, I created from scratch and is the most robust. I really enjoyed creating Cookie Crunch, especially the images. I found there were limitations in AppInventor that a bit clunky to work around, like the inability to spawn sprites. Because of this, all sprites have to be manually put into the program and manually coded. I’m sure I could have gotten more creative with coding to make it more dynamic but I just couldn’t see/find it. Overall, I am quite proud of this app. A lot of time and effort went into it. I hope you enjoy!
Check out my final documentation web site to see the code and/or download the game!
This week in EDTECH 564 we created a mole-mash game. Since I created the original Mole Mash in EDTECH 534, I created a second different version this week. This version takes a different approach to displaying the holes and mole. I found it easier to determine what exactly was touched from the screen allowing me to more easily use the data for not only keeping track of successful whacks but unsuccessful ones as well. This is something I couldn’t figure out in the first version. I changed it up a bit from the tutorial by adding more holes, adding a missed count, updating the UI and adding a background. I definitly like the UI better in this version as well, but I attribute that to working a few more weeks with App Inventor.
This week in EDTECH 534 we created a quiz app with AppInventor. I feel like this is an easy match for educational apps being a quiz n’all. I built the app as the tutorial designed and ended up struggling with ways to make this app better. I mean, aside from UI stuff. This week, I wish there were more people in my course so I had more takes on what could be done with it.. but I don’t so.. I ended up choosing to do an HTML Quiz app as I am currently teaching the subject at my job. There are about a dozen questions that cycle through as the user answers. For my customizations, I added the functionality to disable the next button until the user guesses the correct answer. I also tweaked the UI a bit. I don’t care for the app being static and would like the ability to add questions, maybe push questions out to a group of students. There is a tutorial a few chapters past where we stop in the book that looks like it addresses this. I hope I have a chance to build it.
This week in EDTECH564 we completed the Space Invader tutorial. The app was easy to build but I found it overall quite boring. I decided I would try to improve on the game by converting it to a BrickBreaker type game. I recreated the images and created a fancy color flashing ball. Changing the behaviors so that the ball bounces off of things instead of disappearing was fairly straight forward, especially when referring to the BallBouncer app I created earlier this semester for EDTECH534. My biggest challenge was trying to create the angle bounce off the platform based on where the ball landed. After a while of not figuring it out, I opted to have the bounce angle be random and changed the platform to have odd angles off of it. The game starts off really easy with the ball moving quite slow but as the user progresses, the speed of the ball increases and the game gets quite challenging.
This week in EDTECH534 we created a “find your car” app. We played with location, storing data (I ❤ tinyDB), and the WebViewer. The premise as well as the tutorial is pretty straight forward. The user opens the app (with GPS on) and can save their current location allowing an easy return to that location with the click of a button. My only problem with the app was how the screen was laid out. With all the data on the screen, when the map opens in the WebViewer, you couldn’t really see anything. I added a button on the bottom to allow the user to open the map in the Maps app. I also rearranged the data to take up as little screen space as possible.
I can see this app being useful for finding your car in big parking lots like it was intended for. I also see this app being super useful on a field trip. Although, in version 2.0 I’d love to add some kind of breadcrumb functionality as well as the ability to have pre-programmed points, like we did in the Salem tour app.. maybe a combo of the two?
This week for EDTECH564 we completed a Magic 8-Ball tutorial. This was a fun easy tutorial to complete. I enjoyed using lists as I haven’t yet been able to play with them. It bothered me that the answers showed up in a label below the imagery of the toy so I spent the bulk of my time figuring out how to get the text to display approximately where it should. What I ended up doing was putting the image as a background to a 300×300 horizontal container and center/middle aligned a button whose text I replaced with the answer. I also added a simple radial gradient background to add some flair.
As far as functionality, I removed the tap for an answer because my new setup didn’t allow for the whole ball to be clicked. Plus it seemed more true to the toy to shake it anyway. The noises for this tutorial annoyed me a bit so instead I opted to have the app read the predictions out loud after the user shakes for an answer.