Cosmo 0.7: User Interface/Interaction Archived Designs

This section has been archived from the 0.7 specification

Updated 5/21/07

Revising the time zone picker to appear in both the dashboard and the calendar views.

• Reduced the 'quick item entry' field. Does it look too crowded that area?
• If there is no time zone information then would it look weird if the quick item entry is so small? Could we have it expand post preview?
• Or we could also review previous header design iterations w/ the time zone picker at the top area. See mock up D for another design iteration of the headers accommodating both time zone and subscription drop down list.

A:

B:

C:

D:

---

Updated 5/12/07

Revising the header area to show when the subscription drop down list and the time zone drop down list appears in the header. See e-mail thread.

• Open issues: When the CC clicks on the bookmarkable URL, the browser launches to the hub, 'ticket view' default on dashboard view. If the shared collection has time zone information, then an alert bar will appear. If the user decides to turn on time zone information the settings dialog will not appear because there are no settings for ticket view.
  • Would a dialog box appear specific to turning on time zone information? This would look like a the upper part of the settings dialog, a drop down list and a check box to turn time zone on. But if we decide to have this time zone dialog appear, is there a need to allow the user to open this dialog up again?
  • The time zone drop down list could just appear in the calendar view. Though since the web app defaults on dashboard, then the drop down list would appear only when the user selects calendar view.

• Ticket view, default to dashboard:
  

• Ticket view, switch to calendar:
  

• Logged In view, default to dashboard:
  

• Logged In view, switch to calendar view:
  

Outlining more detail in the workflow for when time zone and subscribe drop down list appear and disappear:

1. User clicks on ticket-URL to view share in ticket view:

• Web UI defaults to dashboard view.
• If there is time zone information, an alert bar will appear to turn on time zone settings.
• User clicks to 'turn on time zone' in the alert bar.
• Time zone drop down list will appear in calendar view.
• If there is no time zone information in the shared collection, no alert bar will appear.
• Subscribe pulldown is also visible in the header area in ticket view.

Questions:

• How do we indicate to users that the time zone drop down list appears in the calendar view if they are default to the dashboard view.
• Is it indicated in the instructions in the alert bar? This will be tough to do since the alert bar is rather small. Or maybe it's not important until the user switches to calendar view and it's there.
• In the current time zone workflows, when the user 'turn on time zone', the 'settings dialog' appears for the user to set their time zone. The problem is, there are no settings in ticket view.
• Do we still prompt the user with a dialog specific to time zones? Or does the drop down list just appear in calendar view (but the user will not see it appear until they switch to calendar view.)

2. User subscribes to share and logs in

• Web UI defaults to dashboard
• User logs in, links are visible.
• Subscribe pulldown is no longer there.
• Time zone drop down may or may not appear whether collection contains tz data and/or whether user turned on time zone support in the UI.

---

• Current design with Button explorations. Dated 4/27/07.

• Dashboard w/ left nav, stacked rows, revamped detail view and pagination UI: Dated 4/25/07.

• Dashboard w/ left nav: Dated 4/23/2007.
  

• Dashboard w/out left nav & dialog box: Dated 4/20/07.
  

• Dashboard w/out left nav & time zone alert bar: Dated 4/20/07.
  

Open issues on the design mock up that needs to be refined.

Still working on:

• Logo text layouts for all contexts
• Pagination nav - Is it enough to just say << [1] of 13 >> where [1] is editable by the user.

Remaining open issues:

• Pull together a proposal for Removing / Deleting / Unsubscribing / Unpublishing
• Follow-up with Bobby re: Time zones workflows for Preview to finalize UI proposal
• What was our next action for Recurrence? I can't remember.

• Bucketize UI elements into 3 categories:
  • Stuff users need to see immediately, whether or not they're looking
  • Stuff users need to be find easily when looking for them
  • Stuff users can find on their own time

• Continue to experiment with button styles for:
• State buttons: View selector and Mark-up bar
• Action buttons: Email this, Remove, Save, Cancel, etc

• Comprehensive visual syntax guide for:
• Font colors, sizes, styles
• Button styles
• Selection highlight
• Glyphs

• Resolve mock-up size: 800x600 versus 1024x768

-- PriscillaChung - 12 May 2007