Developing iDigi applications for Android involves additional elements other than the applications themselves. The following sections introduce several iDigi related concepts required to develop iDigi applications.

The Device ID is used by iDigi to identify client devices. A Device ID is a 16-octet number that is unique to a device and does not change over its lifetime.

The canonical method for writing Device IDs is as four groups of eight hexadecimal digits separated by a dash. An example of a Device ID is:

Data Storage is a service that allows a client to upload data to the iDigi server, where it can later be retrieved from the server by iDigi users. There are no restrictions on the type or format of the data, but XML is recommended. It is also recommended to keep file sizes as small as possible.

This data service is commonly used to acquire period readings, combine them together, then push them up in the form of an XML file.

The Data Storage service can be thought of as a hierarchical file system. Each device has a directory off of the root directory in the storage server, with a name that corresponds to the canonical form of the Device ID. Each device directory may contain subdirectories and files.

The do commands are used to command the remote devices to perform any action. Using client applications, users can send do_command requests to their connected iDigi devices.

A do_command has an ID to identify the type of command (also known as "target") and data. An iDigi Android project exposes an easy way to listen for do_commands with a speficic target (ID) and retrieve the corresponding data of the command.