I am trying to determine how to structure the code of a simple android game I am writing. I am focused on the UI portion. The behind the scenes portion (like a pause/restart/switching/etc) does not concern me. The Android demo games source code already do a great job with this.
Essentially my game will need a UI with a series of objects on the screen (roughly 100 or 10x10) that the user can interact with. I need to supply an image for each object as well as implement the touch events and animation events for each object. What I am wondering is what type of class do I use for each object so that I can successfully implement these methods and how do I implement that particular class. Note that this game only executes on a user interaction with one of these objects, meaning I don't need a "real-time" implementation.
My research seems to point in the direction that each screen object needs to be a view object and that I need to place add each view object inside a viewgroup container. I then need to decide on a layout for the viewgroup, but I’m really not sure. Is this a viable approach or are there better alternatives?
I guess I am looking for design methodology more than anything. Thanks for the advice.