bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1929

Please provide an svg asset to make this easier.
Also note we will want this to be configurable per project.

Initially do we want this to only apply to English Wikipedia or all Wikipedias?
I assume Wiktionary/Wikivoyage/MediaWiki etc will be left alone.

W icon

Attached:

Just for clarity sake:
(I know we previously discussed a hamburger/W hybrid icon)

Are we confident that people will know this is a button that they can click on?

When we released the hamburger for the first time there were various reports of us adding a random feature that had been sitting there for a year or so. We previously had a W icon.

That said there have also been reports the hamburger is not clear as an icon.

It would be good if we had some user testing data to back up this change so it's not just for the sake of change and we don't revisit it yet again later. We are already seeing lots of icon changes (currently the mobile team is having to redo the notifications icon to be a bell icon) and I'd hate this to continue the trend of changing icons willy nilly.

Current users will likely use the access point in the same way they are now, I don't think the change from ≡ to W will affect discoverability there. This is a common pattern both on desktop and mobile for the site logo to go home, or have menu-like functions

ok

Yes, ≡ is not an obvious thing to click on for many users, I think W has the benefits of being both "about the site (branding)" and used in a way that is consistent with other mobile patterns, while avoiding the ≡ that is unclear to many

Testing can be done, but I think that it will be inconclusive (e.g. ≡ and W will test the same in a small sample size), if we can make the change on Beta now it would allow for some quick guerilla testing of the production code rather than a lot of mockups. Sound reasonable?

also as far as the SVG, don't we prefer to use the new wikifont for this?

and yes for now this is a xx.wikipedia only change.

http://bit.ly/WikiFont

.WikiFont-w:before {

content: "\e400";

}

I've created a story card in our backlog to capture this https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1932

Jon asked for some rational, user research, etc. Here is some interesting reading on the subject.

http://exisweb.net/mobile-menu-abtest
http://exisweb.net/menu-eats-hamburger
http://exisweb.net/mobile-menu-icons
http://www.ericmobley.net/the-ambiguous-hamburger-icon-is-the-icon-mystery-meat-to-users/
http://www.getelastic.com/dont-make-these-mobile-menu-mistakes/

I also don't think we should downplay the benefit of having some small amount of branding on the site to identify users what site they are on, which we don't currently have other than the name of the site in text.

Also if we have worries about people not knowing to interact with the button, we could do something like this.

https://github.com/facebook/Shimmer

possibly a bit goofy, but if done subtly it might be interesting.

I know that the code above is for native apps, but it illustrates the idea of subtly drawing attention to the element

this should still happen even without wikifont, title updated.

But it should be configurable. There are a lot of third party users for MobileFrontend. A W icon isn't the best there :)

(In reply to Florian from comment #13)

But it should be configurable. There are a lot of third party users for
MobileFrontend. A W icon isn't the best there :)

This change is only for foundation wikipedias.

Jared yes but as Florian states it should be configurable so that any project can use it and should have a default icon for projects such as Wiktionary or Wikivoyage where a W make no sense.

I just want to balance (swap a single asset on a subset of sites) with (make a configurable system where site admins can change the menu access icon) those are totally separate tasks, and I think we should keep them as such rather than muddying them together as one.

In T65978#682067, @Jaredzimmerman-WMF wrote:

I just want to balance (swap a single asset on a subset of sites) with (make a configurable system where site admins can change the menu access icon) those are totally separate tasks, and I think we should keep them as such rather than muddying them together as one.

Indeed. And I don't think that the menu icon is the correct focus to give some identity to a website; though it can be a side consideration when choosing a new menu icon.

Do we have a separate task for the logo/mark? Related thread: https://www.mediawiki.org/wiki/Thread:Extension_talk:MobileFrontend/%22Mobile_view%22_link_in_footer_is_https,_my_server_doesn%27t_support_that

They are actually the same task. Default should be generic icon such as hamburger and Wikipedia should change it via a config variable.

@Nirzar is this still relevant?