This document summarizes the key steps and considerations for developing an app to solve a problem. It discusses identifying the problem, who it affects, why it is important to solve, and potential solutions. It also provides guidance on interviewing stakeholders to understand functional requirements and learn more about the problem. Finally, it lists some common screens that may be needed for an app, such as login, home, settings, and contact screens.

1. Girls Can Code
M e e t i n g 10 - 1/27/17
+ t e c h n o v a t i o n

2. voting, scheduling, and things
splitting up meetings
alternative meeting times
time commitments

3. finding a problem
What is the problem? In design terms, this also
translates to: what is the need
Who does the problem affect and how? This is
important because the people who are affected by the
problem will be the users of your app. They will be
your stakeholders
Why is it important to solve? Why is this problem
compelling and do you have any evidence of the
problem to back up your argument?
What is the solution? You may have an initial idea for
a solution. You will be experimenting more with the
solution in this unit as you get to know your user and
through paper prototyping!

4. Brainstorm and write down all the possible
stakeholders for your project
To find out what stakeholders want the app
to do, you will need to interview them. You
can ask questions to help you find some
functional requirements of your app.
Interview to learn more about the problem
and get their thoughts about the solution. If
apps already exist to help solve the problem
your team is focusing on, you can ask users
about the app and what they like or what
doesn’t work so well for them.

5. JUNIOR TEAMSENIOR TEAM
first opening screen
login screen
sign in screen
monitor/information screen
how-to-use screen
normal screen v.s alert screen
settings config screen
emergency contact input
screen

6. T H A N K Y O U
for being a part of our day
Love,
Frank & Lily
https://www.youtube.com/watch?v=JMjozqJS44M