With millions of mobile apps being built and deployed, it’s hard to get an understanding of where the usefulness of most of these apps are. Developers today are stuck building for a function or a particular type of app, but it seems as if there’s a greater context missing on both the operating system side, as well as the development methodology.
The operating systems for mobile devices, for the most part, are a blank slate with set interaction paradigms and patterns, but leave a great deal of the interactivity framework up to the developer, outside of the handful of folders and menus one interacts with to get to the program as well as interacting with the “out of the box” functions / apps / etc that come with the phone (clock, PIM manager, etc).
I propose then, the following method to consider how apps can be organized, in terms of a user interaction framework. By thinking about things in terms of roles, tasks, and situations, it’s easier to understand the exact set of circumstances in which someone might be interacting with their mobile device as well as all the considerations that would go into maximizing the level of usefulness within those circumstances.