Swift is trying to plug a hole in the XMPP client landscape, and has these aims:
Wide platform availability.
Doing the "Right Thing" for the user, without configuration.
Doing the "Right Thing" with standards-compliance.
Targeting the end-users, not the system administrators.
Being an XMPP client - not multi-protocol.
Concentrating on the most frequently performed tasks.
Never interrupt the user with something that doesn't need attention.
Use Patent Claims
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.