I’m working on an app in which you can create an endless number of dashboards with (so far) an endless number of reports in them. Considering performance, we came up with the idea to limit the number of reports per each dashboard. However, it doesn’t go hand in hand with the Premium account. Creating your own dashboards is possible only within the highest plan, that’s why I don’t feel good limiting the number of reports in dashboards (“I’m paying you big money, why can’t I have so many reports as I want to?!!?”)
I came up with the following solutions:
- Limit the number of reports per each dashboard. Say explicitly that the User cannot create more than 20 (I don’t like this).
- Educate: do not limit the number of reports, however, when the User does so inform him that it might affect performance. Show some kind of hint or tip that will suggest creating dashboards with fewer than 20 reports.
- Do “nothing”, well… kind of. Create lazy loading for the next reports apart from the first 20 (labor illusion, nudging?), or create pagination that’s not very helpful in case you have over 20 reports. Or anything of the sort.
But I am not sure as to the direction we should go. Did you have a similar problem to solve at your work? Or what would you do in such a situation?