Closed Bug 1660644 Opened 2 years ago Closed 2 years ago

starting calendar use after installation is unintuitive

Categories

(Calendar :: General, defect)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1621135

People

(Reporter: buecher, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

install 78.1 or 78.2

Actual results:

there is no calendar. There is no mainmenu item for calendar (after activating menu). There was for 68, wasn't there?

After clicking around, I found the icon that activates calendar. I am not sure that icon (tiny) is really self explaining if one searches for calendar.

After clicking, the page tells that a (one) calendar needs to be activated. Also, there is a greyed out private calendar. (why would it be greyed out/inactive when a user deliberately activates the calendars? That is unintuitive. The user has already expressed that he/she wants to use calendar).

For a new user: how the hell do I activate a calendar?
For old users: there is a hunch to right click the disabled calendar to verify what can be done there. But even here, activation is hidden under properties.

How do we expect new users to find that?

Expected results:

is should be easy to find and activate calendar, however the UI engineers choose to do it. It should be possible without guessing, clicking around and trying out context menues and submenu items without guidance.

When I installed TB and clicked away the setup email account, there was a page for setting up everything. Anyway, after setting up an email account with the inital dialog, that page is gone and I have no idea how to get back there.

As overall observation, I found that easier in 68

Blocks: tb78found
OS: Unspecified → Windows 10
Hardware: Unspecified → x86

There is a tooltip for the Calendar and Tasks tab icons.
Since Calendar is disabled when creating a new profile, the user needs to create a new calendar, or activate the inactive Home calendar once they open a Calendar or Tasks tab.
To activate it, right-click on Home, select Properties and check "Enable This Calendar".

To get back to the Account Hub just select the email account in the Folder pane.

Component: Untriaged → General
OS: Windows 10 → All
Product: Thunderbird → Calendar
Hardware: x86 → All
Version: 78 → unspecified

I know many people in the social services sector. They would never be able to find this. I feel our UI is too much oriented towards IT affine people.

I don't think the tiny icons can easily be recognised as calendars or tabs. I don't think a therapistor body worker would try out tooltips for the icons. They might not even suspect that toolstips do exist.
As a matter of fact, I know because I support many of them.

How to activate the calendar would be totally a mystery to them. They wouldn't have the idea to search under properties of a deactivated calendar.
Thanks for your consideration.

I live in both worlds, I am a physicist also doing/learning therapy work/body work. These workings are a total mystery to them. We could gain new users by making this easier.

an afterthought: shouldn't clicking the calendar tab/icon be sufficient to activate a default calendar? by clicking, users show their interest, so it should be made easy for them to actually use/try out the calendar. Now, we are leading them into a search and find scenario.

I agree that this could be better. We have plans to improve the UX of setting up and enabling calendars. For example, improving the calendar sidebar in bug 1621135, see especially the mockup in bug 1621135 comment 6.

Would you consider this a regression compared to version 68?

(In reply to Paul Morris [:pmorris] from comment #4)

I agree that this could be better. We have plans to improve the UX of setting up and enabling calendars. For example, improving the calendar sidebar in bug 1621135, see especially the mockup in bug 1621135 comment 6.

But the priority of that bug is P3 (as of three months ago). That "eventual" improvement doesn't help us today.

Flags: needinfo?(buecher)

yes, I think it is a regression. Even I had to consider how to get the calendar. Wasn't there a main menu entry?

And for now, at least don't make the default calendar inactive. As I have said, as soon as the user clicks the calendar icon, he/she expresses interest in calendars, so we should not present a deactivated calendar without clear instructions of howto activate.

Flags: needinfo?(buecher)

The idea is that the user should set up to use an existing calendar, which they very likely have. Using the pre-created "home" calendar only has very limited use cases. I.e. usually you need the calendar information on the go (on your mobile), and a calendar on the local PC will be of little use.

(In reply to Magnus Melin [:mkmelin] from comment #7)

The idea is that the user should set up to use an existing calendar, which they very likely have. Using the pre-created "home" calendar only has very limited use cases. I.e. usually you need the calendar information on the go (on your mobile), and a calendar on the local PC will be of little use.

It would be easier to instruct users that don't want a calendar how to disable it. IMHO.

It's a real PITA for this release candidate tester to enable Home for testing.

Finding the Calendar
I agree that the location and size of those icons is not optimal at all. We need to properly think of a better and long term solution to better guide the user in moving through the various "Main Tabs" of Thunderbird.

Missing menu items
That was done on purpose since the Calendar is disabled on first run, it wouldn't make sense showing items like "Create an Event" as that wouldn't work. Relying on a submenu to find and open the Calendar is not optimal either, therefore this issue needs to be solved with the point above.

Enabling the Calendar
We can improve this aspect by implementing a small iteration of what Paul linked in comment 4 (eg. a more visible ENABLE button), and we could consider improving the notification message that appears when the Calendar Tab is opened without any enabled calendar.

(In reply to Alessandro Castellani (:aleca) from comment #9)

Enabling the Calendar
We can improve this aspect by implementing a small iteration of what Paul linked in comment 4 (eg. a more visible ENABLE button), and we could consider improving the notification message that appears when the Calendar Tab is opened without any enabled calendar.

+1

@some of us (and please don't take this wrong):
'you/we' are too much a computer (IT) oriented user: when you write: >usually you need the calendar information on the go (on your mobile)

There are many TB users - at least in my surround - that
a) never would put their calendar onto their phone for privacy
b) would not know how to use the calendar on the phone - wouldn't even find it there.
c) would not know how to connect a calendar from phone to PC
d) even I would not know which calendar server I would trust for privacy
e) the whole (?) social services sector might be able to use calendar inside TB, but connecting it to somewhere might be a mystery to them. I know many therapists or bodyworkers or craniosacral therapists - just those 'right brain' people who are excellent in helping and feeling what goes on in others. Who are, obviously, using email, but are not skilled in the technicalities. They currently would never be able even to activate the calendar (find the place where to -they would stop searching for that because it needs to much left brain (cognitive) action, and their skill is the feeling instead).
f) are the therapy people even allowed to have their calendar on the phone? With so many apps stealing data?
g) are we sure by now that offline cached calendars work trustworthy? There are still many places in Germany with doubtful online connection, or people might not want to be connected all the time (Google listening?).

Just my 2 cts. Anyway, I know from that social circle that there are users who would happily use the private calendar without connecting it to any other calendar.

(In reply to Paul Morris [:pmorris] from comment #10)

(In reply to Alessandro Castellani (:aleca) from comment #9)

Enabling the Calendar
We can improve this aspect by implementing a small iteration of what Paul linked in comment 4 (eg. a more visible ENABLE button), and we could consider improving the notification message that appears when the Calendar Tab is opened without any enabled calendar.

+1

It is unclear to me what we intend to do for 78.soon. Is comment 4 the short term improvement to be done in the next few weeks?

Flags: needinfo?(paul)

(In reply to Wayne Mery (:wsmwk) from comment #12)

It is unclear to me what we intend to do for 78.soon. Is comment 4 the short term improvement to be done in the next few weeks?

For 78.soon we could do either:

  1. At minimum, add a more visible ENABLE button and possibly also improve the notification message that appears when the Calendar Tab is opened without any enabled calendar. That achieves the biggest wins for improving the UX here, and is in line with the design linked in comment 4.

  2. Less minimally: there are a few other aspects of the design, and we may want to just go ahead and implement all of them in one go rather than piecemeal.

I'd say we should do 2 if that fits in with developer time and other priorities.

Flags: needinfo?(paul)

Thanks for that clarification.

I'm just thinking that to some extent, with our updating of the user base from 68 to 78 "Real Soon Now", that we get the most bang for the buck having this sooner than later.

Yeah, given the tight time frame, I think that makes sense.

I just remembered that due to string freeze, we won't be able to change the notification message for 78, so it's just adding the visible ENABLE buttons.

I'll take care of this in bug 1621135 and try to have it on c-c before the end of the week.

See Also: → 1621135

I see an Enable button in Daily and 81.0b4!

Indeed, let's close this and uplift to 78 bug 1621135

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.