Use Case Description
The user launches Liferea. The user clicks the “New Subscription...” button which results in the New Subscription dialogue being displayed. The user manually types in the feed subscription URL (e.g. http://planet.gnome.org/) (or pastes text from the clipboard) and clicks OK. A new feed item appears in the left-hand subscription tree directly below the last selected feed, at the same hierarchical level. Liferea processes the feed and displays the configured default number of unread items in the headline pane. Liferea fetches any applicable favicon icons for the site and replaces the default icon for the feed based on the feed type with the favicon. Liferea changes the name of the subscription from the initial value of “New Subscription” to the name provided by the feed. Liferea displays the headlines in the appropriate pane, as dictated by the current view.
Thoughts and Considerations
- When adding a feed there is no user feedback while updating the feed for the first time. There is some considerable lag time and it is not clear that anything is happening. The status bar indicates it is updating the subscription, but does not provide any moving indicator to let the user know the app has not frozen. Is it possible to somehow inform the user that an initial set of headlines is being downloaded, along with the other info (name, favicon, etc). Just some UI indication that Liferea is working. Ideal might be to have the icon of the feed not appear as a static default feed type but rather a progress indicator such as a spinner (like the browser tabs often have).
- Is it possible that the Advanced feed dialogue be changed into a disclosure triangle? For example I've simply merged the two dialogues into one in the mockup below, and made a few minor changes to spacing and wording. The one key value this affords the user is the ability to switch back to the basic dialogue without restarting the “Add ...” use case. It also reduces application complexity (2 different add subscription dialogues). The mockup below is just a first brush at creating the right unified dialogue. It is meant for discussion. Further refinement/polishing/HIG-ifying is possible if/when the direction is agreed upon.