Recursos Beta/Cartões Flutuantes

From MediaWiki.org
Jump to: navigation, search
This page is a translated version of the page Beta Features/Hovercards and the translation is 30% complete.

Other languages:
English • ‎polski • ‎português • ‎português do Brasil • ‎سنڌي

O recurso beta Cartões Flutuantes, também conhecido como Previsões de Página, põe um fim ao desastroso problema de ter que abrir várias guias para saber mais sobre uma palavra ou conceito dentro do contexto do assunto a ser lido. Com os Cartões Flutuantes, sempre que o leitor passar o mouse sobre uma ligação para outro artigo, um breve sumário do assunto e uma imagem (se disponível) são exibidos. O usuário pode então decidir entre visitar ou não o assunto antes de continuar com o artigo atual. Uma descrição completa sobre a funcionalidade dos cartões pode ser encontrada aqui.


Introdução[edit]

Os Cartões Flutuantes foram designados para reduzir o custo de exploração de uma ligação, bem como promover o aprendizado, permitindo que o leitor ganhe contexto sobre o artigo a ser lido ou definindo um termo, objeto, evento ou ideia não familiar sem ter de navegar para outra página. Para leitores casuais, os Cartões Flutuantes facilitarão a obtenção de uma visão geral de um artigo, para então decidir abri-lo ou não. Usuários interessados na leitura integral do artigo não serão distraídos nem desencorajados por conceitos não familiares – será possível pré-visualizar o conceito sem navegar para outra página. Consequentemente, a “suavidade” da experiência para esses usuários será maior.

Houveram vários pedidos ao longo dos anos por um recurso semelhante; existem também extensões (veja a lista) e um gadget muito usado (os Popups de navegação) que solucionam o problema. Os Cartões Flutuantes começaram a ser desenvolvidos como recurso beta em 2014, e estiveram entre os nossos recursos beta mais populares em termos de adoção, comentários e impacto no uso. Na página de discussão principal dos Cartões Flutuantes, por 2 anos, inúmeros problemas através de todos os projetos foram identificados e resolvidos. O equivalente móvel aos Cartões Flutuantes, implementados no app para Android em setembro de 2015, levaram a um aumento de 20% no número de ligações clicadas por página.

O painel de configurações dos Cartões Flutuantes permite que usuários anônimos ativem ou desativem o recurso. Usuários autenticados podem ativar ou desativar o recurso pelas página de recursos beta. Caso os Popups de navegação e os Cartões Flutuantes estiverem ativados ao mesmo tempo (geralmente para usuários autenticados que ativaram o recurso beta), os Popups de navegação tomam precedência. Para ativar os cartões, os popups devem ser desativados.

Exemplo de um cartão flutuante sendo exibido.


Design[edit]

Para cada iteração dos Cartões Flutuantes, cada cartão possuirá o seguinte:

  • Uma porção do primeiro parágrafo do artigo;
  • Uma imagem (se disponível) do artigo. Imagens aparecerão na horizontal ou na vertical dependendo da localização da ligação dentro do artigo; e
  • Uma engrenagem que permitirá o usuário ativar ou desativar os Cartões Flutuantes.



Principais diferenças em comparação aos Popups de Navegação[edit]

  • Os popups de navegação são para usuários experientes, e possuem muitos recursos irrelevantes para o usuário mediano.
  • Os cartões flutuantes foram estilizados para facilitar a leitura. Atualmente, o tamanho da fonte dos popups é pequeno, e as margens, curtas.
  • Os cartões flutuantes serão disponibilizados para todos os usuários, não apenas para os autenticados.
  • Eles criam um estilo visual consistente com o artigo;
  • E enfatizam a imagem principal, para que o usuário compreenda o termo visual e literalmente.
  • O conjunto de ações no gadget parece fora de contexto, portanto devemos validar quais dessas ações são realmente úteis para ambos os leitores e os editores.
  • Os cartões flutuantes incluem a data da última edição.


Mudança de nome próxima[edit]

“Cartões Flutuantes” é o nome deste recurso na sua fase Beta. Dado que esse nome contém alguns problemas em potencial (ele não esclarece o que o recurso realmente faz), à medida que o recurso entrará para a fase final, os Cartões Flutuantes serão renomeados para Previsões de Páginas. O nome procede dos nossos experimentos qualitativos, quando estávamos observando os nomes aos quais os usuários se referiam ao recurso.


Configurações[edit]

Ativação/Desativação[edit]

Para usuários anônimos[edit]

Usuários anônimos poderão desativar os Cartões Flutuantes pelo ícone de engrenagem, exibido ao final de cada cartão. Caso o usuário desejar reativar o recurso, será possível clicar na ligação “Enable previews”, disponível no final de toda página wiki.


Para usuários autenticados[edit]

Usuários autenticados podem ativar ou desativar os Cartões Flutuantes através da página de recursos Beta. Devido à promoção do recurso, o usuário poderá controlar suas configurações em dois lugares – na engrenagem de configurações e na página de preferências do usuário. Há um consenso atual de que usuários autenticados devam ativar os recursos nas suas preferências.

  • Se o usuário selecionar a engrenagem, o sistema redirecioná-lo-á às preferências.


Open/Close delay timing[edit]

Logged-in users can change the timing of how fast Hovercards appear and disappear (open/close delay). See Extension:Popups#Show/hide timing for instructions.


Success Metrics and Feature Evaluation[edit]

A number of qualitative and quantitative tests were performed to evaluate the performance of the Hovercards feature. These tests were focused on the following questions:

  • Do users enjoy Hovercards and find them useful?
  • How do Hovercards change reading behavior and do they help users be more accurate when selecting the articles they wish to read?
  • Would launching the Hovercards feature have effects on fundraising?


2015 Greek and Catalan Wikipedia test[edit]

A feature test on was implemented for a period of 4 months on Greek and Catalan Wikipedias. A number of issues and bugs were reported and user satisfaction was recorded using a survey. Users had generally favorable feedback, with the majority of users finding Hovercards useful, easy to use, and enjoyable to use.

Read the full results of these tests.


2016 Qualitative test[edit]

To determine user attitudes towards the Hovercards feature and trace further changes in reader behavior, an unmoderated remote panel study was performed using UserZoom software. The majority of participants reported positive attitudes to the Hovercards feature. In addition, the majority of participants had no issues in turning the feature on and off. Users also described the feature in generally positive terms and reported it was not distracting to their reading experience.

Read the full results and analysis of this test.


2016 A/B tests on Hungarian, Italian, and Russian Wikipedias[edit]

To determine changes in reading behavior and evaluate the success of the Hovercards beta feature, three A/B tests were launched on Hungarian, Italian, and Russian Wikipedias. The A/B test on Hungarian was launched June 7, 2016, the A/B tests on Italian and Russian were launched Sept 23, 2016.

From the results of these tests, we can conclude that Hovercards facilitate positive changes in reading behavior by increasing the precision with which users select the pages they read, reducing the cost of exploration of other pages, and allowing users to selectively focus on a single topic by providing context within a page.

Read the full results and analysis of these tests.

2017 A/B test on English and German Wikipedias[edit]

On August 28, 2017, we launched an A/B test to gauge the performance of the feature prior to release on these projects. The tests will run for two weeks simultaneously as a number of fundraising tests on enwiki.

Blacklisted pages[edit]

For security reasons, Hovercards won't be loaded on certain special pages. We refer to these pages as "blacklisted pages". The initial version of the blacklist can be found here: task T170893.

Future Iterations and Potential Improvements[edit]

Upon success of an initial launch of Hovercards, we are planning on iterating on the feature to add functionality. These items will include:

  • Configuration of images and other settings:
    • a number of users have requested making images configurable within Hovercards. We're marking this feature for future implementation and tracking it in https://phabricator.wikimedia.org/T148995
    • other logged out preferences (more info here)
  • Article titles - currently, only the summary of the article is available within Hovercards. As an iteration, we would like to display the title of each article along with its summary
  • Reference Tooltips (phab:T67114)
  • Cross-wiki Hovercards (phab:T67117), and subsection links (phab:T65792), particularly for Wiktionary
  • Integrate with Navigation Pop-ups - we would also like to expand the configuration of Hovercards to include some of the functionality planned in navigation pop-ups.
  • Interacting with Hovercards text - a number of requests for interacting with Hovercards text have been filed, including being able to copy and paste the text, or export the text as a form or article summary. More info here (phab: T146097)
  • Integrating with Wiktionary items to provide definitions on hover.


FAQ[edit]

Why Hovercards?

This is a feature intended to improve the experience for any reader who normally would have clicked on a blue-link in Wikipedia because they needed an overview (definition) of that entity.

How do we measure Hovercards performance?

The theory of impact for Hovercards is that they lower the cost of exploring a link. This should mean that users are less inhibited and more focused when exploring links. We should see that the overall links clicked + (non-accidental) hovers exceed the number of links clicked without Hovercards. This is what success looks like. There are also some indications of failure that we will look for:

  • hovers can be accidental - we need to measure normal dwell time in a controlled condition to ensure that the likely rate of accidental hovers is not too high. To give an example, if a user must dwell on a link for 250 msecs before a hover shows, then we would want to make sure that there are not a large number of users who tend to dwell on a link for more than 250 msecs without clicking it.
  • Hovercards could lead to fewer pageviews, because the user gets the information that they need from the preview- this is not a problem, but we want to make sure that the decrease (if any) does not result in significantly less editing or fundraising.
  • the % of hovers that result in a user continuing to the page is high - this would suggest that most people wanted to go to the page anyway. If this is the case, then the hover is likely just adding an unnecessary step. We expect some significant % of click throughs for hovers. It is ~60% on Android for a similar feature, but we expect it to be lower on desktop.
  • the percentage of users who disable Hovercards is low (given that users are aware on how to disable the feature) - this suggests that users enjoy the feature.
What if I have Navpops enabled by default?

If you have Navpops enabled, Hovercards are automatically disabled. You will have to disable Navpops in order to experience Hovercards. This is an intentional decision to ensure that Navpop users' do not have their preferences interrupted. Note: for certain browsers, you might have to clear your browser cache first for the change to take place.

How many options do I have in Hovercards preferences?

Right now, Hovercards will either be turned on or off by a user. The option to turn them off lives in each hover event. So at each hover event, a user can decide that they are no longer interested. For logged-in users, Hovercards may be re-enabled from user settings. For logged-out users, Hovercards may be enabled by selecting the "Enable Previews" link at the bottom of the page.

At the project level, administrators can determine how long a user should dwell on a link before a hover is triggered. If a project wants to be conservative, the lag can be longer. WMF will have a recommendation as to optimum dwell time that provides the best user experience while minimizing accidental hovers.

Why can't users just turn on Hovercards if they want them?

Unfortunately, there is no good way to tell users about a new feature without showing it to them first. Central notice banners have been suggested, but running them for 2 weeks would not solve the needs of future users and we do not want to run them continuously. Notifying a user of a new feature is best done using a...hover-over. So that is why we are planning to show an initial hover on the users first hover event, followed by an explanation of what the user has seen. They can choose to turn them off in that dialogue.

If I have Hovercards feedback or if I have a suggestion for making them better, where should I go?

Please go to the Hovercards discussion page, here: Talk:Beta Features/Hovercards


Code[edit]

Analytics and instrumentation
  • Hovercards are currently instrumented to measure various aspects of usage. Please see the popups extension page for details and feel free to ask any clarifying questions.


Project-level rollout discussions[edit]

Rollout Plan[edit]

We would like to begin rolling out to Catalan, Greek, Hungarian, Italian, and Russian Wikipedias in early 2017. Data from the A/B tests represented highly favorable views of the feature. After this, we would like to continue rolling out in stages to other Wikipedias as described in the table below.

Code Language Phase Onboarding Success Dates
ca Catalan 0 [1] March
el Greek 0 [2] March
it Italian 0 [3] March
he Hebrew 0 [4] March
hu Hungarian 1 [5][6] March, 2017
- All other Wikipedias except the remaining top 6 1 [7] July, 2017
ja Japanese 1 [8] August, 2017
es Spanish 1 [9] August, 2017
fr French 1 [10] [11] August, 2017
de German 2 TBD
en English 2 TBD

Onboarding Experience[edit]

The onboarding experience for the feature will depend on the consensus of each community on having Hovercards on by default or providing users with an onboarding experience during which they can reject the feature. The discussion has begun on English Wikipedia with no current consensus. More info here: https://en.Wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_131#Proposal:_Enable_Hovercards_by_default


See also[edit]


References[edit]

  1. https://ca.wikipedia.org/wiki/Tema:Thijlqz8uwve1490
  2. https://el.wikipedia.org/wiki/Βικιπαίδεια:Αγορά/Αρχείο_2016/Δεκέμβριος#.CE.91.CE.BD.CE.B1.CE.B4.CF.85.CF.8C.CE.BC.CE.B5.CE.BD.CE.B5.CF.82_.CE.BA.CE.AC.CF.81.CF.84.CE.B5.CF.82
  3. https://it.wikipedia.org/wiki/Wikipedia:Malfunzionamenti#Hovercards
  4. <https://he.wikipedia.org/wiki/%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%9E%D7%96%D7%A0%D7%95%D7%9F/%D7%90%D7%A8%D7%9B%D7%99%D7%95%D7%9F_387#.D7.94.D7.A6.D7.A2.D7.94:_.D7.94.D7.A4.D7.A2.D7.9C.D7.AA_.D7.9B.D7.A8.D7.98.D7.99.D7.A1.D7.99.D7.9D_.D7.9E.D7.A8.D7.97.D7.A4.D7.99.D7.9D_.D7.91.D7.95.D7.95.D7.99.D7.A7.D7.99.D7.A4.D7.93.D7.99.D7.94_.D7.91.D7.A2.D7.91.D7.A8.D7.99.D7.AA
  5. https://hu.wikipedia.org/wiki/Wikipédia:Kocsmafal_(műszaki)/Arch%C3%ADv104#Inform.C3.A1ci.C3.B3s_k.C3.A1rty.C3.A1k
  6. https://hu.wikipedia.org/wiki/Wikipédia:Kocsmafal_(műszaki)/Arch%C3%ADv105#Inform.C3.A1ci.C3.B3s_k.C3.A1rty.C3.A1k_.28m.C3.A1sodszor.29
  7. this message was sent to Wikipedia Village Pump (or equivalent) of the 247 wikis included in this phase on 19 April
  8. https://ja.wikipedia.org/wiki/Wikipedia:井戸端#New_Page_previews_feature
  9. https://es.wikipedia.org/wiki/Wikipedia:Café/Archivo/Noticias/Actual#Nueva_funci.C3.B3n_Vistas_previas_de_p.C3.A1ginas
  10. https://fr.wikipedia.org/wiki/Wikipédia:Le_Bistro/19_avril_2017#Nouvelle_fonctionnalit.C3.A9_Aper.C3.A7us_des_pages
  11. https://fr.wikipedia.org/wiki/Wikipédia:Le_Bistro_du_jour#Page_Previews_.28Hovercards.29_update