Only registered users can comment.

  1. 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.

  2. 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) 😁

  3. 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.

  4. 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

Leave a Reply

Your email address will not be published. Required fields are marked *