Blogs

From Android Q onwards devices can now operate in a fully gestural system navigation mode. In that mode, there is no longer an on-screen back button, instead users can swipe from both edges to navigate back.

Your icon is one of the most important assets in your app. With a bit of luck, users might even put it on their main launcher screen!

Wrapping up this series on modularization I’d like to share some of the things we’ve learned at Philips Hue while going through this process the past year.

Now that we have a clear idea of how a modularized app could look like how can this be applied to an existing app? Part four will dive deeper into how existing apps can be sliced and how you can gradually migrate to a fully modularized architecture.

With a clear view on how multi-module apps should be architected, let’s dive into a real-life practical example. We’ll discover how the architecture results in a clear application structure, how navigation is handled, how to use staged rollouts, how to test everything and even look at a production app that is using this architecture.

Now that we’ve established that modularization is a really good thing to strive for, how should a modularized app look like? How are the different modules connected?

Modularizing your app seems to be all the hype these days. But why should you actually care? What are the benefits for you and your team?

Are you living the dream? Is your code so clean it makes your eyes just tear a little? Can’t think of anything you would still like to refactor?

Architecture components are one of the most exciting things that happened to Android in the past years. But how do you effectively go about and testing this?

Sitting in our own couch, in our own house, kids safely asleep upstairs,… The road here was brutal, but the result is extraordinary. The past year was (hopefully) the busiest year of my entire life.