Android Developers Dashboard
Developers that code for the android platform use a developers dashboard to track various information. Here is a screenshot of the dashboard used to show platform versions. The android team calls this the device dashboard. In this screenshot, we see a pie chart and table based on the number of android devices that have access to the Android Market. Below that, a stacked line graph provides a history of the relative number of active android devices running different versions of the android platform.
This simple layout is another example of how leveraging the tried-and-true website layout can make for an easy to use dashboard. There’s nothing new here – and that’s the point. Tried and true design patterns make for easy adoption by new dashboard users.
Here’s the dashboard example:
The tabs across the top span the sections below comprised of a left sidebar for navigation and the main content section on right side. A tip for dashboard designers: When using tabs for main navigation, be sure to properly highlight the active tab through the use of color and extend the foot of the tab across the screen. Take a look at the screenshot for an effective example of this.
A word about this style of dashboard design. Whenever I show such an example, I get feedback saying that this is cheating and not true dashboard design. Why? Because it looks just like a website? When is a dashboard called a dashboard? Is it the layout that defines it as a dashboard? Is it the presence of summarized statistics and charts and graphs? Why would you NOT call this a dashboard?
Leave a Reply
You must be logged in to post a comment.