These clients can pair, connect, and send messages:
The desktop clients are ready-to-run executables. They store their local state on the filesystem in the directory where they are launched. You can run multiple copies on one machine, provided you keep those directories distinct.
The above Android/iOS applications needs to be installed on a phone or simulator. If you are a developer for the given platform, you know what to do.
These examples are for embedded boards. We don't provide complete binaries for these development boards, as you have to compile for the actual board you have. Instead we provide example programs similar to the above binaries, but in source code as demo apps. The example app includes a binary version of the communications library for the platform.
Here are the steps to get started using the client libraries.
/email youremail@example.org <Your Name> to register your client for the conference price-draw. This is optional./op to open it for pairings. This should get you an OTP (one time password)./pair <OTP> to pair with the first one./pcr <peerID>. This works in either direction. Both clients should print out "Routing started" and a connection ID (a small integer starting at zero)./send 0 <Message> where "0" is the connection ID you got when you executed /pcr.You may use these examples and demos for evaluation purposes only. Using SecureDeviceGridTM in your product requires a license. Please contact us.