100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

Kotlin Flow Cheat Sheet

Kotlin Flow Cheat Sheet

Building, transforming, and collecting cold asynchronous streams with Kotlin Flow, plus StateFlow/SharedFlow for hot state.

2 PagesIntermediateMar 4, 2026

Building & Collecting a Flow

Flow is cold: the block only runs when collected, and runs fresh per collector.

kotlin
import kotlinx.coroutines.flow.*import kotlinx.coroutines.*fun numbers(): Flow<Int> = flow {    for (i in 1..5) {        delay(100)          // suspend inside the builder is fine        emit(i)               // push a value downstream    }}suspend fun main() {    numbers().collect { value ->        println(value)          // 1, 2, 3, 4, 5 -- printed as they're emitted    }}// flowOf and asFlow for simple sourcesflowOf(1, 2, 3)listOf(1, 2, 3).asFlow()

Transforming Operators

Flow supports familiar sequence-like operators, all suspend-aware.

kotlin
numbers()    .map { it * it }    .filter { it % 2 == 0 }    .take(3)    .onEach { println("saw $it") }    .catch { e -> println("caught: $e") }     // catches upstream exceptions    .collect { println("result: $it") }// flatMapConcat / flatMapMerge / flatMapLatest for flows-of-flowssearchQuery    .debounce(300)    .flatMapLatest { query -> searchApi(query) }   // cancels previous search on new input    .collect { results -> render(results) }

Context Preservation & flowOn

Flow preserves the collector's context; flowOn changes upstream dispatch.

kotlin
fun heavyWork(): Flow<Int> = flow {    for (i in 1..5) {        Thread.sleep(50)      // pretend CPU-bound work        emit(i)    }}.flowOn(Dispatchers.Default)   // upstream (the flow{} builder) runs on Defaultsuspend fun run() {    withContext(Dispatchers.Main) {        heavyWork().collect { value ->            updateUI(value)      // collect lambda runs on Main, as expected        }    }}

StateFlow & SharedFlow

Hot flows for UI state (StateFlow) and event broadcasting (SharedFlow).

kotlin
class CounterViewModel : ViewModel() {    private val _count = MutableStateFlow(0)      // requires an initial value    val count: StateFlow<Int> = _count.asStateFlow()    fun increment() {        _count.update { it + 1 }        // atomic update    }}class EventBus {    private val _events = MutableSharedFlow<String>(replay = 0, extraBufferCapacity = 1)    val events: SharedFlow<String> = _events.asSharedFlow()    suspend fun publish(event: String) = _events.emit(event)}// Collecting StateFlow in Composeval count by viewModel.count.collectAsStateWithLifecycle()

StateFlow vs SharedFlow vs Flow

Choosing the right stream type.

  • Flow- cold, no state, runs fresh per collector, for one-shot async sequences
  • StateFlow- hot, always has a current value, conflates rapid updates, ideal for UI state
  • SharedFlow- hot, configurable replay/buffer, ideal for one-off events (snackbars, navigation)
  • channelFlow- builder for flows that need concurrent emit() from multiple coroutines
  • stateIn / shareIn- convert a cold Flow into a hot StateFlow/SharedFlow scoped to a CoroutineScope

Combining Multiple Flows

combine emits whenever any source updates (using each flow's latest value); zip pairs elements positionally; merge interleaves emissions as they arrive.

kotlin
val name: Flow<String> = flowOf("Ada", "Grace")val age: Flow<Int> = flowOf(30, 40)// combine: recomputes with the LATEST value from each flow on every emissionname.combine(age) { n, a -> "$n is $a" }    .collect { println(it) }// zip: pairs by index, completes when the shorter flow completesname.zip(age) { n, a -> "$n/$a" }    .collect { println(it) }// merge: interleaves emissions from multiple flows of the same typeval fast = flow { emit(1); delay(10); emit(2) }val slow = flow { delay(5); emit(100) }merge(fast, slow).collect { println(it) } // order depends on timing

Backpressure: buffer, conflate, collectLatest

Control how a slow collector handles a fast emitter without blocking the upstream producer.

kotlin
flow {    for (i in 1..100) {        delay(10)        emit(i)          // fast producer    }}.buffer(capacity = 50)                       // decouples producer/consumer with a channel.collect { slowConsume(it) }                   // producer no longer waits on consumer// conflate: drops intermediate values, keeps only the latest when consumer is behindsensorReadings.conflate().collect { render(it) }// collectLatest: cancels the in-progress collector block when a new value arrivessearchQuery.collectLatest { query ->    val results = searchApi(query) // canceled mid-flight if `query` changes again    render(results)}

callbackFlow for Callback-Based APIs

Wraps listener/callback APIs (SDKs, Firebase, sensors) into a cold Flow, with awaitClose for cleanup.

kotlin
fun locationUpdates(client: LocationClient): Flow<Location> = callbackFlow {    val callback = object : LocationCallback() {        override fun onLocationChanged(loc: Location) {            trySend(loc)                 // non-suspending, safe from any thread                .onFailure { /* channel closed/full */ }        }    }    client.requestUpdates(callback)    awaitClose {        client.removeUpdates(callback)  // guaranteed to run when the collector cancels    }}// Contrast with the simpler `flow { }` builder: callbackFlow backs onto a// Channel, so trySend() can be called from a non-suspending callback thread.

retryWhen & Exception Transparency

catch only intercepts upstream exceptions; retryWhen re-subscribes upstream based on a predicate, commonly with exponential backoff.

kotlin
fun fetchData(): Flow<Data> = flow {    emit(api.getData())     // throws on network failure}.retryWhen { cause, attempt ->    if (cause is IOException && attempt < 3) {        delay(1000L * (attempt + 1)) // simple linear backoff        true                            // true = retry, false = rethrow    } else {        false    }}.catch { e -> emit(Data.Empty) }   // final fallback after retries are exhausted// Exception transparency rule: never try/catch around emit() inside a flow{}// builder -- it breaks cancellation semantics. Let exceptions propagate and// handle them with .catch{} downstream instead.

Advanced Flow Operator Reference

Operators beyond the map/filter basics that show up in production Android/Kotlin code.

  • distinctUntilChanged()- suppresses consecutive duplicate emissions, common after combine() to avoid redundant UI updates
  • transform { }- general-purpose operator that can emit zero, one, or many values per upstream item (map/filter are built on it)
  • channelFlow- like callbackFlow but general-purpose, for concurrent emit() from multiple coroutines launched inside the builder
  • onCompletion { }- runs on normal completion, cancellation, or exception -- the Flow analogue of try/finally
  • first() / firstOrNull()- terminal operator that collects one value then cancels the upstream flow
  • flatMapConcat vs flatMapMerge- Concat preserves order and processes sequentially; Merge runs inner flows concurrently, interleaving output
  • SharingStarted.WhileSubscribed(5000)- keeps a shared/stateIn flow active for 5s after the last collector leaves, avoiding restart thrash on config changes
Pro Tip

Don't put one-off events (like 'show a toast') in a StateFlow — because it always replays its latest value to new collectors, a screen rotation or re-subscription will re-fire the last event; use SharedFlow with replay=0 for events, and reserve StateFlow strictly for durable state.

Was this cheat sheet helpful?

Explore Topics

#KotlinFlow#KotlinFlowCheatSheet#Programming#Intermediate#BuildingCollectingAFlow#TransformingOperators#ContextPreservationFlowOn#StateFlowSharedFlow#Concurrency#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse