[aerogear-dev] Modularizing the Android Library

[Summers Pittman]

Earlier in development (pre passos) making the Android SDK into modules 
was not a concern (in fact it was an anti-concern).

Now, however, we have a much more complete project and it is time to 
have that discussion.

Right now we have two BIG questions:

1) Do we want to break out interfaces and implementation?

If we do this then we could reuse a lot of code to make a aerogear-java 
as well.

2) How granular do we want our modules?

IE If we break out push into aerogear-android-push would that include 
GCM, SimplePush, MQTT, etc in one package or would it look like 
aerogear-android-push-core, aerogear-android-push-mqtt etc.

Thoughts?

-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.