As is the case with most SaaS, there is sometimes simply too much data to fit on one section of a page. On the desktop app, we use a standard table view of data. On the mobile app, we use cards in place of a table as they are traditionally hard to read on mobile.
We have begun to run into a problem, where we are running out of room for necessary information within a table view on the desktop iteration of the software. My idea is to convert the tablular data that exists on desktop into cards similar to how they exist on mobile, so we can free up some space and unify some of our mobile concepts with the desktop iteration.
However, each card item takes up a bit more real estate (approx 4 lines of tabular data to a card) than a simple item within a table. By converting the items to cards, we can view all necessary information, and each card can grow as we continue to add info to these tables. The feedback I have gotten is that there is a concern about scroll time.
Out of the 200k+ userbase, there would be a maximum of 30 items on this page as it is an underutilized part of the interface.
Is "too much scroll time" enough of an issue to shoot down this idea altogether? How would one handle too much information on a table without truncating text or using icons in place of text?