https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
a

Arpit Shukla

02/02/2022, 1:36 PM
Reading the guide to app architecture, I found this note:
In some apps, you might have seen ViewModel events being exposed to the UI using Kotlin Channels or other reactive streams. These solutions usually require workarounds such as event wrappers in order to guarantee that events are not lost and that they're consumed only once.
I too (sometimes) use a
Channel
to send events from ViewModel to UI as a
Flow
which I collect in
LaunchedEffect
but I never had to use any
workarounds such as event wrappers in order to guarantee that events are not lost and that they're consumed only once
It is automatically taken care of while using channels. What exactly did the author mean here?
a

Adam Powell

02/02/2022, 2:25 PM
It's referring to some patterns that were mostly only seen alongside LiveData, since LiveData is a state holder and not an event stream. It was sort of a workaround for some other design issues involved with multiple consumer handoff during android activity recreation. If you haven't seen this before, you're not missing out. 🙂
a

Arpit Shukla

02/02/2022, 2:38 PM
I remember the
LiveData<Event<T>>
pattern which was used as a workaround to guarantee that events are consumed only once. But that wasn't in anyway related to channels. The guide specifically refers to Kotlin Channels (and similar reactive streams). Is there any such thing with Channels that I need to watch out for?
h

Halil Ozercan

02/02/2022, 2:49 PM
First thing comes to mind is possibility of using something like
BroadcastChannel
(now deprecated?) which replays some items to new subscribers.
m

madisp

02/02/2022, 5:35 PM
some
Flow
configurations as well
if you've got a channel then I'm pretty sure it guarantees exactly-once delivery though? especially with rendezvous (e.g. no buffer)
a

Arpit Shukla

02/02/2022, 7:27 PM
@madisp Yeah, right. Never faced an issue with this approach.
a

Alex Vanyo

02/04/2022, 10:44 PM
https://github.com/Kotlin/kotlinx.coroutines/issues/2886 has some more information in this area. The edge case specifically with a
Channel
is that an element can be received from a
Channel
, but the receiver is cancelled before the element is processed, which results in behavior of “at-most-once delivery and handling” More general solutions that get closer to that “exactly-once delivery and handling” start getting extremely subtle, can depend on dispatcher behavior, and can break due to depending on a very precise dance of ordering (things like adding intermediate filtering or mapping can break assumptions). It’s possible you’ve avoided those edge cases so far if “at-most-once” is good enough for your use case or if your usage happens to avoid the issue. Just to re-iterate again, exposing state from a ViewModel (either
StateFlow
or Compose
State>
) is the simplest to reason about, test, and should be your go-to approach.
a

Arpit Shukla

02/05/2022, 2:56 PM
Does any of the official Compose samples handle the case of navigation as a result of a ViewModel event?
s

Stylianos Gakis

02/10/2022, 6:17 AM
It is actually a bit unfortunate that the discussion over at https://github.com/Kotlin/kotlinx.coroutines/issues/2886 didn’t seem to continue and instead the suggestion became to bake events inside the State itself, with the dance needed to: • Do whatever action on the ui, send that action to the VM • Depending on that action, update the state to contain a relevant event • Receive the new state, extract the event out of it, process it and then manually ask the VM to set the event as consumed • Have the VM reset the event, again changing the view state. It may be that I find it less than ideal because I am not used to it, but it certainly feels like quite a lot of ceremony over what a channel of events let us do.
a

Alex Vanyo

02/10/2022, 8:40 PM
bake events inside the State
Just to highlight an important mindset here which is fairly subtle: Try to go one step further than just putting the events into a part of the state and thinking about them as events the entire time. So instead of
List<Message>
“here are the list of show message events that haven’t been sent to the UI yet”, think “here are a list of messages pending display to the user”. The underlying data being stored will be very similar, which admittedly makes this a subtle distinction. When you take the mindset of “here are a list of messages pending display to the user,” there’s a bunch of natural follow-up questions that are important: • When is a message considered “displayed” to remove it from the list? • Should the list of messages have a max size if the list keeps growing? • Should the list of messages be stored (for example, to persist through process death)? An approach with a channel with events hide those questions. For example, what happens if you receive an event from a channel just before a configuration change happens? Or the user backgrounds the app 10 milliseconds after starting to show the message? Those questions would still be valid even with a different primitive than a
Channel
. The “dance,” as you put it, between the ViewModel and the UI is a bit longer, but it makes the answers to the above questions for your use case explicit and not depend on the exact internal workings of
Channel
or another primitive. It doesn’t hide the reality that an AAC ViewModel outlives the UI, and that guaranteeing a longer-lived producer telling a shorter-lived consumer to do something exactly once is very difficult.
s

Stylianos Gakis

02/10/2022, 9:50 PM
Very valid points raised. I guess I am mostly salty about the fact that there is no super easy solution to this, and I am definitely not used to handling events as you’re describing. I think that this may be one of those things that just need a bit of time to settle. Like how coroutines made no sense in the beginning. Or how declarative UI doesn’t make sense the first months. I think this scenario is one of those cases, and provided enough time to play around with it, seeing examples and the community discuss it, it will all make much more sense eventually.
a

Arpit Shukla

02/11/2022, 4:51 AM
@Alex Vanyo Btw what is your opinion on putting the
SnackbarHostState
in the ViewModel itself and calling
showSnackbar
right from the ViewModel?
a

Adam Powell

02/11/2022, 2:28 PM
Fwiw I have a few hobby apps that put a snackbar state object like that all the way into an app/singleton scope. The benefit of reducing to state in this way is that it doesn't matter how many things are observing the state at the same time, whether that's zero or many.