**1. Introduction**

Before starting off with the details let us get some terminology of concepts and their usage in terms of computing and processing out of the way with some familiarity. The discussed aspects were altered and customized to provide the final output for the application development.

Firstly, Remote Desktop Connection (RDC) or Remote Desktop Protocol (RDP) is a proprietary protocol which was developed by Microsoft, that provides a user with a Graphical User Interphase (GUI) to connect to another computer over a network connection [1]. In order to create and establish that particular connection, both devices required access with one another, for the user who deploys the RDP client software for the purpose that, while on the other hand the other user must run RDP server software. Microsoft concurrently refers to this official RDP client software as Remote Desktop Connection, formerly "Terminal Services Client" [2]. Added that, the protocol which gets established remains a one-way connection, in other words only one host session but no simultaneous interaction among the associated devices [3–22].

But MONECT came up with the conceptuality and the idea for an application which would have a simultaneous session on both hosts or both of the associated devices [23]. Thus, the idea conceptuality brought a fresh new dimension to the context of the research project, and resulted in the PC Remote application [24, 25]. The approach to the solution was that, a device compatible application which would be connected in a network-associated integration both from the user and the device end. So that, no rendering would take place whether if the user happened to be an IOS or an Android or a Windows Phone user. There had been no limitation towards device compatibility. Various features with integrated functionalities had been developed within the application [26, 27]. On the per of that context, how much calibratable the application would be, varied from user to user as each and every user would have a different set of needs from the privileged application and its utility of tools with features. Also, no need requirement for hardware and assembly for any type of parts or components since the application would take advantage of the onboard integrated peripherals of the smart devices. But users had to install the provided driver for the application in order to run the app which was prebuilt inside the application from both the user end and the device perspective (www.monect. com). To run the app, any user can download the main file from Google Play Store (MONECT PC Remote) [28].

For clarity and max performance along with computation, the link for the individual platform was also provided in the website. The configuration layout of the application was built and developed from the Android Version 4.0 which was termed Ice Cream Sandwich for the reason that, the application would have no compatibility issue with almost 98% of apk platforms. Along with that, if the usable devices were equipped with higher versions which would be much better for the prospective users. The installation process was basically download & install, afterwards, it's an integrated configuration with any basic type of Wi-Fi connectivity to connect and run the application. But bear in mind of the fact that, the user needed to be within the same network for the connection establishment. Within this scope of the chapter, the features and functionalities which were deployed from within the application along with the formulation and advancements to the application which will also be described on a further detailed manner.
