Doesn’t hurt to just try it. Really easy if you have your data in a google sheet. Populate your app with a bunch of test data and see what happens. That’s what I did when I did a test up to 120,000 rows. The design of my test app was not very efficient, so it did get really slow, but if you properly use row owners to restrict the amount of data downloaded to a device, and use simple design without loading a ton of images at once or a ton of rows on one screen, then it might just work for you. The only way to find out is to test with your current design. Most limitations are due to bottlenecks between glide and google or an app trying to overload a device’s cache with too much data and images.
So it does go over the 25k rows?
Every user uses a row if they log register, if the app starts to get used it will easily flow over it.
My app uses a lot of images, and the main page was pretty slow, so I loaded less images, but it is theoretically going to load very long lists with images in other pages so I’ll have to test it I suppose but the main point is if I have the limit of 25k rows or not.