Preferred file/package structure for Circuit

[clarksandholtz]

I have been playing around with Circuit in a fairly small app I have been working on and I've loved it. I've drawn from the sample apps quite a bit, but I noticed some of them have a large ~Circuit.kt file that contains screens, presenters, and UI composables.

In larger apps, how are people organizing things?

I've been starting to do something like this:

presentation/
├─ circuits/
│  ├─ feature/
│  │  ├─ FeaturePresenter.kt
│  │  ├─ FeatureScreen.kt
│  │  ├─ FeatureUi.kt

Would love to know if people have found other patterns they like!

[ZacSweers]

Yeah I think you can spread it around as much as makes sense! I've also seen a good pattern where Screen classes are defined in separate projects for navigation reasons, so they don't also bring along dependencies on the actual implementation.