X'inhuma View Binding u Data Binding fl-Android? · Prattika ta' Intervisti tal-IT

X'inhuma View Binding u Data Binding fl-Android?

View Binding u Data Binding huma features ta' Android għall-konnessjoni tal-kodiċi mal-views fil-layouts XML b'mod aktar sigur u konvenjenti mill-qadim findViewById. View Binding jipprovdi referenzi type-safe tal-views; Data Binding ta' aktar, jorbat id-data direttament mal-layouts.

Il-problema: findViewById

text

The old way: findViewById to get view references:
  val button = findViewById<Button>(R.id.myButton)
  ✗ verbose; NOT type-safe (cast errors); NOT null-safe (wrong id → null → crash at runtime)
→ View/Data Binding solve these.

kotlin

// View Binding generates a binding class per layout with typed references to its views
val binding = ActivityMainBinding.inflate(layoutInflater)
setContentView(binding.root)
binding.myButton.setOnClickListener { /* ... */ }   // typed, null-safe, no findViewById
binding.titleText.text = "Hello"
// → type-safe (compile-checked), null-safe, concise — the recommended replacement for findViewById

xml

<!-- Data Binding lets you bind data/expressions directly in the layout XML -->
<TextView android:text="@{user.name}" />        <!-- binds to a user object's name -->
<Button android:onClick="@{() -> viewModel.submit()}" />

text

DATA BINDING (more powerful than View Binding):
  → bind layout views directly to data/ViewModels in XML (expressions, two-way binding)
  → can reduce UI-update boilerplate; supports observable data → UI auto-updates
  → more complex; View Binding is simpler and often sufficient
→ Modern apps increasingly use Jetpack COMPOSE instead (no XML binding needed).

X'inhuma View Binding u Data Binding fl-Android?

Il-problema: findViewById

View Binding — referenzi type-safe tal-views

Data Binding — orbat id-data direttament fl-XML

Għaliex hija importanti