ADDC 2019 - Shem Magnezi - Good rules for Bad apps

Building a decent app is easy this day, there are plenty of tutorials, videos and blog posts about it. In this session, I’ll try to go over some of the top mistakes that every one of us is doing while building his app. This will cover all the aspects of building a bad app- technical, UI & UX, and product. So each one of you will be able to adapt his favorite bad pattern and ruin his app.

Recordings & more: https://addconf.com/

Transcript

1. GOOD RULES BAD APPS for
2. SHEM MAGNEZI
3. Badass apps
4. Not that good apps
5. Terrible apps that make you want to cry
6. @shemag8 GOOD BAD vs @shemag8
7. @shemag8 BEFORE WE BEGIN
8. @shemag8 There are MANY ways to RUIN your app
9. @shemag8 It’s not “ ALL or NOTHING”
10. @shemag8 Rules depend on TIME & PLACE
11. @shemag8 LET'S START
12. @shemag8 Ask as MANY PERMISSIONS as POSSIBLE 1.
13. @shemag8 Don’t COMMUNICATE what you’re doing 2.
14. @shemag8 Don’t save SCREEN STATE 3.
15. @shemag8 Don’t OPTIMIZE app SIZE 4.
16. @shemag8 Ignore MATERIAL DESIGN specs 5.
17. @shemag8 Create INTRO, OVERLAY and HINTS 6.
18. @shemag8 Mysterious ICONS 7.
19. @shemag8 Create your own LOGIN screen 8.
20. @shemag8 Support the OLDEST ANDROID VERSION I’m not going to GIVE UP on those users!!! 9.
21. @shemag8 Don’t use REAL DATA 10.
22. YOUR PERFECTLY BAD APP
23. 1. Permissions 2. Communications 3. Lose screen state 4. App size 5. Unknown UX 6. Intro 7. Mysterious icons 8. Login 9. Framework version 10. No real data 1. Only what you need 2. Loading and empty state 3. Save screen state 4. Vectors and modules 5. Material Design 6. Hints in context 7. Use predefined icons 8. Use SSO 9. Know your users 10. A/B testing
24. THE FULL LIST blog.shem.dev
25. @shemag8 QUESTIONS?
26. @shemag8 THANK YOU @shemag8 blog.shem.dev