Story points work very smartly on a smartphone. This style is particularly great for a group of related dashboards, although they don’t necessarily have to have a story. This example has many dashboards with different focuses, allowing the user to swipe through the story points to find the specific measures they need.
For these dashboards, I chose a size of 350 x 600 for the story and 320 x 460 for the dashboards. On my phone (which has dimensions of 360 x 598), the top of the story points are cut off, but I can still tap them. And there is plenty of room for my chubby fingers to slide the view up and down. I added the text box with a border to the dashboard as a guide while placing the elements, but decided to leave it in the finished product as I did find it helpful as a guide when viewing.
With respect to interactivity, I kept the filters to a minimum—no more than three per dashboard and specific only to the charts within the dashboard (no global filters). This reduces confusion and helps with performance.
On the sales map dashboard, the map interacts quite smoothly and the tooltips behave nicely, appearing and disappearing when you want them intuitively. I don’t know how much smaller you’d want to go with a map, which limits the amount of information you can add. In this case, the tooltip would be a good spot to add additional fields and values.
The city sales dashboard (the last story point) is probably the most challenging in this bunch. There are two drop-down filters and two chart actions. The sales trend chart has skinny little bars which allow the user to filter on a time period. I don’t recommend using this chart if you like the people you’re building this for. I left it in as an example of the frustration you can experience. Try it out on your phone. The fat city bars are much easier to use as a filter.