A modern programming language that makes developers happier.

kotlinlang

Hey,
so I have a few style questions for anyone who's been using decompose in somewhat larger projects.
How big do your components tend to be? Do you often find yourself decomposing larger components into smaller (I mean when it doesn't involve navigation. E.g. by using `childContext(..)`)?
Are you components generally always related to UI in some way, or do you also build components for pure logic/data handling?

In my medium-sized project (~150KLoC) there are some cases of decomposing the screen component into smaller ones. More like extracting some clearly independent piece of ui+logic into a component.

As for the pure logic components - I do have several stateful shared interactors in my app, but they are not Decompose components. Part of the reason is that they existed before I adopted Decompose, part is that I don't actually have a reason to make them Decompose components - they don't have a tricky lifecycle, and don't use other Decompose features.

The idea of logic components seems plausible, but I have yet to find a good use case for it.

Thanks for your input. I'm still a little in the experimental stage and another opinion or two is helpful :+1: