1028224 - Email UI improvements

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Jean Gong :jgong]

It is unclear what is editable and not in Email.

Comment 1

[Dylan Oliver [:doliver]]

Sri, can you find more details for this bug so we have some idea what to address? 

(+Juwei since this will likely need a trip through UX once we understand the intent.)

Comment 2

[Sri Kasetti]

Adding Wilfred. I have no idea what this feature is.

Comment 3

[Wilfred Mathanaraj [:WDM]]

as we discussed before when we reviewed the tako requirements and Juwei may be able to help you here from the UX side:

this is pure UX review of the items in the email app to ensure users are always clear which are editable/actionable fields and which are not. 

the app may need a general improvement on the look and fell to bring a perceived maturity to the user experience.

i have NI Juwei as she may be already aware of items we can tweak to achieve this.

Comment 4

[Juwei Huang[:juwei]]

As far as I know the requirement is not only focus on email, some other apps have similar requirements as well. I guess once the new building block has implemented, the confusion of editable/actionable field may reduce.

But as Dylan said, this bug is somehow very vague and it would be great if Wilfred can provide more details, such as what specific UI looks confused to them. 

I also list down the possible issues that the bug may describe:

1. In edit mode, the action icons are still tappable even if no items are selected. The correct behaviour should be disable action icons until one or more items are selected. 

2. When opening a message that contains external images, a black banner will display "Show external images". The banner looks untappable but it's tappable, so we may change the visual design to make it looks more reasonable for user to tap on it.

3. In terms of the email settings, some lists are tappable and some are just information, such as "Account type" is untappable but the "Username and password" is tappable. The up coming building block will design a ">" besides the tappable list so that we could distinguish which list is actionable.

If the schedule is doable I will deliver spec for 1) and 2) later. As for 3) it's more about a building block improvement.
Let me know your thought, Sri :)

Comment 5

[Sri Kasetti]

Wilfred, can you ask the partner which of the above 3 items they want us to do.
If its 1) or 2) we can look into it for 2.1

Comment 6

[Sri Kasetti]

Let's get the specs for 1) and 2) done
We can review with the partner if necessary

Comment 7

[Rob MacDonald [:robmac]]

Hi Wilfred... 

Are you able to provide more details on this user story? We just reviewed the bug with the Frameworks team and we're not clear on the scope / nature of the issue.

- Rob

Comment 8

[Wilfred Mathanaraj [:WDM]]

same as before - Mike has some design suggestions - this all falls under the same bucket of general look and feel of the apps. lets get those items into a proposal and we can work with partners to show what we are doing.

Comment 9

[Dylan Oliver [:doliver]]

Juwei, can you attach the current spec to this bug?

Comment 10

[Juwei Huang[:juwei]]

Attachment: [Email] bug 1028224.pdf

Spec attached.

Comment 11

[Dylan Oliver [:doliver]]

Toast styling: Bug 1021981

Will cover the "Unable to connect the server" and "Message marked as unread" items from the attached spec

Comment 12

[Peko Chen [:pekochen]]

Attachment: [spec]Visual Refresh_Email_load_more.pdf

Hi James,

please check attachment for load more message spec.
thanks!!!

Comment 13

[Peko Chen [:pekochen]]

Attachment: [spec]Visual Refresh_Email_load_more.pdf

Comment 14

[Dylan Oliver [:doliver]]

this is a meta bug -- removing release & sprint targets