I have a Pro app running with Email Whitelist authentication and likely to handle about 500 users. Each user will have the ability to provide feedback on themselves on a regular basis. Their feedback is not seen by other users but can be seen by an admin.
My design captures all of the feedback in a single sheet with a row per feedback item. This has a relationship with the users sheet via email so that a user’s feedback items are linked to them. It also uses the email as row owner to ensure that each user can only see their own feedback items. A separate Admin app provides access to all feedback items.
All good so far, however I am going to hit an issue if the users like this app (which I hope they will) and start providing feedback on a regular basis. If I have 500 users then after 50 items of feedback each I will hit the 25,000 row limit in Glide / Google (not actually sure which).
So, my proposed strategy is to only let the user review their last, say, 25 feedback items and use something like Integromat to “clean up things” on a daily basis by extracting the oldest feedback items and moving them to another “data store” somewhere. It is important that they are retained for audit purposes.
However, this in itself introduces some issues:
- It’s a shame that the user won’t be able to see their entire history
- The admin will need to check both Google and the other “data store” to see the full picture
- Integromat (or Zapier) will need to DELETE not just clear the older rows - not sure they do that?
- What could I use as the “data source” to hold the older feedback items?
Whilst I REALLY like Glide I’m wondering if I might be better using a tool that supports a database “back end” rather than relying on Google Sheets. That would be a massive shame since Glide has addressed everything that I’ve needed to date, I love using it, and the community is awesome.
What am I missing? Help!