You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zimbra's contacts UI (the backend also uses CardDAV) is more graceful, more informative, and more space efficient than Nexcloud Contacts. We could learn from there. And surpass!
References to specific bugs will be added (or bugs created).
See screenshots for a sample contact created in both systems.
The noticeable differences:
Address layout:#309 Zimbra changes layout according to Country of UI, Nextcloud doesn't Address layout:#309 Nextcloud includes a clunky POBox field, Zimbra doesn't. Most Users in most countries barely use (and Users can enter POBox manually). Custom fields:#303 Nextcloud does not allow their creation yet, Zimbra does. Default fields:#304
Zimbra automatically displays the commonly-used Notes, Birthday and Website fields, Nextcloud doesn't. Allowing custom layouts would massively help workflow. Missing fields:#302
Zimbra includes 'Department', Nextcloud doesn't Choice of display name: Zimbra allows User to override default display name per contact, in this example, the User wants to see the contact's personal and organisation name for ease. Nextcloud doesn't permit this at all! Name mess:#307 Nextcloud is a big mess once you select detailed name, and nickname. It shows them in three different places, and is unintuitive (which overrides which? the User is thinking). Zimbra displays all the name details gracefully in once place. By default it only shows First and Last and Organisation name (just like Nextcloud) but lets you add 'More', adding Prefix, Suffix, Nickname, Department, Title, Middle names etc.. But all in the same place. No confusion, and taking far less space up, and letting the User focus on the contacts other details. Edit and view mode: Zimbra looks much better than Nextcloud, when a viewer is simply browsing rather than editing contacts (that's the main use of an address book after all). And it also prevents accidental changes. Missing headers:#305
Unlike Zimbra, Nextcloud is missing headers for groups of fields - when looking at a contact in Nextcloud, there is nothing saying what is a phone number, email address, address etc... Yes, it can be worked out from the field entry, but that is more looking and more unnecessary work for a tired and busy User. The lack of headers also prevents easy-scanning of details and make the contact look messy.
The text was updated successfully, but these errors were encountered:
These screenshots show the massive difference in appearance and ease of usability between Nextcloud (top) and Zimbra (middle - edit mode, and bottom - standard [view] mode).
spoorun
changed the title
Contacts UI improvements vs Zimbra
Contacts UI vs Zimbra
Aug 28, 2017
While it is something to improve, let’s please not use Zimbra’s messy interface as any kind of benchmark. Google Contacts or Apple Contacts is way more widely used, and far better designed.
Zimbra's contacts UI (the backend also uses CardDAV) is more graceful, more informative, and more space efficient than Nexcloud Contacts. We could learn from there. And surpass!
References to specific bugs will be added (or bugs created).
See screenshots for a sample contact created in both systems.
The noticeable differences:
Address layout: #309 Zimbra changes layout according to Country of UI, Nextcloud doesn't
Address layout: #309 Nextcloud includes a clunky POBox field, Zimbra doesn't. Most Users in most countries barely use (and Users can enter POBox manually).
Custom fields: #303 Nextcloud does not allow their creation yet, Zimbra does.
Default fields: #304
Zimbra automatically displays the commonly-used Notes, Birthday and Website fields, Nextcloud doesn't. Allowing custom layouts would massively help workflow.
Missing fields: #302
Zimbra includes 'Department', Nextcloud doesn't
Choice of display name: Zimbra allows User to override default display name per contact, in this example, the User wants to see the contact's personal and organisation name for ease. Nextcloud doesn't permit this at all!
Name mess: #307 Nextcloud is a big mess once you select detailed name, and nickname. It shows them in three different places, and is unintuitive (which overrides which? the User is thinking). Zimbra displays all the name details gracefully in once place. By default it only shows First and Last and Organisation name (just like Nextcloud) but lets you add 'More', adding Prefix, Suffix, Nickname, Department, Title, Middle names etc.. But all in the same place. No confusion, and taking far less space up, and letting the User focus on the contacts other details.
Edit and view mode: Zimbra looks much better than Nextcloud, when a viewer is simply browsing rather than editing contacts (that's the main use of an address book after all). And it also prevents accidental changes.
Missing headers: #305
Unlike Zimbra, Nextcloud is missing headers for groups of fields - when looking at a contact in Nextcloud, there is nothing saying what is a phone number, email address, address etc... Yes, it can be worked out from the field entry, but that is more looking and more unnecessary work for a tired and busy User. The lack of headers also prevents easy-scanning of details and make the contact look messy.
The text was updated successfully, but these errors were encountered: