Compose Modifiers deep dive

Поділитися
Вставка
  • Опубліковано 24 жов 2022
  • A deep dive into the history of Modifiers and the constraints of APIs. As well as the problems they are meant to solve leading up to a major overhaul in implementation in 1.3 and the addition of several lower level, but powerful, experimental APIs that we will be migrating to over the course of 1.4. This talk will go into the why’s and how’s of this migration, how it impacts developers, and the performance impact it will have for end users.
    Speaker: Leland Richardson
    Watch more:
    Watch all the Android Dev Summit sessions → goo.gle/ADS-All
    Watch all the Modern Android Development sessions → goo.gle/ADS-MAD
    Subscribe to Android Developers → goo.gle/AndroidDevs
    #Featured #AndroidDevSummit #Compose
  • Наука та технологія

КОМЕНТАРІ • 28

  • @stanislavzemlyakov5442
    @stanislavzemlyakov5442 Рік тому +33

    You guys are doing great job about Compose API. The best UI framework I've worked with!

    • @AndroidDevelopers
      @AndroidDevelopers  Рік тому +33

      You know what they say, some of the best projects are done when U and I work together 😎 😀

  • @alskaa1
    @alskaa1 Рік тому +1

    I really love this talk. Good job compose team

  • @xhivo97
    @xhivo97 Рік тому +11

    Loving this type of content!

    • @AndroidDevelopers
      @AndroidDevelopers  Рік тому +1

      If you are enjoying this type of content, make sure to catch all the Android Dev Summit sessions here: goo.gle/ADS-All
      Let us know what your favorite one is!

  • @pinoy_marites_beh
    @pinoy_marites_beh Рік тому +11

    "We only make public what's absolutely necessary" - I hope you consider exposing more properties or alteast parametarized them that we can easily modify, such as the offset settings of Scaffold's bottombar or floating action button. I understand there are certain Design (Ui/Ux) principles (e.g Material) that we (us) need to follow, but too much of that restricts the creativity or worse preventing a better functionality for users.

  • @nikinsk
    @nikinsk Рік тому +2

    Wonderful talk !!

  • @jam4l
    @jam4l Місяць тому

    One of the best compose engineers 👏

  • @SiamakAshrafi
    @SiamakAshrafi Рік тому +5

    Great talk. Sorry, missed seeing you @ ADS. Hope to catch up soon.

    • @AndroidDevelopers
      @AndroidDevelopers  Рік тому +1

      Not a problem, Siamak! We've got you covered in the video description as well as a link below for more Technical Talks from the Android Dev Summit 2022😊🙌
      Technical Talks at the Android Dev Summit → goo.gle/3sRy9pN

  • @skytech2501
    @skytech2501 Рік тому +1

    love it!

    • @AndroidDevelopers
      @AndroidDevelopers  Рік тому +1

      We're glad to hear it! Don't forget to check out the link below for even more Dev Summit content, including Technical Talks where we discuss your favorite Modern Android Development tools and APIs 😄
      Android Dev Summit '22 Technical Talks → goo.gle/3TU097S

  • @Sin7yuk
    @Sin7yuk Рік тому +1

    🥰Nice talk! Wondering anywhere can I download this copy of keynote ?

  • @kalidsherefuddin
    @kalidsherefuddin Рік тому

    Thanks

  • @juansmdgp
    @juansmdgp Рік тому +3

    Great Job!!!

    • @AndroidDevelopers
      @AndroidDevelopers  Рік тому

      We're thrilled that you enjoyed Leland's video! Thanks for watching, Juan 😎
      If you liked this, be sure to catch even more Android Dev Summit sessions right here→ goo.gle/ADS-All

  • @hongthienvu2000
    @hongthienvu2000 7 місяців тому

    Ở 1 khoảng thời gian lâu về trước khi tôi đang tải game về thì mất kết nối và địa chỉ của tôi từ đó nó bắt đầu không ổn, cảm ơn.

  • @DiegoScoti-rm3kp
    @DiegoScoti-rm3kp 4 місяці тому

    0:09 😢

  • @user-ul2jc8ej2p
    @user-ul2jc8ej2p 11 місяців тому

    Пока flutter лучше. Он еще поддерживает desktop compile

  • @ivarjar
    @ivarjar 5 місяців тому

    Why should a developer ever have to see a video like this? This shows the failure of the team to abstract key concepts.

    • @Zhuinden
      @Zhuinden 5 місяців тому +2

      It's good for reference in case you want to use Modifier.Node, but the talk effectively *is* a post-mortem of how the original Modifier.composed {} was an abstraction with too high cost.

    • @yewo.m
      @yewo.m 3 місяці тому

      You might not find it interesting, but there are lots of people for whom it might be useful to know, whether just out of curiosity for how the underlying infrastructure works, or because they want to make contributions to the project

    • @yewo.m
      @yewo.m 3 місяці тому +1

      And the video is titled "deep dive" for a reason

  • @krokenstiv8777
    @krokenstiv8777 Рік тому +8

    Jetpack Compose is going to dead end

    • @gi1dor
      @gi1dor Рік тому +5

      Why so?

    • @bhargavanaidujaddu4064
      @bhargavanaidujaddu4064 9 місяців тому

      ​@@gi1dortrt😅😅t6t6tt😅😅😅t😅trt😅t6rt😅😅😅😅😅😅😅😅t6tt😅😅😅t😅😅😅😅trtt😅😅t😅😅😅😅😅😅😅😅t😅😅t😅😅😅😅tr😅😅😅😅t😅😅😅😅😅😅😅r😅😅😅😅r😅t😅😅😅😅😅😅trr😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅t😅😅😅😅😅😅😅5😅😅😅😅r😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅😅

    • @scottbiggs8894
      @scottbiggs8894 3 місяці тому

      @@gi1dorThere will always be the next new shiny thing. Google and Apple are especially big on this theme. Been doing Android for eleven years--always something new that requires changing heaps of code that used to work perfectly. Remember how great the Eclipse IDE was--what an improvement over vi and command line compiling!

    • @gi1dor
      @gi1dor 3 місяці тому

      ​@@scottbiggs8894
      Compose is not just the new shiny thing, it's official UI framework of Android, and there is no way back from it. The existing code will work, View will be on maintenance mode forewer, so no urge to rewrite anything if you dono't want
      If something new and better will be created, great, let's see and adopt. But I don't see anything in next 5 years on Android, and it's very minimal estimation, Compose here (same as Views) is until will exist
      > Remember how great the Eclipse IDE
      Not really, Eclipse never was so great, before Android was even released, for BE development (JS/PHP) Eclipse solutions were a few heads below what JetBrains offered 15 years ago when I first migrated. Same for ADT on Eclipse, they were worse than unofficial IDEA support from JB a few years before Google officially switched
      Compared to Vim, yes, but I don't understand why making this comparison and how it related