Structure in Android App Design - Google IO Video notes
If you are an Android developer, this is well worth a watch. It is from this year's Google IO. Below are some of my notes from watching it.
Importantly it introduces the Navigation Drawer (to me at least). I had seen this in a lot of places (Irish Times app for example) and liked the look of it, but was worried about having to pick a library to rely on for this functionality. So the Nav Drawer is now in the support library which makes it usable in most apps.
I'll be taking a look at PhysioTrack over the next few weeks to see how I can enhance its structure by using some of the learnings from this talk.
My Notes:
This is an example of a use case that was used in the talk
Find a Bar
Primary Actor:
Drinker
Precondition:
BarKeeper installed
Primary Scenario:
1 Users launches app
2 Indicates that they want to find a bar
3 App presents a list of choices
4 User selects a bar and is shown the choices
Steps to take to produce your use cases:
Take an inventory:
Actors, Use Cases and relationships
Prioritize the elements. Which are most important use cases.
Sequencing: What use cases happen after others. Are there hub activities? Spend time getting these right.
Decompose: Break up larger use cases. May allow reuse.
Draw all use cases on one sheet of paper. Turn it vertical. This maps roughly to your activities in your app.
Possible structures for app:
6 Pack
Fixed tabs
Spinners
Comments
Post a Comment