@here is there any performance difference between DataBinding / ViewBinding and Kotlin Synthetics ?

Yes, kotlin synthetics is backed by hashmap (or sparse array), so lookup happens each time you're accessing the view. VB just generates a class with a field per view. On the other hand KS is lazy, so findViewBindId will be called for each view separately at the first access time. VB calls findViewById for all views immediately at the binding creation time.

Thanks @bezrukov

Kotlin Synthetic are deprecated, whatever it’s faster or not it’s probably not a good idea to use them

Since when @gildor?

sorry, you right, only Anko was deprected, before it was under the same project, now it’s just android-extensions gradle plugin But I still think use Kotlin Synthetic is a bad idea

Also, what about Data Binding v/s VB ? Should we use Databinding ?

It’s much more complex question. If your goal is to replace findViewById and be more type safe when you work layouts, just use VB, they are faster to compile DataBinding work with views is just a side effect, main feature is binding you data to XML layout directly and generate this glue code for you

To be more specific, what would be the best approach for scenarios in DataBinding vs ViewBinding 1. Where we use <include> layouts and 2. Where we use some recycler views/ custom View Classes. Thanks in advance ! 🙂

not sure that I got your question