What's new in Jetpack Compose | Session 

me, Florian!

Me )

Я

Hahahahah for sure

it was made for people coming from Frontend, Flutter, etc

@Krzysztof Dróbek I have used Compose for a while now, I see how Previews should be used, but still this should be unnecessary boilerplate - hopefully the @Preview function requirement will be removed in future updates. As for your link - that specifically deals with dimens, which is only one facet of resources (I'm sure flutter devs already do something similar already). I was talking about where layouts change based on screen size - changing a bunch of dimens doesn't cut it in a lot of use cases and is simply a limitation. The XML system was organised and structured towards mobile and tablet devices giving the developer a lot of flexbility in an intuitive way. Compose lacks this out of the box, sure you can have a screen in compose with a bunch of if/elses to lay itself out differently - but this leads to difficult to read code that can be hard to reason about and more error prone. Compose looks great for a play around right now, but currently for me the traditional View system is superior. I'll see what updates come along.

Can you suggest best source to learn jetpack compose

BottomSheetScaffold with composables with different states?

@@sahil-dq9cy They have pathway on site visit official site

@@zohaib9381 No, ModalBottomSheetLayout :)

I think the only that deprecate is binding but MVVM remain useful as in some samples with compose it is still used

@Палмер Элдрич why? can you tell me why and what's good solution on it? i'm web developer trying to learn android right now so idk about that

Same developers, almost same product

Compose looks like SwiftUI, SwiftUI looks like Flutter, Flutter looks like QtQuick, and QtQuick looks like JavaFX script. There is nothing new under the sun, just another implementation of a good idea.

essentially: can it be used for generic backtracking?

Yes just create a function that return a value but still annotated with @Composable

@@OliverRhyme Awesome! Thanks for telling me. - I'm looking forward to explore it more, once I have some free time!

It's been out for 3 years as they mentioned, which means the library is stable to use in production now

July

..... I'd wait until 1.0.20+ for production releases .. at least some bugs will be fixed by then .. doesn't stop you develpoing now though as the api is decided for the first major release

@@MK-to4et I am also waiting for it. Next month

ต

@Палмер Элдрич Let's talk in an year's time ...

My best guess at the answer: it is done because Google can't get its developers to concentrate on a single framework until it is really done. Either that or Product Management is deliberately pushing the engineers to put things out before they are really done -- which explains why this happens with so many of their products, not just frameworks!

They don't want to copy SwiftUI that much :D

Why call it Stack or ugly VStack? You're clearly influenced by something and try to pass it as a common sense.

Well maybe, it sounds interesting anyways and doesn’t make compose less exciting. Thanks for replies guys

Exactly flutter like syntax on kotlin. I still remember people saying flutter 's syntax is garbage its not good. Well android just went the same route 😂. Though Kotlin has more features than dart.

Why would they add DI to a COMPOSE sample? This would make knowing DI as a requirements to understand the samples. Not using it doesn't make it bad by any means. Why have you got against DI?

@@abdelilahelaissaoui1827 Check the Android source code. DI is virtually never used. DI doesn't belong in application code. It was designed for testing code and as such, the tooling (Android Studio) should have a feature that allows you to swap a class with a mock class. Google just doesn't seem to get it, like many things they have never figured out over the years. If you need to swap different classes during runtime in a production app, the factory pattern has long esisted for that purpose.

@@SnoopyDoofie DI doesn't belong in Compose samples. Seems to me you're missing the point of dependency injection and inversion of control or you are just trolling.

I always try to avoid DI. DI makes it a mess for onboarding new workers. It removes connections and basic visual understandings of what is being implemented. Its for the birds and takes away from my joy of coding.

@@EugeneRambo oh really? Maybe you still code Android apps in Java? How do you test things without a DI.. now everybody knows Dagger or Hilt which is piece of cake to get into.