UX and why should I care?

https://www.youtube.com/watch?v=k8vChQBaCd8&list=PLmsVHop5qjGEAsY4JTS5_VzccV5h1ZCAS&index=5

Рано чи пізно, працюючи над продуктом, кожен розробник повинен перейти зі стану "я тут щоб писати код" до "я тут щоб писати робочий код, який зробить мій проєкт краще", тож, в решті решт, усі шляхи ведуть до UX.
Ми розберемось що це за птах, а також чому нам, розробникам, треба у це занурюватись
Поговоримо про конкретні дії, які допоможуть нам в цьому (і проговоримо про те, як точно не треба робити).
Розберемо реальні кейси продукту-мільйонника та подивимося на те, які показники бізнесу вдалося збільшити через них.

Transcript

1. 01 UX and why should I care? Denys Rumiantsev iOS Team Lead @ appflame
4. HILY by appflame • Top-5 dating apps • MAU 2M • 13M 20M+ users 04
5. Hily: Before 05
6. Hily: Now 06
7. Hily: Now 07
8. Table of contents • What? • Why? • Why me? • ... and "How?" 08
9. UX. What is this? 09
10. Impact classification • Measurable • Not measurable (almost)
 10
11. Basics 11
12. Basics 10
13. Swipe back? 13
14. iOS != Symbian 14
15. Make it adaptive 15
16. Localize 05
17. Watch your tap! 16
18. Handle errors right
 (and nice) 18
19. But what went wrong? 19
21. And what? • Redesign your API • Give some info to user • Provide error state 21
22. Error configuration 22
23. Error configuration like a boss 23
24. Examples? 24
25. Why should I care? • LT0: ~ 39% 
 LT1-3: ~ 29%
 Other: ~ 12% • Increased avg. session +14%% • Increased active user's session x2-2.3 25
26. ... and what's before? 26
27. Instant feedback 27
28. User doesn't care • About your app's architecture • How it's hard to maintain legacy • Is it UIKit or SwiftUI • \(anotherYourPain) 28
29. Example: connected 29
30. Example: disconnected 30
31. What actually happened? 31
32. What actually happened? 32
33. Deliver feedback as fast as possible 33
34. Why should I care? • Async images uploading
 + 3%% registration completion (daily ~50K new users)
 + 1.4% active users • Mutual screen locally
 + 1%% conversion into first message
 + 3.8%% actions made
 - 45% time between action and result • Instead of conclusion: take more responsibilities 34
35. Don't be annoying
 Be cool 35
38. Explain • Why are you asking? • How will you use those permissions? • Why you're asking about it now? 38
39. Examples? 39
40. Why should I care? • Remote notification permissions screen vs. only system alert
 +4%% granted • Location permission screen vs. only system alert
 +3.3%% granted • Remote notification permissions from chat tail
 +18% granted 40
41. Make it easier • Do it for user • Explain what is expected • Make it responsive, handle states • Make it smooth with new APIs 41
42. Examples? 42
43. Add dark mode 43
44. It depends 44
45. Why should I care? • 65% (US) and 58% (overall) users with dark mode • +4.5%% promotional screen with dark mode convert to pay 45
46. Create design system • Colors • Fonts • Controls • Screen templates 46
47. Result 47
48. Pros • Consistent • Redesign? EASY • Might be first step to modularity • Could be re-used as standalone library in another project 48
49. Cons • Some job to do ¯\_(ツ)_/¯ 49
50. What else? 50
51. What else? • Investigate user's behaviour • Make your own review • Do “field testing” • Contact with support team • Launch survey & ask your user 51
52. Chat 52
53. Feature request 53
55. Summary • Implement basic stuff • Do it locally as much as possible • Handle your errors • Make it quick & responsible • Use bad-conditions sandbox • Implement new API features • Be cool. 55
56. 56 denisrumiantsev@gmail.com