So I know there was a session, I think that @Leland Richardson [G] did at DevSummit about how Compose actually implements its Builders, is there a document? also, lemme cast a vote for an example that shows a builder (domain-specific) that fronts compose…

a builder (domain-specific) that fronts compose

Not sure what you mean by this, can you elaborate?

So let’s say I was going to do something like a construction kit for making surveys, I want to make it a declarative DSL, that looks like Compose code, but is using my own functions for things like question types, etc.

to build a UI for surveys using Compose but using a survey-specific UI DSL, or to use Compose under the hood to build some other (non-UI) survey data structure that changes reactively over time?

well I am already doing the first part, I am just thinking that ultimately the declarative idiom for the actual surveys makes a lot of sense, e.g. for nesting

so you want to have Compose maintain a different data structure for you that is not UI?

no I think the data will use Compose, @model already let’s you have your own types right?

well, android views rather than html in that example 🙂

not sure what you mean by that, I am pretty sure declarative is a great match for surveys

ok, so it is producing a UI for the survey then?

yeah I will show you something in a few days, I am mostly thinking that some of the things that make surveys inscrutable might be solvable with a DSL, which got me all excited..

cool, I'd love to see it 🙂

even without access to

NumberPicker

and some of the other controls, Compose has been great for this so far!

if I'm understanding you right, yes, you should be good to go creating some sort of surveys "design library" similar to how the material design library builds on the other compose UI constructs

exactly!

oh, then in that case, yes of course, that sort of thing is the intended use case for compose in general :)

thanks for the efforts, yeah it is going in the right direction!