I’ve built dozens of internal tools and portals for my clients in Softr and they work great. A client is requesting a content site to host all their content that is currently spread out on various platforms all over the internet. They anticipate a few thousand people using the site every month. Some content will be publicly accessible, some will be behind a login, and some will be behind a paywall.
I know I can build this easily in Softr, but the question is, should I be building it here? We will start with a few hundred videos and a few thousand viewers, with a fraction of them becoming users. Both content and users will grow over time.
At what point should I expect to outgrow Softr for an app like this?
@artur can confirm how we enable users to scale such use cases - but handling hundreds of thousands of database records shouldn’t be an issue on our end
Will those videos be stored as files or URLs? If files, this could quickly consume the allowed file storage in Softr Databases, if URLs, no problem.
The key here for scalability and maintenance will be to, on your end, nail the database structure to make sure it will be easy for you to manage, limiting ad-hoc fields or extra tables that aren’t supporting the core of your app.
Overall, seems like Softr will support this use case nicely
I’m also working on a platform with a lot of content. Just so you know, we’ve chosen a hybrid approach where Softr’s native database handles most of the work, except for storing files.
So far, it seems to be going well, but having years of database and development experience is definitely a plus. AI tools really help speed things up a lot though!
