What's new in Android Jetpack

[@LiranBarsisa]

15:00 For those who want to use the alternative of startActivityForResult, it should have been mentioned that you need to update to these: implementation "androidx.fragment:fragment:1.3.0-alpha06" implementation "androidx.fragment:fragment-ktx:1.3.0-alpha06"

[@codinginflow]

Android development is fun in 2020

[@Zhuinden]

Everything Yigit says is gold. I wasn't a fan of Navigation initially, but Navigation 2.2.0 is already amazing: NavGraph-scoped ViewModels with SavedStateHandle support are a game changer. Tbh it'd actually already solve the result passing that 2.3.0 adds, but I guess it's a nice solution when people really are looking for "the simplest thing".

[@Zhuinden]

Also I was skeptical that Paging 3 would be backwards-compatible with Paging 2, but they did it. Wow.

[@saidooubella]

I tried hilt right after this video and it was way more less headaches. i love it 💚💚💚 !

[@Hackaprende]

Do you know if I need to know Dagger to learn Hilt or can I go straight to it?

[@saidooubella]

@@Hackaprende no, no need to learn dagger if you're an Android developer ! Go-to the documentations to know how to use Hilt on d.android.com/

[@Hackaprende]

@@saidooubella thanks, starting right now!

[@saidooubella]

@@Hackaprende i am glad that i was helpful 😊 !

[@goobar]

Very interested to try out Hilt and see how it compares to the existing approaches 🤔

[@musabnasreldeen2009]

Yes it looks interesting

[@prudhvir3ddy]

@goobar waiting for your videos..

[@nishantgarg7497]

After Jetpack, Android is actually becoming Better. Will try out soon

[@mdalikazi]

Thank you for Hilt. I hate Dagger because of the steep learning curve I only use it if I'm forced to. Now with Hilt hopefully DI will become part of all my projects.

[@arseniykucherenko4960]

How about Koin? Did you try Koin what do you think about it?

[@mdalikazi]

@@arseniykucherenko4960 no never tried koin but I've heard of it.

[@denisshov8518]

The first 3 seconds of the video... I watched them 10 times in a row... Like it.

[@n-o-i-d]

Thank you for the long-running job support for work manager!

[@gabormiklay9209]

This is the 3rd video tonight (about Android 11) and my mind is already blown. 🤩 Amazing work guys! 👍

[@orhanavan7222]

Woaw new DI library inspired from Hilti, I'm excited 😉

[@ragupatt]

Does it make sense to have Bill of Materials (BoM) for jet pack? There are too many libraries now and it will make it easy to be on top of the latest releases.

[@dmitriykarlovsky369]

Hi. Why did you design Paging3 with extension of PagingSource? Extension is always hard to Unit-test. You could create interface with all methods to implement and expect it in ctor. That all reminds old story with Thread-class. Does one should extent it or inject with Runnable?!

[@SumitSahoo]

Hilt is the new Dagger. Long live annotations :)

[@aamernabi]

Title should have been "Whole new Jetpack".

[@coroutinedispatcher]

I loved HIlt. Congratulations, awesome job

[@xpopcornx1747]

What if you want to pass multiple values back from navigation? SavedStateHandle observers only works for one value, so you have to spam observers for each value you want to return which will happen in an unpredictable order.

[@shahrukhmalik8496]

Just went through hilt by making a sample application. Must say that zero amount of boilerplate code is needed to add hilt in your apps. A great wrapper library indeed. Thank you android team.

[@gabormiklay9209]

Theme changing and creating/managing is something that wasn't easy (at least for me).

[@kenjimatsuoka]

I was try introduce hilt to my app. It was super useful and easy. By the way, does remodels mean view model in subtitle 02:38?

[@antoniokomangyudistira4150]

I love android jetpack

[@ohefny]

What is the platform bug on sdk < 26 that makes you write this line config.fontScale =0 as a workaround

[@RaviTejagameboy]

I use rxjava bg thread to run initialization of deps during app launch, whats the benefit of using App startup?

[@thonguyen252]

I am still confuse why does Navigation alway use replace fragment which cause fragment is re-created when I popBack. In many cases, I would like to keep the fragment alive. I tried to use dialog instead of fragment but they consume too much memory.

[@do9core]

Hilt really help me to reduce so many lines of DI codes.

[@kbdevashish7645]

Android Jetpack team already knew the pain of android developers implementing DI frameworks, the comments praising Hilt shows that. Will try out soon.

[@crjacinro]

why Google created another DI instead of embracing the popular Koin DI that is being used now in most apps?

[@RaviTejagameboy]

Its not entirely new Di, just replacement of dagger-android.

[@crjacinro]

@@RaviTejagameboy ok. so why create a replacement then? instead of recommending koin officially?

[@RaviTejagameboy]

@@crjacinro Google always pushed dagger as main DI for android, they are now investing resources to make it easier for beginners by introducing hilt, Koin is never in the picture

[@RaviTejagameboy]

Again its not replacement of Dagger, it's a wrapper around dagger to make DI easy when dealing with Android components

[@SaiTeja-vq8hq]

Umm.. just why hilt.. Koin is way better and readable.. Lesser compilation times (dryRun as a unit test when you actually change your dependencies) Can remove dependencies at run time (unload modules, simpler than scopes) Some 11 ms delay in startup for 400 dependencies which is totally acceptable for the benefits you get (lesser compilation times)..

[@mohamedsaeed1891]

i'm confused what should i use AndroidX or jetpack

[@itscooldawgdonteventrip]

Thanks Yigit. Brilliant.

[@rickmuse3905]

Cool for new api.

[@alexneeky7920]

what about injecting into workers or other cases which previously used with assist inject lib

[@ЕленаБелашова-ц2ф]

I feel happy after this video🤩

[@1990mrnobody]

I thought with next version of Paging you will provide some easier way to update/delete item in RecyclerView and I'm disappointed we are still forced to use Room or do extra work to have such a common scenario

[@gabormiklay9209]

12:47 haha. I was just thinking about Lint yesterday, as I made lot of changes to my codes.

[@AndreuJapan]

It is possible to use injection in objects with Hilt?: object Object1 { @Inject lateinit var myVar1: MyVar1 .... }

[@is0658]

hilt is looking great

[@javalc6]

Nice, but still missing stable release of androidx.appcompat:appcompat:1.2.0 (waiting from last year)

[@arseniykucherenko4960]

How about better game development support when we can develop native mobile games with nice visual editor in Android Studio just using Kotlin and get rid of all this third parties like c# with Unity?

[@Hackaprende]

Do I need to know Dagger to learn Hilt or can I go straight to it?

[@aruny25]

No go straight for it. It's designed for easy adaption

[@shikharraje]

Is Hilt open source? Can't seem to find it on Github...

[@lsanotes]

cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:hilt/

[@shikharraje]

@@lsanotes Thanks! Is this a git repo? And what website is this?

[@GrantOakley]

@@shikharraje dagger.dev/hilt/ went live today

[@igorbrishkoski4073]

dagger.dev/hilt/

[@SaminAliMondal]

I need pagination with mutable data. 😵

[@dilaojermaine]

Agree. They moved Paging to version 3 without even considering it.

[@RhexGomez]

Paging 3.0 exposes a Flow. You can can convert your Immutable Data to Mutable.

[@iris_blake]

Thanks for Hilt🥰😅

[@tamboo_art]

Oh yes

[@dnkilic]

Thank you! Thank you! Thank you!

[@CopernicoTube]

I wish some in house lifecycle support for bound events, because the existent way to use observable live variables to it, is a damn antipattern. Actions aren't data.

[@sivaganeshkantamani2976]

This what's new series is great Yigit Boyar. Really you covered a lot. Hilt is my Favourite

[@manalu-kh6hs]

OK 👍

[@minh3348]

dagger is the besttttttttttttttttttt

[@Shakenbeer]

Google spoiled really cool DI library called Dagger, and now they are trying to reanimate their Frankenstein.

[@TekEffekt]

Sviatoslav Melnychenko why was it spoiled?

[@Shakenbeer]

​@@TekEffekt I was a Dagger user since the very beginning, and it was OK. Dagger was framework-independent, and with proper architecture, one could really easy in-build it into Android application. And then... Google appears with this crazy idea to make Android dev live easier, and the learning curve of Dagger became almost vertical. Eventually, we end up with this monster: github.com/android/architecture-components-samples/blob/master/GithubBrowserSample/app/src/main/java/com/android/example/github/viewmodel/GithubViewModelFactory.kt You could tell, then this is one man's opinion - agree. Actually, the only argument I need is in this video itself (quote): "... we were able to delete 75% of the dependency injection code".

[@queenangle5843]

@@Shakenbeer yes mein vate kar rahi tumhari sab ki soch kiye pagal samajh Rakha tha kya

[@charuwaka1]

What about Dagger Now ?

[@hpmusicbytes]

Rip dagger?

[@Ziptoze]

First

[@gentlepeace-09]

You guys are amazing , I wish I canbe be part of you 🥰 it will be honor for me.