Blog

I tend to use android library projects.  Heavily.  In some cases I end up with eight or nine modules.  Yes, it can be tedious jumping around all the time (since changes in one place usually require changes in another –for instance adding a field to a domain pojo will almost certainly requires updating json serializer, DB insert/query, etc)  But they can help enforce SOLID principles.  Many developers who’ve had to get something done in a hurry may have added a call in the main activity, and called getActivity() from a fragment, casting the result to the main activity in order to access the method.  But, if the fragments are located in a library module included by the app project, this antipattern becomes impossible — the fragment can’t cast to what isn’t imported!  Any mechanism that enforces good design is welcome, even if there are minor annoyances like jumping around in the IDE when making changes.