Deployed in runtime mobile application
Mobile client application
Now, you will follow the true story about mobile and computer integration.
Use below to change slides. You can hover higlighted words to see, what is it about. Try it now, and start the story!
Each application starts with writing and game application. When computer connects cell phone, this is transfered to cell phone and started - it becomes Deployed Mobile Application.
To communicate with cell phone functionality (like accelerometer), and to be able to pass messages to host game application, deployed mobile applications uses PAD Library.
To help You transfer cell phone, there is a library for computer program - GAME library. You should give it a PIN to find launched on cell phone client application. After this - you can send and receive data to and from cell phone.
GAME library takes care of transferring onto cell phone.
In order to get the PIN of mobile client application, your game should prompt user about it. This should be a nice GUI interface. To make it possible to reuse and share this kind of interface - there are PIN-reader libraries.
Handling comunication with remote application using L ByteArray is not an easy job. That is why, this kind of functionality is hidden inside .
It is not that easy to understand all the details of Computer and Cell Phone communication from scratch.
To make it easy to start - there are some , which take care of all the core aspects of connecting, launching remote application and managing communication.
While working with these samples, you will wonder on how to change some aspects of game process. This is the place where you will start playing with bricks introduced here!
In the end - Mobile Client Application is not mandatory piece of software. You can reimplement it, put custom graphics and permit only special applications. This will allow you to interconnect multiple devices together under your own rules!