can @Compose annotated functions return values in newer apis now?

I think it is possible since at least dev03. Because i used it since than. What do you want to do?

I wanted to know whether api has changed or not because during all talks they mentioned its by api design that they want to return unit.

Nah we unified effects and composable functions, you can return values. Generally you won't want a composable function to both emit UI and return a value though; generally if you feel a need to do that you want to use some sort of hoisted state object passed into a UI-emitting composable function instead of having it return something.

Is there any sample where a composable is returning a value. I’d love to see an example!

remember {}

,

state {}

,

.current

on ambients, a bunch of factory methods in the API that read ambients/internally

remember {}

implementation details, all of the `.observeAsState()`/`.subscribeAsState()`/`.collectAsState()` methods for LiveData/RxJava/Flow, respectively...

blows my mind that I didn’t notice that

remember

was returning a value 😮 Does compose assume that if it’s not returning a value then its meant to emit UI and if it returns a value then its not meant for UI ?

Not necessarily. Consider

onCommit { onDispose {} }

constructs which neither return a value nor emit UI

interesting! I’m guessing that the presence of a Layout/LayoutNode/etc type primitive inside a composable causes something to end up on the screen vs just help in the composition?

yes, emitting a node into the tree is an instruction to the composer and generally happens as part of the implementation details of calls to things like

Layout

thank you so much Adam for your consistently thoughtful responses! This really helps the early adopters in understanding the system better. Hopefully we can multiply this and share it with more folks who start learning compose!