Learning Android Development

Jetpack Compose: The Future of Android UI

Android has come a long way and Jetpack Compose is there to grow

Elye
Mobile App Development Publication
6 min readDec 21, 2020

--

Photo by Tomasz Frankowski on Unsplash

Recently, I looked into how Android has progressed in how the code interacts with the UI (View) over the years. Much has been happening the last few years… and finally, it is landing with Jetpack Composes.

Of course, the question arises — is this just hype or is it to stay? Should one start learning it, or just wait for the next real messiah?

My view is, even if Jetpack Compose might not be the final way of how Android interacts with the UI, it will definitely be the path moving forward.

Here’s why…

Making XML working with code has never been perfect.

Since day one, XML is the way for one to define the UI of the App.

The little infamous findViewById where every iteration tries to get rid of using it, starting with ButterKnife, then Kotlin Synthetics, and DataBinding, and then ViewBinding of late.

Things have improved over the years, but there’s still imperfection in using the XML approach. The UI logic works best using Kotlin than the XML, hence making two separate UI entity that Google still try hard to reconcile them.

There’s even a try to move the Modal from the Code into XML in the DataBinding feature.

Still then too much code boilerplate for the support. Moving more things into XML is not desirable.

XML + Code will never be perfect.

Jetpack Compose, on the other hand, removes the need for XML and replaces it with complete Kotlin Code for the UI.

--

--