Seek information on android architectural design patterns - evt. through this link: http://stackoverflow.com/search?q=android+design-patterns+architecture
Hardy Henneberg http://www.maxikeys.com On 22 Nov., 20:33, Rajib <rajibkanu...@gmail.com> wrote: > Hello Friends, > > I am new to Android. I am coming from web background. I am currently > working on developing a game score recording application for android > phones. The design that I am thinking of is as follows > > 1) View or the Activity Classes > 2) Customer Controller Class which will be a middle layer between the > Activity Class and the Business layer > 3) Business Classes > 4) SQLLite Database. > > As per my design, the view or activity classes will be talking to the > controller layer only. So there will be an instance of controller > layer created and kept alive until the application closes. > > The Controller layer will be talking to the business class. For > example, if I have a requirement to retrieve list of players from > database, the UI or activity layer will call the controller layer's > getPlayerlist. The controller layer will then create an instance of > the "Player" businesss class and call the getPlayerlistFromDB. The > data will then be sent back from Business layer to controller layer > and then to the UI layer in List<playerclass>. > > I want to understand is this the right approach or right architecture. > Please help me here. > > Thanks, > > Rajib -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
