How to Support Future Update in SharePoint App in Single SharePoint OnlineTenant Environment

What does it mean? How does it impact to developer and end users? When we say single talent environment (Dedicated environment), it means.

1. We can have only one App Catalog
2. We can have only one Term Store Service
3. We can have only one Content Hub.

This article will suggest about “how to push future changes in SharePoint hosted App” with consideration that same app can be being used on INT/QA/Prod. In other word what is the best way to support this 3-tier architecture of deployment.

So considering  these factors, you do things as below.

1. You need to add App package in SharePoint “App catalog” through Admin site. Then this app can be available for all site collections to install.
   
   
2. You cannot add Multiple version of same app(or even you just did renaming the app file name and uploaded in App catalog) in one site collection (if they have same product id )
   
   
3. Once you add “App” to SharePoint Site, app will be exists and work on SharePoint site collection until you go and remove it from Site Collections.
   
   
4. Once you upgrade “App” with new version in “App Catalog” , new version will not be reflect in those SharePoint site collection where you have installed previous version unless you go, delete the previous version of app, and then install the new version.

When you understood these above points, you would have already got  fare idea  about how to handle the App upgrades.

Option 1

You can create different Apps file with different Product ID.(just rename the app name and use the different Product ID).

Option 2

If you see handling multiple versions is overhead, then you can use upgrades with same product id and name but make sure that you don’t remove and delete it from Production version until you sure about you want to move it to production.