At this stage, enterprise is very custom to each case, so yeah, ptentially
because I can’t offer a full white-label tool. With one app, domain is still my company.com and sent email are sent with my company name & logo.
If ddb can’t be shared, I don’t see how I could maintain several apps without being able to easily update child apps’ ddb.
I need to maintain different states (most important!) of Things with different properties, text categories, background picture for theme, presentation pictures, list of quality labels, price tables, automatic messages.
All these are just text, numbers and pictures. I mean they are not linked to any other Type of Things. So if kind of Master Tables would exist, there would not have any dependency issue. Any Thing from a child app could have a Field referring to one of this Master Table.
If bubble allows subdomains you would be able to do this (i.e. client1.company.com; client2.company.com). You could setup your price tables etc to take the sub domain into account. For instance you could have prices segregated by domain. client1.company.com $5
client2.comapny.com $10
etc…
the only thing i think it would be great to add is if you could add styles at the subdomain level then you could have global styles based on subdomain. If you had master tables that don’t need sharing, just don’t include the subdomain as a field of reference
Thanks, but segregating, for instance prices, according to a child app is not the issue I tried to point out.
Let’s take one exemple. I’ve got Orders (with products, quantity, etc). Each Order is in a table “State” (pending, approved, canceled, waiting for payment, etc…). Properties of these States will change ove time.
So if I want to make a change to this State table, I wish I would not have to go in each app dashboard, loggin in and manually update the States. The more child app there are, less maintainable it would be.
You’d only have 1 application that has the ability to respond to different subdomains. So the bubble configuration tab would allow you to add multiple sub domains that it responds to. There’s only 1 database and the tables within that database use sub domain to filter. So there are no “child apps” just a single app that can respond to multiple domain requests. Your Orders table would have a field for sub domain that would get set based on the base domain/url. So you could have multiple orders in one table from different clients. When a client accesses your app from client1.company.com you only show orders for that client. So let’s say your primary domain is www.nicolasdap.com and you had IBM as a client the sub domain would be ibm.nicolasdap.com. In your orders table you would have your orders segregated by ibm.nicolasdap.com and if IBM accessed your site via ibm.nicolasdap.com they would only see their data
Ok i think I get what you mean.
It’s actually pretty close to what I have right now. My ddb is not split according to subdomain but it’s like I’ve got www.nicolasdap.com/client1-123456789x123456789/ www.nicolasdap.com/client2-123456789x123456789/
But in the case you describe, you could not personalize email sender name, logo, favicon or even define a custom domain which is the greatest value I’d see in this feature, right ?
Correct. I’m not sure how Emanuel will do it but if bubble could respond to multiple sub domains it would work. It would also be great if you could define a master style sheet and a logo for each subdomain so that you don’t have to have the branding logic scattered throughout the app. In regards to the custom domain, I think most clients would be ok with their name being at the front of your domain (i.e. ibm.nicolasdap.com). I work for a large company and we use many saas services and it’s always the prefix of the domain that gets branded as the company. Anyway, wouldn’t you want the brand recognition so that people could advertise your product? Any emails sent would come from admin@nicolasdap.com. There’s no reason for it to seem as if it came directly from ibm. Most companies won’t like that as it could pose a security risk.
So we actually just deployed an initial version that lets you do what I was describing earlier:
- have a main app
- create some copies of it that are sub apps. Entirely different apps, with different db, domain names, favicon, plugin keys, etc.
- push from the main app to the sub apps. Everything gets overwritten, except the db, the keys, etc.
At this stage we put that on the production plan. As it’s new though I’d be happy to have one or two users to try this and see how that goes. Reach out if you have a good use case.
Hey @emmanuel Thanks for adding this, is there is a way to test this feature out before committing to the production plan?
in the forum_app2 ?
Yes, reach out to us by email.
Just did.
Thanks, it will be good
I would be interested in testing this out as well. If it works for my use case, I’d be interested in upgrading my plan now. I will reach out by email.
Very curious to see how the “sub-apps” have been working for people…
Databases separate?
Push Parent update to child apps working well, or any undesired results?
- is there a way or need to push the update to only a select number of child apps at once? (to keep any errors causing problems at a minimum)
I have a SaaS product (MVP for the Lean Startup fans) almost ready to test with a single customer, but would be good to know how/if I could expand and accommodate more customers, and that the economics of it make sense
for the Production monthly plan, do sub-apps count towards the max number of applications of 15? so if i have one parent app, i can have up to 14 sub-apps? and if i need more sub-apps over that number i need to look into an enterprise plan?
just trying to figure out the economics of a SaaS app built in Bubble.
thanks!
Yes, they count toward the number of apps. If you have a use case for which it’s an issue let us know, but in general yes.
Hi @emmanuel, are there any planned updates to the main/sub-app feature to support deploying the sub-apps to subdomains? I’m developing an enterprise SaaS tool and would like to give each enterprise customer a clean instance of a sub-app on a separate subdomain. I saw this same use case mentioned earlier by @donaldlh. For example, enterprise customer 1 gets a sub-app w/ clean database on customer1.mydomain.com, same with customer2.mydomain.com, etc… Thinking about supporting this or not? I’d be happy to pay more per sub-app deployed. The use case I have for Bubble depends on this feature. Thanks!
You can already do this, as each sub app is on a different domain, and for bubble two different sub domains are two different domains. You’ll be able to modify the master app and push changes to the children once in a while.
Just now realized what was the Sub APPS in Professional Plan, that’s great to know.