@riggaroo Good to know!
What is the best approach to use Material Symbols in Compose Multiplatform?

@Aurimas There's this plugin from Google that for some reason sits under the Maps platform https://developers.google.com/maps/documentation/android-sdk/secrets-gradle-plugin
Not sure if it's best practice to use it. You could achieve something similar to a .env file with it.

@Aurimas yes, both of those. There's secrets that need to be used only during the build process, like keystores or google-services.json on Android, and then there's secrets that end up being embedded in a bundle to be used at runtime, like API keys and other identifiers. The latter are of course avoided altogether.

@Aurimas Thought of another one. How to work with secrets to keep them out of version control. I feel everyone is doing different things to inject secrets from places like Vault, Infiscal, or 1Password, into a Gradle build.

@Aurimas maybe just when to use them to share build logic. What they are good for and what they are not good for.

@Aurimas Convention plugins ?

@Aurimas
Are the version catalog examples here flipped? 🤔
https://docs.gradle.org/current/userguide/bp_dependencies.html#dont_do_this

@keyboardsurfer Nice! Would be nice to get some GitHub Actions building blocks, like utils to generate baseline profiles, officially from the Android team.

@simonbs @kylebshr
If it's just a small Cron job that calls an endpoint, maybe something simple like trigger.dev or even val.town could work 🤔
I haven't tried https://trigger.dev but I've considered as an alternative to very simple Workers.

@ashdavies They "deprecated it without replacement" and recommend "forking their implementation and adapting it to your needs"
https://medium.com/androiddevelopers/an-update-on-jetpack-compose-accompanist-libraries-august-2023-ac4cbbf059f1