Approach for accessing third-party content collaboration services on interactive whiteboard appliances by an application using a wrapper application program interface

One or more non-transitory computer-readable media storing instructions which, when processed by one or more processors, cause:

• an annotation application executing on an interactive whiteboard (IWB) appliance to allow a user of the IWB appliance to annotate electronic content displayed on the user interface of the IWB appliance;
• and
• a collaboration application executing on the IWB appliance, wherein the collaboration application is configured to access a plurality of third-party collaboration services via a management service that is separate from both the collaboration application and the plurality of third-party collaboration services;
• wherein each third-party collaboration service, from the plurality of third-party collaboration services, and the management service supports a different Application Program Interface (API);
• the collaboration application supports the API of the management service, but not the API of each third-party collaboration service from the plurality of third-party collaboration services;
• and
• wherein the collaboration application is configured to access a particular collaboration function on a particular third-party collaboration service, from the plurality of collaboration services, by generating and transmitting, to the management service, a request to access the particular collaboration function that satisfies requirements of the API of the management service, but not requirements of the API of the particular third-party collaboration service.

A computer-implemented method comprising:

• allowing, by an annotation application executing on an interactive whiteboard (IWB) appliance, a user of the IWB appliance to annotate electronic content displayed on the user interface of the IWB appliance;
• and
• accessing, by a collaboration application executing on the IWB appliance, a plurality of third-party collaboration services via a management service that is separate from both the collaboration application and the plurality of third-party collaboration services;
• wherein each third-party collaboration service, from the plurality of third-party collaboration services, and the management service supports a different Application Program Interface (API);
• the collaboration application supports the API of the management service, but not the API of each third-party collaboration service from the plurality of third-party collaboration services;
• and
• wherein the collaboration application is configured to access a particular collaboration function on a particular third-party collaboration service, from the plurality of collaboration services, by generating and transmitting, to the management service, a request to access the particular collaboration function that satisfies requirements of the API of the management service, but not requirements of the API of the particular third-party collaboration service.