PeterMobDev
@pemodev.bsky.social
Android Dev & Kotlin 📱 | Learning 🚀 | I'm currently studying to become a mobile developer. On this account, I'll be sharing my entire journey—the lessons I learn, the projects I build, and the challenges I face.
It really makes you think about which option to choose. My common approach is just to go with whatever is most readable in that context. Thanks!
September 18, 2025 at 2:24 AM
It really makes you think about which option to choose. My common approach is just to go with whatever is most readable in that context. Thanks!
That's a great point. You're right, a more verbose, object-oriented approach using classes and interfaces is definitely more readable. It makes a lot of sense.
September 18, 2025 at 2:21 AM
That's a great point. You're right, a more verbose, object-oriented approach using classes and interfaces is definitely more readable. It makes a lot of sense.
Thank you so much for the reply and the link! 🙏 That was super helpful. I'm seeing now that it's not just about keeping the composable simple, but also about preventing unwanted work from happening every time the UI re-renders. That makes a lot of sense now. 💡
September 14, 2025 at 12:12 PM
Thank you so much for the reply and the link! 🙏 That was super helpful. I'm seeing now that it's not just about keeping the composable simple, but also about preventing unwanted work from happening every time the UI re-renders. That makes a lot of sense now. 💡