:question: Hey Composers, I need your help. I’ll be moderating a panel at a conference this week abo...

# compose

[Zach Klippenstein (he/him) [MOD]]

❓ Hey Composers, I need your help. I’ll be moderating a panel at a conference this week about adopting Compose at scale. We’ve got some great panelists with interesting stories to share, but here’s where I need your help: What would you like to know?

If your company or team has started using Compose, what would you like to compare notes on?

If you haven’t yet, what would you like to hear from people who have?

Feel free to reply to this thread or DM me. The session will be recorded so you’ll be able to see the responses even if you’re not coming to droidcon SF.

[Arjan van Wieringen]

Is this Compose for Android or also Desktop? If Desktop I am interested in how they manage application state and view state for large apps. This differs heavily from phone/tablet UiS

[statmark56]

How they dealt with crashes from compose internal

[Stylianos Gakis]

I'd be curious to hear about how their experience has been onboarding everyone. Compose is very easy to get started, and is very powerful for folks who have used for a long time and have learned a bunch of those things you learn through experience, or from reading, hanging out in this or other forums etc.

On the other hand, for devs who've gone over the "this is pretty neat and easy" period, there's this period where you make a lot of mistakes.
A dev in that position would do things like, write poorly optimized compose code, forget how remember and all the recomposition related things work, key things wrong (or not at all), don't understand what recomposition scopes are, run side effects in composition, misunderstand state objects from normal objects and forget to use rememberUpdatedState when you need to, carry over bad habits from the xml days, and so on and so forth. This list can be quite extensive the more I think about it.

What do they do to bring everyone in a team up to speed, especially the ones not as motivated or excited to learn about all this by themselves.

Strong lint checks? (A lot of upfront work, maybe not worth it for a small team)
Try to be extra meticulous in Compose PR reviews? (Human factors, easy to miss stuff)
What else?

[Landry Norris]

I'd like to know more about what compose multiplatform will look like and to what degree Google will focus on Android vs common

[Zach Klippenstein (he/him) [MOD]]

Thanks for all the responses! Keep ‘em coming

[Sunil Kumar]

I'd like to know to what extent google will be supporting compose multiplatform, because they already have cross platform framework flutter already doing great. And if yes they will be supporting it, what will be the exact reason they will support it equally with flutter?

[Zach Klippenstein (he/him) [MOD]]

So nobody on this panel is at google. It will not be about development of compose itself, just adopting compose in larger codebases

[lesincs]

1.When introducing Compose to an existing codebase, it is inevitable that you will need to mix view-based components and Compose. Sometimes, you may encounter strange behaviors, such as infinite recompose when nesting Compose in a view-based MotionLayout or incorrect calculation of the height of a WebView when nesting it in a Compose BottomNavigationSheet. These are compatibility issues that may be impossible to fix. As a result, you may need to compromise by using full Compose or view instead of mixing them. This may hold people back from refactoring pages using Compose step by step. How do you perceive this?
2.Currently, there is no official recommended way to manage state in Compose, and all the Compose samples seem simple and have limited value as a reference. This has resulted in messy, error-prone, and inconsistent state management, with different understandings among developers. Is there any plan to address this?
3.The performance of Compose can differ between debug and release versions. For example, you may easily feel lag in a LazyColumn in the debug version, but in release, it’s all good. This makes it hard to decide whether you should do some performance optimization. How do we handle this situation?

[Chris Fillmore]

I’d be curious to hear from people who have built out design systems using Compose. Any challenges you have run into? What is your workflow like with designers? Are you using Relay or…?

Our web platform projects are doing this now (to be clear, in React, not compose). It’s a project that may come to our mobile clients someday, so I would definitely be interested in hearing if you’ve done this, particularly in any small shops (eg we have 3 mobile devs and 2 designers)

[estevanfick]

If they have a not UDF architecture (like MVP), how are they implementing Compose?

[Stylianos Gakis]

Was the recording for this published btw? Would be nice to be able to be able to hear this discussion

[Zach Klippenstein (he/him) [MOD]]

Yes! https://www.droidcon.com/2023/07/20/panel-discussion-adopting-jetpack-compose-scale/

[Zach Klippenstein (he/him) [MOD]]

And we’re doing a slightly longer version in New York next month!