A modern programming language that makes developers happier.

kotlinlang

I'm a bit surprised that the AndroidStudio "New Project" prompt for Empty Activity doesn't include a Scaffold. Or that the only "composified" template is the Empty Activity one. Anyone add any insight into why that is?

Why would you expect a scaffold to be there?

I guess because when I go here: <https://developer.android.com/jetpack/compose/components>

the first component listed on the left is Scaffold. And the opening paragraph of that component is:

&gt; In Material Design, a scaffold is a fundamental structure that provides a standardized platform for complex user interfaces. It holds together different parts of the UI, such as app bars and floating action buttons, giving apps a coherent look and feel.
Doesn't seem like a "flutter only" thing when it's at the top of the material compose pages.

Maybe I've overestimated the priority of material in the Android ecosystem though? Maybe it's more "optional" than I realized?

What do you want a scaffold for is what I wonder?
Why not just start with a Scaffold and then go from there according to your app needs?

Great question. I don't know if I want one. I've been observing very much a "use the parts you understand/need" with my compose learning curve, instead of just "throw it all in mashup style and figure it out later". So I've gotten quite a bit of mileage out so far without a scaffold. But I was experimenting with Snackbars, and it seemed that they really wanted to live as part of a Scaffold. So I was considering using them to get the snackbars.

Sounds like a great thing to experiment with in your use case where you have snackbars. But sounds like a horrible default to put in *ALL* new compose projects just because one *may* want to use a snackbar at some point in the future.