1) I have gone the getAllAssets route (back when there was no pagination support) and that did not work out for me (meaning not using pagination). The only way IMO to present that in a good way and be quick is to use the pagination and only fetch something like 10 assets at a time, a user can only see something like 10 rows on a screen so that should be enough.
2) What could also work is to use the assets search API when people type in the name filter (will be slow without the websockets of course) and otherwise use the GetAllAssets API to offer pagination (endless scrolling) the only thing with the GetAllAssets is the default sort order which you might not like.
Great, perhaps it can be added to the core.
1) pagination works good though, on mobile platforms user tend to find what they want quickly otherwise they just won't use it.
2) searchAsset api might improve this, in a way we don't have to fetch assets, but there is also disadvantages, beside POST being slower compare to GET, this also requires user's input to get data, user also has to be trained how to use it. (e.g. I can be wrong but "nxt" query returns all assets because accountRS starts with nxt)
I have improved performance expensive operations, release is coming soon.