Best practice for deploying apps for clients

Hi @AjBruce.

At this time we have a small number of paying customers (each of which has one or two apps, often one for their clients and one for them to administer with).

For each customer we allow them a maximum number of clients (which we restrict in the app). We then invoice them once per month to cover our licences (Glide, Integromat, Clicksend and other services that we may require for their solution) and our ongoing support and app maintenance. They can add more clients in chunks of 20 or 50 and this increases their monthly invoice amount.

We will be able to operate like this up to about 20 customers i.e. 20 invoices per month but beyond that we will need something more automated. We are not charging individual subscriptions for any current or planned apps.

Hope this makes sense?

What about the sheet? The ownership of the sheet will remain with the creator right? How do we port user data from the sheet to the new sheet?

Hi, David,

I had developed a Web App in different platform where we had developed below process.

  1. App Developer - Sell Subscription of App using Online Payment to Multiple client. Efforts are worth it for developers without creating multiple set up.
    -1.1 App Developer can set limits of organization under project, data storage, number of users for invited organizations.
  • 1.2 Provision of upgrade is available for project, data storage, number of users for Payee Organization
  1. Payment Confirmation - Clients Organization which is paying for multiple organization gets an invitation link to register the company with required data.
  2. Organization Registered will now be getting an access to Menu & Forms related to Business Process app is meant for.
  3. Payee Organization can add projects and invite multiple registered organization to Project to collaborate. Each organization is created in fashion of Grouping a Database under Organization Name with Project Code
  4. Each invited Organization will have standard access based on the role defined.
  5. Project Owner Payee organization can allow or revoke access of invited organizations.
  6. Here all transactions are filtered based global or non global data type which is dynamic in nature.
  7. Unless data hasn’t been shared with other organization user its non global and vice versa.
  8. Project users can view directory of user directory, documents, communication, logs, reports based on the organization ownership.
  9. There is strict silos to control any non global data access by different organizations.

I would like to know from you , can we develop above using glide from google sheet or glide table.