Designing scalable Compose APIs

Поділитися
Вставка
  • Опубліковано 12 чер 2024
  • This talk will cover best practices and guidelines for developing idiomatic Compose APIs. We'll go over how to think about and plan for your components, how to leverage Kotlin and naming conventions, how to define a solid structure for your component, and how to verify and maintain these APIs. We'll discuss how these guidelines can help developers write code that is more scalable, performant, and consistent.
    API Guidelines for @Composable components in Jetpack Compose → goo.gle/3UozIK6
    API Guidelines for Jetpack Compose → goo.gle/4b2MweN
    Kotlin for Jetpack Compose → goo.gle/4b20EVH
    Adopt Compose for View-based libraries → goo.gle/4b4AYYG
    Speakers: Simona Milanovic
    Watch more:
    Check out all the Mobile videos at Google I/O 2024 → goo.gle/io24-mobile-yt
    Check out all the Android & Play sessions from Google I/O → goo.gle/io24-androidplay-yt
    Subscribe to Android Developers → goo.gle/AndroidDevs
    #GoogleIO #Featured #JetpackCompose #AndroidDevelopers
    Products Mentioned: Android Jetpack Compose
    Event: Google I/O 2024
  • Наука та технологія

КОМЕНТАРІ • 15

  • @AndroidDevelopers
    @AndroidDevelopers  Місяць тому +6

    Check out all the Android & Play sessions from Google I/O → goo.gle/io24-androidplay-yt

  • @marlonlom
    @marlonlom 25 днів тому

    Great talk about planning, applying the standard naming and writing conventions, notes about testing and documenting the api that as a android/jetpack compose developer must think about ! :)

  • @maxfir
    @maxfir 13 днів тому

    Thank you, wait for the next tutorial!

  • @calixtoandrade996
    @calixtoandrade996 26 днів тому

    great video
    thanks

  • @julioconradomarinardila3269
    @julioconradomarinardila3269 18 днів тому

    Excelente Google

  • @walrider7374
    @walrider7374 27 днів тому +4

    I just discovered this channel, awesome tips!
    I wish the best to Flutter, but honestly, I hope KMM with Compose becomes Google's favorite kid.

    • @michalkubizna
      @michalkubizna 26 днів тому

      Actually, I think Google had plans to replace Android with Fuchsia eventually. And Flutter is a default framework for Fuchsia just like Android SDK/KMM is for Android. So if that happens, Flutter will actually replace KMM. Nothing is certain though so it will be interesting to watch as it unfolds.

    • @michalkubizna
      @michalkubizna 26 днів тому

      Also, Google has full control over Dart so they might actually prefer it.

    • @walrider7374
      @walrider7374 26 днів тому

      @@michalkubizna Man, I've been hearing about Fuschia for so long already... feels like a huge bait. Why would Google replace Android? It's a functional world-wide knew product, used by hundreds of companies that feed them data.

    • @meidy3795
      @meidy3795 26 днів тому +1

      ​@@michalkubizna umm no, android itself is based using Kotlin and Java, changing it will eventually wiped out support for older devices as google would not used it. Also Google just lay offs half of Flutter developer so..

    • @meidy3795
      @meidy3795 26 днів тому

      ​@@michalkubiznaEven Google removes Chrome from Fuschia