I love modern Android. I spent years absent from the Android developer ecosystem after my first app in 2014 and then during a co-op in 2016. And when I was back to Android in 2022, I was in shock how many things have changed, a new language—Kotlin, Coroutines, LiveData, Flows, many other Jetpack libraries, and countless quality of life improvements in the Android Studio! Every day since I’ve been leaning something new and still don’t feel I’ve caught up. But you know one familiar thing I am still seeing? Tons of XMLs! Even with the view binding, there’s still so much boilerplate codes and disconnections between business logic and UI definitions. In the years I haven’t worked with Android, I explored other mobile platforms like iOS and React Native, both of which untilizes declarative UI framworks. If there’s one thing I miss from those times, it’s the flexibility of declaring and changing UI states in a single stream of code. With Compose, now I can truly say Android has evolved into a new species. And I can’t wait to see Compose more and more in production. #Android #JetpackCompose
The Google Drive team rebuilt its app home page from the ground up in half the time using our recommended architecture and Jetpack Compose. Learn how they did it → https://goo.gle/3PUcSaK The original home screen required over 12,000 lines of code. The new Compose-based home screen has many new features and only required 5,100 lines of code—a 57% reduction. Testing the new UI in Jetpack Compose also required significantly less code. Before Compose, Drive developers used roughly 9,000 lines of code to test about 62% of the UI. With Compose, it took only 2,200 lines to test over 80% of the new UI. Get started with Jetpack Compose → https://goo.gle/3TOirc4