Travis Griggs

09/02/2022, 4:45 PM
Colleague and I are playing with rewriting a screen of our app in Compose. For better or worse, we've been working our way "top down". As we convert more and more of the view to composables, the file starts to get pretty large. Is there a generally agreed strategy for how to organize lots of composables? One per file seems kind of redundant. But everything in one big file is also taxing my scrolling

Stylianos Gakis

09/02/2022, 5:11 PM
I usually keep them in the same file if they're really local and only to be used there. But if it starts getting big just move some more big and distinct composables to another file on the same package and slap the internal visibility modifier to it.

Colton Idle

09/04/2022, 11:35 PM
I have pretty much done the same. I dont use multiple modules in my apps often, but I have been doing more apps where we create a module for just composables.