In think the issue is that till now we needed to create separate lists to load different values. Now with your extension I load the hole table, no need to create separate lists. So using for example a google spreadsheet it took 3 seconds to get a big table and once you have the data you don’t need to call again the spreadsheet
From the votes, it is clear that Data property is more readable and understandable than Count property. Therefor I will deprecate Count block. It will still work so the porjects will not break too much. However after next version, it will be remove and it won’t be present in newer projects either.
Once again i felt the magical work of your extension…
Loaded 13k items from gsheet to app , created custom layout in microseconds, recreated again custom layout based on search result also flashes in microseconds…
Dont know the exact reason. Is it working fine V1 with anybody? Even i was created an app few days before , it was worked fine but today it is too throwing the same in companion
I tried it on google sheet about 16500 rows
And it didn’t take long (4 seconds online ) and 0.9 mseconds in offline
It’s better than dynamic… when you reach more than 3000 rows because you will fce problem like app stop working in dynamic component extension if you use more than 3000 get all row at screen initialize
Well FYI, it’s not the responsibility of recycler view to load your data fast from server. Recycler view’s job is to recycle your dynamic components to show the whole list data by making few components. So your apps work smooth even if it have thousands of items.
No way of hanging with airtable, runs as much as smoother… I just tested with 500 data’s, loads created view in less than 5 sec , upon refresh created view even more less than previous value