@remco.plasmeijer,
If you could tell us your use case, and why do you need 10-20k of items, maybe we could help out with a custom solution, as we haven’t received a similar request for now.
If you want to know that just for the sake of numbers, we are not focusing on that right now. Some other features which we think are more valuable to most of the customers. Do you need some data store that is capable of storing thousands of records?
.csv import has been very challenging feature to build as it should cover literally thousands of different scenarios and use cases on how can members map their data, link their rows/columns to the attributes, etc.
We did mention that the .csv could be messy in the future, and I think our dev team is fixing and updating that feature every week, as every week we get a new use case and a problem we need to solve.
Just one of the reasons why our workload is a mess.
Updating current features, fixing bugs/issues, building new features, web development, payment details, etc.
Marketing + Community + Product (suggestions/reporting bugs) + Support + Sales team is a team of 3 people.
So there’s obviously a workload, and I’m sorry if we’re missing something out.
I’ve published an update on our Social Media pages regarding Public Boards & Forms.
We’ve optimized the speed and performance of the app 2 months ago, and we’ll continue to do so, that’s not even a question. As it’s almost the end of the year, we’re finishing stuff up, features we’re almost done creating, after which there will be new priorities, in which speed + performance improvements, discussions about csv import, integrations, automations, webhooks, etc will take place.
And @micck is a community member of ours. I’ve got a vibe that you’re confused that we have members that use our product and support us? I’m not. And neither is Michael, obviously.