CodePath Mobile App Development - Week 1

Transcript

1. Welcome to CodePath’s Mobile App Design Week 1! Make sure you’re muted Turn on your webcam! Feel free to talk in the room chat
2. • Intros • Why mobile and Android? • Course schedule and expectations • Breaking down Android apps • Quick break! • Setting yourself up for success • Debugging Agenda
3. Intros!
4. Why mobile?
5. Why mobile?
6. Why mobile?
7. • 80% of adults in the world own a smartphone Why mobile?
8. • 80% of adults in the world own a smartphone • Estimated 1 out of 3 human beings today own a smartphone Why mobile?
9. • 80% of adults in the world own a smartphone • Estimated 1 out of 3 human beings today own a smartphone • Mobile internet usage has taken over desktop internet usage since 2015 Why mobile?
10. • 80% of adults in the world own a smartphone • Estimated 1 out of 3 human beings today own a smartphone • Mobile internet usage has taken over desktop internet usage since 2015 • Many companies are mobile-first focused Why mobile?
11. • 80% of adults in the world own a smartphone • Estimated 1 out of 3 human beings today own a smartphone • Mobile internet usage has taken over desktop internet usage since 2015 • Many companies are mobile-first focused • Average salary for mobile developer in the US is $122k, and $157k in San Francisco Why mobile?
12. Why Android?
13. • There’s an estimated 2.5 billion active Android devices Why Android?
14. • There’s an estimated 2.5 billion active Android devices • Over half of all smartphones in the world are running Android Why Android?
15. • There’s an estimated 2.5 billion active Android devices • Over half of all smartphones in the world are running Android • Huge demand with short supply of Android developers Why Android?
16. • There’s an estimated 2.5 billion active Android devices • Over half of all smartphones in the world are running Android • Huge demand with short supply of Android developers • Android is used in all kinds of devices! Cars, watches, refrigerators, ovens, … Why Android?
17. Goals for the course
18. Goals for the course • Gain a better understanding of the tech industry
19. Goals for the course • Gain a better understanding of the tech industry • Learn how to build Android apps
20. Goals for the course • Gain a better understanding of the tech industry • Learn how to build Android apps • Connect with other students
21. Goals for the course • Gain a better understanding of the tech industry • Learn how to build Android apps • Connect with other students What is your personal goal for the next 8 weeks?
22. Course format
23. Course format • Coding labs • Lecture about technical topics • Work on Flashcard app
24. Course format • Coding labs • Lecture about technical topics • Work on Flashcard app • Panels • Hear from industry experts about their roles • Ask questions about their journey!
25. Course format • Coding labs • Lecture about technical topics • Work on Flashcard app • Panels • Hear from industry experts about their roles • Ask questions about their journey! • Group activities • Work with other students to brainstorm ideas and collaborate
26. • Week 1: Intro / Debugging • Week 2: Flashcard app (Building Screens) • Week 3: Panel • Week 4: Flashcard app (Handling user interaction) • Week 5: Flashcard app (Saving data) • Week 6: Panel • Week 7: Flashcard app (Styling and animations) • Week 8: Building a prototype!
27. Communication • Course Portal
28. Communication • Course Portal • Slack channel @android-help
29. Breaking down apps
30. What makes a good app?
31. What makes a good app? • Is it easy to use? • Is it fun to use?
32. What makes a bad app?
33. What makes a bad app? • Hard to use • Buggy and crashes a lot
34. Let’s Discuss! What makes a good app?
35. • Breakout rooms • 5 minutes: Introduce yourselves • 5-10 minutes: 2-3 good apps, 2-3 bad apps • 10 minutes: why are they good / bad? • Regroup after 25 minutes Let’s Discuss! What makes a good app?
36. Break!
37. Learning to program is hard. And building apps is hard. You’ll feel discouraged when you can’t get something to work just right. You’ll feel frustrated when you’ve been stuck for hours on the same problem. And you may want to quit when you don’t understand something.
38. Learning to program is hard. And building apps is hard. You’ll feel discouraged when you can’t get something to work just right. You’ll feel frustrated when you’ve been stuck for hours on the same problem. And you may want to quit when you don’t understand something. But it gets easier. It turns into a puzzle. You’ll experience a rush of adrenaline when you hit the Run button and your app works. You’ll smile when you write code that runs perfectly on the first try. And you’ll celebrate when your first app goes live.
39. Set yourself up for success!
40. Set yourself up for success! • Android development is hard!
41. Set yourself up for success! • Android development is hard! • Utilize your resources! • Google!! • Ask for help after 30 minutes of being stuck
42. Set yourself up for success! • Android development is hard! • Utilize your resources! • Google!! • Ask for help after 30 minutes of being stuck • Understand your code
43. Set yourself up for success! • Android development is hard! • Utilize your resources! • Google!! • Ask for help after 30 minutes of being stuck • Understand your code • Everybody is going to go at their own pace
44. Debugging • Understanding build errors • Understanding crash logs • Print statements
45. Debugging • Invalidating caches / restart