There is a number of integration options depending on the development time.
White-label web client
This is the fastest integration method and it could be as simple as changing the logo and colors in the VXG web client:
For example:
White-label web client and mobile apps
The same as above plus mobile applications will be re-branded. This will require publishing new mobile applications on Google Play and Apple App Store under the customer’s name. VXG will guide you through the process and assist with publishing.
White-label web and mobile clients with your authentication & authorization services
VXG Cloud VMS is detached from authentication and authorization services. VXG web and mobile clients use Google Firebase for authentication and a simple PHP backend code for authorization of users. The easiest way to change the authentication service will be to just change the Google Firebase account to the account managed by a customer. Another approach will be to completely replace the authentication mechanism. VXG will provide the full source code of the authorization backend. It can be hosted on any web server that supports PHP.
Integration with existing front-end
It’s very easy to integrate VXG Cloud VMS with existing UI. You can just publish an iframe on your website by copying and pasting it from the integrator’s dashboard:
The iframe contains a reference to the channel’s “access token”.
Another approach will be to use the VXG Web SDK https://github.com/VideoExpertsGroup/VXG.WebPlayer.SDK and integrate the web player with your existing UI. For integration with mobile applications, VXG provides Mobile SDKs for Android https://github.com/VideoExpertsGroup/VXG.Media.SDK.Android and for iOS https://github.com/VideoExpertsGroup/VXG.Media.SDK.iOS. In all the cases, the SDKs will need to know the channel “access token” to access live and recorded video and other resources and information associated with the channel.
Integration with existing front and back-end
A back-end should know a list of “access tokens” (channels or cameras) that a user should have access to. Usually, this list is stored in the back-end database.
The list of “access tokens” can be created and managed by the back-end using VXG Admin API. For example, when a new camera is created a function POST /channels/ will create a new “access token”.
The back-end will then return a list of “access tokens” to the front-end and the front-end will use the Web or Mobile SDKs for playing video. Or, alternatively, the front-end will use VXG REST API to retrieve all the information associated with the channels, including live and recorded video URLs and play video using other tools.