130 likes | 255 Views
Week 4. Check-in : paper prototype. By now, your paper prototype should be complete, so that you can begin creating your app. Agenda. Topic Databases Testing your app and incorporating feedback Activities General app improvements feedback Interface feedback . Remember.
E N D
Check-in: paper prototype • By now, your paper prototype should be complete, so that you can begin creating your app
Agenda • Topic • Databases • Testing your app and incorporating feedback • Activities • General app improvements feedback • Interface feedback
Remember • What does a database do? • How can you use one in your application?
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
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
Databases in App Inventor • If you want to save data after the application is closed you must use a database • For example: saving the custom responses in No Text • TinyDBstores data directly on the phone and will only used by that phone • TinyWebDB stores data on a web database that can be shared among phones
Check-In: Q&A • Now let’s take a moment to answer the tutorial questions in your group if you haven’t already • Who can volunteer their answer for the first question?
Incorporating feedback: the point of testing your app is to make it 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)
Activity: Test your paper prototype with another team (30 mins) • Remember your paper prototype from last week? • Run a team through your paper prototype, screen by screen, so they’d know what it would be like to interact with it • Give feedback about the other team’s user interface • Take notes on the feedback that you receive Record your ideas in page 18 of the workbook
Activity: Incorporating feedback (15 mins) • Incorporate any helpful feedback you receive by revising your paper prototype Record your ideas in page 18 of the workbook
Activity: Create Prototype Skeleton (45 min.) • Use your paper prototype to develop a skeleton of screens in App Inventor: • Make and name a screen in App Inventor for each screen your app will have • “Screen1” must be your welcome screen! • Include all critical transition buttons (naming each one appropriately) that will take you to another screen. • Do not make them pretty yet or add any content, just a title to name the page and its buttons.
Task List • Finish incorporating feedback into a final paper prototype • Finish your skeleton of screens in App Inventor • Next week before class: Implement all the transitions in the blocks editor to help the user move from one page to another