This message was deleted.

I know that Seb and others will have more insight to offer, but just as a starting point it’s important to keep in mind that it isn’t as simple as a user count; all of the users, data connections, tables, fields, etc. that compose an app have an impact on its performance (along with client hardware and software resources, browser, extensions, network connectivity, etc.) So there isn’t any easy answer to questions about what “Stacker” can support, since each app and its data and user base will be very different — which is also why we can’t really test for a lot of this to try to get concrete answers to these kinds of questions/concerns. Individual Stacker apps are not only what we put into the platform, but also to a large degree what folks like you put into them (an new empty Stacker app doesn’t do much of anything). This is very different than if we made a monolithic “app” software product that was the same for all users. It’s one of Stacker’s greatest assets (which is why you’re using it) and also challenges (which is why you’re bringing this up!) That’s not to diminish the issues you and your users have been having, but rather to kick off a discussion about the complex topic you raise. We’ll continue to work with you to do whatever we can to help. <3

Yeah, I understand it can be hard to identify precisely, but rough figures would help. For instance, how many active users could be handled by a very small app? That would basically be the “cap”, as any bigger app would typically not be able to handle that many users. And, if it’s hard to anticipate, it could be figured out from actual response times and charge issues. For instance, my app A (a really big one) could let me know than it cannot handle gracefully more than 100 users at once, while the app B (a small one) could handle up to 500 users at once. Those metrics are important for business, and they could be “derived” from how our app behaves for real. Performance never were a key issue so far, but this page crashing is a game changer, it makes the whole app unusable. I knew perfs weren’t super great but the app was still usable. If I can’t scale with Stacker, I need to know, and fast.

Absolutely. Personally, I like the idea of Stacker having some threshold of degraded performance that results in appropriate parties being notified…but defining that is the hard part. I’ll let others chime in here.

Hey @sticky-night-20812, while I don’t know the specifics about the number of users being able to use the app simultaneously, crashes shouldn’t happen either way. This is not the experience we want you (or anyone else) to be having. We could definitely do a better job at setting boundaries of what is possible and what isn’t, and I’ll make sure to share that with the team. Perhaps we could expose some basic metrics and estimates like you suggested. All that said, we do have indications that the issue you are seeing is isolated to your specific app and are actively looking into it. I’ll follow up with you in a DM with some private details.