Ultimate magazine theme for WordPress.

Understanding Compose (Android Dev Summit '19)


This session covers the benefits of a declarative reactive UI system like Jetpack Compose and how it applies to real problems that Android developers have today. Additionally, this talk expands on the programming model of Jetpack Compose and some of its implementation details the can help you understand how Compose works.

Presented by: Leland Richardson‎

Jetpack Sessions →
Android Dev Summit ’19 all sessions playlist →

Subscribe to the Android Developers channel! →

Check out the photo album →


Source: https://blogema.org
Read more all post Android Technology : https://blogema.org/android/
  1. Apenschi says

    So, if you make Kotlin like Flutter, then why shouldn't I use Flutter in the first place?

  2. chethan HB says

    I do not understand exact reasons of introducing compose . Even XML layout are also declarative. Isn't ? we leave out exact position and make that to be more generic to fit all type of devices .

  3. Abner Williams says

    awesome share for go deep into ui development construct.

  4. Evert Smits says

    9:35 alright so if (count > 0 && !hasPaper()) remove the paper anyway. I guess we're not getting any paper boys. Maybe this mistake was to show us how easily bugs are introduced 😉

  5. Axel Katerbau says

    Betting on Kotlin takes its toll. Requiring changes to a compiler for such things is ridiculous. But as the CTO of Jetbrains often reiterates, he doesn't see use cases for compile time functions (aka real macros). Well this here is one of 'em.

  6. Jack Vial says

    Can’t we just have Swift on Android already and make app devs lives easier

  7. RinoSs says

    Welcome Flutter!

  8. TheDnaitsirc says

    Is this still a thing? Android associate certification doesn't cover this

  9. Siddartha Reddy says

    I think at 9:38 Last second if statement is wrong

  10. Jibran Iqbal says

    So it's react and that's cool.

  11. Samuel H says

    First comment from Brazil

  12. Robert Chrzanowski says

    You had me at declarative ui

  13. Developer Mobile says

    it is much more convenient to build ui in android than in iOS,but experience in iOS is better.

  14. Great

  15. nOx1D3 says

    9:32 , that code is wrong.

  16. Oreste Acacia says

    For me is total no-sense, I think they will provide this as an external library to integrate in projects but we still be able to use XML layouts, then this approach for me has so much lacks. For example how this approach would works if I want to build a custom animated drawable?

    Then, how to extend a Button() to make a custom view? Then how to see layout changes in real time while creating the view inside the editor itself? It should let me see a preview of what the final result is

    I will prefer XML so far, it is much clear then with dataBinding it is the top of the top

  17. Meridian Software says

    Well, you convinced me!

  18. YISHU Kr. BAGHEL says

    Can anyone tell me that how can I improve my coding skill without any cost?…
    . please

  19. Moshe Waisberg says

    Google is trying to migrate layout XMLs to be like Flutter?

  20. Gianetan Sekhon says

    Second comment from India, first one from 50 ft under the ground.

  21. Alex Neeky says

    Google io 2021 we are introducing redux-compose and redux-coroutines for communication between different layers

  22. deepak kumar says

    I really don't like this flutter version of the Android. We have already XML which manages layouts amazingly amd also separates the UI logic, then why bringing this one, a component driven programming like flutter/react does.

  23. هادي says

    Did the flutter team help with this

  24. Cody Engel says

    Really awesome video, I can't wait to see how Compose progresses. Playing around with it during the conference was very promising though. I think after I get through the rest of my Modern Android Development video series I'll start creating one for future looking things (such as Compose) ?

  25. Некто Лохматый says

    If I understand this properly, it's able to memorize states of your UI and change views only if the state changes. Seems powerful, but the usage is still confusing.
    First, I didn't get what the '+' operator means.
    Next, it was told that "a composable function can be called from only within a composable function", so, how can one use this with libraries like, for example, RxJava?
    In the presentation there is a call to getData() function (25:42), which either returns the prepared data or returns null, if the data is not ready yet. And thus, there must be a way to re-call the composable App function when the data is ready. How is this handled? Does the module which provides the data call the UI module's App function? – But that's a total snafu because it's typically the UI which calls the data module's methods.
    So, after watching 2 videos from Google IO's about composable UI I'm left with a huge misunderstanding.

Leave A Reply

Your email address will not be published.