4 ms·
No need to use kapt to kill compilation times. Data Binding is good enough. We started using it a year ago and since then instant run does not work and the debu
by seviu 9y ago
No need to use kapt to kill compilation times. Data Binding is good enough. We started using it a year ago and since then instant run does not work and the debugger takes three minutes to start. Sometimes it mixes generated classes and we have to do a full clean / rebuild.
Since then we have introduced Kotlin and Dagger and we are super happy with it.
As with Dagger, the learning curve is pretty steep. Having it working with modules + activities + fragments + architecture components has been a real challenge but we love it.
For those who are struggling with Dagger: version 2.10 introduced major changes for Android, for good reasons, but it made much harder to use and understand. Many tutorials focus on Dagger < 2.10. You probably should ignore those.
And for those who are going crazy with compilation times, Jrebel for Android is a huge time saver. It has an incremental compiler which works with annotation processors. They will stop supporting it in one year, but even then I think it is worth using it. Who knows: if enough people buy licenses maybe they reconsider killing it.