Calligra/Usability and UX/Common/Startup/Startup view integrated with the File menu

Started by Jstaniek 20:41, 14 January 2011 (UTC)

Known Issues

• UX of the KOffice 2.3 (and Calligra 2.4 alpha) Startup view is low
  • Misplaced thumbnails (e.g. in Words)
  • oldish icons used as template previews (e.g. in Words)

• Usability of the Startup view is better but there's a lot to improve too

Questions

These may or may not be issues, depending who you ask. Let's decide on these.

Q0: Shouldn't we agree that the main UX these days is web browser?

(asked by jstaniek)

• If so, adjusting some of our UI elements may help to improve UX (the apps will have more modern feel) and Usability (users will discover functionality easier)
• Quick check list: remove modal dialogs if not really necessary. This is laborious task of course can be rewarding.
• Mockups on this page use these ideas.

Q1: "Always use this template" has problems

(asked by jstaniek)

• Once it's set on, the startup view disappears on another startup. Then user has to find completely different place to switch the

Q2: The meaning of the File Menu versus the startup screen

(asked by jstaniek)

• Are the two objects really different? They share a number of elements

Q3: The list of recent documents is now linear. How about adding grouping?

(asked by jstaniek)

• by places (directories/urls)
• by access date
• (enter your idea)
• Example: MSO 2010 has some groupping by folder [1]

Q4: We have deep search feature in KDE already. Use it.

(asked by jstaniek) Let's insert search entry in the the Recent Document part of the startup view and focus it by default. How about checking usability of this?

• Rationale: Users may remember only part of the document name.
• Rationale: Users may think they remember the document name but in fact they remember the name _inside_ of the document (e.g. heading or title) while the filename is highly random.
• Rationale: Document names can be misleading. User have troubles naming documents, if the name is created by them, they look like "Document.odt" or "2011.odt"; if the name is created automatically by the app based on the first paragraph or heading, user does not record the name, since the name can be created just befor closing the application, the name created this way can be not representative for the real content of the document.
  • Rationale: Familiarity. Search box is the most used tool to locate information, more than browsing GUIs.
  • Discussion: But KDE has "nepomuk search" text entry elsewhere. It does not break.
  • Idea: display results in real time; sort multiple results by access/modification time.
  • Technical Discussion: What if the strong KDE search feature is not available in given installation? (for whatever reason: because is broken or not installed or disabled intentionally) At least fall back to searching through file names, document properties of the recently accessed documents. Extract this information when accessing the file, check if the file changed (if so, update the cache entry). This all should be cheap for desktop systems.

• • TODO: Mockup

Mockups

(jstaniek)

TODO