New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 905152 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Feature



Sign in to add a comment

Enterprise policy: enable the Home Button and set a Home Page

Project Member Reported by massimop...@google.com, Nov 14

Issue description

Description:
Create a policy (Managed Configuration) that the admin can use to enable the Home Button (chrome://flags/#force-enable-home-page-button) and set the home page to replace the new tab page.

Use case:
Any time the admin wants to make sure users have easy access to a specific page and wants to set it as the home page.
This feature is essential for a kiosk UX (COSU).

Motivation:
Without this feature, on Chrome for Android it's not possible to provide enterprise users with a home page. It's possible to manage bookmarks, but those require extra taps every time the app is opened, and they're a bit hidden in the mobile UI.

Existing workarounds:
The user needs to be given a long list of not-easy-to-follow instructions to apply this configuration on every device, with no guarantee that such instructions will be followed.
In the kiosk scenario, the admin needs to apply the configuration manually on each device before deploying them.
 
Owner: tedc...@chromium.org
I'm somewhat confused about how this applies to COSU (why would people run Chrome in COSU mode rather than a webview).

But the FR here is to support http://www.chromium.org/administrators/policy-list-3#ShowHomeButton and http://www.chromium.org/administrators/policy-list-3#HomepageLocation on Android.
Labels: Enterprise-Triaged
Status: Assigned (was: Untriaged)
>> why would people run Chrome in COSU mode rather than a webview
By using a webview for kiosks, other features that Managed Configurations support wouldn't be available, plus Chrome features like Chrome notifications would also be missing.
Cc: tedc...@chromium.org nickrad@google.com
Owner: lzbylut@google.com
Assigning to product to comment on whether this is something we would want to support on Android.

We allow OEMs/Carriers to configure the Homepage by installing a content provider on the device.  I don't know how much we want to go down the path of yet another way of configuring this on Android.

There are some experiments that are also trying to make the home button go to a Chrome owned page universally and then making the carrier configured option be placed elsewhere.  This particular point makes me think that the home page is not something we'd want to start providing other channels of configuration for.
Cc: nkostylev@google.com
Point of view of an MDM sysadmin:
Configuring the home page is vital to provide the correct experience on Kiosk devices, and on Enterprise managed devices in general.
I don't see why we would allow Carriers/OEM to do that, but not MDM admins.
(+nkostylev@ FYI)

Sign in to add a comment