Applivery provides a very powerful way to distribute Apps using Public or Private App Stores that support multiple security and branding configurations. Additionally, we also provide the possibility of having different configurations for each individual App and each individual User.
Below we will go through the different options provided by the platform. Please read it carefully since they represent most important concepts in Applivery.
Applivery supports both Public and Private App Stores.
Public App Stores:
- Your App Store is totally public and available under your URL: (yourname.applivery.com or your Custom Domain).
- Anyone knowing the URL of the App will have access to the list of Published Apps, as long as they are not unlisted or inactive.
- Your App Store and it’s content might be indexed by search engines like Google or Bing.
Private App Stores:
- Your App Store is not available to the general public. Users will be asked to enter their credentials to access the list of Apps.
- Users can login using their Applivery Account and/or the Single Sign On of your organization (if available)
- Private App Stores homepage might be indexed by search engines like Google or Bing
In both cases, users will be able to Add the App Store to their Home Screen to have a more direct and easy access to your Organization Apps.
For each App (project) you have in Applivery you will be able to have one or more Published Apps that will help you organize how your Apps are available within your project Collaborators and Employees through the App Store. There are three important concepts to properly configure them:
Depending on the type of distribution you select a subset of builds will be provided to the users through that distribution, always ordered in descending order by date of upload and for both iOS and Android operating systems, when available. You can choose from the following options:
- Builds: distributes an specific iOS and Android build from the list of builds. It does not support the enabling the history of builds.
- Tags: Use the custom tags of your build to distribute any App that matches a tag or set of tags.
- Git Tag and Git Branch: deploy any build that matches the provided git branch (i.e.:
develop) or Git Tag (i.e.:
- Last: Deploy the very last builds you have uploaded for each operative system
- Inactive: App is not accessible to anyone in the App Store.
- Active: App is visible to everyone in the App Store.
- Unlisted: App is not visible in the App Store but is accessible to anyone knowing the URL.
- Public: no authentication or login is required to access the App details and installation.
- Private: authentication and login (either Applivery login or Custom Single Sign On) will be required to access the App details and installation.
- Password protected: a password (defined by you) will be required to access App details and installation.
Now let’s deep dive on the different options mentioned above.
Restricting access to certain User Groups
When configuring Logged Published Apps (either using Applivery Login or Single Sign On) you can also specify which user groups will have access to the App itself. To do so, add the list of user groups below the Security Selector and then click Save.