It won’t have much impact. Confusion optimization will be done, and unused libraries will be optimized during packaging. But if a project has too many dependencies, it may cause slow compilation during debugging.
It is recommended to add all dependencies without any dependencies, which will really slow down the compilation time. Of course, artifacts such as instant run can be used very well in most cases.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It won’t have much impact. Confusion optimization will be done, and unused libraries will be optimized during packaging.
But if a project has too many dependencies, it may cause slow compilation during debugging.
gradle is just a packaging tool and will not affect the app.
If there are too many dependencies, the compilation time will be very long. . . . . .
It is recommended to add all dependencies without any dependencies, which will really slow down the compilation time. Of course, artifacts such as instant run can be used very well in most cases.
xml attributes may have naming conflicts