Every App is a Dashboard
I just realized today that I can barely design an application without turning it into a dashboard. I'm really trying specifically not to build another dashboard application, but whenever I step back, it looks suspiciously similar to other dashboards I've built.
Web applications generally consist of task-oriented pages and reports. In my domain (primarily enterprise supply chain), many of the tasks are done by hand-held devices of some kind. That leaves a handful of data entry screens and the reports. Greenbar is probably not the way to go these days so the reports are going to be online. Displaying HTML tables with thousands of rows is not all that useful so we need to summarize, highlight, and allow drilldowns to details. Hmm... that sounds familiar.
I'm not saying this is a bad thing, it's just kind of amusing. The challenge is to really think about the layout so that it provides the most value to the user, without getting trapped into assuming a grid of gauges/widgets is the way to go.
Web applications generally consist of task-oriented pages and reports. In my domain (primarily enterprise supply chain), many of the tasks are done by hand-held devices of some kind. That leaves a handful of data entry screens and the reports. Greenbar is probably not the way to go these days so the reports are going to be online. Displaying HTML tables with thousands of rows is not all that useful so we need to summarize, highlight, and allow drilldowns to details. Hmm... that sounds familiar.
I'm not saying this is a bad thing, it's just kind of amusing. The challenge is to really think about the layout so that it provides the most value to the user, without getting trapped into assuming a grid of gauges/widgets is the way to go.
posted by Dashboard Blogger at
10:29 PM
0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home