3. Check-in: paper prototype
• Team members share paper prototype of their app idea
• Explain the key functionalities and features
2
4. Databases
• Organized collection of data
• Intended to organize, store, and retrieve large
amounts of data easily
Examples:
• iTunes is a database for all your music
• Google has a database of websites which is used for
Google Search
• Facebook is a database of people
3
5. Databases in App Inventor
• Reference to the colored Dots tutorial from last
session: http://tinyurl.com/k2qahq7
• If participants want to save data after the
application is closed they must use a database
Two types of databases:
• TinyDB stores data directly on the phone and will
only be used by that phone (hand-set)
• TinyWebDB stores data on a web database that can
be shared among phones
4
6. Data
• Key – label for what’s inside
• Value – data that’s inside
We use the Key to look up the Value in the database
Example:
Phone Book (a database of contact information)
Key = name
Value = phone number
5
8. Incorporating feedback:
Making your App better
• Feedback from potential customers will…
Tell you if your solution (app) to a
problem is accurate
Suggest improvements that can be
made in the design of the app
Suggest other features to add (either
now or in the future)
7
9. Activity: Usability Testing
• Test your paper prototype
Ideas for testing paper prototype:
Create a short video walking the audience through
the features of the paper prototype
Create a PowerPoint presentation listing each screen
on a slide
Share the video/presentation with your survey
respondents, friends and colleagues, WeTech team
(wetech@iie.org)
8
10. Activity: Usability Testing
• Create video/PowerPoint presentations
• Decide on how will the prototype be circulated for
feedback
• Create timeline for collecting and incorporating
feedback
9
11. Collecting Feedback on Prototype
10
Questions Notes Suggested Changes
Is there anything that is
unclear or confusing in
the user-interface?
Would your user prefer
the app look or behave
differently?
Which features of your
app interface and
usability
are of highest value to
your target market?
Are there any missing
buttons or other content
from your app?
Did the user’s
expectations differ from
the intended
functionality
of the app?
12. Task List
• Collect feedback for prototype
• Each team member can be assigned
responsibility for updating different
prototype screens based on feedback
received
11
13. Wrap-Up
• Share a photo of your session with WeTech at
wetech@iie.org
• Encourage participants to join WeTech
Technovation Facebook group to stay
connected with the larger community -
http://tinyurl.com/mmzjwed
Editor's Notes
Objectives: • Students will learn how to use a database • At this point, students should have: o Gathered results from at least 20 surveys to understand their market o Completed their paper prototype • After this lesson, students will better understand the importance of giving and incorporating others’ feedback into their paper prototype.This lesson is great for students’ professional development. Beyond the Technovation Challenge, a goal of this lesson is to be able to incorporate feedback and criticism, which will help them in their school life, college career, and professional career. By being able to handle constructive criticism and remove an emotional reaction to other’s feedback, students will be able to grow.
Last week when we participants looked at ColoredDotsthey used TinyDB to build their app. This week they will go further into databases .
For our purposes, data has two attributes – a key that defines it and a value that is the data. The key is unique. The value doesn'thave to be unique – more than one person in this room go to the same schoolYou cannot find out the key from the value, you can only find out the value from the key. Analogy to the key to your house
List some ways a database can potentially be used. Have the team members share ideas on what features/functionalities of their app would require a database.
Incorporating feedback goes along with the topics we’ve discussed in the past: lean thinking, usability testing, customer development and the prototype lifecycle. Basically, feedback from others makes the app better. Everyone comes at life with a slightly different perspective. Participants would want their app to appeal to as many different people as it can.
Before the participants create their app on the app inventor platform, they can test the prototype and make necessary changes by testing their paper prototype.
Before the participants create their app on the app inventor platform, they can test the prototype and make necessary changes by testing their paper prototype.
Participants can use the above form to collect feedback and record changes that would like to make for their app design.