Allow add to homescreen and app banner language to be varied via Finch |
||
Issue descriptionWe want to experiment with different UI strings to see if changing the language for add to homescreen has an impact on click through rates and user comprehension of what add to homescreen is. This means implementing the ability to query variations for a parameter to control the string, and passing that parameter through to Java to render the menu/dialog/banner. Due to i18n requirements, the strings must be hardcoded into the binary and can't be sent through variations.
,
Nov 15 2016
,
Mar 9 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1055c94a39ee3096f347bd1293a3742e77a0474c commit 1055c94a39ee3096f347bd1293a3742e77a0474c Author: dominickn <dominickn@chromium.org> Date: Thu Mar 09 22:10:38 2017 Change "add shortcut" back to "add to homescreen" for the "ADD" language variant. Experimental results have shown that using the string "Add" in the app banner leads to an increase in CTR. However, "Add shortcut" in the menu item reduces CTR compared to "Add to homescreen". This CL changes "Add shortcut" back to "Add to homescreen" in the menu item when variations specifies that the language should be "Add" in the app banner. BUG= 662286 Review-Url: https://codereview.chromium.org/2738053003 Cr-Commit-Position: refs/heads/master@{#455877} [modify] https://crrev.com/1055c94a39ee3096f347bd1293a3742e77a0474c/chrome/android/java/src/org/chromium/chrome/browser/banners/AppBannerManager.java [modify] https://crrev.com/1055c94a39ee3096f347bd1293a3742e77a0474c/chrome/android/java/strings/android_chrome_strings.grd |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Nov 10 2016