Quote:
Originally Posted by Adult IT
I was actually looking at doing something like that, but i'm overwhelmed TBH and new to the adult industry in general.
Did you look at existing adult SAAS CMS, like StagCMS? How do you plan to do it better given that they are doing exactly what you plan to do, just with a few years head start? Don't want to discourage you just seem like a tough one to compete with. StagCMS even does static file hosting, pretty discouraging to compete with.
|
You should do it, the adult world needs more innovators.
I'm not discouraged at all. Facebook came around after Myspace was well entrenched, ModelMayhem displaced OneModelPlace. Rarely are the early market leaders the ones who dominate the market a decade later.
In terms of what I plan to do differently? I'm building it as a true Cloud based SaaS platform. From what I've seen, the existing solutions just take the individual software and install it on a managed server for you. That's not really Cloud and Cloud is a requirement for SaaS. They are doing managed hosting with the software installed for you so you don't have to do it yourself. That kind of model makes things really expensive when you need 1 server per customer. A true cloud platform means an individual HTTP request could go to any server really and you just add servers as needed to keep things performant.
Also, I'm focusing on ease of use. If the user has to use FTP then forget about it. It's an archaic protocol that nobody uses anymore and is riddled with problems and confusion for non-technical people.
Also, using a modern tech stack (Node.js, React). So it's a Single Page Application from the get go. That makes building easy to use interfaces much easier. Node.js is also extremely performant too so that means much less server costs. Competing against legacy PHP systems is like taking candy from a baby.
There's a lot of nice touches already. For the galleries, you just drag and drop your folder of files to the gallery page in the CMS and it queues them and uploads them. You can see the progress as they upload. When it is done uploading the file gets assigned to a job queue and processed on a separate server so it doesn't slow down real users. It then creates thumbnails for photos. Then uses pub/sub style push notifications over websockets to notify the CMS user the status of the processing. As thumbnails are created on the server they pop up in the user's browser realtime within milliseconds.
It was kind of cool because I was onboarding a model that lives in another state. She created a gallery within 2 minutes of me emailing her a login. And since there were push notifications I saw the gallery photos pop up in my browser at the exact same time she saw them as well. So I knew instantly that she figured it out.