@maybe_riya Earlier it was Google searches and StackOverflow, now the first and default resort for any blockers is ChatGPT/Copilot Chat.
To understand the concept I prefer reading the docs.
🚀 Exciting news! 🚀 Just launched a new blog on my website!
Learn how to build a Todo app using Angular, NestJS, and NgRx. Check it out now at https://t.co/kWS7jsq1jO 🐧💻 #Angular#NestJS#NgRx
Thank you @ankitsharma_007 for reviewing it, and motivating me to get it done!!
39 steps to update your app:
1. Decide it’s finally time to transition to Kotlin. Because big tech said so.
2. Click “Convert Java File to Kotlin” button and watch the magic happen. Spoiler: it’s not always magical.
3. Discover new Kotlin bugs. Debug issues you never knew existed.
4. Spend hours watching the Gradle build run. It’s like watching paint dry, but less rewarding.
5. Realize half your libraries are deprecated. Fetch new versions. Now half is experimental.
6. Dive into the abyss of GitHub to find forks of unmaintained libraries.
7. Migrate to AndroidX. Because you have to.
8. Write CRON job to run invalidate cache and restart every hour.
10. Rewrite the UI, because supposedly Compose is the future.
11. Try to understand Compose. Realize it’s completely new language and your old presentation layer is not reusable.
12. Add dark mode. Because your app isn’t cool without it.
13. Realize your app violates new guidelines you didn’t know existed.
14. Update privacy policy. Write a novel about user data you don’t even collect.
15. Add accessibility features: because it’s actually important (and also, pre-release report will haunt you).
16. Use gen AI for multi-language support. Insult someone in a language you don’t speak.
17. Cry over fragmentation. Why does every device manufacturer want to be a unique snowflake?
18. Implement new navigation. Realize halfway that the old one wasn’t so bad.
19. Bump API level. Face the existential dread of dropping support for 0.3% users.
20. Optimize for foldables. Because your app definitely needs to work on the two foldable devices in existence.
21. Introduce a memory leak, accidentally, of course.
22. Fix the memory leak. Pretend you knew what you were doing all along.
23. Read about ASO, change your app’s name to “A1 Best App” to appear first in search.
24. Integrate Firebase. For all the analytics you swear you’ll look at.
25. Spam your users with push notifications because “engagement metrics”.
26. Realize you need better backend, attempt to learn cloud functions overnight.
27. Cry over your serverless bill.
28. Implement offline mode. Because not everyone has 5G.
29. Hold your breath and pray that app won’t break on Xiaomi.
30. Buy 17 different low-end devices to make an attempt to reproduce crashes.
31. Read a 1-star review “the app is yellow and I hate yellow”.
32. Get featured on app stores, realize it brings more 1-star reviews about the app being yellow.
33. Add that one niche feature for that one loud user.
34. Market your app. People won’t come unless you scream about it on social media.
35. Adopt material design, just before new design system is introduced.
36. Learn that colors mean different things in different cultures and you don’t have RTL.
37. Jump on the gen AI & Web3 bandwagon, only to find it’s not your band, or your wagon.
38. Therapy. Because by now, you realize you might need professional help.
39. Start planning for the next update.