Planning an Android User Interface… for dummies
February 26th, 2010So I’ve been recently looking into Android development, and have been abusing the internet searching for information. I found that the easiest way for me to absorb the Android framework was to create a power point presentation as I went along with useful information. As I was going through, I realized that the “stack” idea (explained REALLY well here) of how Activities are created and managed was familiar to me, and was trying to figure out how to best leverage this familiarity. I determined that it was similar to creating index cards, and as you create new Activities, to put the new Activity “card” on top of the previous Activity “card”. As you finish Activities, you pop them off of the stack, so you’d remove the Activity card from your stack (see the analogy here?). You could certainly use a power point slide show to provide a similar model, but I feel that you get a little more use out of physical cards. I’m still working on developing this model, but my card composition (currently) is as follows:[img coming soon]Front of Card:
- A label showing the name of this Activity. This is merely used as reference between the different cards.
- A series of UI Components which display different Activities to the user.
- These components will show the layout, and will be represented in the appropriate layout xml file in your project.
Back of Card:
- List of Activity interactions. These will outline which Activities on the front will spawn new Activities (push them onto the Stack).
- List of incoming parameters. Might populate certain text fields, or retrieve data from a SQLite DB based on this info.
- List of Services, Content Providers, and Broadcast Receivers which will be called within this Activity. Data from these objects might populate some UI Activities here.
Some other really useful utilities that I’ve found:
- Stack Overflow
- Android Developer Site
- Developer Life tutorials
- and of course, Google

