I think it'd be pretty nice for new users or simpl...
# decompose
a
I think it'd be pretty nice for new users or simpler use cases, to provide a master/detail approach that is a bit more "batteries included". The current approach is nice because it's very flexible, but I think it's a bit much for a user who is probably new to compose, and decompose
a
The master/detail sample is there only for demonstration of dynamic single/multi-pane layouts. For simpler cases there is the todoapp. Does it make sense?
a
I was thinking a base component, part of the library, that automates a lot of what is going on
a
Do you have any specific ideas? I'm afraid such a component would become useless as soon as you want to customize it with your own requirements. For new users onboarding, there was an idea of code labs. But I find that's too much work for me, currently. I will think about it again.
a
ya understandable from the work load side of things, I have some ideas, I'll try to work something up, put it up for PR, see what you think
a
Maybe it's worth just throwing your ideas here, should be quicker to receive feedback
a
ya sounds good, i'll work up something more concrete
a
Or a code snippet. Thanks anyway! I'm aware that onboarding is not straightforward, especially if you are not familiar with Compose/KMP/componentisation etc
a
ya, i finially got over the hump and am enjoying decompose & KMP.
🎉 1
IDE is still not understanding KMP some times, but over all it's pretty good.
l
+1 I mainly maintained legacy code until a year or so ago. The whole idea of BLoC and declarative UI was really new to me, and it took a while to get used to it. The first project I used with decompose went through several basic rewrites in terms of how I used decompose.
a
Looks like the Getting Started section in the docs is missing a basic example. I will try adding one and see if this improves the onboarding.