It's a big ask but the experience of a large google spreadsheet is for more responsive and useable than a table view of podio which I believe to be (once the filtering and search has been completed) effectively the same thing. Just whatever those guys are doing is super fast.
I can load a spreadsheet on google and scroll both horizontally and vertically through hundreds (even thousands of rows) with dozens of columns very quickly.
Podio limits us to just 30 rows and then fetches from the server ever additional 30, this makes it feel really sluggish to scroll through a table. I measured it on average on our particular app to be around 2-5 seconds for each chunk to load... on a good run it'll take at least 30 seconds to scroll through 300 rows and yes we've already filtered our list down. We'd filter on a text field as well but thats not a feature yet.
Horizontal scroll is missing from the interface most of the time, leaving us with buttons to click through to see more columns or go back and forth which is simply archaic. Using podio on a trackpad is much nicer simply because you can scroll horizontally with ease.
I think if you can fix it so the horizontal scroll bar is there permanently in the same way the vertical is. Then maybe fetch data from the server in bigger chunks thank just 30, perhaps 100 or make it user configurable. That'd go a bit in the right direction of making it a great deal more usable in the mean time until you can make it like google spreadsheets and handle thousands of rows :)
I'm converting users from spreadsheets to a database system for many reasons and they've been spoilt with google spreadsheets but I find it hard to defend this particular part of podio.
Please sign in to leave a comment.