A modern programming language that makes developers happier.

kotlinlang

Guys, great work on the progress. It's great to see that our feedback is actually being listened to. 

Quick question. 
Where is it better to write compose functions? In a class or a file?

It seems like file are the preferred route for things annotated with `Composable`. At least the components I’ve been looking at from Compose seem that way.

`Text`, `TextField`, `Flex`, etc all end up as top level functions at least.

Since state that needs to be rendered is passed down as input-parameters to these `@Compose` functions, making them static (top-level) seems like a good idea. No 'accidental' using state from the Activity or other such classes to render your 'Compose'd UI.

Composable functions on classes make sense when you're using the class as sort of a place for private hoisted state that the composable uses. We're still playing with some potential recommendations there