3 ms·
They do exist. Check out rxjava from netflix, dagger and butterknife and okhttp and retrofit and picasso (and and....) from square, MVP libraries, kotlin and a
by jmfayard 10y ago
They do exist.
Check out rxjava from netflix, dagger and butterknife and okhttp and retrofit and picasso (and and....) from square, MVP libraries, kotlin and anko from jetbrains
What is truly holding back many developers is the above cargo cult that the path mentionned in android.developer.com is always the right one.
There have been some harsh comments on Dianne Hackborn, but I find that she is actually doing us a great service here by dissiping this myth. I find she does a great job at explaining what is the scope they really care about, and the one where you are free to discover better alternative that do not have the "Google" label on it.
- kodroid 10y agoI agree with your last two statements, but the idea the RxJava and Dagger make things _easier_ to understand for developers (I'm inferring this relates more to newcomers to Android as they are the once which have a hard time grokking this stuff) is a joke. RxJava and Dagger only increase ramp up time and the amount of stuff to learn, regardless of how useful they are. If someone came to me confused and I pointed them in that direction, Im sure they would get lost in the woods somewhere and Id never see them again.
- jmfayard 10y agoFair point. They make things simpler, not easier
- HillaryBriss 10y ago> What is truly holding back many developers is the above cargo cult that the path mentionned in android.developer.com is always the right one. Yes. I sometimes think we need to embrace an "Android-free Android programming" approach where we use builtin Android components as little as possible and better written 3rd party components and libraries for everything else.
- st3v3r 10y agoBecause I shouldn't have to go somewhere else to have a sane framework for writing Android apps.