Hello fellow developers. I and 3 of my fellow students are doing a school project, writing an Android app. We are taking a bachelors degree in Software Development, so we have studied Design Paradigms for desktop applications, from Craig Larman' book, "Applying UML and Patterns: An introduction to object oriented design and analysis".
We usually do a domain model, a data model, and a design class model. Ending up with 3 to 4 layers. such as a technical layer(sql and network connections), a domain layer (business rules, and domain objects), a controller layer (controllers for managing domain objects, or usecases), and a UI layer. We are used to building our applications this way and can't really wrap our heads around the optimal way to design the architecture for an Android application. Question 1. Is there any reading material, books, articles from google or such? (We need to reference it in our final report) Question 2. How do we go about it? - Do we put the controllers in a service, with the domain layer, and handle the tech layer with "Handler" classes, for separating it out into different threads? - How do we make the connection between a service and an activity then? Via AIDL? - Is an activity only meant for gui, or should it contain controllers? - Do we incorporate broadcast listeners into the service, or do we bind the service to the broad cast listener once it gets a message which needs action? Hope you can enlighten us :) Any reading material is much desired. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
