You will implement your proposed design and produce a complete mobile app using App Inventor, and then report on your progress. The app should evidently follow from the previously approved proposal, although iteration is expected. Discuss major changes with the instructional staff.
The App
The final app should be functionally complete and demonstrate several meaningful task flows.
Review the rubric for a full breakdown, but you will be graded on:
completeness-- did you complete the features you proposed, or are justifications provided? Does the app have an icon and a descriptive app name?
user interface-- Is the app well designed? Can a new user figure out how to use it? Did you create/find nice graphics, e.g., for the buttons/background?
bug-free-- does the app have bugs? Be sure and test all possibilities (especially for variations in user input).
creativity and complexity-- Does your app have complex logic? Does it use sophisticated app inventor features? Did you come up with a creative idea that demonstrates persuasive intent?
Report / Project Page
The final written deliverable is a report cataloguing your design process, your design rationale and user research, the ways you adapted to issues you encountered, and what you might change going forward. If completed as a Word document/PDF, this should follow standard APA format. This could also be done as a website or gallery page in the App Inventor system. In that case, the content requirements are the same, but your format may deviate in obvious ways.
Content requirements:
- Business section:
- Title and list of developers with headshots or other representative images
- Short one-paragraph executive summary of your app and the design process used to create it
- Brief business plan for your app: what "problem" are you solving, key related apps, how yours is different, target audience of your app. This could be a SWOT analysis or use a similar framework. Cite relevant research in this section.
- Design section:
- Outline of the design process, including important stages and realizations (this outline can integrate the following design documents)
- Final primary persona of a user
- Relevant prototypes (i.e. screenshots of previous versions, Balsamiq wireframes, or photos of drawings developed during design)
- Implementation Section
- Link to source code (zip file with .aia and/or published app in gallery) for your app.
- Detailed specification of your app's features. In this section, you can list all features you'd like the app to have, but clearly state what has been completed (e.g., mark features you haven't completed as "future work"). This section is important as your grader will compare it to the actual app.
- Screenshots of code blocks with explanations. Explain how key functionality within your app works. Showcase your proudest achievements.
- The comments can be interspersed between screenshots or as comments within App Inventor if they are legible (right-click on a block and choose Add Comment).
- Testing results. Following the final week's in-class testing and any other testing you do, report on usability or bugs that the users found, and briefly describe what you did to address them. Completing the summary sheet (module 12) and including that text is sufficient and appropriate.
- Future direction -- a paragraph or two explaining what the next steps will be if the project were to be continued. If a feature isn't completely functional, describe how it could be developed.