Ömer Okumuş @drmobiledev

Software Developer | Things about Mobile App Developing | Android, Kotlin, Jetpack Compose, iOS, Swift, SwiftUI | https://t.co/wYZMxKFQaT Istanbul Joined April 2025

Tweets

51
Followers

35
Following

50
Likes

55

Ömer Okumuş @drmobiledev

4 hours ago

Today I experienced that using combine with SharedFlows are quite dangerous. I am lucky that combined flow is not changing in the subsequent requests, thus, no emitting, so no unexpected navigations occur 😂😂

0 0 0 8 0

Ömer Okumuş @drmobiledev

13 hours ago

How to create a simple Observable using lambdas in Kotlin 👇🏼 #AndroidDev #KotlinDev

0 0 1 5 0

Download Image

Ömer Okumuş @drmobiledev

2 days ago

One of the common mistake is not being careful about SharedFlow collecting. SharedFlow does not hold the last value it emitted. Be sure you collect SharedFlow before it emits. Otherwise, you lose the event.

0 0 3 371 0

Ömer Okumuş @drmobiledev

2 days ago

You don’t need to write observables manually! Kotlin provides an elegant, built-in way to get automatic callbacks. No boilerplate, just pure reactive goodness. 👇🏼 #KotlinDev #AndroidDev

0 0 2 28 1

Download Image

Ömer Okumuş @drmobiledev

3 days ago

Many cross-platform developers complain about Android. I don't understand why. Both Android and iOS have pros and cons.

0 0 1 16 0

Ömer Okumuş @drmobiledev

3 days ago

Do you use where clause in Kotlin? Which situations does it fit well in your opinion?

0 0 3 594 1

Ömer Okumuş @drmobiledev

4 days ago

As your software grows larger, you'll hit the Dependency Coordination Problem. The solution lies in the article. Later, I'll examine the mobile application side here.

Omer Okumus @omerokumusx

5 days ago

As your software grows larger, you'll hit the Dependency Coordination Problem. The solution lies in the article. Later, I'll examine the mobile application side here.

0 1 5 453 3

0 0 1 26 0

Ömer Okumuş @drmobiledev

2 weeks ago

Kotlin - Data Structures IntRange does not create all elements eagerly. It works lazily under the hood, which brings huge memory optimization👇🏼 #KotlinDev #AndroidDev

0 0 3 42 2

Download Image

Ömer Okumuş @drmobiledev

3 weeks ago

I'll explore the #Android and #iOS aspects later. For now, read the article to understand the Single Responsibility Principle in #Software. Stay tuned for more.

Omer Okumus @omerokumusx

3 weeks ago

I'll explore the #Android and #iOS aspects later. For now, read the article to understand the Single Responsibility Principle in #Software. Stay tuned for more.

0 0 2 97 2

0 0 2 56 2

Ömer Okumuş @drmobiledev

4 weeks ago

Here, I will share detailed and important information about how the Observable design pattern plays an important role in mobile app development! #iOS #Android

Omer Okumus @omerokumusx

4 weeks ago

Here, I will share detailed and important information about how the Observable design pattern plays an important role in mobile app development! #iOS #Android

0 0 0 57 0

0 0 0 16 0

Ömer Okumuş @drmobiledev

2 months ago

In #Kotlin, ‘where’ clause is used in generic type constraints to specify additional rules that type parameters must satisfy. It allows you to apply multiple constraints to a single type parameter in a clean and readable way. Check below👇🏼#KotlinDev #AndroidDev

0 0 3 41 1

Download Image

Ömer Okumuş @drmobiledev

3 months ago

Do not forget that arrays in #Swift are structs, meaning they are value type. Hence, they are copied when assigned to a new variable. Check the code below 👇🏼 #iOS #iOSDev

0 0 0 39 0

Download Image

Ömer Okumuş @drmobiledev

3 months ago

Do not update a state inside another state update using StateFlows. Instead, update sequentially. Check the code below 👇🏽 #AndroidDev #Kotlin

0 0 3 17 3

Download Image

Ömer Okumuş @drmobiledev

3 months ago

In #Swift, function arguments are defined as ‘let’, meaning they are immutable. Hence, you can’t mutate them. So, how do you mutate it in a function? Here it is 👇🏼 #iOSDev

0 0 1 23 1

Download Image

Ömer Okumuş @drmobiledev

3 months ago

#iOS | UIKit optimizes or batches layout passes, and the view hierarchy might not be fully committed by the time you're doing something on the view hierarchy. That is why you use layoutIfNeeded right before doing something on the layout. #Swift