Android Architecture: Introducing Dynamo

Written on April 3, 2015

Dynamo has been superseded by Pilot

Welcome, welcome. Come in, it looks mighty cold out there. The code is laying heavy across the hills, disorder rules the day and the nights are long. We yearn for a day where the suns shines forth once more.

This is post #2 of my very short Android Architecture series (can two be a series?). Post #1 was a primer for this post. It contained

  1. A brief outline of the problems when defaulting to stock Android architecture.
  2. An overview of common general architectural concepts.

This post is really a short intro to a small library + Wiki I have created. This library fills an architectural hole which I see in the Android dev world. There is no unified approach to generic Android app architecture and this creates a vacuum which sucks in well meaning devs and results is messy codebases strewn across the land. It is also my reponse to the many MVP blog posts out there, which have really helped me think about this issue but also I have my own take on.

Plus, I feel sorry for new Android devs who are turning up later to the party and are overwhealmed by the Android ecosystem and need to get up to speed quickly on what these issues are before even getting to the point of thinking about potential solutions. Some of the issues addressed by this approach are solved by fantastic existing libraries, but again, I think for a large chunk of devs these can be difficult concepts to grasp and get running with. These are mentioned in the projects wiki for further reading.

In my experience at least there are two core ideas around the center of most apps codebases. From the codebases I have seen & inherited both ideas seem to have too few brain cycles spent on them.

1. State

Most apps and views are state-based however the spaghetti-level that captures the state logic is generally very high.

2. Asynchronous code

Pretty much every app involves some asynchronous code. Pretty much every app allows this to touch the Android lifecycle. This always leads to sadness.

I spoke about this in the first part of this brain dump of a blog post

Introducing Dynamo

dynamo droid

Dynamo is a small library and wiki I have created to show my approach to an Android architecure that works with these two bug-spawning-hair-loss-inducing areas.

It will reduce your Activity, Fragment and View classes to dealing with View behaviour and States only via a simple interface, for example

Its a simple approach to decouple your UI from the core app logic which results in easy-to-understand and easy-to-test code.

Check Dynamo out.