Recommandé
Recommandé
Contenu connexe
Similaire à A dangerous game - Visma Mobile Meet-up 2019 - Helsinki
Similaire à A dangerous game - Visma Mobile Meet-up 2019 - Helsinki (20)
Dernier
Dernier (20)
A dangerous game - Visma Mobile Meet-up 2019 - Helsinki
- 1. A dangerous game 💣 How to deal with breaking customers’ habits Tudor Dragan Senior Mobile Developer 08.05.2019
- 2. Hello 👋
- 4. About me Senior Mobile Developer 👨🎨 🇷🇴🇩🇰 📱👨💻
- 7. Expenses
- 8. A dangerous game 💣 How to deal with breaking customers’ habits Tudor Dragan Senior Mobile Developer 08.05.2019 not
- 10. Macedonia 🇲🇰
- 11. 2700 unique users each month Expenses
- 12. The problem 💔
- 13. The problems 💔💔
- 14. Old Expenses 1. Built in Xamarin 2. “God Activity” architecture 👼 3. No crash reporting tool 💥 4. No dependency injection 🗡 5. No CI pipeline⚙ 6. Really really outdated nuget packages ☎ 7. Do you want me to mention tests? 😅
- 15. Old Expenses
- 16. Use Xamarin & C# Same code in 3 programming languages Support another runtime environment Redo all our libraries in C#
- 19. Use Xamarin & C# Same code in 3 programming languages Go full native with KotlinSupport another runtime environment Redo all our libraries in C# Swift & Kotlin Reuse current libraries Native
- 27. ☠
- 30. The problems 💔💔
- 33. ✋ 😭API 21
- 34. What now?! 😩
- 36. Ends up in our message queue Finally into customer’s Inbox 📱 Sendgrid mail service Proxy ServiceClient * Yes, you heard that right, an e-mail *
- 37. Sendgrid mail service Ends up in our message queue Finally into customer’s Inbox * Yes, you heard that right, an e-mail *
- 38. Latency 🐌 Sendgrid mail service Proxy Service The client Message queue e-conomic application
- 39. Sendgrid mail service Proxy Service The client Message queue e-conomic application Latency 🐌 Especially the e-mail part 📧
- 41. 🎛 More control 🔪📧 Kill the proxy 📈 Performance metrics The client e-conomic application
- 42. SHUT UP AND SHOW US THE APP
- 43. Old App
- 44. New App
- 51. New Expenses • Native app build in Kotlin • Reusing our core libraries • Using fastlane on Travis • Instant App support • Heavily using RxKotlin/RxJava • Dependency injection with Dagger 2 • Using the latest AndroidX libraries and Camera APIs • 1 UI test 🤪
- 53. So how was the feedback? ⭐
- 54. uha for a bad update. User friendliness on the old version was significantly better. In addition, annoying that the agreement number and user ID are deleted by updating, so you have to go back in the stores and find them. Had to call support who did an excellent job. But the bad new version is so bad. Very angry user
- 55. • User friendliness on the old version was significantly better. Very angry user
- 56. • the agreement number and user ID are deleted by updating Very angry user
- 57. • But the bad new version is so bad. Very angry user
- 58. Hi e-cobomic, Why make an "UPDATE" for something that is significantly worse? From spending less than 2 minutes I now use up to 20 minutes and many times do not solve the task. Frustrating info. Want the old app. again. No stars from here, but need to give 1 to send. Another angry user
- 59. • From spending less than 2 minutes I now use up to 20 minutes and many times do not solve the task. Another angry user
- 60. It does not work on my phone Samsung Galaxy s5 Active Doesn’t work on my phone user
- 62. –Developers But should we trust those reviews? 🤔
- 63. 100K successful responses 👍 4.6K failed responses 👎
- 64. 95% of requests are successful
- 66. Most of them were Payload Too Large
- 67. We limited the file size here
- 68. Trust the numbers 🙈* * But help the users that have problems
- 70. Conclusions
- 71. If you need to change something Do incremental changes
- 72. If reviews are your key metric Suggest the user to rate
- 73. Don’t stress about the vocal minority Trust your data KEEP CALM AND TRUST YOUR DATA
- 74. Design your applications to Reuse components and libraries