There is a number of integration options depending on the development time.
#1. White-label web client hosted by VXG
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:
All you need is to send us your logo, colors, and other changes that you want us to make on your copy of the web front-end and we’ll create it for you within hours.
#2. White-label web client hosted by Customer
VXG will send you a complete Web client source code that is a package with HTML, JS, and CSS files.
You can just copy it on your web server and you’ll have your Web client up and running on your server, under your domain name, and with full source code that you can change according to your product needs.
See more information on how to deploy the web client package here.
Mobile applications will be also 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.
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 the 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.
#3. 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:
Another approach will be to use the VXG Web SDK and integrate the web player with your existing UI. The Web SDK comes with a number of samples that take the channel’s “access token” as input.
The Web SDK can be used for integration with an existing UI or for building a new UI:
For integration with mobile applications, VXG provides Mobile SDK for Android and Mobile SDK for iOS. In all the cases, the SDKs will need to know the channel’s “access token” to access live and recorded videos and other resources and information associated with the channel.
#4. 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.
VXG has published a number of HTML and Python samples showing how to call VXG REST API functions on GitHub.
More information about integration with an existing front and back-end can be found here.