2 ms·
I started my first Android app recently, and decided to go with their "Jetpack" stack recommendations. I wasted hours trying to get Dagger 2 injection working,
by sterlind 8y ago
I started my first Android app recently, and decided to go with their "Jetpack" stack recommendations. I wasted hours trying to get Dagger 2 injection working, only to discover I had to write tons of glue code which obviated the purpose of the DI framework in the first place! I don't want to worry about transitive dependencies over an object graph and writing ViewModelProviderFactories (actual name) and persisting my data with Room.... I just want widgets, logic and layout.
Next I tried GKE and it was an absolute joy. I had a simple web app serving traffic an hour in. Probably because unlike Android, they have to make people like GKE to sell it.
- izacus 8y agoWhy are you bringing in Dagger 2, a non-platform separate dependency injection library here? :) Do you think a proprietary Windows C++ compiler for an embedded platform will make your DI uses easier? :)
- sterlind 8y agoThe Android Jetpack guidelines strongly recommend Dagger 2, and it's a Google product so I thought I should comply.