{"id":30679,"date":"2025-09-30T18:02:10","date_gmt":"2025-09-30T15:02:10","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/"},"modified":"2025-09-30T18:02:10","modified_gmt":"2025-09-30T15:02:10","slug":"android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/","title":{"rendered":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife"},"content":{"rendered":"<p><body><\/p>\n<p>Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin&#8217;in g\u00fc\u00e7l\u00fc <code>sealed class<\/code> \u00f6zelli\u011fi!<\/p>\n<p>Android uygulama geli\u015ftirirken, kullan\u0131c\u0131 aray\u00fcz\u00fcn\u00fcz\u00fcn (UI) farkl\u0131 durumlar\u0131 y\u00f6netmesi, tek seferlik olaylar\u0131 do\u011fru \u015fekilde i\u015flemesi ve a\u011f isteklerinden gelen \u00e7e\u015fitli yan\u0131tlar\u0131 tutarl\u0131 bir \u015fekilde ele almas\u0131 gerekti\u011fini s\u0131k\u00e7a g\u00f6r\u00fcr\u00fcz. \u00d6rne\u011fin, bir veri y\u00fcklenirken &#8220;Y\u00fckleniyor&#8230;&#8221;, hata olu\u015ftu\u011funda &#8220;Bir hata olu\u015ftu!&#8221; ve ba\u015far\u0131l\u0131 oldu\u011funda verinin kendisinin g\u00f6sterilmesi gerekir. Ya da bir butona bas\u0131ld\u0131\u011f\u0131nda sadece bir kez g\u00f6sterilmesi gereken bir &#8220;Snackbar&#8221; mesaj\u0131 veya ba\u015fka bir ekrana navigasyon gibi olaylar\u0131 nas\u0131l ele almal\u0131y\u0131z?<\/p>\n<p>Bu senaryolar, uygun bir yap\u0131land\u0131rma olmadan h\u0131zla bir &#8220;callback cehennemi&#8221;ne veya &#8220;Boolean bayraklar&#8221; labirentine d\u00f6n\u00fc\u015febilir. Geli\u015ftiriciler olarak, bu t\u00fcr sorunlar\u0131 \u00e7\u00f6zmek i\u00e7in s\u00fcrekli daha iyi yollar ar\u0131yoruz. \u0130\u015fte tam bu noktada Kotlin&#8217;in <code>sealed class<\/code> \u00f6zelli\u011fi devreye giriyor. Bu makalede, <code>sealed class<\/code>&#8216;lar\u0131n temel mant\u0131\u011f\u0131ndan ba\u015flayarak, Android projelerinizde hemen kullanabilece\u011finiz \u00fc\u00e7 pratik ve \u00fcretim haz\u0131r &#8220;tarif&#8221; sunaca\u011f\u0131z. Bu tarifler, UI durumu y\u00f6netimi, tek seferlik olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almada size yeni bir bak\u0131\u015f a\u00e7\u0131s\u0131 kazand\u0131racak. Haz\u0131rsan\u0131z, bu lezzetli kod tariflerini birlikte ke\u015ffedelim!<\/p>\n<h2>Sealed Class Nedir ve Neden Android Geli\u015ftirmede Vazge\u00e7ilmezdir?<\/h2>\n<p><code>sealed class<\/code>&#8216;lar, Kotlin&#8217;in en g\u00fc\u00e7l\u00fc \u00f6zelliklerinden biridir ve t\u00fcr g\u00fcvenli\u011fi ile ifade g\u00fcc\u00fcn\u00fc bir araya getirir. Temel olarak, bir <code>sealed class<\/code> (veya <code>sealed interface<\/code>), belirli bir s\u0131n\u0131f hiyerar\u015fisi i\u00e7indeki t\u00fcm alt s\u0131n\u0131flar\u0131n\u0131n derleme zaman\u0131nda bilindi\u011fini garanti eden k\u0131s\u0131tlanm\u0131\u015f bir hiyerar\u015fi olu\u015fturman\u0131za olanak tan\u0131r. Bu, \u00f6zellikle bir durum veya olay\u0131n belirli ve s\u0131n\u0131rl\u0131 say\u0131da olas\u0131 de\u011feri oldu\u011funda \u00e7ok kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n<p>Bir <code>enum class<\/code>&#8216;\u0131 d\u00fc\u015f\u00fcn\u00fcn: <code>enum class Status { LOADING, SUCCESS, ERROR }<\/code>. Bu yap\u0131, durumlar\u0131n sadece belirli sabit de\u011ferlerden ibaret oldu\u011fu senaryolar i\u00e7in harikad\u0131r. Ancak, ya durumlar\u0131m\u0131za veri de eklemek istersek? \u00d6rne\u011fin, <code>SUCCESS<\/code> durumunda y\u00fcklenen veriyi, <code>ERROR<\/code> durumunda ise hata mesaj\u0131n\u0131 ta\u015f\u0131mak istersek <code>enum class<\/code> yetersiz kal\u0131r. \u0130\u015fte <code>sealed class<\/code> burada fark yarat\u0131r. <code>sealed class<\/code>&#8216;\u0131n her bir alt s\u0131n\u0131f\u0131, kendi \u00f6zel verilerini ve davran\u0131\u015flar\u0131n\u0131 i\u00e7erebilirken, yine de ana <code>sealed class<\/code>&#8216;\u0131n k\u0131s\u0131tl\u0131 hiyerar\u015fisinin bir par\u00e7as\u0131 olmaya devam eder. Bu sayede, uygulaman\u0131z\u0131n farkl\u0131 durumlar\u0131n\u0131 veya olaylar\u0131n\u0131 temsil eden nesneleri kolayca olu\u015fturabilir, bunlar\u0131 tek bir \u00e7at\u0131 alt\u0131nda toplayabilir ve derleme zaman\u0131nda kapsaml\u0131 kontrol sa\u011flayabilirsiniz.<\/p>\n<p>Peki, <code>sealed class<\/code>&#8216;lar\u0131 bu kadar vazge\u00e7ilmez k\u0131lan nedir? En \u00f6nemli avantajlar\u0131ndan biri, Kotlin&#8217;in <code>when<\/code> ifadesiyle m\u00fckemmel entegrasyonudur. Bir <code>sealed class<\/code>&#8216;\u0131n t\u00fcm olas\u0131 alt s\u0131n\u0131flar\u0131n\u0131 <code>when<\/code> ifadesinde ele ald\u0131\u011f\u0131n\u0131zda, Kotlin derleyicisi bu durumu alg\u0131lar ve ba\u015fka bir <code>else<\/code> dal\u0131na ihtiya\u00e7 duymadan &#8220;exhaustiveness&#8221; (t\u00fcm durumlar\u0131n ele al\u0131nd\u0131\u011f\u0131) kontrol\u00fcn\u00fc yapar. Bu, gelecekte yeni bir alt s\u0131n\u0131f ekledi\u011finizde, <code>when<\/code> ifadesini kullanan t\u00fcm yerlerde bir derleme hatas\u0131 alaca\u011f\u0131n\u0131z anlam\u0131na gelir. Bu hata, eksik durum y\u00f6netimini proaktif olarak tespit etmenizi sa\u011flar ve b\u00f6ylece \u00e7al\u0131\u015fma zaman\u0131 hatalar\u0131n\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde azalt\u0131r. \u00d6rne\u011fin, bir UI durumunu y\u00f6netirken, <code>Loading<\/code>, <code>Success<\/code> ve <code>Error<\/code> durumlar\u0131na ek olarak yeni bir <code>Empty<\/code> durumu ekledi\u011finizde, bu yeni durumu ele almayan t\u00fcm <code>when<\/code> bloklar\u0131 derleme hatas\u0131 verecek ve sizi bu durumu ele almaya zorlayacakt\u0131r. Bu, \u00f6zellikle b\u00fcy\u00fck ve karma\u015f\u0131k uygulamalarda kodun s\u00fcrd\u00fcr\u00fclebilirli\u011fini ve g\u00fcvenli\u011fini art\u0131ran kritik bir \u00f6zelliktir. <code>abstract class<\/code> veya <code>interface<\/code> kulland\u0131\u011f\u0131n\u0131zda bu t\u00fcr bir derleme zaman\u0131 kontrol\u00fcne sahip olamazs\u0131n\u0131z, \u00e7\u00fcnk\u00fc derleyici t\u00fcm olas\u0131 uygulamalar\u0131 bilemez.<\/p>\n<p>Basit bir \u00f6rnekle <code>sealed class<\/code>&#8216;\u0131n g\u00fcc\u00fcn\u00fc g\u00f6relim:<\/p>\n<pre><code>\nsealed class Shape {\n    data class Circle(val radius: Double) : Shape()\n    data class Rectangle(val width: Double, val height: Double) : Shape()\n    object Triangle : Shape() \/\/ \u00dc\u00e7genin \u00f6zel bir verisi olmad\u0131\u011f\u0131n\u0131 varsayal\u0131m\n}\n\nfun calculateArea(shape: Shape): Double {\n    return when (shape) {\n        is Shape.Circle -> Math.PI * shape.radius * shape.radius\n        is Shape.Rectangle -> shape.width * shape.height\n        is Shape.Triangle -> 10.0 \/\/ Varsay\u0131msal sabit alan\n        \/\/ Yeni bir Shape t\u00fcr\u00fc ekledi\u011finizde, buras\u0131 derleme hatas\u0131 verecektir!\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Yukar\u0131daki \u00f6rnekte, <code>Shape<\/code> bir <code>sealed class<\/code>'t\u0131r. <code>Circle<\/code>, <code>Rectangle<\/code> ve <code>Triangle<\/code> onun alt s\u0131n\u0131flar\u0131d\u0131r. <code>calculateArea<\/code> fonksiyonunda, <code>when<\/code> ifadesi <code>Shape<\/code>'in t\u00fcm olas\u0131 alt s\u0131n\u0131flar\u0131n\u0131 kapsad\u0131\u011f\u0131 i\u00e7in, Kotlin derleyicisi bu kodun g\u00fcvenli oldu\u011funu ve ba\u015fka bir duruma ihtiya\u00e7 duymad\u0131\u011f\u0131n\u0131 bilir. Bu sayede, durumlar aras\u0131ndaki ge\u00e7i\u015fleri ve veri ak\u0131\u015f\u0131n\u0131 \u00e7ok daha y\u00f6netilebilir hale getiririz.<\/p>\n<div class=\"info-box\">\n  Uzman \u0130pucu: <code>sealed class<\/code>'lar varsay\u0131lan olarak <code>abstract<\/code>'t\u0131r, bu nedenle kendileri do\u011frudan \u00f6rneklenemezler. Alt s\u0131n\u0131flar\u0131 ise herhangi bir t\u00fcrden olabilir: <code>data class<\/code>, <code>class<\/code>, <code>object<\/code> veya hatta ba\u015fka bir <code>sealed class<\/code>.\n<\/div>\n<h2>Android Uygulamalar\u0131nda Ekran Durumlar\u0131n\u0131 Sealed Class ile Nas\u0131l Y\u00f6netece\u011fiz?<\/h2>\n<p>Herhangi bir modern Android uygulamas\u0131nda, kullan\u0131c\u0131 aray\u00fcz\u00fc s\u00fcrekli olarak farkl\u0131 durumlar aras\u0131nda ge\u00e7i\u015f yapar: veri y\u00fckleniyor olabilir, ba\u015far\u0131yla y\u00fcklenebilir, bir hata olu\u015fabilir veya belki de g\u00f6sterilecek hi\u00e7 veri yoktur. Bu durumlar\u0131 tutarl\u0131 ve g\u00fcvenli bir \u015fekilde y\u00f6netmek, uygulaman\u0131n kullan\u0131c\u0131 deneyimi ve kararl\u0131l\u0131\u011f\u0131 i\u00e7in kritik \u00f6neme sahiptir. Geleneksel yakla\u015f\u0131mlar genellikle bir dizi Boolean bayrak veya karma\u015f\u0131k mant\u0131k i\u00e7erir, bu da kodun okunabilirli\u011fini azalt\u0131r ve hatalara a\u00e7\u0131k hale getirir. \u0130\u015fte <code>sealed class<\/code>'lar\u0131n parlad\u0131\u011f\u0131 ilk alan, UI durum y\u00f6netimi.<\/p>\n<h3>Vaka Analizi: Bir Veri Y\u00fckleme Ekran\u0131<\/h3>\n<p>Hayal edin ki, bir film listesi uygulamas\u0131nda ana ekran\u0131n film verilerini bir API'den \u00e7ekmesi gerekiyor. Bu ekran\u0131n d\u00f6rt temel durumu olabilir:<\/p>\n<ol>\n<li><strong>Loading (Y\u00fckleniyor):<\/strong> Veriler hen\u00fcz API'den gelmedi ve bir y\u00fcklenme g\u00f6stergesi (\u00f6rne\u011fin, <code>ProgressBar<\/code>) g\u00f6sterilmeli.<\/li>\n<li><strong>Success (Ba\u015far\u0131l\u0131):<\/strong> Veriler ba\u015far\u0131yla \u00e7ekildi ve film listesi g\u00f6sterilmeli.<\/li>\n<li><strong>Error (Hata):<\/strong> A\u011f hatas\u0131, sunucu hatas\u0131 gibi bir sorun olu\u015ftu ve bir hata mesaj\u0131 g\u00f6sterilmeli.<\/li>\n<li><strong>Empty (Bo\u015f):<\/strong> Veriler ba\u015far\u0131yla \u00e7ekildi ancak liste bo\u015f (\u00f6rne\u011fin, API'den hi\u00e7 film gelmedi). Bu \u00f6zel bir ba\u015far\u0131 durumu olabilir, ancak kullan\u0131c\u0131ya \"Hi\u00e7 film bulunamad\u0131\" gibi bir mesaj g\u00f6stermek isteyebiliriz.<\/li>\n<\/ol>\n<p>Bu durumlar\u0131 <code>sealed class<\/code> ile temsil etmek, hem g\u00fcvenli hem de okunabilir bir \u00e7\u00f6z\u00fcm sunar.<\/p>\n<h3>Tarif 1: UI Durum Y\u00f6netimi i\u00e7in Sealed Class<\/h3>\n<p>\u0130lk ad\u0131m olarak, uygulaman\u0131z\u0131n ekran durumlar\u0131n\u0131 temsil edecek bir <code>sealed class<\/code> tan\u0131mlayal\u0131m. Bu s\u0131n\u0131f, her bir durumu ve ilgili veriyi i\u00e7erecek:<\/p>\n<pre><code>\n\/\/ data class ve object'ler ayn\u0131 sealed class'\u0131n alt s\u0131n\u0131flar\u0131 olabilir\nsealed class MovieListUiState {\n    object Loading : MovieListUiState()\n    data class Success(val movies: List<Movie>) : MovieListUiState()\n    data class Error(val message: String) : MovieListUiState()\n    object Empty : MovieListUiState() \/\/ Yeni eklenen durum\n}\n\ndata class Movie(val id: String, val title: String, val imageUrl: String) \/\/ Varsay\u0131msal Movie s\u0131n\u0131f\u0131\n\n<\/pre>\n<p><\/code><\/p>\n<p>\u015eimdi, bu <code>MovieListUiState<\/code>'i bir <code>ViewModel<\/code> i\u00e7inde nas\u0131l kullanaca\u011f\u0131m\u0131z\u0131 g\u00f6relim. <code>ViewModel<\/code>, UI durumunu y\u00f6netmek ve bunu <code>MutableStateFlow<\/code> arac\u0131l\u0131\u011f\u0131yla UI'a bildirmek i\u00e7in ideal bir yerdir:<\/p>\n<pre><code>\n\/\/ ViewModel Katman\u0131\nimport androidx.lifecycle.ViewModel\nimport androidx.lifecycle.viewModelScope\nimport kotlinx.coroutines.flow.MutableStateFlow\nimport kotlinx.coroutines.flow.StateFlow\nimport kotlinx.coroutines.launch\n\nclass MovieListViewModel(private val movieRepository: MovieRepository) : ViewModel() {\n\n    private val _uiState = MutableStateFlow<MovieListUiState>(MovieListUiState.Loading)\n    val uiState: StateFlow<MovieListUiState> = _uiState\n\n    init {\n        fetchMovies()\n    }\n\n    fun fetchMovies() {\n        viewModelScope.launch {\n            _uiState.value = MovieListUiState.Loading \/\/ Y\u00fckleme durumunu ba\u015flat\n            try {\n                val movies = movieRepository.getMovies()\n                if (movies.isEmpty()) {\n                    _uiState.value = MovieListUiState.Empty\n                } else {\n                    _uiState.value = MovieListUiState.Success(movies)\n                }\n            } catch (e: Exception) {\n                _uiState.value = MovieListUiState.Error(\"Filmler y\u00fcklenirken bir hata olu\u015ftu: ${e.localizedMessage}\")\n            }\n        }\n    }\n}\n\n\/\/ Varsay\u0131msal Repository Katman\u0131\nclass MovieRepository {\n    suspend fun getMovies(): List<Movie> {\n        kotlinx.coroutines.delay(2000) \/\/ A\u011f gecikmesi sim\u00fclasyonu\n        return if (Math.random() > 0.3) { \/\/ %70 ba\u015far\u0131l\u0131, %30 hata\n            if (Math.random() > 0.8) emptyList() \/\/ %20 bo\u015f liste\n            else listOf(\n                Movie(\"1\", \"Inception\", \"url1\"),\n                Movie(\"2\", \"The Matrix\", \"url2\"),\n                Movie(\"3\", \"Interstellar\", \"url3\")\n            )\n        } else {\n            throw IOException(\"A\u011f ba\u011flant\u0131s\u0131 hatas\u0131!\")\n        }\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Son olarak, bu durumu kullan\u0131c\u0131 aray\u00fcz\u00fcn\u00fczde (\u00f6rne\u011fin, bir Composable fonksiyonunda veya bir Fragment\/Activity'de) nas\u0131l t\u00fcketece\u011fimizi g\u00f6relim. Kotlin'in <code>when<\/code> ifadesi, <code>sealed class<\/code>'lar ile m\u00fckemmel bir uyum i\u00e7indedir ve t\u00fcm olas\u0131 durumlar\u0131 ele ald\u0131\u011f\u0131n\u0131zdan emin olman\u0131z\u0131 sa\u011flar:<\/p>\n<pre><code>\n\/\/ UI Katman\u0131 (Jetpack Compose \u00f6rne\u011fi)\nimport androidx.compose.foundation.layout.*\nimport androidx.compose.foundation.lazy.LazyColumn\nimport androidx.compose.foundation.lazy.items\nimport androidx.compose.material.CircularProgressIndicator\nimport androidx.compose.material.Text\nimport androidx.compose.runtime.Composable\nimport androidx.compose.runtime.collectAsState\nimport androidx.compose.runtime.getValue\nimport androidx.compose.ui.Alignment\nimport androidx.compose.ui.Modifier\nimport androidx.compose.ui.unit.dp\nimport androidx.lifecycle.viewmodel.compose.viewModel\nimport java.io.IOException\n\n@Composable\nfun MovieListScreen(viewModel: MovieListViewModel = viewModel()) {\n    val uiState by viewModel.uiState.collectAsState()\n\n    Box(modifier = Modifier.fillMaxSize(), contentAlignment = Alignment.Center) {\n        when (uiState) {\n            is MovieListUiState.Loading -> {\n                CircularProgressIndicator()\n                Text(\"Filmler y\u00fckleniyor...\", modifier = Modifier.padding(top = 80.dp))\n            }\n            is MovieListUiState.Success -> {\n                val movies = (uiState as MovieListUiState.Success).movies\n                LazyColumn(modifier = Modifier.fillMaxSize()) {\n                    items(movies) { movie ->\n                        Text(movie.title, modifier = Modifier.padding(16.dp))\n                    }\n                }\n            }\n            is MovieListUiState.Error -> {\n                val errorMessage = (uiState as MovieListUiState.Error).message\n                Column(horizontalAlignment = Alignment.CenterHorizontally) {\n                    Text(\"Hata: $errorMessage\", color = androidx.compose.ui.graphics.Color.Red)\n                    androidx.compose.material.Button(onClick = { viewModel.fetchMovies() }) {\n                        Text(\"Tekrar Dene\")\n                    }\n                }\n            }\n            is MovieListUiState.Empty -> { \/\/ Yeni durumu ele al\u0131yoruz\n                Text(\"Hi\u00e7 film bulunamad\u0131.\", modifier = Modifier.padding(16.dp))\n                androidx.compose.material.Button(onClick = { viewModel.fetchMovies() }) {\n                    Text(\"Yenile\")\n                }\n            }\n        }\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Bu \"yemek tarifi\" ile, uygulaman\u0131z\u0131n UI durumlar\u0131n\u0131 y\u00f6netmek i\u00e7in temiz, tip g\u00fcvenli ve kapsaml\u0131 bir yakla\u015f\u0131m elde etmi\u015f olursunuz. Yeni bir durum ekledi\u011finizde, derleyici sizi UI'da bu durumu ele almaya zorlayarak potansiyel hatalar\u0131n \u00f6n\u00fcne ge\u00e7er. Bu y\u00f6ntem, uygulaman\u0131z\u0131n b\u00fcy\u00fckl\u00fc\u011f\u00fc ve karma\u015f\u0131kl\u0131\u011f\u0131 ne olursa olsun tutarl\u0131 bir durum y\u00f6netim deseni sa\u011flaman\u0131za yard\u0131mc\u0131 olur. B\u00f6ylece, hem geli\u015ftirici deneyiminiz iyile\u015fir hem de son kullan\u0131c\u0131ya sunulan uygulaman\u0131n kalitesi artar.<\/p>\n<h2>Snackbar G\u00f6sterme veya Navigasyon Gibi Tek Seferlik Olaylar \u0130\u00e7in Sealed Class Nas\u0131l Kullan\u0131l\u0131r?<\/h2>\n<p>UI durum y\u00f6netimi kadar \u00f6nemli olan bir di\u011fer konu da, kullan\u0131c\u0131 aray\u00fcz\u00fcnde sadece bir kez ger\u00e7ekle\u015fmesi gereken \"tek seferlik olaylar\u0131n\" y\u00f6netilmesidir. \u00d6rne\u011fin, bir butona bas\u0131ld\u0131\u011f\u0131nda bir <code>Snackbar<\/code> mesaj\u0131 g\u00f6stermek, ba\u015fka bir ekrana gitmek (navigasyon), bir bildirim g\u00f6stermek veya bir kullan\u0131c\u0131ya uyar\u0131 penceresi sunmak gibi eylemler tek seferlik olaylard\u0131r. Bu t\u00fcr olaylar\u0131 do\u011frudan <code>StateFlow<\/code> veya <code>LiveData<\/code> gibi g\u00f6zlemlenebilir durum tutucularla y\u00f6netmeye \u00e7al\u0131\u015fmak, genellikle istenmeyen sonu\u00e7lara yol a\u00e7ar. \u00c7\u00fcnk\u00fc <code>StateFlow<\/code> de\u011fer tutucudur ve UI her yeniden olu\u015fturuldu\u011funda veya konfig\u00fcrasyon de\u011fi\u015fikli\u011finde (ekran d\u00f6nd\u00fcrme gibi) en son de\u011feri tekrar yayabilir, bu da ayn\u0131 olay\u0131n tekrar tekrar tetiklenmesine neden olabilir (\u00f6rne\u011fin, <code>Snackbar<\/code>'\u0131n s\u00fcrekli g\u00f6sterilmesi).<\/p>\n<h3>Vaka Analizi: Kullan\u0131c\u0131 Kay\u0131t Sonras\u0131 Geri Bildirim<\/h3>\n<p>Bir kullan\u0131c\u0131 kay\u0131t formunu doldurdu ve \"Kay\u0131t Ol\" butonuna bast\u0131. Sunucuya bir istek g\u00f6nderildi ve i\u015flem ba\u015far\u0131l\u0131 oldu. Bu durumda, kullan\u0131c\u0131ya \"Kay\u0131t i\u015flemi ba\u015far\u0131yla tamamland\u0131!\" mesaj\u0131n\u0131 bir <code>Snackbar<\/code> ile g\u00f6stermek ve ard\u0131ndan ana ekrana y\u00f6nlendirmek istiyoruz. E\u011fer bu olaylar <code>StateFlow<\/code> i\u00e7inde basit\u00e7e bir string mesaj olarak tutulursa, ekran d\u00f6nd\u00fcr\u00fcld\u00fc\u011f\u00fcnde <code>Snackbar<\/code> tekrar g\u00f6r\u00fcnebilir ve kullan\u0131c\u0131 tekrar ana ekrana y\u00f6nlendirilebilir ki bu istenmeyen bir durumdur.<\/p>\n<h3>Tarif 2: Tek Seferlik Olay Y\u00f6netimi i\u00e7in Sealed Class<\/h3>\n<p>Bu problemi \u00e7\u00f6zmek i\u00e7in, tek seferlik olaylar\u0131 temsil eden bir <code>sealed class<\/code> kullanabiliriz. Ancak, bu <code>sealed class<\/code>'\u0131 do\u011frudan bir <code>StateFlow<\/code> i\u00e7inde tutmak yerine, olaylar\u0131n yaln\u0131zca bir kez t\u00fcketilmesini sa\u011flamak i\u00e7in ek bir mekanizma, \u00f6rne\u011fin bir <code>Channel<\/code> veya Google'\u0131n \u00f6nerdi\u011fi gibi bir <code>Event<\/code> sarmalay\u0131c\u0131 s\u0131n\u0131f\u0131 ile birle\u015ftirmemiz gerekir.<\/p>\n<p>\u00d6ncelikle, olaylar\u0131 tan\u0131mlayan <code>sealed class<\/code>'\u0131m\u0131z\u0131 olu\u015ftural\u0131m:<\/p>\n<pre><code>\n\/\/ Olaylar\u0131 temsil eden Sealed Class\nsealed class UserRegistrationEvent {\n    data class ShowSnackbar(val message: String) : UserRegistrationEvent()\n    data class NavigateToHome(val userId: String) : UserRegistrationEvent()\n    object ShowLoadingDialog : UserRegistrationEvent()\n    object HideLoadingDialog : UserRegistrationEvent()\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>\u015eimdi, bu olaylar\u0131 <code>ViewModel<\/code>'dan UI'a g\u00fcvenli bir \u015fekilde aktaracak bir mekanizmaya ihtiyac\u0131m\u0131z var. Genellikle Kotlin Coroutines <code>Channel<\/code> veya tek seferlik olaylar\u0131 sarmalayan bir generic <code>Event<\/code> s\u0131n\u0131f\u0131 tercih edilir. Burada <code>Channel<\/code> kullan\u0131m\u0131na odaklanal\u0131m, \u00e7\u00fcnk\u00fc daha modern ve reaktif bir yakla\u015f\u0131m sunar:<\/p>\n<pre><code>\n\/\/ ViewModel Katman\u0131\nimport androidx.lifecycle.ViewModel\nimport androidx.lifecycle.viewModelScope\nimport kotlinx.coroutines.channels.Channel\nimport kotlinx.coroutines.flow.receiveAsFlow\nimport kotlinx.coroutines.launch\n\nclass UserRegistrationViewModel(private val authRepository: AuthRepository) : ViewModel() {\n\n    \/\/ Olaylar\u0131 UI'a tek seferlik g\u00f6ndermek i\u00e7in Channel\n    private val _events = Channel<UserRegistrationEvent>()\n    val events = _events.receiveAsFlow() \/\/ UI, bu Flow'u dinleyecek\n\n    fun registerUser(username: String, email: String, password: String) {\n        viewModelScope.launch {\n            _events.send(UserRegistrationEvent.ShowLoadingDialog) \/\/ Y\u00fckleme diyalo\u011funu g\u00f6ster\n            try {\n                val userId = authRepository.register(username, email, password)\n                _events.send(UserRegistrationEvent.ShowSnackbar(\"Kay\u0131t ba\u015far\u0131yla tamamland\u0131!\"))\n                _events.send(UserRegistrationEvent.NavigateToHome(userId))\n            } catch (e: Exception) {\n                _events.send(UserRegistrationEvent.ShowSnackbar(\"Kay\u0131t hatas\u0131: ${e.localizedMessage}\"))\n            } finally {\n                _events.send(UserRegistrationEvent.HideLoadingDialog) \/\/ Y\u00fckleme diyalo\u011funu gizle\n            }\n        }\n    }\n}\n\n\/\/ Varsay\u0131msal Authentication Repository\nclass AuthRepository {\n    suspend fun register(username: String, email: String, password: String): String {\n        kotlinx.coroutines.delay(1500) \/\/ A\u011f gecikmesi sim\u00fclasyonu\n        if (username == \"test\" && password == \"123\") {\n            throw IllegalArgumentException(\"Bu kullan\u0131c\u0131 ad\u0131 zaten mevcut!\")\n        }\n        return \"user_${System.currentTimeMillis()}\" \/\/ Ba\u015far\u0131l\u0131 kay\u0131t, userId d\u00f6nd\u00fcr\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>\u015eimdi bu olaylar\u0131 UI katman\u0131nda nas\u0131l t\u00fcketece\u011fimizi g\u00f6relim. <code>Channel<\/code>'dan gelen olaylar\u0131 bir <code>LaunchedEffect<\/code> i\u00e7inde dinlemek, Compose'da tek seferlik olaylar\u0131 i\u015flemenin g\u00fcvenli bir yoludur. Android View sisteminde ise <code>Lifecycle.RepeatOnLifecycle<\/code> blo\u011fu i\u00e7inde dinlemek tercih edilir:<\/p>\n<pre><code>\n\/\/ UI Katman\u0131 (Jetpack Compose \u00f6rne\u011fi)\nimport androidx.compose.material.Scaffold\nimport androidx.compose.material.rememberScaffoldState\nimport androidx.compose.runtime.LaunchedEffect\nimport androidx.compose.runtime.collectAsState\nimport androidx.compose.runtime.getValue\nimport androidx.compose.ui.platform.LocalContext\nimport androidx.lifecycle.viewmodel.compose.viewModel\nimport androidx.navigation.NavController\nimport androidx.compose.material.SnackbarDuration\n\n@Composable\nfun UserRegistrationScreen(\n    viewModel: UserRegistrationViewModel = viewModel(),\n    navController: NavController\n) {\n    val scaffoldState = rememberScaffoldState()\n    val context = LocalContext.current\n\n    \/\/ ViewModel'dan gelen olaylar\u0131 dinle\n    LaunchedEffect(Unit) {\n        viewModel.events.collect { event ->\n            when (event) {\n                is UserRegistrationEvent.ShowSnackbar -> {\n                    scaffoldState.snackbarHostState.showSnackbar(event.message, duration = SnackbarDuration.Short)\n                }\n                is UserRegistrationEvent.NavigateToHome -> {\n                    navController.navigate(\"home\/${event.userId}\") {\n                        popUpTo(\"registration\") { inclusive = true } \/\/ Kay\u0131t ekran\u0131n\u0131 back stack'ten temizle\n                    }\n                }\n                is UserRegistrationEvent.ShowLoadingDialog -> {\n                    \/\/ Y\u00fckleme diyalo\u011funu g\u00f6ster (\u00f6rne\u011fin, bir Dialog Composable)\n                    \/\/ Ger\u00e7ek uygulamada, bu bir StateFlow ile daha iyi y\u00f6netilebilir.\n                    \/\/ Bu \u00f6rnekte basitle\u015ftirildi.\n                }\n                is UserRegistrationEvent.HideLoadingDialog -> {\n                    \/\/ Y\u00fckleme diyalo\u011funu gizle\n                }\n            }\n        }\n    }\n\n    Scaffold(scaffoldState = scaffoldState) { paddingValues ->\n        \/\/ Kay\u0131t formu UI'\u0131 buraya gelecek\n        \/\/ \u00d6rnek olarak basit bir buton ekleyelim\n        androidx.compose.material.Button(\n            onClick = { viewModel.registerUser(\"ali\", \"ali@example.com\", \"password123\") },\n            modifier = androidx.compose.ui.Modifier.padding(paddingValues).fillMaxWidth().wrapContentHeight()\n        ) {\n            Text(\"Kay\u0131t Ol\")\n        }\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Bu yakla\u015f\u0131mla, tek seferlik olaylar\u0131n\u0131z\u0131 g\u00fcvenli, okunabilir ve tekrar oynatma riski olmadan y\u00f6netebilirsiniz. <code>sealed class<\/code>, olaylar\u0131n t\u00fcrlerini a\u00e7\u0131k\u00e7a tan\u0131mlaman\u0131za olanak tan\u0131rken, <code>Channel<\/code> ise bu olaylar\u0131n sadece bir kez t\u00fcketilmesini garanti eder. Bu \"tarif\", uygulaman\u0131z\u0131n etkile\u015fimli \u00f6\u011felerini ve geri bildirim mekanizmalar\u0131n\u0131 \u00e7ok daha sa\u011flam hale getirecektir. Ayr\u0131ca, yeni bir olay t\u00fcr\u00fc ekledi\u011finizde, <code>when<\/code> ifadesi sizi otomatik olarak bu yeni durumu ele almaya zorlayarak hata yapma olas\u0131l\u0131\u011f\u0131n\u0131z\u0131 minimuma indirir.<\/p>\n<div class=\"info-box\">\n  Uzman \u0130pucu: Tek seferlik olaylar i\u00e7in <code>Channel<\/code> kullan\u0131rken, <code>Channel<\/code>'\u0131n \u00f6mr\u00fcn\u00fc UI'\u0131n \u00f6mr\u00fcne ba\u011flamak i\u00e7in <code>LaunchedEffect(Unit)<\/code> veya <code>Lifecycle.RepeatOnLifecycle<\/code> kullanmak \u00f6nemlidir. Aksi takdirde, g\u00f6zlemleme i\u015flemi UI'dan daha uzun s\u00fcrebilir veya istenmeyen \u015fekilde sonlanabilir.\n<\/div>\n<h2>A\u011f \u0130steklerinden Gelen Cevaplar\u0131 Daha Robust Bir \u015eekilde Nas\u0131l \u0130\u015fleriz?<\/h2>\n<p>Modern Android uygulamalar\u0131, verileri genellikle a\u011f \u00fczerinden bir sunucudan \u00e7eker. Bu a\u011f istekleri, bir\u00e7ok farkl\u0131 sonuca yol a\u00e7abilir: ba\u015far\u0131l\u0131 bir yan\u0131t (veri ile veya verisiz), \u00e7e\u015fitli hata t\u00fcrleri (a\u011f hatas\u0131, sunucu hatas\u0131, yetkilendirme hatas\u0131, veri d\u00f6n\u00fc\u015f\u00fcm hatas\u0131 vb.). Bu farkl\u0131 senaryolar\u0131 tutarl\u0131, g\u00fcvenli ve kolayca y\u00f6netilebilir bir \u015fekilde ele almak, uygulaman\u0131n sa\u011flaml\u0131\u011f\u0131 ve kullan\u0131c\u0131 deneyimi i\u00e7in hayati \u00f6neme sahiptir. Geleneksel olarak, bu durumlar genellikle <code>try-catch<\/code> bloklar\u0131, HTTP durum kodlar\u0131n\u0131n manuel kontrol\u00fc veya callback aray\u00fczleri ile y\u00f6netilir, ancak bu yakla\u015f\u0131mlar genellikle kod tekrar\u0131na ve kar\u0131\u015f\u0131kl\u0131\u011fa neden olabilir. \u0130\u015fte <code>sealed class<\/code>'lar, API yan\u0131tlar\u0131n\u0131 modellemek ve i\u015flemek i\u00e7in g\u00fc\u00e7l\u00fc bir soyutlama katman\u0131 sa\u011flar.<\/p>\n<h3>Vaka Analizi: Bir E-ticaret Uygulamas\u0131nda \u00dcr\u00fcn Listesi \u00c7ekme<\/h3>\n<p>Bir e-ticaret uygulamas\u0131nda, kullan\u0131c\u0131 bir kategori se\u00e7ti\u011finde ilgili \u00fcr\u00fcn listesini bir API'den \u00e7ekmemiz gerekiyor. Bu i\u015flem s\u0131ras\u0131nda a\u015fa\u011f\u0131daki durumlarla kar\u015f\u0131la\u015fabiliriz:<\/p>\n<ol>\n<li><strong>Loading (Y\u00fckleniyor):<\/strong> \u00dcr\u00fcn verileri hen\u00fcz API'den gelmedi.<\/li>\n<li><strong>Success (Ba\u015far\u0131l\u0131):<\/strong> \u00dcr\u00fcnler ba\u015far\u0131yla \u00e7ekildi. Liste bo\u015f da olabilir.<\/li>\n<li><strong>Error (Hata):<\/strong> Farkl\u0131 t\u00fcrde hatalar olu\u015fabilir:\n<ul>\n<li><strong>Network Error (A\u011f Hatas\u0131):<\/strong> \u0130nternet ba\u011flant\u0131s\u0131 yok veya sunucuya eri\u015filemiyor.<\/li>\n<li><strong>Server Error (Sunucu Hatas\u0131):<\/strong> Sunucu taraf\u0131nda bir sorun (HTTP 5xx).<\/li>\n<li><strong>Client Error (\u0130stemci Hatas\u0131):<\/strong> Ge\u00e7ersiz istek (HTTP 4xx, \u00f6rne\u011fin yetkilendirme hatas\u0131 401).<\/li>\n<li><strong>Unknown Error (Bilinmeyen Hata):<\/strong> Beklenmedik bir durum olu\u015ftu.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p>Bu zengin hata senaryolar\u0131n\u0131 tek bir <code>sealed class<\/code> alt\u0131nda toplamak, kodumuzu hem daha okunakl\u0131 hem de daha g\u00fcvenli hale getirir.<\/p>\n<h3>Tarif 3: Geli\u015fmi\u015f API Yan\u0131t\u0131 \u0130\u015fleme i\u00e7in Sealed Class<\/h3>\n<p>Bu tarif i\u00e7in, API yan\u0131tlar\u0131m\u0131z\u0131 temsil edecek genel bir <code>sealed class Result<T><\/code> tan\u0131mlayaca\u011f\u0131z. Bu, herhangi bir t\u00fcrdeki (<code>T<\/code>) veriyi ta\u015f\u0131yabilir ve farkl\u0131 hata t\u00fcrlerini i\u00e7erebilir.<\/p>\n<pre><code>\n\/\/ API yan\u0131tlar\u0131n\u0131 temsil eden Sealed Class\nsealed class Result<out T> { \/\/ 'out' anahtar kelimesi kovaryans i\u00e7in kullan\u0131l\u0131r\n    object Loading : Result<Nothing>()\n    data class Success<out T>(val data: T) : Result<T>()\n    data class Error(val exception: Throwable) : Result<Nothing>()\n}\n\n\/\/ Hata tiplerini daha detayland\u0131rmak i\u00e7in ba\u015fka bir sealed class kullanabiliriz\nsealed class CustomError : Throwable() {\n    data class NetworkError(override val message: String = \"A\u011f ba\u011flant\u0131s\u0131 hatas\u0131!\") : CustomError()\n    data class ServerError(val code: Int, override val message: String) : CustomError()\n    data class ClientError(val code: Int, override val message: String) : CustomError()\n    data class UnknownError(override val message: String = \"Bilinmeyen bir hata olu\u015ftu.\") : CustomError()\n}\n\ndata class Product(val id: String, val name: String, val price: Double, val imageUrl: String) \/\/ Varsay\u0131msal Product s\u0131n\u0131f\u0131\n\n<\/pre>\n<p><\/code><\/p>\n<p>\u015eimdi, bu <code>Result<\/code> s\u0131n\u0131f\u0131n\u0131 bir Repository katman\u0131nda nas\u0131l kullanaca\u011f\u0131m\u0131za bakal\u0131m. Repository, API \u00e7a\u011fr\u0131lar\u0131n\u0131 yapar ve sonucu bir <code>Result<\/code> nesnesi olarak d\u00f6nd\u00fcr\u00fcr. Bu sayede, a\u011f i\u015fleminin t\u00fcm olas\u0131 \u00e7\u0131kt\u0131lar\u0131 tek bir t\u00fcrde paketlenmi\u015f olur.<\/p>\n<pre><code>\n\/\/ Repository Katman\u0131\nimport java.io.IOException\nimport retrofit2.HttpException\n\nclass ProductRepository(private val apiService: ProductApiService) {\n\n    suspend fun getProducts(categoryId: String): Result<List<Product>> {\n        return try {\n            val response = apiService.getProductsByCategory(categoryId)\n            if (response.isSuccessful && response.body() != null) {\n                Result.Success(response.body()!!)\n            } else {\n                val errorBody = response.errorBody()?.string()\n                val errorMessage = errorBody ?: \"Sunucu hatas\u0131: ${response.code()}\"\n                Result.Error(CustomError.ServerError(response.code(), errorMessage))\n            }\n        } catch (e: IOException) {\n            Result.Error(CustomError.NetworkError())\n        } catch (e: HttpException) {\n            when (e.code()) {\n                in 400..499 -> Result.Error(CustomError.ClientError(e.code(), e.message()))\n                in 500..599 -> Result.Error(CustomError.ServerError(e.code(), e.message()))\n                else -> Result.Error(CustomError.UnknownError(e.message()))\n            }\n        } catch (e: Exception) {\n            Result.Error(CustomError.UnknownError(e.localizedMessage ?: \"Bilinmeyen hata\"))\n        }\n    }\n}\n\n\/\/ Varsay\u0131msal Retrofit API Servisi\ninterface ProductApiService {\n    @GET(\"products\/{categoryId}\")\n    suspend fun getProductsByCategory(@Path(\"categoryId\") categoryId: String): Response<List<Product>>\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Son olarak, <code>ViewModel<\/code> bu <code>Result<\/code>'\u0131 t\u00fcketir ve bunu UI katman\u0131n\u0131n anlayaca\u011f\u0131 bir <code>UiState<\/code>'e d\u00f6n\u00fc\u015ft\u00fcr\u00fcr. Bu, sorumluluk ayr\u0131m\u0131n\u0131 koruman\u0131n ve UI katman\u0131n\u0131 API'nin detaylar\u0131ndan izole etmenin iyi bir yoludur:<\/p>\n<pre><code>\n\/\/ ViewModel Katman\u0131\nimport androidx.lifecycle.ViewModel\nimport androidx.lifecycle.viewModelScope\nimport kotlinx.coroutines.flow.MutableStateFlow\nimport kotlinx.coroutines.flow.StateFlow\nimport kotlinx.coroutines.launch\n\nclass ProductListViewModel(private val productRepository: ProductRepository) : ViewModel() {\n\n    private val _uiState = MutableStateFlow<ProductListUiState>(ProductListUiState.Loading)\n    val uiState: StateFlow<ProductListUiState> = _uiState\n\n    init {\n        fetchProducts(\"electronics\") \/\/ Ba\u015flang\u0131\u00e7ta bir kategori i\u00e7in \u00fcr\u00fcnleri \u00e7ek\n    }\n\n    fun fetchProducts(categoryId: String) {\n        viewModelScope.launch {\n            _uiState.value = ProductListUiState.Loading\n            when (val result = productRepository.getProducts(categoryId)) {\n                is Result.Loading -> _uiState.value = ProductListUiState.Loading \/\/ Normalde repository'den gelmez, UI i\u00e7in tutulur\n                is Result.Success -> {\n                    if (result.data.isEmpty()) {\n                        _uiState.value = ProductListUiState.Empty\n                    } else {\n                        _uiState.value = ProductListUiState.Success(result.data)\n                    }\n                }\n                is Result.Error -> {\n                    val errorMessage = when (val error = result.exception) {\n                        is CustomError.NetworkError -> \"\u0130nternet ba\u011flant\u0131n\u0131z\u0131 kontrol edin.\"\n                        is CustomError.ServerError -> \"Sunucu hatas\u0131: ${error.code} - ${error.message}\"\n                        is CustomError.ClientError -> \"\u0130stek hatas\u0131: ${error.code} - ${error.message}\"\n                        is CustomError.UnknownError -> \"Beklenmeyen bir hata olu\u015ftu: ${error.message}\"\n                        else -> \"Genel bir hata olu\u015ftu.\"\n                    }\n                    _uiState.value = ProductListUiState.Error(errorMessage)\n                }\n            }\n        }\n    }\n}\n\n\/\/ UI Katman\u0131 i\u00e7in \u00f6zel bir Sealed Class (yukar\u0131daki MovieListUiState'e benzer)\nsealed class ProductListUiState {\n    object Loading : ProductListUiState()\n    data class Success(val products: List<Product>) : ProductListUiState()\n    data class Error(val message: String) : ProductListUiState()\n    object Empty : ProductListUiState()\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Bu \"yemek tarifi\", API yan\u0131tlar\u0131n\u0131 i\u015flemek i\u00e7in g\u00fc\u00e7l\u00fc, tip g\u00fcvenli ve mod\u00fcler bir yakla\u015f\u0131m sunar. <code>Result<\/code> <code>sealed class<\/code>'\u0131 sayesinde, olas\u0131 t\u00fcm yan\u0131t durumlar\u0131n\u0131 (ba\u015far\u0131l\u0131 veri, farkl\u0131 hata t\u00fcrleri) tek bir soyutlama alt\u0131nda toplar\u0131z. Bu, hem Repository hem de ViewModel katmanlar\u0131nda kodun okunabilirli\u011fini art\u0131r\u0131r hem de her bir durumun \u00f6zel olarak ele al\u0131nmas\u0131n\u0131 sa\u011flar. Yeni bir hata t\u00fcr\u00fc veya yan\u0131t senaryosu ekledi\u011finizde, <code>when<\/code> ifadeleri sizi bu yeni durumu ele almaya zorlayarak uygulaman\u0131z\u0131n daha sa\u011flam ve hatas\u0131z olmas\u0131n\u0131 garantiler. B\u00f6ylece, uygulaman\u0131z\u0131n a\u011f i\u015flemlerini \u00e7ok daha g\u00fcvenilir ve y\u00f6netilebilir bir \u015fekilde tasarlayabilirsiniz.<\/p>\n<h2>Sealed Class'lar\u0131 Daha Verimli ve G\u00fcvenli Kullanmak \u0130\u00e7in P\u00fcf Noktalar\u0131 Nelerdir?<\/h2>\n<p><code>sealed class<\/code>'lar\u0131n g\u00fcc\u00fcn\u00fc ve esnekli\u011fini g\u00f6rd\u00fck. Ancak, bu harika arac\u0131 daha da verimli ve g\u00fcvenli kullanmak i\u00e7in dikkat etmemiz gereken baz\u0131 p\u00fcf noktalar\u0131 ve ileri d\u00fczey konular bulunmaktad\u0131r. Bu ipu\u00e7lar\u0131, \u00f6zellikle b\u00fcy\u00fck \u00f6l\u00e7ekli ve uzun \u00f6m\u00fcrl\u00fc projelerde kod kalitenizi art\u0131rman\u0131za yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h3>\u0130\u00e7i \u0130\u00e7e Sealed Class'lar (Nested Sealed Classes)<\/h3>\n<p>Bazen, bir <code>sealed class<\/code>'\u0131n alt s\u0131n\u0131flar\u0131 bile kendi i\u00e7inde daha fazla durumu veya varyant\u0131 i\u00e7erebilir. Bu t\u00fcr senaryolarda, i\u00e7i i\u00e7e <code>sealed class<\/code>'lar kullanmak hiyerar\u015fiyi daha okunabilir ve mod\u00fcler hale getirebilir. \u00d6rne\u011fin, bir \u00f6nceki \"API Yan\u0131t\u0131 \u0130\u015fleme\" tarifindeki <code>CustomError<\/code> s\u0131n\u0131f\u0131 asl\u0131nda bir <code>sealed class<\/code> olarak tan\u0131mlanm\u0131\u015ft\u0131r ve <code>Result.Error<\/code> s\u0131n\u0131f\u0131 i\u00e7indeki <code>exception<\/code> parametresini daha spesifik hale getirmemizi sa\u011flar. Bu, hata y\u00f6netiminde detay seviyesini art\u0131r\u0131r ve UI'da hata t\u00fcr\u00fcne g\u00f6re farkl\u0131 mesajlar veya eylemler g\u00f6stermemize olanak tan\u0131r.<\/p>\n<pre><code>\n\/\/ \u00d6rnek: Bir mesajla\u015fma uygulamas\u0131nda mesaj t\u00fcrleri\nsealed class Message {\n    data class TextMessage(val content: String, val timestamp: Long) : Message()\n    sealed class MediaMessage : Message() {\n        data class Image(val imageUrl: String, val caption: String?) : MediaMessage()\n        data class Video(val videoUrl: String, val duration: Long) : MediaMessage()\n    }\n    data class SystemMessage(val event: String) : Message()\n}\n\nfun displayMessage(message: Message) {\n    when (message) {\n        is Message.TextMessage -> println(\"Metin: ${message.content}\")\n        is Message.MediaMessage.Image -> println(\"Resim: ${message.imageUrl}\")\n        is Message.MediaMessage.Video -> println(\"Video: ${message.videoUrl}\")\n        is Message.SystemMessage -> println(\"Sistem: ${message.event}\")\n    }\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Bu yap\u0131, karma\u015f\u0131k veri modellerini temiz bir \u015fekilde d\u00fczenlemek i\u00e7in idealdir.<\/p>\n<h3>Sealed Interface mi, Sealed Class m\u0131? Ne Zaman Hangisini Tercih Etmeliyiz?<\/h3>\n<p>Kotlin 1.5 itibar\u0131yla <code>sealed interface<\/code>'ler de tan\u0131t\u0131ld\u0131. Temel fark \u015fudur:<\/p>\n<ul>\n<li><strong><code>sealed class<\/code>:<\/strong> Kal\u0131t\u0131m hiyerar\u015fisi olu\u015fturur. Alt s\u0131n\u0131flar hem <code>sealed class<\/code>'\u0131n kendisinden miras alabilir hem de kendi i\u00e7inde veri ta\u015f\u0131yabilir. Genellikle durumlar\u0131 veya olaylar\u0131 somut bir \u015fekilde temsil etmek i\u00e7in kullan\u0131l\u0131r.<\/li>\n<li><strong><code>sealed interface<\/code>:<\/strong> Yaln\u0131zca aray\u00fczlerin (interface) k\u0131s\u0131tl\u0131 bir hiyerar\u015fisini olu\u015fturur. Alt s\u0131n\u0131flar, hem <code>sealed interface<\/code>'i uygulayabilir hem de ba\u015fka s\u0131n\u0131flardan miras alabilirler (\u00e7oklu kal\u0131t\u0131m faydas\u0131). E\u011fer temel <code>sealed<\/code> yap\u0131s\u0131n\u0131n bir davran\u0131\u015f s\u00f6zle\u015fmesi (interface) olmas\u0131n\u0131 ve farkl\u0131 hiyerar\u015filerdeki s\u0131n\u0131flar\u0131n bu s\u00f6zle\u015fmeyi uygulamas\u0131n\u0131 istiyorsan\u0131z <code>sealed interface<\/code> tercih edin.<\/li>\n<\/ul>\n<p>\u00d6rnek olarak, e\u011fer bir <code>sealed class<\/code>'\u0131n t\u00fcm alt s\u0131n\u0131flar\u0131n\u0131n belirli bir metodu uygulamas\u0131 gerekiyorsa ve bu alt s\u0131n\u0131flar farkl\u0131 temel s\u0131n\u0131flardan t\u00fcreyebiliyorsa, <code>sealed interface<\/code> daha uygun olabilir. Ancak \u00e7o\u011fu durum y\u00f6netimi senaryosunda <code>sealed class<\/code> yeterli ve daha yayg\u0131n bir kullan\u0131md\u0131r.<\/p>\n<h3>Serialization ile Sealed Class Kullan\u0131m\u0131<\/h3>\n<p>Uygulaman\u0131z\u0131n durumunu kaydetmek (\u00f6rne\u011fin, bir <code>Bundle<\/code> i\u00e7ine veya <code>DataStore<\/code>'a) veya a\u011f \u00fczerinden g\u00f6ndermek istedi\u011finizde <code>sealed class<\/code>'lar\u0131 serialize etmeniz gerekebilir. Kotlin Serialization k\u00fct\u00fcphanesi (<code>kotlinx.serialization<\/code>) <code>sealed class<\/code>'lar i\u00e7in yerle\u015fik deste\u011fe sahiptir. Her bir alt s\u0131n\u0131f i\u00e7in bir <code>@Serializable<\/code> ve ana <code>sealed class<\/code> i\u00e7in <code>@Serializable<\/code> ve <code>@Subclass<\/code> anotasyonlar\u0131n\u0131 kullanman\u0131z yeterlidir. Parcelable ile kullan\u0131rken ise her alt s\u0131n\u0131f\u0131n ayr\u0131 ayr\u0131 <code>Parcelable<\/code> aray\u00fcz\u00fcn\u00fc uygulamas\u0131 gerekir.<\/p>\n<pre><code>\n\/\/ build.gradle.kts (module level)\n\/\/ plugins { id(\"org.jetbrains.kotlin.plugin.serialization\") version \"1.X.X\" }\n\/\/ dependencies { implementation(\"org.jetbrains.kotlinx:kotlinx-serialization-json:1.X.X\") }\n\nimport kotlinx.serialization.Serializable\nimport kotlinx.serialization.json.Json\n\n@Serializable\nsealed class DataEvent {\n    @Serializable\n    data class DataLoaded(val items: List<String>) : DataEvent()\n    @Serializable\n    object LoadingData : DataEvent()\n    @Serializable\n    data class ErrorLoading(val code: Int, val message: String) : DataEvent()\n}\n\nfun main() {\n    val event: DataEvent = DataEvent.DataLoaded(listOf(\"Item A\", \"Item B\"))\n    val jsonString = Json.encodeToString(DataEvent.serializer(), event)\n    println(jsonString) \/\/ {\"type\":\"DataLoaded\",\"items\":[\"Item A\",\"Item B\"]}\n\n    val decodedEvent = Json.decodeFromString(DataEvent.serializer(), jsonString)\n    println(decodedEvent) \/\/ DataLoaded(items=[Item A, Item B])\n}\n\n<\/pre>\n<p><\/code><\/p>\n<p>Bu, karma\u015f\u0131k durum objelerini kolayca kaydetmenize ve geri y\u00fcklemenize olanak tan\u0131r.<\/p>\n<h3>Testing Stratejileri<\/h3>\n<p><code>sealed class<\/code>'lar, test edilebilirli\u011fi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde art\u0131r\u0131r. Bir <code>ViewModel<\/code>'\u0131n veya i\u015f mant\u0131\u011f\u0131 s\u0131n\u0131f\u0131n\u0131n bir <code>sealed class<\/code> d\u00f6nd\u00fcrd\u00fc\u011f\u00fc durumlarda, her bir olas\u0131 durumu (<code>Loading<\/code>, <code>Success<\/code>, <code>Error<\/code>, vb.) ayr\u0131 ayr\u0131 test edebilirsiniz. <code>when<\/code> ifadesinin kapsaml\u0131 yap\u0131s\u0131 sayesinde, her durumun do\u011fru \u015fekilde ele al\u0131nd\u0131\u011f\u0131n\u0131 do\u011frulamak \u00e7ok daha kolayd\u0131r. Testlerinizde her alt s\u0131n\u0131f \u00f6rne\u011fini olu\u015fturup ilgili fonksiyona ge\u00e7irerek beklenen \u00e7\u0131kt\u0131y\u0131 kontrol edebilirsiniz.<\/p>\n<h3>Object Kullan\u0131m\u0131<\/h3>\n<p>E\u011fer bir <code>sealed class<\/code> alt s\u0131n\u0131f\u0131n\u0131n hi\u00e7bir durum verisi ta\u015f\u0131mayan tekil bir \u00f6rnek olmas\u0131 gerekiyorsa (\u00f6rne\u011fin, <code>Loading<\/code> veya <code>Empty<\/code> durumlar\u0131 gibi), <code>object<\/code> deklarasyonu kullan\u0131n. Bu, haf\u0131za optimizasyonu sa\u011flar ve gereksiz nesne olu\u015fturmaktan ka\u00e7\u0131n\u0131r. \u00d6rne\u011fin, <code>MovieListUiState.Loading<\/code> ve <code>MovieListUiState.Empty<\/code> durumlar\u0131 i\u00e7in <code>object<\/code> kullanm\u0131\u015ft\u0131k. Bu, okunabilirli\u011fi art\u0131r\u0131r ve kodun amac\u0131n\u0131 daha net bir \u015fekilde ifade eder.<\/p>\n<p>Bu ileri d\u00fczey ipu\u00e7lar\u0131 ve p\u00fcf noktalar\u0131, <code>sealed class<\/code>'lar\u0131n g\u00fcc\u00fcn\u00fc tam olarak kullanman\u0131za ve Android uygulamalar\u0131n\u0131z\u0131 daha sa\u011flam, bak\u0131m\u0131 kolay ve geli\u015ftirici dostu hale getirmenize yard\u0131mc\u0131 olacakt\u0131r. Unutmay\u0131n, do\u011fru arac\u0131 do\u011fru yerde kullanmak, kaliteli yaz\u0131l\u0131m geli\u015ftirmenin anahtar\u0131d\u0131r.<\/p>\n<h2>Sealed Class'lar\u0131n Android Geli\u015ftirmedeki G\u00fcc\u00fcn\u00fc Ke\u015ffettik<\/h2>\n<p>Bu makalede, Kotlin'in <code>sealed class<\/code> \u00f6zelli\u011finin Android uygulama geli\u015ftirmedeki paha bi\u00e7ilmez rol\u00fcn\u00fc derinlemesine inceledik. G\u00f6rd\u00fck ki, <code>sealed class<\/code>'lar, uygulaman\u0131z\u0131n farkl\u0131 durumlar\u0131n\u0131, tek seferlik olaylar\u0131n\u0131 ve API yan\u0131tlar\u0131n\u0131 y\u00f6netmek i\u00e7in son derece etkili, tip g\u00fcvenli ve okunabilir bir yol sunuyor. Geleneksel yakla\u015f\u0131mlar\u0131n getirdi\u011fi karma\u015f\u0131kl\u0131k, hata riski ve s\u00fcrd\u00fcr\u00fclebilirlik sorunlar\u0131na kar\u015f\u0131, <code>sealed class<\/code>'lar modern ve g\u00fc\u00e7l\u00fc bir alternatif olarak \u00f6ne \u00e7\u0131k\u0131yor.<\/p>\n<p>UI durum y\u00f6netimi tarifimizle, bir ekran\u0131n olas\u0131 t\u00fcm durumlar\u0131n\u0131 (y\u00fckleme, ba\u015far\u0131l\u0131, hata, bo\u015f) tek bir <code>sealed class<\/code> alt\u0131nda toplayarak, UI'\u0131n bu durumlar\u0131 tutarl\u0131 bir \u015fekilde g\u00f6stermesini sa\u011flad\u0131k. Tek seferlik olay y\u00f6netimi tarifimiz, <code>Snackbar<\/code> mesajlar\u0131 veya navigasyon gibi eylemlerin yaln\u0131zca bir kez tetiklenmesini garanti etmek i\u00e7in <code>sealed class<\/code>'lar\u0131 <code>Channel<\/code> ile birle\u015ftirmeyi \u00f6\u011fretti. Son olarak, geli\u015fmi\u015f API yan\u0131t\u0131 i\u015fleme tarifimiz, a\u011f isteklerinden gelen \u00e7e\u015fitli ba\u015far\u0131 ve hata senaryolar\u0131n\u0131 (a\u011f hatas\u0131, sunucu hatas\u0131, istemci hatas\u0131) <code>sealed class Result<T><\/code> ve i\u00e7i i\u00e7e <code>sealed class<\/code>'lar arac\u0131l\u0131\u011f\u0131yla nas\u0131l daha sa\u011flam bir \u015fekilde ele alaca\u011f\u0131m\u0131z\u0131 g\u00f6sterdi.<\/p>\n<p><code>sealed class<\/code>'lar\u0131n sundu\u011fu en b\u00fcy\u00fck avantajlardan biri, Kotlin derleyicisinin <code>when<\/code> ifadesiyle yapt\u0131\u011f\u0131 \"exhaustive check\" yetene\u011fidir. Bu sayede, yeni bir durum veya olay ekledi\u011finizde, ilgili <code>when<\/code> bloklar\u0131n\u0131 g\u00fcncellemedi\u011finiz takdirde derleme hatas\u0131 alarak potansiyel \u00e7al\u0131\u015fma zaman\u0131 hatalar\u0131n\u0131 daha kod yazma a\u015famas\u0131nda tespit edersiniz. Bu proaktif hata tespiti, uygulaman\u0131z\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 art\u0131r\u0131r ve geli\u015ftirme s\u00fcrecindeki \"debugging\" y\u00fck\u00fcn\u00fc azalt\u0131r.<\/p>\n<p>\u00d6zetle, <code>sealed class<\/code>'lar Android geli\u015ftiricileri i\u00e7in sadece bir dil \u00f6zelli\u011fi olmaktan \u00f6te, kod kalitesini, okunabilirli\u011fini ve s\u00fcrd\u00fcr\u00fclebilirli\u011fini art\u0131ran temel bir ara\u00e7 setidir. Bu \"yemek kitab\u0131\"ndaki tarifleri kendi projelerinizde uygulayarak, daha sa\u011flam, daha az hatal\u0131 ve geli\u015ftirilmesi daha keyifli uygulamalar olu\u015fturabilirsiniz. Kotlin'in bu g\u00fc\u00e7l\u00fc \u00f6zelli\u011fini kullanarak, karma\u015f\u0131k problemleri zarif \u00e7\u00f6z\u00fcmlerle a\u015fman\u0131n keyfini \u00e7\u0131kar\u0131n!<\/p>\n<h3>Sealed Class'lar ile \u0130lgili Merak Edilenler<\/h3>\n<p>\u0130\u015fte <code>sealed class<\/code>'lar hakk\u0131nda s\u0131k\u00e7a sorulan baz\u0131 sorular ve cevaplar\u0131:<\/p>\n<ul>\n<li>\n<h3>Q1: <code>enum<\/code> ile <code>sealed class<\/code> aras\u0131ndaki temel fark nedir?<\/h3>\n<p>A1: <code>enum class<\/code>'lar sabit ve \u00f6nceden tan\u0131mlanm\u0131\u015f de\u011ferler k\u00fcmesini temsil eder ve her bir enum sabiti tekil bir objedir. Kendi i\u00e7inde ek veri ta\u015f\u0131yamazlar. <code>sealed class<\/code>'lar ise k\u0131s\u0131tl\u0131 bir s\u0131n\u0131f hiyerar\u015fisi tan\u0131mlar ve her alt s\u0131n\u0131f kendi i\u00e7inde veri ta\u015f\u0131yabilir. Ayr\u0131ca, alt s\u0131n\u0131flar <code>data class<\/code>, <code>object<\/code> veya s\u0131radan <code>class<\/code> olabilir, bu da onlara daha fazla esneklik kazand\u0131r\u0131r. <code>sealed class<\/code>'lar durum ve olay y\u00f6netimi gibi daha karma\u015f\u0131k senaryolar i\u00e7in idealdir, <code>enum<\/code>'lar ise basit, sabit de\u011fer k\u00fcmeleri i\u00e7in.<\/p>\n<\/li>\n<li>\n<h3>Q2: <code>sealed interface<\/code> ne zaman <code>sealed class<\/code> yerine tercih edilmeli?<\/h3>\n<p>A2: <code>sealed interface<\/code>, alt s\u0131n\u0131flar\u0131n\u0131n birden fazla temel s\u0131n\u0131ftan miras alabilece\u011fi veya ba\u015fka aray\u00fczleri uygulayabilece\u011fi durumlarda tercih edilmelidir. <code>sealed class<\/code>'lar tek bir temel s\u0131n\u0131ftan miras alma k\u0131s\u0131tlamas\u0131na sahiptir. E\u011fer temel soyutlaman\u0131z bir davran\u0131\u015f s\u00f6zle\u015fmesi (interface) olacaksa ve bu davran\u0131\u015f\u0131 uygulayan farkl\u0131 t\u00fcrdeki s\u0131n\u0131flar\u0131 k\u0131s\u0131tl\u0131 bir hiyerar\u015fide toplamak istiyorsan\u0131z <code>sealed interface<\/code> kullan\u0131\u015fl\u0131d\u0131r. \u00c7o\u011fu durum veya olay y\u00f6netimi senaryosunda <code>sealed class<\/code> yeterli olacakt\u0131r.<\/p>\n<\/li>\n<li>\n<h3>Q3: <code>sealed class<\/code>'lar performans \u00fczerinde olumsuz bir etki yarat\u0131r m\u0131?<\/h3>\n<p>A3: Hay\u0131r, <code>sealed class<\/code>'lar\u0131n kendileri performans \u00fczerinde kayda de\u011fer bir olumsuz etki yaratmaz. Derleyici, <code>sealed class<\/code>'lar\u0131 ve <code>when<\/code> ifadelerini optimize eder. Asl\u0131nda, <code>sealed class<\/code>'lar sayesinde elde edilen tip g\u00fcvenli\u011fi ve derleme zaman\u0131 kontrolleri, \u00e7al\u0131\u015fma zaman\u0131 hatalar\u0131n\u0131 azaltarak ve daha temiz kod yaz\u0131m\u0131n\u0131 te\u015fvik ederek genel uygulama performans\u0131na ve kararl\u0131l\u0131\u011f\u0131na olumlu katk\u0131 sa\u011flayabilir.<\/p>\n<\/li>\n<li>\n<h3>Q4: <code>sealed class<\/code>'lar\u0131 serialization (\u00f6rne\u011fin Parcelable) ile nas\u0131l kullanabiliriz?<\/h3>\n<p>A4: <code>sealed class<\/code>'lar\u0131 serialization i\u00e7in kullanmak m\u00fcmk\u00fcnd\u00fcr. <code>kotlinx.serialization<\/code> k\u00fct\u00fcphanesi, <code>@Serializable<\/code> ve <code>@Subclass<\/code> anotasyonlar\u0131 ile <code>sealed class<\/code>'lar\u0131n serialization'\u0131n\u0131 do\u011fal olarak destekler. Parcelable ile kullan\u0131rken, her alt s\u0131n\u0131f\u0131n ayr\u0131 ayr\u0131 <code>Parcelable<\/code> aray\u00fcz\u00fcn\u00fc uygulamas\u0131 ve gerekli <code>CREATOR<\/code> objesini sa\u011flamas\u0131 gerekir. Bu, genellikle her alt s\u0131n\u0131f\u0131 ba\u011f\u0131ms\u0131z bir <code>Parcelable<\/code> olarak ele almay\u0131 gerektirir.<\/p>\n<\/li>\n<li>\n<h3>Q5: <code>sealed class<\/code>'lar yerine normal abstract class veya interface kullansak ne olur?<\/h3>\n<p>A5: Normal <code>abstract class<\/code> veya <code>interface<\/code> kullanmak, Kotlin derleyicisinin <code>when<\/code> ifadelerinde \"exhaustive check\" yapmas\u0131n\u0131 engeller. Yani, <code>abstract class<\/code>'\u0131 uygulayan veya <code>interface<\/code>'i implemente eden t\u00fcm alt s\u0131n\u0131flar\u0131 bir <code>when<\/code> ifadesinde ele alsan\u0131z bile, derleyici size bunu garanti etmez ve genellikle bir <code>else<\/code> dal\u0131 eklemenizi ister. Bu, yeni bir alt s\u0131n\u0131f ekledi\u011finizde mevcut <code>when<\/code> bloklar\u0131n\u0131 g\u00fcncellemedi\u011finiz takdirde \u00e7al\u0131\u015fma zaman\u0131 hatalar\u0131na yol a\u00e7abilecek potansiyel bir eksikli\u011fi maskeler. <code>sealed class<\/code>'lar bu riski ortadan kald\u0131rarak daha g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir kod yaz\u0131m\u0131n\u0131 te\u015fvik eder.<\/p>\n<\/li>\n<\/ul>\n<p><\/body><br \/>\n<\/html><\/p>\n","protected":false},"excerpt":{"rendered":"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar,&hellip;","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-30679","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife<\/title>\n<meta name=\"description\" content=\"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin&#039;in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife\" \/>\n<meta property=\"og:description\" content=\"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin&#039;in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-30T15:02:10+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"28 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife\",\"datePublished\":\"2025-09-30T15:02:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\"},\"wordCount\":3813,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\",\"name\":\"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-09-30T15:02:10+00:00\",\"description\":\"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin'in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife","description":"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin'in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/","og_locale":"tr_TR","og_type":"article","og_title":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife","og_description":"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin'in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!","og_url":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-09-30T15:02:10+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"28 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife","datePublished":"2025-09-30T15:02:10+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/"},"wordCount":3813,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/","url":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/","name":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-09-30T15:02:10+00:00","description":"Modern Android uygulamalar\u0131nda durum y\u00f6netimi, olay i\u015fleme ve API yan\u0131tlar\u0131n\u0131 ele almak karma\u015f\u0131k bir hal alabiliyor. Bu zorluklar, geli\u015ftirme s\u00fcrecini uzatabilir ve uygulaman\u0131n kararl\u0131l\u0131\u011f\u0131n\u0131 riske atabilir. Peki, bu kaosu ortadan kald\u0131racak, kodunuzu daha okunabilir, g\u00fcvenli ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir \u00e7\u00f6z\u00fcm olsa nas\u0131l olurdu? Cevap: Kotlin'in g\u00fc\u00e7l\u00fc sealed class \u00f6zelli\u011fi!","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/android-gelistiricileri-icin-sealed-class-yemek-kitabi-3-uretim-hazir-tarife\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Android Geli\u015ftiricileri \u0130\u00e7in Sealed Class Yemek Kitab\u0131: 3 \u00dcretim Haz\u0131r Tarife"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/30679","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=30679"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/30679\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=30679"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=30679"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=30679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}