Data Binding — asoslar, Android da ikki tomonlama bog'lash

Android da Data Binding nima?

Data Binding — 2015 yilda Google I/O da taqdim etilgan va Android Gradle Plugin 1.5 da barqarorlashtirilgan qo'llab-quvvatlash kutubxonasi (Android Jetpack). U UI komponentlarini XML da Activity yoki Fragment kodida findViewById() chaqirmasdan to'g'ridan-to'g'ri layout ichida ma'lumot manbalari (POJO, ViewModel, LiveData) bilan bog'lash imkonini beradi.

Ishlash printsipi: XML layout <layout> tegiga o'raladi, unda ma'lumot turi bilan <variable> e'lon qilinadi. Layout ichida ma'lumotlar jingalak qavslardagi ifodalar orqali joylashtiriladi @{}. Kompilyatsiya bosqichida Android Gradle Plugin to'g'ri turlar bilan View ga to'g'ridan-to'g'ri havolalar va ma'lumot o'rnatish usullarini o'z ichiga olgan Binding sinfini (masalan, ActivityMainBinding) yaratadi.

Android Developers so'roviga ko'ra (2024), Data Binding bog'lash mantiqini XML ga ko'chirish orqali Activity/Fragment dagi UI kod hajmini 30–50% kamaytiradi. Noto'g'ri View turi bilan bog'liq xatolar soni (findViewById() da ClassCastException) nolga tushadi, chunki barcha turlar kompilyatsiya bosqichida tekshiriladi.

Data Binding vs ViewBinding: nimani tanlash kerak

ViewBinding — Android Studio 3.6 da (2020) paydo bo'lgan Data Binding ning engilroq alternativi. ViewBinding har bir layout fayl uchun Binding sinfini yaratadi, lekin ifodalar, o'zgaruvchilar va reaktivlikni qo'llab-quvvatlamaydi. Asosiy mezonlar bo'yicha taqqoslash:

Google tavsiyasi (Android Developers, 2025): ko'pchilik loyihalar uchun ViewBinding yetarli — Data Binding ning qo'shimcha yuklamasisiz View ga type-safe kirishni ta'minlaydi. Data Binding ni tanlang, agar kerak bo'lsa: (1) XML dan LiveData/StateFlow bilan reaktiv bog'lash, (2) formalar uchun ikki tomonlama bog'lash, (3) maxsus atributlar uchun BindingAdapter, (4) formatlash uchun XML da ifodalar. IT Sectr da oddiy ekranlar uchun ViewBinding, murakkab formalar va panellar uchun Data Binding ishlatamiz.

Ikki tomonlama bog'lash: @{} va @={}

Bir tomonlama bog'lash (@{}) ma'lumotni manbadan (ViewModel) View ga uzatadi. Ikki tomonlama bog'lash (@={}) ma'lumotni har ikki yo'nalishda sinxronlashtiradi: View dagi o'zgarish (matn kiritish, Switch almashtirish) avtomatik ravishda manbani yangilaydi.

<layout xmlns:android="http://schemas.android.com/apk/res/android">
    <data>
        <variable
            name="viewModel"
            type="com.example.app.LoginViewModel" />
    </data>

    <LinearLayout ...>
        <!-- Bir tomonlama: ViewModel dan TextView ga ma'lumot -->
        <TextView
            android:text="@{viewModel.userName}" />

        <!-- Ikki tomonlama: EditText o'zgarishlari → ViewModel, ViewModel → EditText -->
        <EditText
            android:text="@{=viewModel.email}" />

        <CheckBox
            android:checked="@{=viewModel.agreeToTerms}" />
    </LinearLayout>
</layout>

Ikki tomonlama bog'lash uchun ViewModel ObservableField, LiveData yoki StateFlow dan foydalanishi kerak. Foydalanuvchi kiritishi orqali ma'lumot o'zgarganda, Data Binding avtomatik ravishda manbaning setterini chaqiradi. Muhim: ikki tomonlama bog'lash @InverseBindingAdapter aniqlangan atributlar bilan ishlaydi. Android o'rnatilgan adapterlarni taqdim etadi: text, checked, visibility, progress, rating va boshqa standart atributlar uchun.

@BindingAdapter: maxsus atributlar va konvertorlar

@BindingAdapter — Kotlin extension funksiyalari uchun annotatsiya, istalgan View atributi uchun maxsus bog'lash mantiqini belgilash imkonini beradi. Masalan, XML da URL ko'rsatilganda Glide orqali rasm yuklash yoki TextView bilan bog'lashda sanani formatlash.

// URL bo'yicha rasm yuklash uchun BindingAdapter
@BindingAdapter("imageUrl")
fun ImageView.setImageUrl(url: String?) {
    Glide.with(this.context)
        .load(url)
        .placeholder(R.drawable.placeholder)
        .error(R.drawable.error)
        .into(this)
}

// Bir necha atributli BindingAdapter
@BindingAdapter("visibleGone")
fun View.setVisibleGone(visible: Boolean) {
    visibility = if (visible) View.VISIBLE else View.GONE
}

// Konvertor bilan BindingAdapter (formatDate)
@BindingAdapter("formattedDate")
fun TextView.setFormattedDate(timestamp: Long) {
    text = SimpleDateFormat("dd.MM.yyyy", Locale.getDefault()).format(Date(timestamp))
}

<!-- XML da BindingAdapter dan foydalanish -->
<ImageView
    imageUrl="@{user.avatarUrl}"
    android:layout_width="48dp"
    android:layout_height="48dp" />

<TextView
    formattedDate="@{message.createdAt}"
    visibleGone="@{message.isVisible}" />

@BindingAdapter bir nechta atributni qabul qilishi mumkin (requireAll = true/false), bu qiymatlarni birlashtirish imkonini beradi. Masalan, @BindingAdapter("imageUrl", "circleCrop") — agar circleCrop true bo'lsa, Glide CircleCrop transformatsiyasini qo'llaydi. Google ma'lumotlariga ko'ra (Android Performance, 2024), Data Binding da Glide bilan BindingAdapter RecyclerView skrollashda sekundiga 60 kadrgacha ishlaydi, chunki asinxron yuklash UI threadini bloklamaydi.

Data Binding LiveData va StateFlow bilan

Data Binding LiveData ni native qo'llab-quvvatlaydi Android Architecture Components 1.0 versiyasidan boshlab. Agar layoutdagi o'zgaruvchi LiveData turiga ega bo'lsa, Binding avtomatik ravishda unga obuna bo'ladi va qiymat o'zgarganda UI ni yangilaydi. To'g'ri ishlash uchun Binding sinfida LifecycleOwner o'rnatilishi kerak: binding.lifecycleOwner = viewLifecycleOwner.

// LiveData bilan ViewModel
class WeatherViewModel : ViewModel() {
    private val _temperature = MutableLiveData("--")
    val temperature: LiveData<String> get() = _temperature

    val cityName = MutableLiveData("Moskva")
    val weatherIcon = MutableLiveData(R.drawable.ic_sunny)

    fun refresh() {
        viewModelScope.launch {
            _temperature.value = weatherRepository.getTemperature()
        }
    }
}

// Fragment da:
val binding = FragmentWeatherBinding.inflate(inflater, container, false)
binding.viewModel = weatherViewModel
binding.lifecycleOwner = viewLifecycleOwner  // ← LiveData uchun majburiy

<layout>
    <data>
        <variable name="viewModel" type="com.example.app.WeatherViewModel" />
    </data>

    <LinearLayout ...>
        <TextView
            android:text="@string/temperature_format(viewModel.temperature)" />
        <TextView android:text="@{viewModel.cityName}" />
        <ImageView
            android:src="@{viewModel.weatherIcon}"
            contentDescription="@{viewModel.cityName}" />
    </LinearLayout>
</layout>

Data Binding StateFlow ni lifecycle 2.5.0 dan Flow.asLiveData() yoki to'g'ridan-to'g'ri konvertatsiya orqali qo'llab-quvvatlaydi. Data Binding da StateFlow ishlatganda, hayot siklini binding.lifecycleOwner orqali o'rnatilganligiga ishonch hosil qiling. LifecycleOwner o'rnatilmagan bo'lsa, LiveData/StateFlow UI ni yangilamaydi, chunki Binding obunachi qachon faol ekanligini bilmaydi.

Kod namunalari: Data Binding Kotlin va XML da

1-misol: Data Binding bilan profil ekrani

Avatar, ism, bio va tahrirlash tugmasi bilan to'liq profil ekrani. ViewModel reaktivlik uchun ObservableField dan foydalanadi.

<layout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto">
    <data>
        <variable name="profile" type="com.example.app.ProfileViewModel" />
    </data>

    <androidx.constraintlayout...>
        <ImageView
            app:imageUrl="@{profile.avatarUrl}"
            android:contentDescription="@{profile.name}" />

        <TextView
            android:text="@{profile.name}"
            android:textStyle="bold" />

        <TextView
            android:text="@{profile.bio}"
            android:visibility="@{profile.hasBio ? View.VISIBLE : View.GONE}" />

        <Button
            android:onClick="@{() -> profile.onEdit()}"
            android:text="@string/edit" />
    </androidx.constraintlayout...>
</layout>

class ProfileViewModel : ViewModel() {
    val name = ObservableField("Anna Petrova")
    val bio = ObservableField("Android-ishlab chiqaruvchi, 5 yil tajriba")
    val avatarUrl = ObservableField("https://example.com/avatar.jpg")
    val hasBio = ObservableBoolean(true)

    fun onEdit() {
        // Profilni tahrirlash mantig'i
    }
}

// Fragment da:
val binding = FragmentProfileBinding.inflate(inflater, container, false)
binding.profile = profileViewModel
binding.lifecycleOwner = viewLifecycleOwner

2-misol: Ikki tomonlama bog'lash bilan kirish formasi

Maydon validatsiyasi va kirish tugmasi bilan kirish formasi. Ikki tomonlama bog'lash (@={}) foydalanuvchi kiritishini ViewModel bilan sinxronlashtiradi.

<layout xmlns:android="http://schemas.android.com/apk/res/android">
    <data>
        <variable name="login" type="com.example.app.LoginViewModel" />
    </data>

    <LinearLayout ...>
        <TextInputLayout>
            <TextInputEditText
                android:text="@{=login.email}"
                android:hint="@string/email_hint" />
        </TextInputLayout>

        <TextInputLayout>
            <TextInputEditText
                android:text="@{=login.password}"
                android:inputType="textPassword" />
        </TextInputLayout>

        <Button
            android:onClick="@{() -> login.onLogin()}"
            android:enabled="@{login.isValid}"
            android:text="@string/login" />

        <ProgressBar
            android:visibility="@{login.isLoading ? View.VISIBLE : View.GONE}" />
    </LinearLayout>
</layout>

XML da ifodalar ishlatiladi: tugma holati uchun @{login.isValid} (faol/faol emas), yuklash indikatori uchun @{login.isLoading ? View.VISIBLE : View.GONE}, ikki tomonlama sinxronizatsiya uchun @{=login.email}. Barcha validatsiya mantig'i ViewModel da yashaydi, View faqat holatni ko'rsatadi. Google ma'lumotlariga ko'ra (Android Guide, 2025), bu yondashuv UI mantiqidagi xatolar sonini 50–60% kamaytiradi.