Rotating the phone to landscape caused users of the app to experience a suboptimal experience. Turns out we had some legacy code that was manually calculating the size and position of each “chip”. 😱

ones and zeros
Rotating the phone to landscape caused users of the app to experience a suboptimal experience. Turns out we had some legacy code that was manually calculating the size and position of each “chip”. 😱
In this talk, I share my initial thoughts on Kotlin Multiplatform Mobile (KMM). I walk through how I started on this journey. I also compare my experience with KMM to that of working with Flutter. Flutter is another cross-platform solution that I’ve worked with in the past.
Â
Everyone’s busy. Code is committed every day. Yet the feature fails to ship. Have you ever had this happen on your team? No doubt. But how can you figure out what’s holding the team back? Code commits.
Continue ReadingWe’re adding the use of dynamic feature modules to our app. This will help us to improve build speeds, conditionally include features and decouple our code. As noted previously, we make use of Dagger Multibinding and the Android Job library to handle our background tasks.
When we created our first feature module we ran into an issue when we attempted to move the associated Job
classes. Let me walk you through the problem, the solution we settled on and then proposed next steps.