Love the scalable dashboards as they offer more flexibility on rendering.
However, one of the limitations for just ‘button’ based dashboards is that one needs to create a separate dashboard for each device metric one uses. This is a slightly different problem from the reflowing dashboards which also needed a fixed pixel size definition.
Consider the best of both worlds: Dynamically reflowing scalable dashboards (TM pending )
Ability to specify dynamically in the URL itself, how many columns should the dashboard render at run-time.
For example consider the dashboard example screenshots currently set as scalable and 4 columns to fit a portrait average iPhone (not the Mini and not the Max):
- On the iphone it shows great. If I load it up on my breakfast ipad (which is landscape), buttons are huge and screen only fits a few. If I load it up on my Mac chrome, even bigger and not very usable.
- However, if I specified in the URL for the iPhone something like: SharpTools App it would show nicely
- and if I took the parameter to ?columns=8 - it would render perfectly on my iPad Mini
- and if I took it to 10 then it would show nicely on my regular iPad
- and perhaps 12 or 14 would look good on my Mac
yes, it starts sounding and looking like the reflowing version but even the reflowing is fixed pixels (perhaps consider ?tile_size=120px as an alternative parameter that can be handed over at run-time?
and if we wanted to get fancy, the parameter can be generated from a property or set of properties on the dashboard management screen as attributes and it would still be much easier than maintaining many separate versions of the same dashboard on a per device basis.
How a scalable dashboard looks on my iPhone:
and what it looks like on my Macbook via Chrome as a 4 column layout that fills up most of the screen: