Android uygulama geli\u015ftirme, kullan\u0131c\u0131 aray\u00fcz\u00fc (UI) g\u00fcncellemelerini y\u00f6netme, veri ak\u0131\u015f\u0131n\u0131 sa\u011flama ve \u00f6zellikle cihaz\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fc (Activity, Fragment gibi bile\u015fenlerin olu\u015fturulmas\u0131, ba\u015flat\u0131lmas\u0131, duraklat\u0131lmas\u0131, yok edilmesi) ile do\u011fru bir \u015fekilde etkile\u015fim kurma konusunda karma\u015f\u0131kl\u0131klar bar\u0131nd\u0131r\u0131r. Bu zorluklar\u0131n \u00fcstesinden gelmek i\u00e7in Google, Android Architecture Components serisinin bir par\u00e7as\u0131 olarak LiveData<\/strong>‘y\u0131 tan\u0131tt\u0131. LiveData, g\u00f6zlemlenebilir bir veri tutucu s\u0131n\u0131f\u0131d\u0131r ve en \u00f6nemli \u00f6zelli\u011fi, Android ya\u015fam d\u00f6ng\u00fcs\u00fcne duyarl\u0131 olmas\u0131d\u0131r. Bu makalede, LiveData’n\u0131n ne oldu\u011funu, nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131, avantajlar\u0131n\u0131, kullan\u0131m senaryolar\u0131n\u0131, d\u00f6n\u00fc\u015f\u00fcmlerini ve modern Android geli\u015ftirme ekosistemindeki yerini ayr\u0131nt\u0131l\u0131 olarak inceleyece\u011fiz.<\/p>\n LiveData, bir veri par\u00e7as\u0131n\u0131 tutan ve bu veri de\u011fi\u015fti\u011finde ba\u011fl\u0131 g\u00f6zlemcilere (observer) bildirim g\u00f6nderen bir veri tutucu s\u0131n\u0131ft\u0131r. Ancak LiveData’y\u0131 di\u011fer g\u00f6zlemlenebilir veri tutuculardan ay\u0131ran en temel \u00f6zellik, Android ya\u015fam d\u00f6ng\u00fcs\u00fcne duyarl\u0131 olmas\u0131d\u0131r. Bu, LiveData’n\u0131n yaln\u0131zca g\u00f6zlemci aktif bir ya\u015fam d\u00f6ng\u00fcs\u00fc durumundaysa (\u00f6rne\u011fin, Activity veya Fragment LiveData’n\u0131n geli\u015ftirilmesinin temel nedenleri ve \u00e7\u00f6zd\u00fc\u011f\u00fc sorunlar \u015funlard\u0131r:<\/p>\n * Bellek S\u0131z\u0131nt\u0131lar\u0131:<\/strong> Geleneksel g\u00f6zlemci desenlerinde, g\u00f6zlemciler manuel olarak abonelikten \u00e7\u0131kar\u0131lmazsa, Activity veya Fragment yok edildi\u011finde bile referanslar\u0131 tutmaya devam ederek bellek s\u0131z\u0131nt\u0131lar\u0131na yol a\u00e7abilirler. LiveData, ya\u015fam d\u00f6ng\u00fcs\u00fcne duyarl\u0131 oldu\u011fu i\u00e7in bu sorunu otomatik olarak \u00e7\u00f6zer. LiveData’y\u0131 anlamak i\u00e7in baz\u0131 temel kavramlar\u0131 bilmek \u00f6nemlidir:<\/p>\n LiveData’n\u0131n kalbinde yatan bu \u00f6zellik, onun Android bile\u015fenlerinin (Activity, Fragment, Service gibi) ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc tan\u0131mas\u0131n\u0131 ve buna g\u00f6re davranmas\u0131n\u0131 sa\u011flar. Bir LiveData, temel olarak g\u00f6zlemci desenini kullan\u0131r. Bir * * LiveData’n\u0131n sundu\u011fu avantajlar, modern Android uygulamalar\u0131nda onu vazge\u00e7ilmez bir bile\u015fen haline getirmi\u015ftir:<\/p>\n G\u00f6zlemciler, genellikle Activity veya Fragment gibi ya\u015fam d\u00f6ng\u00fcs\u00fc bile\u015fenleridir. Bu bile\u015fenler yok edildi\u011finde, LiveData otomatik olarak ili\u015fkili g\u00f6zlemciyi abonelikten \u00e7\u0131kar\u0131r. Bu sayede, yok edilmi\u015f bir Activity’nin hala veri g\u00fcncellemelerini dinlemesini ve dolay\u0131s\u0131yla bellek s\u0131z\u0131nt\u0131s\u0131na yol a\u00e7mas\u0131n\u0131 engeller.<\/p>\n LiveData, g\u00f6zlemci aktif bir ya\u015fam d\u00f6ng\u00fcs\u00fc durumunda de\u011filse (\u00f6rne\u011fin, Activity duraklat\u0131lm\u0131\u015f veya arka planda ise) veri g\u00fcncellemelerini g\u00f6ndermez. Bu, uygulaman\u0131n, UI bile\u015fenleri g\u00fcncellemeyi i\u015fleyemeyecek durumdayken kilitlenmesini \u00f6nler.<\/p>\n Bir g\u00f6zlemci (\u00f6rne\u011fin, bir Activity) aktif duruma ge\u00e7ti\u011finde (\u00f6rne\u011fin, kullan\u0131c\u0131 uygulamaya geri d\u00f6nd\u00fc\u011f\u00fcnde), LiveData otomatik olarak en son veriyi g\u00f6nderir. Bu, kullan\u0131c\u0131n\u0131n her zaman g\u00fcncel veriyi g\u00f6rmesini sa\u011flar ve UI’\u0131n eski veya ge\u00e7ersiz verilerle g\u00f6sterilmesini engeller.<\/p>\n LiveData’n\u0131n API’si olduk\u00e7a basittir. Veriyi ayarlamak ( En temel ve kritik avantaj\u0131d\u0131r. Geli\u015ftiricilerin, Android ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn karma\u015f\u0131kl\u0131klar\u0131yla manuel olarak u\u011fra\u015fma ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r. Bu, daha az hataya a\u00e7\u0131k ve daha sa\u011flam uygulamalar yaz\u0131lmas\u0131na olanak tan\u0131r.<\/p>\n Geleneksel olarak, veri g\u00fcncellemelerini ve ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc y\u00f6netmek i\u00e7in LiveData’n\u0131n yayg\u0131n kullan\u0131m senaryosu, genellikle ViewModel ile birlikte kullan\u0131lmas\u0131d\u0131r. Bu, veri ak\u0131\u015f\u0131n\u0131 ve UI mant\u0131\u011f\u0131n\u0131 UI bile\u015fenlerinden (Activity\/Fragment) ay\u0131rmak i\u00e7in \u00f6nerilen bir yakla\u015f\u0131md\u0131r.<\/p>\n ViewModel, UI ile ilgili verileri ya\u015fam d\u00f6ng\u00fcs\u00fc de\u011fi\u015fikliklerine (\u00f6rne\u011fin, ekran d\u00f6nd\u00fcrme) ra\u011fmen tutabilen bir s\u0131n\u0131ft\u0131r. LiveData, ViewModel i\u00e7inde veriyi tutmak ve bu veriyi UI’a g\u00fcvenli bir \u015fekilde sunmak i\u00e7in m\u00fckemmel bir ara\u00e7t\u0131r.<\/p>\n 1. ViewModel’de Burada UI bile\u015fenleri (Activity veya Fragment), ViewModel’deki 1. Yukar\u0131daki \u00f6rnekte, 2. 3. Bazen bir Bu metot, bir UI’da Bu metot, bir Burada Kotlin Coroutines, Android’de e\u015fzamans\u0131z programlama i\u00e7in modern ve \u00f6nerilen bir yakla\u015f\u0131md\u0131r. Bu \u00f6rnekte, LiveData, \u00e7o\u011fu senaryo i\u00e7in m\u00fckemmel bir \u00e7\u00f6z\u00fcm olsa da, baz\u0131 s\u0131n\u0131rlamalara sahiptir ve baz\u0131 durumlarda daha g\u00fc\u00e7l\u00fc alternatifler d\u00fc\u015f\u00fcn\u00fclebilir.<\/p>\n 1. Geri Bas\u0131n\u00e7 (Backpressure) Mekanizmas\u0131 Yok:<\/strong> LiveData’n\u0131n bir geri bas\u0131n\u00e7 mekanizmas\u0131 yoktur. Bu, g\u00f6zlemcinin verileri \u00fcretildi\u011fi h\u0131zda i\u015fleyemedi\u011fi durumlarda (\u00f6rne\u011fin, \u00e7ok h\u0131zl\u0131 akan veri ak\u0131\u015flar\u0131), LiveData’n\u0131n en son de\u011feri tutmas\u0131 ve \u00f6nceki de\u011ferleri atmas\u0131 anlam\u0131na gelir. Bu, baz\u0131 reaktif programlama senaryolar\u0131nda sorun yaratabilir. 1. Kotlin Flow (Coroutines):<\/strong> Kotlin Coroutines’in bir par\u00e7as\u0131 olan Flow, LiveData’n\u0131n bir\u00e7ok avantaj\u0131n\u0131 sunarken, ayn\u0131 zamanda geri bas\u0131n\u00e7 deste\u011fi, zengin operat\u00f6rler ve daha esnek ak\u0131\u015f kontrol\u00fc gibi ek yetenekler sa\u011flar. Flow, \u00f6zellikle karma\u015f\u0131k veri ak\u0131\u015flar\u0131, s\u00fcrekli g\u00fcncellenen veriler ve geri bas\u0131n\u00e7 gerektiren senaryolar i\u00e7in g\u00fc\u00e7l\u00fc bir alternatiftir. 2. RxJava\/RxKotlin:<\/strong> Reaktif programlama i\u00e7in uzun s\u00fcredir kullan\u0131lan g\u00fc\u00e7l\u00fc bir k\u00fct\u00fcphanedir. LiveData, genellikle UI katman\u0131 ile ViewModel aras\u0131ndaki veri ak\u0131\u015f\u0131 i\u00e7in yeterli ve basit bir \u00e7\u00f6z\u00fcmd\u00fcr. Daha karma\u015f\u0131k veri katman\u0131 veya i\u015f mant\u0131\u011f\u0131 senaryolar\u0131nda, Flow veya RxJava gibi daha g\u00fc\u00e7l\u00fc reaktif ak\u0131\u015f k\u00fct\u00fcphaneleri tercih edilebilir. Modern Android geli\u015ftirme, genellikle ViewModel’de LiveData’y\u0131 kullan\u0131rken, Repository katman\u0131nda Flow’u kullanarak bu iki teknolojiyi birle\u015ftiren bir yakla\u015f\u0131m\u0131 benimser.<\/p>\n LiveData’y\u0131 verimli ve do\u011fru bir \u015fekilde kullanmak i\u00e7in baz\u0131 en iyi uygulamalar\u0131 takip etmek \u00f6nemlidir:<\/p>\n 1. ViewModel’den Sadece 2. UI’da 3. Arka Plan \u0130\u015flemlerini 4. 5. 6. Hata Durumlar\u0131n\u0131 Y\u00f6netme:<\/strong> LiveData, varsay\u0131lan olarak hata durumlar\u0131n\u0131 do\u011frudan y\u00f6netmez. Veri nesnenizin i\u00e7ine bir 7. Test Edilebilirlik:<\/strong> LiveData, JUnit testlerinde kolayca test edilebilir. Android LiveData, modern Android uygulama geli\u015ftirmede veri ak\u0131\u015f\u0131n\u0131 y\u00f6netmek i\u00e7in g\u00fc\u00e7l\u00fc, ya\u015fam d\u00f6ng\u00fcs\u00fcne duyarl\u0131 ve kullan\u0131m\u0131 kolay bir \u00e7\u00f6z\u00fcmd\u00fcr. Bellek s\u0131z\u0131nt\u0131lar\u0131n\u0131, kilitlenmeleri ve karma\u015f\u0131k ya\u015fam d\u00f6ng\u00fcs\u00fc y\u00f6netimini otomatikle\u015ftirerek geli\u015ftiricilerin UI ve i\u015f mant\u0131\u011f\u0131na odaklanmas\u0131n\u0131 sa\u011flar. ViewModel ile birlikte kullan\u0131ld\u0131\u011f\u0131nda, uygulamalar daha sa\u011flam, bak\u0131m\u0131 daha kolay ve daha test edilebilir hale gelir.<\/p>\nLiveData Nedir ve Neden \u00d6nemlidir?<\/h3>\n
STARTED<\/code> veya RESUMED<\/code> durumundaysa) g\u00fcncellemeleri g\u00f6nderece\u011fi anlam\u0131na gelir. G\u00f6zlemci STOPPED<\/code> durumdaysa, LiveData herhangi bir g\u00fcncelleme g\u00f6ndermez. G\u00f6zlemci DESTROYED<\/code> durumdaysa, LiveData otomatik olarak g\u00f6zlemciyi abonelikten \u00e7\u0131kar\u0131r ve bellek s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nler.<\/p>\n
\n* Kilitlenmeler (Crashes):<\/strong> UI bile\u015fenleri aktif de\u011filken veri g\u00fcncellemeleri almaya devam etmek, uygulaman\u0131n kilitlenmesine neden olabilir. LiveData, yaln\u0131zca aktif g\u00f6zlemcilere g\u00fcncelleme g\u00f6ndererek bu t\u00fcr kilitlenmeleri engeller.
\n* Karma\u015f\u0131k Ya\u015fam D\u00f6ng\u00fcs\u00fc Y\u00f6netimi:<\/strong> Android’in ya\u015fam d\u00f6ng\u00fcs\u00fc karma\u015f\u0131kt\u0131r ve Activity\/Fragment’\u0131n farkl\u0131 durumlar\u0131 aras\u0131nda ge\u00e7i\u015f yaparken veri ak\u0131\u015f\u0131n\u0131 ve UI g\u00fcncellemelerini manuel olarak y\u00f6netmek hataya a\u00e7\u0131kt\u0131r. LiveData, bu y\u00f6netimi otomatikle\u015ftirerek geli\u015ftiricinin y\u00fck\u00fcn\u00fc azalt\u0131r.
\n* Veri Tutarl\u0131l\u0131\u011f\u0131:<\/strong> LiveData, bir g\u00f6zlemci aktif hale geldi\u011finde (\u00f6rne\u011fin, bir Activity arka plandan \u00f6n plana geldi\u011finde), en son veriyi an\u0131nda almas\u0131n\u0131 sa\u011flar. Bu, kullan\u0131c\u0131 aray\u00fcz\u00fcn\u00fcn her zaman g\u00fcncel veriyi g\u00f6stermesini garanti eder.
\n* Daha Az Boilerplate Kodu:<\/strong> Ya\u015fam d\u00f6ng\u00fcs\u00fc y\u00f6netimi i\u00e7in gereken manuel kontrol ve if-else bloklar\u0131n\u0131 ortadan kald\u0131rarak daha temiz ve okunabilir kod yazmaya olanak tan\u0131r.<\/p>\nTemel Kavramlar<\/h3>\n
Ya\u015fam D\u00f6ng\u00fcs\u00fc Bilinci (Lifecycle-awareness)<\/h4>\n
LifecycleOwner<\/code> (genellikle Activity veya Fragment) ile ili\u015fkilendirildi\u011finde, LiveData yaln\u0131zca bu LifecycleOwner<\/code> aktif durumdayken (yani STARTED<\/code> veya RESUMED<\/code> durumdayken) g\u00f6zlemcilere veri g\u00fcncellemeleri g\u00f6nderir. LifecycleOwner<\/code> STOPPED<\/code> durumuna ge\u00e7ti\u011finde g\u00fcncellemeler durdurulur, DESTROYED<\/code> durumuna ge\u00e7ti\u011finde ise g\u00f6zlemci otomatik olarak abonelikten \u00e7\u0131kar\u0131l\u0131r. Bu mekanizma, uygulaman\u0131n performans\u0131n\u0131 art\u0131r\u0131r ve kaynak t\u00fcketimini optimize eder.<\/p>\nObserver Pattern (G\u00f6zlemci Deseni)<\/h4>\n
LiveData<\/code> nesnesi, g\u00f6zlemlenen veriyi tutar. Observer<\/code> aray\u00fcz\u00fcn\u00fc uygulayan bir s\u0131n\u0131f (genellikle Activity veya Fragment), bu LiveData<\/code> nesnesine abone olur. LiveData<\/code> i\u00e7indeki veri de\u011fi\u015fti\u011finde, t\u00fcm abone olan Observer<\/code>‘lara bildirim g\u00f6nderilir. Fark, LiveData’n\u0131n bu bildirimleri g\u00f6ndermeden \u00f6nce g\u00f6zlemcinin ya\u015fam d\u00f6ng\u00fcs\u00fc durumunu kontrol etmesidir.<\/p>\nLiveData S\u0131n\u0131f\u0131<\/h4>\n
LiveData<\/code> soyut bir s\u0131n\u0131ft\u0131r ve do\u011frudan \u00f6rneklenemez. Genellikle MutableLiveData<\/code> veya MediatorLiveData<\/code> gibi alt s\u0131n\u0131flar\u0131 kullan\u0131l\u0131r.<\/p>\nMutableLiveData vs. LiveData<\/h4>\n
MutableLiveDataLiveData<\/code>‘n\u0131n de\u011fi\u015ftirilebilir bir alt s\u0131n\u0131f\u0131d\u0131r. value<\/code> \u00f6zelli\u011fini veya postValue()<\/code> metodunu kullanarak veriyi de\u011fi\u015ftirebilirsiniz. Bu, genellikle ViewModel i\u00e7inde veriyi g\u00fcncelleyen ve UI’a yans\u0131tan birincil LiveData t\u00fcr\u00fcd\u00fcr.<\/p>\nval myMutableLiveData = MutableLiveDataLiveDataMutableLiveData<\/code>‘n\u0131n aksine, LiveData<\/code> s\u0131n\u0131f\u0131n\u0131n kendisi value<\/code> \u00f6zelli\u011fini veya postValue()<\/code> metodunu d\u0131\u015far\u0131ya a\u00e7maz. Bu, genellikle ViewModel’den UI’a veri sa\u011flarken kullan\u0131l\u0131r. ViewModel’deki MutableLiveData<\/code>‘y\u0131 \u00f6zel (private) tutarak, UI’\u0131n do\u011frudan veriyi de\u011fi\u015ftirmesini engeller ve veri ak\u0131\u015f\u0131n\u0131 tek y\u00f6nl\u00fc hale getiririz.<\/p>\nprivate val _myMutableLiveData = MutableLiveDataLiveData’n\u0131n Avantajlar\u0131<\/h3>\n
1. Bellek S\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00d6nleme<\/h4>\n
2. Kilitlenmeleri \u00d6nleme<\/h4>\n
3. Veri Tutarl\u0131l\u0131\u011f\u0131<\/h4>\n
4. Basit Kullan\u0131m<\/h4>\n
setValue<\/code>\/postValue<\/code>) ve g\u00f6zlemlemek (observe<\/code>) kolayd\u0131r. Bu, \u00f6\u011frenme e\u011frisini d\u00fc\u015f\u00fcr\u00fcr ve geli\u015ftirme s\u00fcrecini h\u0131zland\u0131r\u0131r.<\/p>\n5. Ya\u015fam D\u00f6ng\u00fcs\u00fc Fark\u0131ndal\u0131\u011f\u0131<\/h4>\n
6. Daha Az Boilerplate Kodu<\/h4>\n
onResume()<\/code>, onPause()<\/code>, onDestroy()<\/code> gibi metotlarda manuel kontroller ve abonelik\/abonelikten \u00e7\u0131karma i\u015flemleri yapmak gerekirdi. LiveData bu boilerplate kodu b\u00fcy\u00fck \u00f6l\u00e7\u00fcde azalt\u0131r.<\/p>\nLiveData Nas\u0131l Kullan\u0131l\u0131r?<\/h3>\n
ViewModel ile Entegrasyon<\/h4>\n
MutableLiveData<\/code> Kullan\u0131m\u0131:<\/strong>
\n ViewModel i\u00e7inde, d\u0131\u015far\u0131dan de\u011fi\u015ftirilebilecek veriler i\u00e7in MutableLiveData<\/code> kullan\u0131l\u0131r. Ancak bu MutableLiveData<\/code> genellikle private<\/code> olarak tan\u0131mlan\u0131r.<\/p>\n\/\/ MyViewModel.kt\n import androidx.lifecycle.LiveData\n import androidx.lifecycle.MutableLiveData\n import androidx.lifecycle.ViewModel\n\n class MyViewModel : ViewModel() {\n private val _counter = MutableLiveData_counter<\/code> \u00f6zel (private) oldu\u011fu i\u00e7in sadece ViewModel i\u00e7inden de\u011fi\u015ftirilebilir. counter<\/code> ise d\u0131\u015far\u0131ya LiveData<\/code> olarak a\u00e7\u0131ld\u0131\u011f\u0131 i\u00e7in UI sadece onu g\u00f6zlemleyebilir, de\u011fi\u015ftiremez. Bu, tek y\u00f6nl\u00fc veri ak\u0131\u015f\u0131n\u0131 (Unidirectional Data Flow) destekler.<\/p>\nUI Katman\u0131nda G\u00f6zlemleme (Activity\/Fragment)<\/h4>\n
LiveData<\/code>‘y\u0131 g\u00f6zlemleyerek veri de\u011fi\u015fikliklerine tepki verir.<\/p>\nobserve()<\/code> Metodu:<\/strong>
\n LiveData<\/code>‘y\u0131 g\u00f6zlemlemek i\u00e7in observe()<\/code> metodunu kullan\u0131r\u0131z. Bu metod iki parametre al\u0131r: bir LifecycleOwner<\/code> (genellikle this<\/code> – Activity\/Fragment’\u0131n kendisi) ve bir Observer<\/code> lambda ifadesi.<\/p>\n\/\/ MainActivity.kt\n import androidx.appcompat.app.AppCompatActivity\n import android.os.Bundle\n import android.widget.Button\n import android.widget.TextView\n import androidx.activity.viewModels\n\n class MainActivity : AppCompatActivity() {\n\n private val viewModel: MyViewModel by viewModels() \/\/ ViewModel'i ba\u015flat\n\n override fun onCreate(savedInstanceState: Bundle?) {\n super.onCreate(savedInstanceState)\n setContentView(R.layout.activity_main)\n\n val textViewCounter: TextView = findViewById(R.id.textViewCounter)\n val buttonIncrement: Button = findViewById(R.id.buttonIncrement)\n\n \/\/ LiveData'y\u0131 g\u00f6zlemle\n viewModel.counter.observe(this) { newCounterValue ->\n \/\/ Veri de\u011fi\u015fti\u011finde UI'\u0131 g\u00fcncelle\n textViewCounter.text = \"Saya\u00e7: $newCounterValue\"\n }\n\n buttonIncrement.setOnClickListener {\n viewModel.incrementCounter()\n }\n }\n }<\/code><\/pre>\nviewModel.counter.observe(this)<\/code> \u00e7a\u011fr\u0131s\u0131, MainActivity<\/code> ya\u015fam d\u00f6ng\u00fcs\u00fcne duyarl\u0131 bir g\u00f6zlemci olu\u015fturur. MainActivity<\/code> aktif durumdayken (STARTED veya RESUMED), newCounterValue<\/code> her de\u011fi\u015fti\u011finde lambda ifadesi \u00e7al\u0131\u015f\u0131r ve textViewCounter<\/code> g\u00fcncellenir. Activity duraklat\u0131ld\u0131\u011f\u0131nda veya yok edildi\u011finde, LiveData otomatik olarak g\u00f6zlemlemeyi durdurur veya abonelikten \u00e7\u0131kar\u0131r.<\/p>\nobserveForever()<\/code> (Dikkatli Kullan\u0131m):<\/strong>
\n Bu metot, g\u00f6zlemcinin ya\u015fam d\u00f6ng\u00fcs\u00fcnden ba\u011f\u0131ms\u0131z olarak s\u00fcrekli olarak veri g\u00fcncellemelerini almas\u0131n\u0131 sa\u011flar. Ancak bu durumda, bellek s\u0131z\u0131nt\u0131lar\u0131n\u0131 \u00f6nlemek i\u00e7in g\u00f6zlemciyi manuel olarak removeObserver()<\/code> ile kald\u0131rman\u0131z gerekir. Genellikle uygulama seviyesindeki singleton’lar veya Service’ler gibi ya\u015fam d\u00f6ng\u00fcs\u00fc olmayan bile\u015fenler i\u00e7in kullan\u0131l\u0131r ve Activity\/Fragment i\u00e7inde kullan\u0131lmas\u0131 tavsiye edilmez.<\/p>\nremoveObserver()<\/code>:<\/strong>
\n observeForever()<\/code> ile eklenen bir g\u00f6zlemciyi kald\u0131rmak veya belirli durumlarda bir g\u00f6zlemciyi manuel olarak durdurmak i\u00e7in kullan\u0131l\u0131r. LiveData’n\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fc fark\u0131ndal\u0131\u011f\u0131 sayesinde observe()<\/code> ile eklenen g\u00f6zlemciler i\u00e7in genellikle manuel kald\u0131rmaya gerek kalmaz.<\/p>\nLiveData D\u00f6n\u00fc\u015f\u00fcmleri (LiveData Transformations)<\/h3>\n
LiveData<\/code>‘n\u0131n de\u011ferini do\u011frudan kullanmak yerine, onu ba\u015fka bir t\u00fcre d\u00f6n\u00fc\u015ft\u00fcrmek veya birden fazla LiveData<\/code> kayna\u011f\u0131n\u0131 birle\u015ftirmek isteyebiliriz. Transformations<\/code> s\u0131n\u0131f\u0131 ve MediatorLiveData<\/code>, bu t\u00fcr senaryolar i\u00e7in g\u00fc\u00e7l\u00fc ara\u00e7lar sunar.<\/p>\nTransformations.map()<\/code><\/h4>\nLiveData<\/code>‘n\u0131n de\u011ferini d\u00f6n\u00fc\u015ft\u00fcrerek yeni bir LiveData<\/code> nesnesi d\u00f6nd\u00fcr\u00fcr. Kaynak LiveData<\/code>‘n\u0131n de\u011feri de\u011fi\u015fti\u011finde, d\u00f6n\u00fc\u015f\u00fcm uygulan\u0131r ve yeni LiveData<\/code>‘n\u0131n de\u011feri g\u00fcncellenir.
\n\u00d6rne\u011fin, bir User<\/code> nesnesinden sadece kullan\u0131c\u0131n\u0131n ad\u0131n\u0131 g\u00f6r\u00fcnt\u00fclemek istedi\u011fimizde:<\/p>\ndata class User(val id: String, val name: String, val email: String)\n\nclass UserViewModel : ViewModel() {\n private val _user = MutableLiveDatauserViewModel.userName.observe(this) { name -> ... }<\/code> \u015feklinde userName<\/code>‘i g\u00f6zlemleyebiliriz. _user<\/code> de\u011fi\u015fti\u011finde, userName<\/code> otomatik olarak g\u00fcncellenecektir.<\/p>\nTransformations.switchMap()<\/code><\/h4>\nLiveData<\/code>‘n\u0131n de\u011ferine ba\u011fl\u0131 olarak farkl\u0131 bir LiveData<\/code> nesnesi d\u00f6nd\u00fcr\u00fcr. Genellikle, bir girdi de\u011ferine g\u00f6re veritaban\u0131 sorgular\u0131n\u0131 veya a\u011f isteklerini tetiklemek i\u00e7in kullan\u0131l\u0131r. \u00d6rne\u011fin, bir arama sorgusuna g\u00f6re kullan\u0131c\u0131 listesini getirmek:<\/p>\nclass SearchViewModel : ViewModel() {\n private val _searchQuery = MutableLiveData_searchQuery<\/code> de\u011fi\u015fti\u011finde, switchMap<\/code> yeni sorguya g\u00f6re UserRepository.searchUsers()<\/code> metodunu \u00e7a\u011f\u0131r\u0131r ve bu metodun d\u00f6nd\u00fcrd\u00fc\u011f\u00fc LiveData<\/code>‘y\u0131 searchResults<\/code> olarak sunar.<\/p>\nMediatorLiveData<\/code><\/h4>\nMediatorLiveData<\/code>, birden fazla LiveData<\/code> kayna\u011f\u0131n\u0131 g\u00f6zlemlemenize ve bu kaynaklardan herhangi biri de\u011fi\u015fti\u011finde kendi de\u011ferini g\u00fcncellemenize olanak tan\u0131r. Bu, karma\u015f\u0131k ba\u011f\u0131ml\u0131l\u0131klara sahip verileri birle\u015ftirmek i\u00e7in idealdir.
\n\u00d6rne\u011fin, hem kullan\u0131c\u0131 ad\u0131 hem de e-posta g\u00fcncellendi\u011finde bir profil \u00f6zetini g\u00fcncellemek:<\/p>\nclass ProfileViewModel : ViewModel() {\n val userName = MutableLiveDataprofileSummary<\/code>, userName<\/code> veya userEmail<\/code>‘den herhangi biri de\u011fi\u015fti\u011finde g\u00fcncellenir. addSource()<\/code> metodu ile birden fazla LiveData<\/code> kayna\u011f\u0131 eklenebilir.<\/p>\nLiveData ve Coroutines<\/h3>\n
androidx.lifecycle:lifecycle-livedata-ktx<\/code> k\u00fct\u00fcphanesi, LiveData ile Coroutines’i entegre etmek i\u00e7in bir dizi uzant\u0131 fonksiyonu ve liveData<\/code> builder’\u0131 sunar.<\/p>\nliveData<\/code> Builder<\/h4>\nliveData<\/code> builder, bir Coroutine blo\u011fu i\u00e7inde LiveData<\/code> \u00fcretebilmenizi sa\u011flar. Bu, uzun s\u00fcren veya e\u015fzamans\u0131z i\u015flemleri (\u00f6rne\u011fin, a\u011f istekleri, veritaban\u0131 sorgular\u0131) LiveData<\/code>‘ya ba\u011flamak i\u00e7in \u00e7ok kullan\u0131\u015fl\u0131d\u0131r.<\/p>\nimport androidx.lifecycle.liveData\nimport kotlinx.coroutines.Dispatchers\nimport kotlinx.coroutines.delay\n\nclass MyDataViewModel : ViewModel() {\n\n val data: LiveDataliveData<\/code> builder, belirtilen CoroutineContext<\/code>‘te (\u00f6rne\u011fin Dispatchers.IO<\/code> a\u011f veya disk i\u015flemleri i\u00e7in) \u00e7al\u0131\u015f\u0131r. emit()<\/code> fonksiyonunu kullanarak LiveData<\/code>‘n\u0131n de\u011ferini g\u00fcncelleyebiliriz. liveData<\/code> blo\u011fu iptal edildi\u011finde (\u00f6rne\u011fin, ViewModel temizlendi\u011finde), i\u00e7indeki Coroutine de otomatik olarak iptal edilir.<\/p>\nemitSource()<\/code><\/h4>\nemitSource()<\/code> metodu, liveData<\/code> blo\u011fu i\u00e7inde ba\u015fka bir LiveData<\/code> kayna\u011f\u0131n\u0131 ge\u00e7ici olarak yay\u0131nlaman\u0131za olanak tan\u0131r. Bu, bir \u00f6nbellek (cache) mekanizmas\u0131 veya farkl\u0131 veri kaynaklar\u0131 aras\u0131nda ge\u00e7i\u015f yapmak i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\nclass CachedDataViewModel : ViewModel() {\n private val repository = MyRepository()\n\n val cachedData: LiveDatacachedData<\/code> ilk olarak repository.getCacheData()<\/code>‘dan gelen de\u011ferleri yay\u0131nlar. Ard\u0131ndan, fetchFreshData()<\/code> tamamland\u0131\u011f\u0131nda, yeni veri yay\u0131nlan\u0131r ve emitSource<\/code> ile yay\u0131nlanan \u00f6nceki kaynak otomatik olarak durdurulur.<\/p>\nLiveData’n\u0131n S\u0131n\u0131rlamalar\u0131 ve Alternatifleri<\/h3>\n
S\u0131n\u0131rlamalar<\/h4>\n
\n2. Temel Operasyonlar:<\/strong> LiveData, map<\/code>, switchMap<\/code>, addSource<\/code> gibi temel d\u00f6n\u00fc\u015f\u00fcmleri destekler. Ancak RxJava veya Kotlin Flow gibi reaktif ak\u0131\u015f k\u00fct\u00fcphanelerinin sundu\u011fu zengin operat\u00f6r setine sahip de\u011fildir.
\n3. Tek De\u011fer Yay\u0131mlama:<\/strong> LiveData, varsay\u0131lan olarak yaln\u0131zca en son de\u011feri tutar ve yay\u0131mlar. Bir de\u011ferin ge\u00e7mi\u015fini veya bir dizi olay\u0131 i\u015flemek i\u00e7in tasarlanmam\u0131\u015ft\u0131r.<\/p>\nAlternatifler<\/h4>\n
StateFlow<\/code> ve SharedFlow<\/code> gibi \u00f6zel Flow t\u00fcrleri, LiveData’ya benzer \u015fekilde durum tutma ve payla\u015fma yetenekleri sunar.
\n * Avantajlar\u0131:<\/strong> Geri bas\u0131n\u00e7, zengin operat\u00f6rler, yap\u0131land\u0131r\u0131lm\u0131\u015f e\u015fzamanl\u0131l\u0131k, cold\/hot ak\u0131\u015flar.
\n * Ne Zaman Kullan\u0131l\u0131r:<\/strong> Karma\u015f\u0131k veri ak\u0131\u015flar\u0131, s\u00fcrekli g\u00fcncellenen veriler, performans kritik uygulamalar, reaktif programlama desenleri.<\/p>\nObservable<\/code>, Flowable<\/code>, Single<\/code>, Maybe<\/code>, Completable<\/code> gibi \u00e7e\u015fitli tipler sunar ve geni\u015f bir operat\u00f6r setiyle karma\u015f\u0131k asenkron i\u015flemleri y\u00f6netmeyi kolayla\u015ft\u0131r\u0131r.
\n * Avantajlar\u0131:<\/strong> \u00c7ok g\u00fc\u00e7l\u00fc ve kapsaml\u0131, geni\u015f topluluk deste\u011fi, zengin operat\u00f6rler, geri bas\u0131n\u00e7 deste\u011fi.
\n * Ne Zaman Kullan\u0131l\u0131r:<\/strong> Mevcut RxJava projeleri, \u00e7ok karma\u015f\u0131k reaktif ak\u0131\u015flar, \u00f6zel gereksinimler. Ancak Kotlin Coroutines’in y\u00fckseli\u015fiyle yeni projelerde daha az tercih edilmektedir.<\/p>\nLiveData ile \u0130lgili En \u0130yi Uygulamalar<\/h3>\n
LiveData<\/code> Pozlamak:<\/strong> ViewModel’den d\u0131\u015far\u0131ya MutableLiveData<\/code> yerine LiveData<\/code> pozlayarak, UI’\u0131n veriyi do\u011frudan de\u011fi\u015ftirmesini engelleyin. Bu, tek y\u00f6nl\u00fc veri ak\u0131\u015f\u0131n\u0131 korur ve veri tutarl\u0131l\u0131\u011f\u0131n\u0131 sa\u011flar.<\/p>\n\/\/ Do\u011fru\n private val _data = MutableLiveDataMutableLiveData<\/code> Kullanmaktan Ka\u00e7\u0131nma:<\/strong> Activity veya Fragment i\u00e7inde MutableLiveData<\/code> tan\u0131mlamaktan ka\u00e7\u0131n\u0131n. UI, ViewModel’den gelen veriyi g\u00f6zlemlemeli, ancak do\u011frudan de\u011fi\u015ftirmemeli. UI’dan ViewModel’e olaylar\u0131 iletmek i\u00e7in fonksiyon \u00e7a\u011fr\u0131lar\u0131 kullan\u0131n.<\/p>\nViewModel<\/code> veya Repository<\/code>‘de Yapma:<\/strong> A\u011f istekleri, veritaban\u0131 i\u015flemleri gibi uzun s\u00fcreli veya I\/O yo\u011fun i\u015flemlerini ViewModel veya Repository katman\u0131nda ger\u00e7ekle\u015ftirin. LiveData’y\u0131 sadece bu i\u015flemlerin sonu\u00e7lar\u0131n\u0131 UI’a iletmek i\u00e7in kullan\u0131n. liveData<\/code> builder, bu t\u00fcr i\u015flemleri LiveData’ya ba\u011flamak i\u00e7in idealdir.<\/p>\nMediatorLiveData<\/code> ile Karma\u015f\u0131k Durumlar\u0131 Y\u00f6netme:<\/strong> Birden fazla LiveData kayna\u011f\u0131ndan gelen verileri birle\u015ftirmeniz veya farkl\u0131 ko\u015fullara g\u00f6re LiveData’n\u0131n de\u011ferini g\u00fcncellemeniz gerekti\u011finde MediatorLiveData<\/code>‘y\u0131 kullan\u0131n.<\/p>\nliveData<\/code> Builder ile E\u015fzamans\u0131z \u0130\u015flemleri Basitle\u015ftirme:<\/strong> Coroutines ile e\u015fzamans\u0131z veri y\u00fckleme i\u015flemleri i\u00e7in liveData<\/code> builder’\u0131 tercih edin. Bu, kodunuzu daha okunabilir ve y\u00f6netilebilir hale getirir, ayn\u0131 zamanda ya\u015fam d\u00f6ng\u00fcs\u00fc fark\u0131ndal\u0131\u011f\u0131n\u0131 otomatik olarak sa\u011flar.<\/p>\nResource<\/code> veya Result<\/code> s\u0131n\u0131f\u0131 sarmalayarak (\u00f6rne\u011fin, LiveDataInstantTaskExecutorRule<\/code> kullanarak LiveData’n\u0131n arka plan i\u015flemlerinin an\u0131nda y\u00fcr\u00fct\u00fclmesini sa\u011flayabilir ve g\u00f6zlemcilerin do\u011fru de\u011ferleri al\u0131p almad\u0131\u011f\u0131n\u0131 kontrol edebilirsiniz.<\/p>\nSonu\u00e7<\/h3>\n
Transformations<\/code> ve MediatorLiveData<\/code> gibi \u00f6zellikler, veri d\u00f6n\u00fc\u015f\u00fcmlerini ve birle\u015ftirmelerini basitle\u015ftirirken, Kotlin Coroutines ile entegrasyonu (