Hi all, I'm thinking in develop a base project to ...
# android
a
Hi all, I'm thinking in develop a base project to use as a skeleton and reuse it in order to avoid a similar setup every time a new project is started from scratch. What setup do you think is important and should be in this base project?
a
MVVM design pattern. Use Google Architecture Components https://developer.android.com/jetpack/docs/guide
a
Yes, I've in mind to use Google Architecture Components, androidx. Do you think that is a good idea if I also implement a dagger support and its base setup?
a
I personally don't like and don't use Dagger. I don't see a big advantage using Dagger, but maybe I'm wrong.
a
and what do you use? Koin?
I mean, in order to implement dependency injection in a project
a
I haven't used Koin. I have used Dagger in a few projects, but I don't like it :)
a
oh, I see
hahah
😁 1
f
Lots of base class and a util package 😂
a
what do you mean with “base class”? haha
k
For exp: you can create a mvpbase module with clean architecture, rxjava, dagger including: base classes (activity, fragment, custom views like dialog, progress, extensions) and utils(network, permisson, file..)
a
Thanks!