[@JacquesSmuts]

I've seen so many examples and guides explain that you should do the code at 02:00. Thank you for calling that out.

[@FilippoVigani]

Does the definition of the eventSink function inside the state cause composables that call it (such as the button) to recompose when the state changes?

[@andy_lamax]

Nice talk

[@tamim7460]

Compose iOS support should be there!!

[@Mrdresden]

How about you contribute it to the project then.

[@tamim7460]

@@Mrdresden I’m thinking about that actually

[@Pandanomic]

​@@tamim7460 Landed preliminary support on main :). When we were preparing the talk, compose for iOS was not yet in alpha (announced at the same conference)

[@tamim7460]

@@Pandanomic awesome, thanks for the info

[@elsenalmasli1499]

It is for great for MVP and Compose. But I have a bad news it is same thing MVVM
fun foo(vm){
collect state
}
fun foo(state){
state
} 😕

[@abdelrahmanesam3684]

why should I do that ? what is the benefit of that over MVVM/MVI ?

[@shahar19971]

Can i use circuit with Hilt?

[@Pandanomic]

We haven't tried it but nothing should prohibit it, once you get to compose then Circuit can run from there.

[@Pandanomic]

@@johnbuhanan5857 circuitinject, as its readme says, is intended for use with Anvil. You can build something else for use with hilt if you want though, my comment was more that there's nothing inherently stopping you

[@shahar19971]

​@@Pandanomic so generally speaking, if i open a new project (moving from an old monolith to new modularized project, circuit will happy with Dagger Anvil?

[@Pandanomic]

@@shahar19971 that's how we use it at slack and in the circuit star sample

[@johnbuhanan5857]

Circuit is the future...