While just about every developer can find some value in implementing remote access and control software within their application, building that functionality has never been easy. Starting this summer RealVNC intends to make embedding remote access and control software inside an application easier via the release of a VNC developer kit that can be implemented on Windows, Linux, Mac, iOS, Android and HTML5 platforms.
Adam Byrne, vice president of strategic alliances, says that while the company’s remote access and control software has been available for years, the company only recently made it available as a cloud service. Now RealVNC is looking to extend the reach of that cloud service by making it possible to invoke its APIs using an SDK that is currently available to developers that sign up to be part of an early access program.
Byrne says that developers can choose to simply connect to the existing RealVNC service or “white label” it under their own brands. In either scenario, developers no longer have to write their own remote access and control software.
Using sockets, the RealVNC SDK enables developers to establish a peer-to-peer connection with the RealVNC cloud. In addition to being used to connect to, for example, mobile computing devices, it can also be used for new classes of devices that are being connected to the Web as part of the Internet of Things phenomenon. Invariably, developers are going to want to provide a way for customers using their software to be able to access those devices, says Byrne.
What makes the RealVNC approach unique, says Byrne, is that those connections can be established without requiring developers to open holes in corporate firewalls.
In general, SDKs and APIs are transforming how network services are delivered. Instead of having to manually provision network services, developers can increasingly invoke them using a variety of programming tools. Byrne says that rather than relying on traditional telecommunications carriers to provide those services, it’s more cost effective to invoke a cloud service managed by the entities that developed the networking software in the first place. In the case of RealVNC, that means making use of dedicated data center facilities in the U.S. and the United Kingdom that are managed by RealVNC.
Obviously, it will take awhile for SDKs and APIs to fundamentally transform how network services are delivered. But it’s also clear that every major telecommunications carrier and cloud service provider is moving in this direction. In fact, in the not too distant future it may very well be hard to tell one from the other.