Native peer-to-peer is the built-in ability of the ArcGIS Mission Responder app to use an available local-area-network, such as wifi or cellular, to maintain contact between devices when a connection to the ArcGIS Mission Server is unavailable. This allows Responder users to maintain communication and awareness of each other, as well as performing mission actions, in the event that they move into an area where a connection to Server is unavailable.
This peer-to-peer capability is supported by a variety of caching and forwarding operations, allowing data to be stored locally on the device and then sent to the Server when the device reconnects.
While disconnect from the Server, Responder users also lose their connection to any Manager users. Because of this, certain features and functionalities are limited and it should be assumed that any features that involve direct communication with Manager users (such as Tasks) will not be received until after reconnect. A comprehensive list of these limitations can be found in the table below.
Peer-to-peer Limitations
| Feature | Limitations |
|---|---|
Mission List | New Missions will not appear in the mission list until users reconnect. |
Downloadable Map Areas | Map areas must be downloaded prior to entering peer-to-peer mode. |
Mission Details | Changes to Mission details will not update while a user is in peer-to-peer mode. |
Teams and Members | Changes to teams and members will not update while a user is in peer-to-peer mode. |
Additional Materials | Additional Materials must be downloaded prior to entering peer-to-peer mode. New additional materials will not be visible until reconnect. |
Mission Map | Upon transition to peer-to-peer mode, the connected map will be cached at the visible extent and remain usable with limited functionality. Changes made to the mission map will not be visible until reconnect. |
Geomessage tool | Geomessage attachments are not sent while in peer-to-peer mode. They are visible in the feed as a placeholder, but will not be available for download until reconnect. |
Tasks | New tasks will not be visible until reconnect, and updates made to tasks will only be stored locally until reconnect. |
Reports | New reports submitted by users will be stored locally and not sent to anyone (and therefore not visible to anyone except the sender) until after reconnect. |
Basemap | Only basemaps which are part of a downloaded map area, or a cached area of the connected map, will be accessible in peer-to-peer mode. |
Layers | Layers that are part of a downloaded map area or cached map area will remain visible, but will have limited interactions. |