Custom outer payloads

If you have implemented a Custom application using the Herald protocol then you may wish to completely change what data is passed between devices.

The Herald Envelope Payload is an example of such a payload.

Your outer payload may be an envelope payload with multiple wrapped payloads, or a full payload custom to your application.

How to implement an Outer payload

This is simply a case of plugging in your own Payload provide directly to the Herald Protocol. You can still use the Herald Protocol even for a completely new payload. Callbacks are provided to customise its behaviour. See the integration guide for details.

Wrapping an inner protocol

You can either provide just an outer payload or perform a similar outer header approach that we adopt. See the Herald Envelope Header page for more details on that approach.

Interoperability

Because your payload is completely custom, do not forget to use your own Service and Characteristic UUIDs for the Herald Protocol. This is described on the Custom Protocol page.

Doing this will stop your app interfering with others’ apps, and prevent those apps from interfering with yours.

Share your work!

We will happily list and mention your payload, whether commercial or open source, on this site. Please provide high level details of your payload and a website link for further details via a GitHub Issues request.