Can anyone share any tips / strategies for efficiently migrating a ton of legacy Data Binding based ...

# compose-android

[james]

Can anyone share any tips / strategies for efficiently migrating a ton of legacy Data Binding based views to Compose? I work on a large B2B app with many modules and many screens, and even though we have been using Compose in production for 18 months we still have 50+ Fragments or Activities that are using Data Binding. As you can imagine, kapt has a huge impact on our build performance, and Data Binding is the only dependency we have left that doesn’t support KSP 😢

At least 25 of these views are not using two-way binding, so perhaps we could simply migrate those ones to View Binding rather than Compose as a phase 1 step, and Compose as a phase 2.. but the rest which use two way binding may be better done as a full DB->Compose conversion in one go?

Any advice here much appreciated 🙏

[Jakub Syty]

to reduce build impact it would be good to move those screens to separate module with kapt

[Jakub Syty]

as long as you build the dependency tree properly it won't be built until anything there changes

[Jakub Syty]

and you can use kapt only in that single module

[Jakub Syty]

with that approach you can separate modules that require further migration. Of course this is not that easy if the code is tightly coupled. But i think it would be nice to solve that issue too 🙂