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.
This week in EDTECH534 I completed the Map Tour tutorial using my favorite day trip location, Salem, Massachusetts. The tutorial was pretty simple this week so I took it as an opportunity to explore using multiple screens in my app. In the last few weeks I thought about adding a game-over screen a couple of times but haven’t been brave enough to really try it (plus I was thinking a tutorial would present this to me eventually). The very first part of the tutorial, using the Activity Starter, did not work for me at all. I suspected it was due to the properties entered. Since I’ve worked on Java apps before, the paths LOOKED ok to me but in this context, I had no idea. This forced me to use the Web Viewer and pray it worked. Thankfully, it did. In the process, since I still had to use Activity Starter, I found that all I really needed was the Action and URI properties.
When the user clicks on the “Choose Your Destination” ListPicker on the first screen (Screen1), they are presented with a pre-defined list of landmarks. The user then selects the landmark they want to explore. The app then opens a new screen (Screen2) with 2 Web Viewers on it, one for the landmark web site and one for the landmark Google map. Now, I have a Samsung Galaxy s6edge+ so my screen real-estate is ample and I still felt a little cramped at this point so I added “pop-out” buttons that open each option in their respective apps. I found in my testing that the device back button kicked me out of the app altogether so I also added an in-app back button (come to find out, it kicked me out because I was using the Companion app, the device back works just fine in the finished app).
This week in EDTECH534, we continued learning about AppInventor’s abilities by building the “Ladybug Chase” tutorial. In the process of extending my app, my name and theme changed to Cheesy Chase. I ended up doing all the extensions the tutorial suggested including: adding better graphics &/or theme, stopping all movement when gameplay ends (although I left the little wiggle from the cheese and cat because I though it was cute), increasing the energy bar visibility (I had done this before I realized it was an extension, it just seemed necessary) , increased difficulty by increasing the cat speed over time, added a timer label letting the user know how long they made it, and removing the mouse if he’s eaten by the cat. I also added a game over indicator since it didn’t seem immediately obvious that the game was over.
As usual, I enjoyed creating this app and am looking forward to what we create next. I must say I am getting nervous to not have tutorials to rely on soon as the final project gets closer. While I know I’m creative, I don’t always have big ideas without inspiration.
This week in EDTECH564 we started to build mobile apps using AppInventor. Since I am taking EDTECH534 at the same time and have been using the tool for a few weeks now, I completed this alternate assignment “Ball Bounce” instead of repeating Hello Purr. The original tutorial has a ball on screen that you fling with your finger to bounce off the walls. I extended the app with a colorful background, purposefully overly colorful to try and add some difficulty to the game. I also added a good guy and a bad guy. If you fling the ball into a good guy, you add to the score and the bad guy takes from your score. Additionally, in order to increase difficulty with game play, I increase the speed of the ball with every bounce off a wall. There are also buttons to stop the ball while keeping game play alive and reset the game. The “Score” and ” Speed” labels allow you to keep track of your game play on the fly.