Intuitive: Thinking in Compose - MAD Skills

preview_player
Показать описание
In this episode of MAD skills on Compose basics, we will cover how to think in Compose. Building with Compose lets you focus on ‘what’, and not ‘how’, unlike the View system.

#Featured #Compose #MADSkills
Рекомендации по теме
Комментарии
Автор

Summary:
Emphasise on 'what' rather 'how'.
Declarative way of building the UI.
The UI element state is defined by the argument we pass them.
We can create UI entirely in Kotlin.
Avoids errors that were coming in xml Ui due to conflicting view updates.
In compose, the creation of UI happens in same fashion as in xml.
UI elements are functions and not objects.
Recomposition - the process of regenerating the UI when state changes.

paramvirsingh
Автор

This is a very well written episode, like there's a lot of quite complicated terminology here esp. for noobs but you have made it very easy to understand, so thanks!

SoulReaperDan
Автор

Thanks to Google devs team 😘 for making Android development easier.

Sherimankind
Автор

No xml, great. No internal state to worry about, great. Some things that sound a little off though: stating that there is no need for findViewById seems a little weird. No one uses that anymore. Also, with the Views framework, when a radio button is selected, you would notify the ViewModel about a new selected choice, who would then emit an observable value indicating that the Next button should be enabled. Presenting that scenario as problematic sounds like those fake ads where people are trying to open a milk carton and they suddenly rip it in half cause they don't have the right tool. For the most part, Compose looks good so far.

ellasaro
Автор

You need to create a room code lab in compose, that would help a huge lot. For the nubes like myself.

randyii
Автор

I would like to know when you guys plan to support better:
- Webviews.
- Fingerprint.
- Permissions.

Web views with accompanist is incomplete and full of issues

darienalvarez
Автор

Why are composable functions not in lowerCamelCase? Should i use this pattern on my own composable functions?

whatahellMW
Автор

Please make video on dagger hilt library

jatinsingalEARCS
Автор

How to write custom controls UI in jetpack compose in exoplayer.??? Reply please

irsathkareem
Автор

INTUITIVE : THINKING IN COMPOSE - MAD SKILLS

jg-jsbg
Автор

Who decided that white text on a light blue background was a good idea?

markrussell
Автор

Declarative GUI only work for simple ui

llothar
Автор

You're purposely misrepresenting *your own* standard practices. No one uses find view by id. Viewbinding or data binding what does all what compose do but with way better preview options. Compose is actively encouraging high coupling of UI and business logic. Not a good option 👎

TheMikkelet
Автор

Why Android sucks? Because they first invented XML UI to separate UI from coding. And now they are putting UI into code? Why they often change the way of coding. Tomorrow they will again say, no no the XML UI way is good. And there will be no end.
Well, as I understood by stepping into Android Developoment, I find basically the whole Android Development system is a mess.
Problem is in Android the Learning Curve is not fixed. Today you devote your time of learning some tool or way of coding and tomorrow you come to know that the stuff you were learning is now obsolete or deprecated. There is no fixed way. Again learn new way. And again after some time the current new way will become obsolete or deprecated. And so Android sucks.
Simply put, there is no fixed way to learn. For example, can you simply tell me if MVVM architecture is good or MVI? No fixed answer, right? That's Android.

vkrsoft
Автор

was monetized, so that company could aim for Nice tutorials channel to make money

aungmyat