One of the areas where Cheogram Android seeks to forge ahead is to provide high-quality mobile-first UI for services that operate of the Jabber network.
Registration
Many kinds of services require a registration or login flow. These are all covered by XEP-0077 so if you need this feature your service should implement that.
You may find that sometimes your flow needs more than the one-form-one-step model that XEP-0077 supports. In this case it is recommended to also have a XEP-0050 command with node of jabber:iq:register. The response from a XEP-0077 registration attempt by a new user thus becomes only a reply with instructions to use the command instead. Sensible clients can detect this situation and work it to their UI accordingly.
XEP-0077 remains important for use cases where a user checks if they are still registered or removed their registration.
Command Payloads
Most service interaction with a user happens over XEP-0050 and family.
A command MAY contain zero or more <note/> elements and MAY contain other namespaced elements as payload. Elements qualified by the "jabber:x:data" and "jabber:x:oob" namespaces are the typical payload. The order of these elements denote their precedence, so that those elements earlier in the list have higher precedence.
So each step of the flow can be defined by one or more elements, to allow clients with different abilities to render what works for them, for example:
<command xmlns='http://jabber.org/protocol/commands' node='doit' status='excecuting'>
<x xmlns="jabber:x:oob">
<url>scheme:some-uri</url>
<desc>This is what's up here...</desc>
</x>
<note type="info">This is what's up here: scheme:some-uri</note>
</command>Cheogram Android currently supports OOB by always rendering as a webview (with some optional JavaScript hooks injected to allow the page to advance the flow when done, it ). Likely for most other schemes it makes sense to instead render a button to trigger the URI as an intent, which will be done in a future release.
Data Forms
Most command payloads are based on XEP-0004. Cheogram Android implements basics of this XEP though currently lacks a good UI for list-multi editing and improvements are always possible.
The XEP does not ban mixing a single reported table with other result fields, and so we support this, but due to confusion out in the community if this is desirable no sopranica service currently generates this.
One of our pain points in data forms is it's not trivial to have a form that is partly results but also has any submittable fields. type=fixed can be used, but then more specific type information is lost, and some implementations do not support type=fixed with a label (though cheogram Android supports this of course).
XEP-0122 provides a way to give more granular type information about a field. This can be used for client-side validation of submittable fields (and Cheogram Android does this), but can also provide UX hints (for example cheogram Android changes the keyboard in use for html:tel type etc. Even for result or fixed fields this is useful to give type information for use in formatting. For example a date type can be localized, a URI made a clickable link, etc
Extensions
Cheogram Android injects a JavaScript API in the xmpp_xep0050 variable for interaction with the flow from the page.
RSM tags be used to limit the length of a result. Since no other client supports this, if you support in your service the result will be their client getting your default/small size. Cheogram Android sends RSM with a large max when present because it has UI designed to work well with eg long lists.
proposed: not implemented, but we are considering interpreting a field of var http://jabber.org/protocol/commands#actions as augmenting/replacing the buttons generated for command actions, to allow for custom actions like "generate new BTC address"