I have an app that other companies want. Is it possible for me to make multiple copies of the same application - and have it controlled by 1 master template, so any updates I do in the master app will flow through to the individual apps?
I was thinking of having the following scenario:
have multiple versions of the same app in 1 billing account. each app for a company. Then Create user groups for each company that uses the app - The group (company) will then have access to their own version of the app.
I dont know if there is some best practice documentation on this type of stuff. The idea is simple; i have an app that I want to monetize - what is the best way of doing it under 1 umbrella billing company.
Question
multiple copies of same app
You may want to consider uploading it to the application library ( QuickBase Exchange ) and providing the name of the app and link of the Exchange to interested associates.
+12If you are going to be managing the Apps; I would recommend building your app so that all your users can be in the same app; but they only see their own records.
You cannot make updates in one app and have them "flow through" to another app; so maintaining multiple "duplicate" applications will be arduous and time consuming.
Since you will be paying for the subscription; my recommendation here would be to create 1 app, and setup Users associated to Companies and permission those users for only records associated to that Company. This is a very common usage case for QuickBase.
You cannot make updates in one app and have them "flow through" to another app; so maintaining multiple "duplicate" applications will be arduous and time consuming.
Since you will be paying for the subscription; my recommendation here would be to create 1 app, and setup Users associated to Companies and permission those users for only records associated to that Company. This is a very common usage case for QuickBase.
Be careful with "sub-leasing" your account? QuickBase doesn't like that, and its technically a breach of the terms and conditions. They could suspend or delete your account without notice if you farm out your account to others. (This has happened to some accounts I know of)
If they truly are different companies, you can sell them the app outright for whatever fee you set, but they should have their own account. They can then hire you to maintain it, or farm that work out to some developing company.
If they truly are different companies, you can sell them the app outright for whatever fee you set, but they should have their own account. They can then hire you to maintain it, or farm that work out to some developing company.
What if they are clients that are using my "software" that I have developed? Surely I can charge someone to use something that I have developed?
You can charge for the software (your app) but you cannot charge for access to the service (QuickBase User Account)
http://www.quickbase.com/terms-of-service
http://www.quickbase.com/acceptable-use-policy
"""
5.3 Restrictions.
http://www.quickbase.com/terms-of-service
http://www.quickbase.com/acceptable-use-policy
"""
5.3 Restrictions.
You agree not to copy, sell, rent or sublicense (including offering the Service to third parties on an applications service provider or time-sharing basis), lease, loan, redistribute, or create a derivative work of any portion of the Service (except solely to the extent necessary for you to create applications permitted under Section 7 (�Application Development and Distribution via QuickBase Exchange�) of these Terms of Service), use of the Service, or access to the Service. Such restrictions do not apply to the Content you place on the Service. You agree not to access the Service by any means other than through the interface that is provided by QuickBase for use in accessing the Service.
""""
Trust me, I wish with all my heart I could do this. But they have to protect themselves, and their income stream somehow.
I dont understand this logic. They will be getting more income with me loading more users onto the platform, since its a pay per user principle not so? All i am doing is charging users to access the app that i created in order for me to cover costs and make some margin.
Correct me if I am wrong, but what you are suggesting is that the quickbase platform is soley for the use of customers in their "specific busines" use case.
My business is to have hundreds of Paid users access the app. I hope quickbase reads this because for what it is worth, i have no intention of breaking the rules, I just think there is something missing from my understanding of what you are saying. Another point is; how will any one ever know that I am charging a user to access the app?
Correct me if I am wrong, but what you are suggesting is that the quickbase platform is soley for the use of customers in their "specific busines" use case.
My business is to have hundreds of Paid users access the app. I hope quickbase reads this because for what it is worth, i have no intention of breaking the rules, I just think there is something missing from my understanding of what you are saying. Another point is; how will any one ever know that I am charging a user to access the app?
+12This is less applicable in today's QuickBase pricing plans than it used to be. In the current environment, your extra users will be added to your Plan on the next cycle automatically unless you manage them properly. This was not necessarily so historically.
Since you are building, managing and maintaining the Application/Account there is no conflict; since you own it and can control access to it. As long as the fees your clients pay you includes QuickBase and includes your management/maintenance services; then you should be free to charge as you see fit for their access to your system.
Since you are building, managing and maintaining the Application/Account there is no conflict; since you own it and can control access to it. As long as the fees your clients pay you includes QuickBase and includes your management/maintenance services; then you should be free to charge as you see fit for their access to your system.
Geoffrey,
Did this work out for you? What did you end up doing? I am thinking about a similar setup.
Thank you for your help.
Jeff
Did this work out for you? What did you end up doing? I am thinking about a similar setup.
Thank you for your help.
Jeff
+11Hi Jeff and Alex. Since there is some renewed interest in this content, I thought I would clarify a few things:
- Our Enterprise Governance team is currently looking at Application Lifecycle Management (ALM) utilities that could be considered a more robust sandbox. We are also thinking about the notion of master/child template deployments.
- I suggest reaching out to your account executive (connect with Care via support if you need to be routed) regarding pricing as we have a lot of options to facilitate these types of agreements.
Thanks, Harrison. We've done #2 (and our experience so far has been great as we figure out how to negotiate, in partnership, the next few steps we take), I was just curious to see that any conversation on the topic had taken place in public, even if it was a bit dated.
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.