Modern Dependency Management With Version Catalogs - Android Studio Tutorial 💻 

So a tip I figured out by trial and error: My recommendation is to always add -"core" to to artifact ids like 'androidx.compose.ui:ui' that have a package name that will be part of other imports. That way auto complete plays nicely and it actually improves the wizard tooltip accuracy when you do that by allowing you to click "androidx.compose.ui.core" in your gradle files and it properly auto click through to the correct dependency. This works so nicely since Import Names and even Version Names don't have to 1:1 match the artifact IDs, and you can use "-base", or any other suffix you like to make it that auto-complete works nicely all the time, etc.

You can also have a bundles section, where you set up way add multiple dependencies will a single line. It's very handy for things you always use together. Like all the compose dependencies.

This is nice and definitely makes it easier to manage dependencies for large projects. When I look at build scripts that use version catalogs, I just find it a bit hard to build a mental model of dependencies. Before version catalogs, it was easier on the eyes to figure out what "groups" we are using in our application.

thanks for this video. this tutorial helped me a lot upgrading my gradle from to old and I now understand toml very well. thanks again bro

thanks philips, this is great 🤙

This is awesome, man!

Great video to know about the version catalog ❤

Nice to see this is being done. Sad that I did this all manually and now I have to unwind it. :)

You're the best, Native developer!!!

Another nice feature is that you can create "bundles". So say that you have related dependencies like compose for instance, then you can create a bundle of these. You can then in you app gradle file just refer to "implementation(libs.bundles.compose)" for instance.

your videos are very top! Thank you so much for sharing your knowledge. 😍🤩🥳❤🙏

Thanks for this Philipp

this was helpful i was watching an old tutorial on app development that was released on 2021 and i was confused as to why my dependency lines were red while his was fine XD

Will you make a video combining versionCatalog with buildSrc ?

I hope to see a new video about buildSrc module that supports this toml file

Ah! This is great. Been working on the same big project for a while, so when i created a new project in Jellyfish for a small app this morning and went to add dependencies, the first reaction seeing the libs system was "WTF!?". Was tempted to revert back, but the OCD had won 😂 After it had taken me the best part of the morning to figure out the version catalog system on my own and add all my drpendencies manually, decided to migrate my big project... for which this video was, as usual, A GODSEND! Seriously, you're a lifesaver ❤

It would be nice to mention about bundle in version catalog. And it would be pretty convenient if version catalog has opportunity to define groups like versions )))

Would be great if you could make a video on automating Gradle dependency updates through Github Actions.

Thank you philipp :)

Thanks Philipp for your great work ! I have seen gradle team has inculded this video link in their latest newsletter published for march, 2024. I have a question related to it though, appreciate if you can point me to something. With version catalog added to my project, I am not able to generate a gradle.lock file, and it always fails to identify the dependencies. There are multiple open bugs pending with gradle for the same and gradle team not showing the appetite to fix those as well.

How about Version Catalogue vs Gradle Kotlin DSL comparation?

In addition to your content I'm also making use of "bundles" there. For example all the compose dependencies could be bundle together and instead of 4 implementation you only got 1 left in your gradle file. But that's of course an indivuall preference 🙂

Very cool. BTW. Should androidx-compose-tooling-ui-manifest be named androidx-copmose-ui-test-manifest?

will you update multi-module course with version catalogs instead buildSrc ??

Great video, Philipp! Is it possible to use the versions catalog and group dependencies like you did in the video "Perfect Dependency Management"? I mean, call room() and add all the dependendencies related to it.

Thank you BRO

Thank you for great video! :) I'm trying to migrate from buildSrc Deps object in KMM to that catalogs ;) P.S.: Don't forget to update KMM Translator ;) P.S.S.: The name of lib in 21 line should be androidx-compose-ui-test-manifest ;)

King of Android.

I'm using version catalog for a while but I didn't know that was possible uses the shortcuts to move build.gralde depencies into toml file.

Hi Philip Kindly Make an App Demo for a Live Streaming app For HLS or RU-vid Using Jetpack Compose and Kotlin.

Can you also do this with hilt dependency injection? I cant make ik work.

We have the same + build conventions

Something is not clear for me. For example, if we use timber library we can use : timber="5.0.1" timber = { group = "com.jakewharton.timber", name="timber",version.ref="timber"} timber = { module = "com.jakewharton.timber:timber",version.ref="timber"} ? It is the same thing if we use group or module? I don't understand the difference between them.

Updated to the nosebleed version of android studio, ksp, jdk 21 etc. Dependency management is nice. They have done something new with resources as well. factoring and refactoring and rere.... I swear building the framework for an application takes longer than writing the logic. For MVVM I should just be able to configure the entities and click generate. stub the business logic and save a bunch of time. by the time you write 3 mvvm applications it's going to get pretty dull

how do we defind a dependency to a module when using version catalog?

Version Catalogs are the default in Android Studio Jellyfish | 2023.3.1 Canary 11

I tried recreating your room beginner project with this version catalog android studio and I keep getting an error with classes conflicts

Hey your location tracking app doesnt seem to auto update anymore, do you know why?

i am learning android using your old projects but i am facing issue in your news app. I am stuck at a point from 3 days but i don't get any solution.i am using new version of android that is hedgehog. Please tell me what should i do?

Can someone explain why use this!? It look like few steps more then before, and I don't see any extra benefits from doing stuff this way

They are just increasing complexity, adding dependency is much easier in other frameworks, this is the thing which i don't like about android.

How to add kotlin-kapt

I'm been using this for 2 years now. It's a big improvement but I still don't like the TOML file format.

I prefer your approach to using kotlin build src folder with variables and so forth. Its easier to manage and clean. Or am i missing something?

Came here to solve the same problem at 12:56 (material reference error) and you cut how you solved it :/ update: New projects don't include old material dependency, only material3

Hi, I'm new to android developmet, is it better to get started with view xml or jetpack compose?

Why not they introduce yaml file like Flutter

would you say this is more ideal than using a buildSrc in a multi-module app?

What is the advantage of using this over the regular build.gradle?

Do they also support notices about new versions of the dependencies?

I’m waiting for the day when they’ll create a dependency manager like Rust’s Cargo or JavaScript’s npm.

Can we have more of your opinions? If you dont want to put then on the main channel i understand

Bundles is missing here.

Already know sir but thanks for the video ❤

how to create hilt plugin with version catalog? I didn't find instruction at docs. I was find it for dagger, not for hilt

Hello world !

This is so bad, as if it wasn't complicated enough already they decided to add a new language file 😢, why can't we take an idea out of flutters playbook? Their pubspec file makes all of this so easy

"Finally, developers can now use one language, Kotlin, for the logic, UI and also build config" "Unacceptable, let's bring in a completely new language without logic, code completion or even type safety. We'll build an extra tool to handle that." "Emmm, ok. We could then group the libraries together. For example with a dot like in the rest of the code?" "Boooooring, let's use dash on one side and dot on the other. So that they can't do a litelar search. Wink wink"

👍

Wouldn't using Version Catalogs be more relevant for Multi-Module Apps?

This feels so unnecessarily over-engineered

My college faculty be like this could be done by creating val for version 😂

Hi Philip I am not able to add the Hilt dependency using this approach, as it gives this error: Duplicate class org.intellij.lang.annotations.Identifier found in modules annotations-12.0.jar -> annotations-12.0 (com.intellij:annotations:12.0) and annotations-23.0.0.jar -> annotations-23.0.0 (org.jetbrains:annotations:23.0.0) I have this in toml [versions] hiltCompiler = "1.2.0" [libraries] androidx-hilt-compiler = { group = "androidx.hilt", name = "hilt-compiler", version.ref = "hiltCompiler" } in build.gradle(apps) implementation(libs.androidx.hilt.compiler) see if if you could help here