• Linked Applications


Specific Instructions Per Client

What is Branding?

Branding Vibe is a means to give Vibe and its supporting services the look and feel of your organization. The goal of branding is to allow the Managed Service Provider or Enterprise Partner the ability to present Vibe as their own product to their own customers.

Branding is a bit of an involved process that may require input from various parts of your organization including graphics, marketing, and technical representatives.

 This work involves changing the look and feel of:

Desktop computer Vibe clients (Windows, Mac and Linux)

Desktop computer Vibe player (Windows, Mac and Linux)

Android devices (Phones and Tablets)

iOS devices (iPhones and iPads)

WebRTC Pages

The Auto Attendant for dial-in users

The graphic displayed in Video Conference when no participants have video cameras enabled

The Web Portal that users go to when they create meetings

eMails and Notifications sent to users

Links for support in the Application


Branding is very involved work. This effort can take 1 to 2 months depending on how quickly each task is completed.

Customer Work

The customer should review this wiki section, evaluate the branding files and ask any questions before starting.

Next up, the customer should design the look and feel required in each client. This is up to the customer and this will happen according to your designer timetable.

The customer would then create and supply all branding files. This can be done by the customer or the customer's designer.

eZuce Initial Development Work

eZuce needs to schedule this work with the development team. This usually takes one to two weeks to slot the work into the development cycle.

The branding process then takes approximately two weeks for our staff to create and test the clients.

Customer Testing and Acceptance

This should take no longer than 1 week for the customer to complete. The customer should return any and all changes they require to eZuce.

eZuce Final Build

eZuce will create final builds for all clients with the required changes from the customer.

Publishing to Mobile Stores

This can take 1 to 2 weeks. We're a bit at the mercy of Apple and Google here. Google is generally faster to approve.

Other Clients for Download

This will take 1 to 2 days to complete by the customer.

Server Configuration

Any server configuration work by eZuce will take 1 to 2 days to schedule and can be completed within one day.

Any server configuration work required by the customer (modifying the WebRTC services, establishing PSTN connectivity with an ITSP, installing base operating systems on servers) is up to the customer's timetables


The organization will want to work with their designer to pick a look and feel for their application logo and color choices.

What is included in the branding process is changing the logos and particular textual information that the user can see. We've attempted to keep branding simple to minimize the effort involved for all. Certain elements such as icons for menus do not change as part of the branding process.

Supplying Artifacts

The customer is responsible for providing specific text and graphical elements in specific sizes to be used in the application (See the Supplying Artifacts following below on this page). Examples are included in the ZIP file to help speed along the process. The size and graphics file formats are important to maintain.


Once the new client is built, it is up to the customer to test all aspects of the program to ensure it looks and performs as the customer would like.

Once the application is accepted, further requested changes for customization or changes outside the scope of branding will be worked through your account representative. The goal of testing is to fully evaluate that the client application performs and looks as the customer would like. Back and forth small changes between development and the customer are timely for all parties involved. By allowing for a single iteration its hoped that the client applications will be fully reviewed and commented on and thus modified a single time.


eZuce can assist in making your application available in your iTunes and Android stores as well as enabling the Desktop and Player clients for download.

For the iTunes and Android stores, eZuce will be the publisher and it will be listed as the customer's application. To attempt to do otherwise is a complex and time-consuming process that most do not understand. If this becomes easier in the future or a customer has the expertise and can take this on themselves, we're open to working with the customer.

For the download of other clients and updates, the customer has the option to have eZuce host these files or the customer to host these files. See Branding Vibe Desktop Client#Distribution

Branding the User Portal

The User Portal can also be branded. Users come to this site to modify, create and delete meetings. Changes here are limited to certain graphics and colors. Larger changes are not possible as all customers using the portal would be affected. It is possible for customers to build their own portal and reference our APIs to modify meetings. Assisting with this sort of effort, however, is not included in the typical branding exercise.

Information for this is found in the Branding Vibe Portal section.


During the design, the customer’s graphic designer will want to work within the constraints of each device.  We provide specific branding guides for each client.  The client should review each guide and design within the limits of the clients.

Figure 1. Android screenshot example - eZuce Vibe logo in upper right would be replaced for a branded client.

Figure 2. Desktop application start page example - eZuce Vibe logo and colors on this page would be replaced for a branded client.

Supplying Artifacts (Download Branding Files Here)

The artifacts are all of the specific files as required by our developers. The effort involved in eZuce manipulating of your graphics files is not included in the cost of branding services. The customer must supply the files exactly as we have requested them.  There are specific file directories, names, sizes and file types required for branding.

The Branding Resource List (included with the BrandingResourceList.xlsx.zip) has tabs for common information as well as each client (Desktop, iOS, Android and WebRTC).

To go along with the Branding Resource List we will provide ZIP files with all of the stock images in their appropriate directories. The customer is responsible for editing any graphics they’d like to modify, playing close attention to not modifying the physical image size or format of the file.

Download zip file here: BrandingResourceList.xlsx.zip

Download WebRTC2 files here: ezuceWebRTC2.0.1.zip


During testing, the customer should test all variations of clients with their supplied graphics to ensure that they are satisfied with the look and feel of the application.

We recommend testing the following:

Windows 7, 8 and 10 Desktop Client

Mac OS/X 10.6 and later Desktop Client

Fedora 21 Desktop Client


Windows 7, 8 and 10 Desktop Player


Mac OS/X 10.6 and later Desktop Player


Fedora 21 Desktop Player


iPhone 5 or better Client

iPad 2 or better Client


Phone running KitKat or better (Samsung Galaxy 5 for example)

Tablet running KitKat or better (Samsung Galaxy Tab for example)

WebRTC Client

Test on all WebRTC compatible browsers required by your customers.

At the time of this writing, Chrome, Firefox, Safari, Edge are all supported browsers

H.323 or SIP Endpoints

Verify 'spash' screens are as you'd like.

Once a client is accepted as final, additional changes will not be accepted unless a bug is found or a future application change forces changes. The goal here is to test thoroughly and minimize the back and forth with the development team. Thorough testing by the customer will minimize time and hassle for all parties involved.

Availability of Mobile Client

The mobile platform stores require some specific graphics and text information.  The customer will also need to provide information required by the mobile platform's respective stores. Some of this you will not be able to provide to eZuce until after testing is completed so that you can get proper screenshots of your applications on those devices.

This process can be confusing for people who haven’t been through it before.  To aid in getting your app into the stores we’ll require specific graphics and textual information. Please see the respective mobile client wiki pages for this information. 

  • No labels