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

Alexander Maryanovsky

03/03/2022, 2:17 PM
Is there a reason to expose properties in a viewmodel as
StateFlow
rather than just state values (e.g. by
by mutableStateOf
)?
f

Filip Wiesner

03/03/2022, 2:18 PM
a

Alexander Maryanovsky

03/03/2022, 2:22 PM
Ok, so I guess the answer is “not unless you have a specific reason”
f

Filip Wiesner

03/03/2022, 2:24 PM
The answer is
You should use the thing that most suits your project and codestyle
😄 Use whatever you feel like using. There is no "problem" with either approach
a

Alexander Maryanovsky

03/03/2022, 2:31 PM
Got it, thanks
I think for me state values win because I don’t have to have two flow fields for each property.
and no
_foo
ugliness
f

Filip Wiesner

03/03/2022, 2:38 PM
While I personally agree with your solution, you should bear in mind that the Android documentation suggests using one data holder for all your data so you shouldn't have multiple properties.
a

Alexander Maryanovsky

03/03/2022, 2:50 PM
Can you point me to that? Seems strange and would cause unnecessary recompositions.
m

Michael Paus

03/03/2022, 2:52 PM
One difference is that
StateFlow
is a pure Kotlin concept and does not depend on the compose framework but
mutableStateOf
is not. So if you want to keep your models pure it is better to follow the guidelines. In general it is not a good idea trying to be smarter than the inventors of a technology.
🇳🇴 1
f

Filip Wiesner

03/03/2022, 2:57 PM
Can you point me to that? Seems strange and would cause unnecessary recompositions.
https://developer.android.com/jetpack/guide/ui-layer#define-ui-state
a

Alexander Maryanovsky

03/03/2022, 3:00 PM
@Michael Paus I understand that, but it seems too puritanical for me. The models are View models, so I don’t think it’s such a big deal to have them depend on compose. Moreover, I was told the state/snapshot stuff in compose is completely separate from all the UI library.
:yes: 1
f

Filip Wiesner

03/03/2022, 3:01 PM
One difference is that
StateFlow
is a pure Kotlin concept and does not depend on the compose framework but
mutableStateOf
is not. So if you want to keep your models pure it is better to follow the guidelines.
It is suggested in Adroid guidelines that you can use Compose State when building your app with Compose UI:
In Jetpack Compose apps, you can use Compose's observable State APIs such as
mutableStateOf
or
snapshotFlow
for the exposure of UI state. Any type of observable data holder such as
StateFlow
or
LiveData
that you see in this guide can be easily consumed in Compose using the appropriate extensions.
m

Michael Paus

03/03/2022, 3:07 PM
For me this distinction is important because I can then drive a JavaFX GUI with the exact same view model that I use for the Compose GUI.
a

Alexander Maryanovsky

03/03/2022, 3:15 PM
If you have
StateFlow
in your viewmodel, you need to convert it to a compose state via
StateFlow.collectAsState
to be able to use in in compose UI. If you have compose state in your viewmodel, you need to convert it to a flow via
snapshotFlow
to be able to use it in JavaFX UI. Seems symmetrical. No?
1
@Filip Wiesner This is the relevant paragraph?
UI states: single stream or multiple streams? The key guiding principle for choosing between exposing UI state in a single stream or in multiple streams is the previous bullet point: the relationship between the items emitted. The biggest advantage to a single-stream exposure is convenience and data consistency: consumers of state always have the latest information available at any instant in time. However, there are instances where separate streams of state from the ViewModel might be appropriate:
Unrelated data types: Some states that are needed to render the UI might be completely independent from each other. In cases like these, the costs of bundling these disparate states together might outweigh the benefits, especially if one of these states is updated more frequently than the other.
UiState
diffing:
The more fields there are in a
UiState
object, the more likely it is that the stream will emit as a result of one of its fields being updated. Because views don’t have a diffing mechanism to understand whether consecutive emissions are different or the same, every emission causes an update to the view. This means that mitigation using the
Flow
APIs or methods like
distinctUntilChanged()
on the
LiveData
might be necessary.
Compose does have a diffing mechanism, though.
But I think it will still result in some unnecessary recompositions
m

Michael Paus

03/03/2022, 3:39 PM
@Alexander Maryanovsky In the second case my JavaFX application has an unwanted dependency on the Compose framework.
l

Landry Norris

03/03/2022, 6:38 PM
One use case for using Flows instead is KMM. I use ViewModels for both iOS and Android. iOS doesn’t support compose currently, so if my ViewModels use state, I can’t use them in iOS. I generally prefer to expose a flow that I can collectAsState, so it will work with both Compose, which supports state and SwiftUI, which does not.
1