183
edits
Neustradamus (talk | contribs) m |
m (Make some language gender neutral) |
||
Line 9: | Line 9: | ||
=== Description === | === Description === | ||
XMPP Clients should only ask the user for | XMPP Clients should only ask the user for their JID and password. A proper XMPP setup does not require more information in order for the client to establish a successful connection to the server. There should be a single JID text field in which the user is expected to enter their bare JID. Visual feedback once it was detected that a valid bare JID was entered, e.g. a green check mark or changing the field's background color (from red) to green, is also a good idea. | ||
=== Rationale === | === Rationale === | ||
Splitting the JID into multiple input fields makes it impossible for the user to simply copy&paste | Splitting the JID into multiple input fields makes it impossible for the user to simply copy&paste their JID into the field. Asking the user for more then their bare JID and password increases the UI elements and reduces the usability. | ||
== Provide an advanced option allowing the user to specify the host and port to connect to == | == Provide an advanced option allowing the user to specify the host and port to connect to == | ||
Line 65: | Line 65: | ||
=== Description === | === Description === | ||
Users want to know the type of a remote resource, e.g. "Is this the resource of my friends mobile device or of | Users want to know the type of a remote resource, e.g. "Is this the resource of my friends mobile device or of their desktop?". Clients should display the type using the 'identity' information provided by [http://xmpp.org/extensions/xep-0030.html#info-basic XEP-30 disco#info] query results. Also they should set a meaningful XEP-30 'identity'. So instead of having a resource like '/work-pc', the client should return | ||
<pre name='xml'> | <pre name='xml'> |
edits