Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I am making an interactive calendar, where user can make an event for themselves, or to invite others (very much similar to Google Calendar).

Only difference from G Cal is that these events has a state of "completion". Completion is happening automatically, and there is nothing user needs to take an action. However, the system that updates the calendar:
a) only updates once couple hours
b) sometimes the performance fails

So I need to indicate that the event did not perform one way or the other (there is no way to be able to distinguish why until someone manually looks at it.

So far, my ideas were:
1. Do it like google (past event is in pale color. if the event did not performed yet/ failed, show it as a future event in full color)
2. Do strikethrough style (line in the middle) for the past event.
3. Put some sort of 'error' or 'pending' icon next to event title.

Solution 2 is, I looked up strikethrough, but grammatically that's a scramble, rather than a meaning of completion, so I am hesitant to use it.

Solution 3, the challenge is the calendar is already full of information and already very hard to digest what's going on. I am not interested in adding another icon that user needs to learn and be familiarize themselves.

I am wondering if there is any other method to indicate this special indication.

share|improve this question
    
So your question is how to indicate past events, which didn't happen? –  Alexey Kolchenko Jul 29 '13 at 17:37
    
Right. Technically indicate past events which system did not verify. They all happened, but the system needs to verify the completion which is important cue for the users. –  Jade Jul 29 '13 at 17:39
    
What sense this state has for user? To which activity or behavior change it should motivate? –  Alexey Kolchenko Jul 29 '13 at 17:48
    
If system fails to update, that means user won't get paid. (Most likely it will get updated within couple hours as system only updates every couple hours) If the error stays for more than couple hours, then most likely, user will contact someone in charge in person to fix the error. There is really no motivational call to action that interface wants to encourage people, but being clear on what's going on. –  Jade Jul 29 '13 at 18:42
    
@Jade - From your previous comment it sounds like the message to the user should be something urgent ('OH NO! Payment missed!') and the call to action is "Contact [Fixer Person]". If that's true, then you should make the past event a red or yellow color and possible throw in an icon ("!" or "X") to indicate a problem. –  Luke Jan 17 at 21:16

1 Answer 1

You've mentioned your calendar is similar to Google Calendar, it is worth to be consistent with it. You have three event states which are future, pending (unconfirmed) and past.

As future and past events are color-coded in Google Calendar, to be consistent, use same mean for pending events. It could be yellowish (middle transition state, like traffic-light) or orange toned (current event).

It is also necessary for users to understand the essence of the events' states. It could be achieved with system description, FAQ section, tooltip for calendar events.

share|improve this answer
    
+1 for following googles set standards and for tooltips. –  Joseph Neathawk Sep 23 at 3:07

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.