Template for flutter create cupertino

[xster]

A flutter create template that doesn't import material

[zoechi]

Related #15279, #14719, #13611

[matthew-carroll]

CC @willlarche

@devoncarew working on this ticket implies the possibility of having multiple project templates. Is this something that your team can help with? Or, is there any particular reason why multiple project templates would be an issue?

[willlarche]

I support multiple templates. But that should be spec'd out by needs and research. Has it? (I actually don't know.)

[matthew-carroll]

CC @InMatrix were any investigations ever done into multiple templates? If not, can we chat a little bit about it? There are likely benefits across multiple use-cases. I know I had brought this up at some point when were in 1842, but then it got away from me as I focused more on Android APIs instead of tooling...

[Hixie]

We need to be really really careful when designing extra templates. Our single existing template is a massive part of our first hour experience and anything that risks derailing new users from that experience is extremely dangerous in terms of our user adoption. Please make sure to loop me in on any design discussions and code reviews.

[devoncarew]

Mechanically, the IDEs need to be told about each additional template (we support app, package, and plugin) currently.

If the number grows too large, we'll have to change how we present them in the UI. One additional one won't cause issues. We'll just need to be aware, and perhaps do some version detection so we only offer it with versions of the framework that have those templates.

[matthew-carroll]

@Hixie - Will do.

@devoncarew what about a new screen in the flow after you select the app template? I guess technically this isn't so much about project structure as it is about initial Dart source code. Maybe we could make it accessible via a subtle button that wouldn't distract new users?

[devoncarew]

We do have a bit of logic there that's template dependent - we'd want to update that as well for new templates.

Here's the UI for IntelliJ project creation:

And for Android studio project creation:

Note that in Android Studio, there is (frequently) and follow-on wizard page which is customized for the project type. cc @stevemessick for fyi

[matthew-carroll]

Thanks @devoncarew. And as @Hixie said, we have to be very careful here not to distract from the first hour experience. So I'm wondering where we can take this from here?

Should we collect some data with @InMatrix and @jayoung-lee? Or should we propose a specific wizard UI that would allow for selecting other source code configs?

Since this conversation has happened multiple times over the last year, I think it would be good to get the ball moving in some direction. Thoughts?

[xster]

My original thought was just to add a flutter create --ios or flutter create -t app-ios or some such that doesn't impact the onboarding flow.

For IDEs, since it's not an additional dimension (i.e. plugin/packages are already android+iOS), it'd just be another entry in the project type. It can either be Application/Cupertino Application or Application - Material/Application - Cupertino or something like that.