I got no answers on the compose channel figured that maybe h kotlinlang #codingconventions

Channels

fluid-libraries

jhipster-kotlin

effectivekotlin

effective-kotlin

android-architecture

algolialibraries

stayhungrystayfoolish

pattern-matching

kotlin-data-storage

skia-wasm-interop-temp

squarelibraries

beepiz-libraries

cscenter-course-2016

kotlin-foundation

compose-android

lambdaworld_cadiz

kotlin-pakistan

java-to-kotlin-refactoring

event21-community-content

fb-internal-demo

kotlinprogrammers

kotlinx-datetime

framework-elide

github-workflows-kt

library-development

arrow-contributors

spring-security

pocketgitclient

domain-driven-design

swiss-user-group

refactoring-to-kotlin

ohio-kotlin-users

introduce-yourself

kotlin-by-example

kotlin-multiplatform-contest

graviton-browser

tricity-kotlin-user-group

kotlin-in-action

android-databinding

kotlintest-devs

compose-desktop

cincinnati-user-group

codemash-precompiler

kotlingforbeginners

prozis-android-backup

realworldkotlin

connect-audit-events

russian-kotlinasfirst

androidgithubprojects

intellij-tricks

machinelearningbawas

swagger-gradle-codegen

100daysofkotlin

competitive-programming

compose-ui-showcase

androidx-xprocessing

navigation-architecture-component

strife-discord-lib

embedded-kotlin

image-processing

myndocs-oauth2-server

leedskotlinusergroup

kotest-contributors

practical-functional-programming

kotlinultimatechallenge

kotlinforbeginners

competitivecoding

100daysofkotlin-2021

k2-early-adopters

refreshversions

language-evolution

jvm-ir-backend-feedback

python-contributors

codingconventions

sofl-user-group

getting-started

language-proposals

intellij-plugins

#codingconventions

Title

# codingconventions

m

Michal Klimczak

09/07/2023, 10:11 AM

I got no answers on the compose channel, figured that maybe here I will have more luck and it seems to fit the theme. https://kotlinlang.slack.com/archives/CJLTWPH7S/p1693389803639179

p

Pablichjenkov

09/07/2023, 7:20 PM

I prefer

, not quite exactly like the above code but some composable that remembers a State. The magic happens inside the State. I would place its own coroutine and expose StateSnapshots or StateFlows in case is needed to refresh the composable UI

But it is up to the requirements. If you don't need to keep track of the State or in other words having State history. Then 2 works, one single shot, that's it. Is just that most of the time I use 1 method