What a week to begin complexity! Just as I was beginning to get the hang of App inventor and spreading my wings to put out new versions of the basic apps, along comes an assignment with location generators, memory, and text-to-voice capabilities. In the midst of it all, widespread ISP server failures, two ambulance runs, and a wounded foal only added to the confusion. The tutorial seemed straightforward, but I kept encountering problems such as having to search for components the drawers. My Blocks Editor did NOT match the screens in the book because the instructions have me rename elements, but their tutorial images are not renamed. I work late at night, so had difficulties finding a second phone. My emulator kept crashing despite multiple reboots. After more than six app hours, my tutorial app worked and was ready to be saved. This experience has given me a lot of insight into developing course materials for online activities. How many times do we educators fail to provide visual or contextual clues on how to proceed when technology fails? How often do I provide my students with misaligned images and text? How do my learners approach new challenges, and what is my role in guiding them through the course? Finally, and most challenging of all, what to do for extending the app? My family members seem to have a deep-seated need to know where I am at all times…given my schedule this past week, perhaps a “Do Not Disturb” is in order.
EDTECH 597: Do Not Disturb
October 9, 2012 at 12:16 AM · Filed under 1.1 Instructional Systems Design, 1.2 Message Design, 2.2 Audiovisual Technologies, 2.3 Computer-Based Technologies, 2.4 Integrated Technologies, 5.1 Problem Analysis, EDTECH597
Leave a Reply