997845 - [Camera][Madai] Preview/Gallery both label and arrow should be clickable

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::Camera, defect)

Description

[Diego Marcos [:dmarcos]]

If I want to return to camera I have to tap on the arrow. I would expect also the text to be clickable (see video)

Comment 1

[Diego Marcos [:dmarcos]]

Attachment: tapPreview.MOV

Comment 2

[Tiffanie Shakespeare [:tif]]

Confirmed the behaviour of the building block and it's working as it should. 

This is a phone wide behaviour and would need to be looked at by the building block team before making changes. 

NI'ing Harly, who is in charge of building blocks, to consider the change for the future.

Comment 3

[Diego Marcos [:dmarcos]]

That only the arrow is clickable is specially annoying on big screen devices (e.g Nexus 4) You have to over reach with the finger all the way to the corner. It's very bad UX. Who can fix this?

Comment 4

[Tiffanie Shakespeare [:tif]]

Since it's a building block, it has to start with that team. Harly will be able to better help/answer questions related to the header building block.

Comment 5

[Hema Koka [:hema]]

(In reply to Diego Marcos [:dmarcos] from comment #3)
> That only the arrow is clickable is specially annoying on big screen devices
> (e.g Nexus 4) You have to over reach with the finger all the way to the
> corner. It's very bad UX. Who can fix this?

It will be annoying even on small screen devices too

Comment 6

[Tiffanie Shakespeare [:tif]]

Comment on attachment 8408371 [details]
tapPreview.MOV

Forgot to clear my flag from before.

Comment 7

[Harly Hsu[:harly]]

Currently, the Building Blocks team are working on moving the header text to the center in order to accommodate a large back button. So this issue would be fixed by that in 2.0.

Comment 8

[Diego Marcos [:dmarcos]]

This makes our camera UX crappy. Should we reimplement a custom header menu until the building block is properly done? Madai is going to ship before 2.0

Comment 9

[Tiffanie Shakespeare [:tif]]

I know it's hard, but we should not be using custom things instead of the building blocks. We want to present a consistent experience even if it isn't ideal.

Comment 10

[Diego Marcos [:dmarcos]]

We can make the menu look different so there's no consistency issues. In my opinion shipping a bad camera is worse than breaking consistency in such a small scale. I really want to ship the best camera we possibly can.

Comment 11

[Diego Marcos [:dmarcos]]

If building blocks are sub par we shouldn't use them. O tolerance for crappy UX

Comment 12

[Diego Marcos [:dmarcos]]

Can we prioritize this so our partner can ship its device with decent UX? What's the roadmap for building blocks?

Comment 13

[Wayne Chang [:wchang]]

Attachment: 2014-04-21-03-23-55.png

I checked this on my peak with master and the UX from preview to camera looks like the attached image, which IMO is better UX than what's in Diego's video.

Has something changed?

Comment 14

[Hema Koka [:hema]]

lets discuss for 2.0 in triage

Comment 15

[David Flanagan [:djf]]

(In reply to Wayne Chang [:wchang] from comment #13)
> Created attachment 8409570 [details]
> 2014-04-21-03-23-55.png
> 
> I checked this on my peak with master and the UX from preview to camera
> looks like the attached image, which IMO is better UX than what's in Diego's
> video.
> 
> Has something changed?

Wayne: yes, the preview UX changed substantially after some usability studies. You have a slightly out of date build.

Hema: if this is a building blocks issue, it isn't really something we have any control over, even in 2.0.

Diego: our header now matches every other bizarrely narrow back button on the system. We can't fight UX on this, so I'm going to close this. It is possible that there is supposed to be some touch area fluffing going on and that is not working. If you find that other back buttons in other apps are more responsive than our back button, then please re-open and let's fix that somehow.  Otherwise I think we need to trust the UX team on this.

Comment 16

[Diego Marcos [:dmarcos]]

I think this shouldn't be closed. What about moving it to the building blocks component. They can decide to close or mark it as duplicate. This is a very bad UX issue. We're mimicking an iOS UI pattern that millions of people use and changing how it behaves (label is not clickable and it indicates the section you are instead of where you are going back). It looks like iOS but it's not iOS. We have to rise the priority of this kind of UX issues. We should use this bug to put pressure on the building blocks people.

Comment 17

[David Flanagan [:djf]]

Bulk edit to clear old and out of date needinfo requests that I never responded to. I'm assuming that these are no longer relevant. If you are still waiting for an answer from me, please set needinfo? again.