Apps for Appalachia: SOTU App - Testing Report

SOTU App - Testing Report

NOTE: I’ve bumped the deadline to Saturday midnight.

You’ve done some lo-fi prototyping and testing. You’ve developed a persona. You’ve worked on your implementation. This report should capture the following:

  1. Introduction. What is your app about? This is context for the project based on your initial research.

  2. Prototype and Test. What were the essential interface elements of your prototype, and why is that critical to your design? (Pictures of your lo-fi prototypes are welcome here.) What was your vision for how the app would function (pre-implementation)? Finally, what did your testing tell you about your app, and how did that influence your implementation plan.

  3. Personas. Present the two personas you’ve developed for this app. How do you feel your design addresses the psychology/background of this persona? (Comments on your personas are in your standards spreadsheet, if you wish to respond to those as part of this submission.)

  4. Implementation. You had your idea. You developed a prototype. Then, you dove into coding. Describe (including screen shots where possible):

    1. Elements. What elements that were critical to your implementation? For example, you may have required a timer, ImageSprites, database, or other components that were essential to your implementation.

    2. Information. What information (often captured in variables) was essential to the operation of your app?

    3. Events. Finally, what events that were critical to your implementation? For example, you may have relied heavily on buttons, canvas touch events, or something else. How did these events interact with the information that was critical to the app?

  5. Reflection. Finally, many of you are at a point where you either 1) have an incomplete app, or 2) have a complete app, but had to give up on aspects of your design to achieve completion. Reflect on two or three choices you made that you think could have, in hindsight, been made differently that you think would have moved you to a complete implementation sooner. It could be that you did not invest enough time in your implementation. It could be that you realized you needed tools that you have not mastered yet. It may be other things entirely (we discussed quite a few in class.)

Submission

Please submit your report (in Word or Open Office format) to Moodle, along with the .aia file of your app. You can get this by going into the Projects menu in App Inventor and selecting “Export selected project (.aia) to my computer.”

Learning Objectives

This is a first report; I’m looking for the text to be reasonable, but will not be assessing this at the detailed grammatical level. I am looking for how well you capture the work you have done, and especially the quality of your reflection on the effort you have (or, you may feel, have not) invested up until this point.

Remember, this is the first time we’ve engaged in this process, and we’re going through this design process very rapidly, so that we can experience the process. We will engage in this ideate-prototype-test-develop loop multiple times this term.

This report, and the code you submit, represent forward progress on a number of learning objectives:

  • Usability Testing and Theory 1.1: Demonstrate the ability to develop basic mobile interfaces in low-fidelity materials.
  • Usability Testing and Theory 1.3: Perform light-weight tests within a group as part of the prototyping process.
  • Usability Testing and Theory 2.3: Discuss application interfaces objectively from user- and heuristic-centered perspectives.
  • Program Design and Development 1.1: Use event handlers for concrete user actions in an interface (eg. button presses).
  • Program Design and Development 1.2: Identify concrete/visible aspects of program state (app background color, etc.) and the ability to change those values in response to user action.
  • Program Design and Development 2.1: Use variables to store program state, and control program actions between the handling of one event and the next.
  • Program Design and Development 2.4: Discuss what an algorithm is, and why the idea of an algorithm matters in the design and implementation of programs.