![]() With an iOS remote desktop tool, teams can deliver services and solutions quickly and efficiently from anywhere with a reliable internet connection, eliminating travel time and streamlining the logistics of providing effective and responsive IT support. When using an iOS device to provide remote support, an iOS remote desktop solution. When connecting to an iOS device, it can allow you view-only access to help streamline troubleshooting. In two words my recent efforts are directed towards architecting connected systems (specifically in mobile area) with focus on cross-platform development methodologies, modern communication paradigms and highly automated workflows.An iOS remote desktop tool allows you to connect to an end user’s mobile iOS device (like iPhone and iPad), or use an iOS device to reach another remote desktop. Refer to resources listed below to get a better sense of my activities and interests. IRemote project was brought to life by Egor Pushkin. IRemote source code is available under MIT license. Simple media streaming server was integrated into Remote PC allowing remotely connected client to browse workstation file system and stream any content supported by native WebView control. iPad application is about 90% complete at this point. IRemote for iOS was transformed into universal application and iPad UI was prototyped around SFB technology. iPad Support in Universal iOS Application Tablet users were supposed to be primary consumers of this technology. The SFB technology was designed to allow streaming the entire screen (rather than just seeing a portion of it) in an efficient way. These are some of iRemote features that were implemented (at least partially) but were not shipped. This should shed light on some UX-level decisions made at that point. In those dark days there were still users asking not to leave 1.5 overboard. IRemote was ported to Android shortly after Honeycomb was released. We could not even dream about ARC and other cool things back then. IOS client was shipped prior to background support was introduced in iOS. Not a lot to say here, but still I want to make a note that now I add underscore ("_") in the beginning of member variables and no longer use Camel notation for method names :) For the most part cleanup was related to removing resources and demos that could not be published due to licensing limitations. The repository was cleaned up when the decision was made to make the source public. You will notice that repository history does not go all the way back to the origins of the project. ![]() dev - Contains mobile and desktop application source and 3rd party dependencies (or references to it). doc - Project related documentation, EULA, manuals and some other materials can be found here. This repository contains most materials related to the project: Common Kit library ( ) powers iRemote object model and networking on iOS and desktop platforms. Mobile apps are native.Īmong other 3rd Party dependencies (full list can be found here REPO/doc/License/LIBS.txt) there is another project of mine, which actually preceded iRemote. It gives good overview of how desktop and mobile applications are organized.ĭesktop application is built in QT ( ). Not much have changed since the moment when this article on iRemote architecture was published. This neat story was timed to the submission of Android build to Google Play: Windows XP / Windows Vista / Windows 7 / Windows 8.Mouse control (mouse movement, mouse clicks, tap-to-click, scrolling).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |