I just noticed that there are 8,135 followers of t...

# compose

[Travis Griggs]

I just noticed that there are 8,135 followers of this channel, 653 of compose-android. I know there's a post now and then again encouraging android specific questions to be in the compose-android channel. I find it harder to believe that only 8% of compose programmers (or time spent by all) are doing android specific stuff, while the remaining 92% is spent on compose things that could happen on any target.

[Casey Brooks]

For one: this is actually mostly true. Compose was written from the beginning for multiplatform, so most of the core functionality is actually not Android specific.

But a big contribution to these numbers is that this is the original Compose channel and only recently was #compose-android created, so it’s taking time to get folks moved over there. Plus, not everyone in this channel is even using Compose for Android, so there may be some folks here that won’t move over to that channel. Or there are probably a lot of people that are developing for Compose on Android, but don’t do enough stuff that’s really Android-specific to bother going over to that channel.

[Travis Griggs]

My confusion, not being a hard core platform follower, is that I often don't know if something is Android specific. I've been asking my IME questions over in Android, because I guess those would be Android specific? Now I'm starting to explore maps-compose... is that Android or general?

[Travis Griggs]

But my suspicion/worry, is that I'd actually get more feedback even on my IME questions here, rather than in Android specific.

[Travis Griggs]

Not trying to whine though. Sorry if it sounds like that. Sort of just a stoic/resigned observation

[Casey Brooks]

In general, you should expect that libraries for complex UI features, or libraries developed by Google (typically under the Jetpack banner), are going to be Android specific, and are best directed to #compose-android. This includes Maps, WebView, Navigation, things to do with Permissions or app lifecycles, the androidx.lifecycle.ViewModel class, etc.

Things that have to do with the core Compose Foundation, UI, or Material libraries are generally all Multiplatform-enabled, and can be asked here. This includes most of the gestures, animations, and other stuff like that. But there are some specific features of those libraries that are target-specific, like AlertDialog for example, and those specific APIs can be directed to the channel for the platform you’re trying to use them on.

[Marcin Wisniowski]

Well thanks for letting me know #compose-android exists in any case. One less to go.

[Travis Griggs]

Thanks. That helps to have a general guideline. I appreciate it.

I'm still left with a prisoners dillema of sorts. I know, sadly, that most people will be slow to adopt this bifurcation. So I'm likely to get better responses for some of these here, even if I am "up to date" and "on board" with the division. But I want to be a good citizen and Do The Right Thing(tm). But if a significant majority does not, then the networking effect encourages a lackadaisical compliance.

Of course, having asked now, I don't dare ask my maps question here. 🙂

[Travis Griggs]

It's unfortunate that the larger group wasn't left with the original charter, and a new group for "purely-compose" wasn't created for those that wanted to chat about compose without the baggage of those around

[Casey Brooks]

Yeah, I think originally some folks were wanting to rename this channel to #compose-android for the reason of maintaining members and search history, and creating a new #compose for common stuff. But I don’t think that’s going to happen.

To that end, I’d post your questions in the most appropriate channel first, and if you don’t get a response in a day or so, maybe then reach out in this channel. Cross-posting generally is not encouraged, and while I’m not a mod, given the start differences in membership I think it would be OK during this transition period. In this case, sharing the original post from #compose-android into this channel would be appreciated, to keep the actual conversation over there and encourage movement toward the platform-specific channels.

[Stylianos Gakis]

See the responses to this https://kotlinlang.slack.com/archives/C04TPPEQKEJ/p1678887235193679 it should provide some extra context on the decision

[Loney Chou]

We have #compose-X for individual platforms, true for #compose-android. This channel should be platform agnostic anyway, despite most are doing android. It all depends on what question one asks, general or platform specific.

[Loney Chou]

Given the momentum here, if we did the other way, that rename this channel for android specific and the new one for common practice, then those who don't do android would miss these useful resources here which can be shared across platforms, because people don't know they can be shared.

[rocketraman]

A mass invitation to #compose-android could be issued to everyone in #compose. That way people are quickly made aware of #compose-android and the relatively few people that are not interested in #compose-android can just leave the channel.

[rocketraman]

But there are probably too many people here for that to fly.

[Travis Griggs]

Obviously, mailing lists and slack channels have different dynamics, but it's notable (to me) that the Python mailing list runs as many as 200 posts per day, but people don't seem to need to bifurcate and organize things.