Thanks for the quick response. Much appreciated.
I guess I feel now is the time if I do need to get some data out of sheets and into glide tables. I’m happy with the app as it works now but how will it look/function in 5 years? I keep reading that 25k rows is actually ok as long as your app isn’t overly complicated. I’m not sure mine would fit that description though. It’s essentially an event register. I create a team and that team has members (user signs up and then joins a team). The teams have associated events that the team members can then confirm or decline their attendance to. Approx 100 members per team. Currently only a handful of teams but I expect over time there could be a lot.
As a note on above….attendance is recorded using an array vs the event and not a new row entry in a sheet (to try and reduce the number of entries)
I feel like I could get lots of users if I wanted them so the question really relates to a longer term strategy around scalability.
How many users could I add before I need to throttle back? There’s quite a bit going on in the app but the 2 tables I’m concerned about are the users and events.
A lot of what’s written above is just me getting it off my chest and writing it down. Appreciate you listening if anyone got this far I’m sure it’s not unusual and many folks here face the same question. And obviously I’m conscious I actually need to get to a point where I’ve got enough users to hit the wall. But no point crying about it then. Better to plan for it now. Or at least understand the limitations.
It would be possible to flush out old users and events periodically so maybe staying on sheets makes more sense from that perspective.