The development of the Swift XMPP client is something we’ve been tracking internally at Isode for some time. There are a number of reasons for our interest:

  1. It supports XEP-0258 (Security Labels in XMPP), SCRAM Authentication and stream compression for bandwidth savings, all items of interest to one of the major target markets for the M-Link XMPP server. We’ve been using pre-beta Swift screenshots in whitepapers and product pages demonstrating security labelling for some time.
  2. It’s designed with the end-user in mind, a client that “just works” (as Apple would say) without complex configuration.
  3. The developers have concentrated on producing an excellent XMPP client and aren’t allowing themselves to be sidetracked into multi-protocol support.
  4. It has a good, clean look and feel which helps the users concentrate on the important tasks (communications & presence information) without distraction.
  5. It’s free and, given that the developers are well known in the XMPP community & have a track record of involvement in good client projects (Psi), likely to successful.

I should also mention that one of the developers, Kevin Smith, works full-time for Isode in our XMPP team as well as working on the Swift XMPP client in the spare time he has left after chairing the Council of the XMPP Standards Foundation. We’re not sure that he has a life outside of XMPP.

More information on the Swift beta, together with links to binaries (Windows and Mac) and source code can be found at the Swift Blog.

Swift MUC Room

Swift MUC Room