When should a product use "subdomains" for each customer?
So, lets take a page builder as an example, a user creates his page in there but it's under "username.builder.com", and this is what the user is going to send his contact to see his content.
Now... what if the builder is for a very specific niche? like a builder for artists, like dribbble, or behance, the user can share his dribbble or behance as portfolios, but those are not in a subdomain.
So my question is, when do you think is better to use a subdomain approach rather than an "account" on a product?
Usually subdomains are used for multi-tenant support - like your client has number of users. You can do without it (in a convoluted and hard way) but this is an architecture choice.
For single user where there are no isolation required (auth, data, infrastructure etc.), the usual practices are like "builder.com/username".
Hope this helps.
I would say almost never.
One exception: if you allow them to have a custom domain.
In B2B case if there is an expectation of setting custom domains from the customers, custom subdomains could also be worth having.
In B2C, I think it gives more personality, which could be nice.
I had the idea of creating a hosted reverse proxy to help makers easily implement custom domains and subdomains for when they use static ipless modern tools to deploy their projects.
But I ended up not convincing myself to this idea because I did not think the cost was worth the benefit.