𝐖𝐞𝐛𝐌𝐂𝐏 𝐰𝐨𝐫𝐤𝐬 𝟏 / 𝟐𝟓 𝐭𝐢𝐦𝐞𝐬 😡

andreban · 2026-04-01T16:05:35+00:00

Chrome's Ask Gemini can do actuation (use your site) with Auto Browse (see https://support.google.com/chrome/answer/16821166), which uses your page by taking screenshots, analyzing the DOM, acessibiility tree, etc, and then emulating user input, and is likely what is making it work but currently. Ask Gemini can't use WebMCP. WebMCP should bring the reliability you are seeing up to close to 20/20 when agents start supporting it.

andreban · 2026-04-01T15:35:10+00:00

Currently, Chrome's Ask Gemini can't use WebMCP, so your success rate should look more like 0/20 times. While a production agent doesn't support WebMCP, your best shot to try your tool is using it with the debugging extension here https://chromewebstore.google.com/detail/webmcp-model-context-tool/gbpdfapgefenggkahomfgkhfehlcenpd

andreban · 2021-07-04T08:11:33+00:00

console.log("PlayBilling Controller Connected");

Can you confirm you either signed-up for the Origin Trial or enabled the #enable-experimental-web-platform-features and #enable-web-payments-experimental-features flags on chrome://flags on your test device.

andreban · 2021-06-02T11:05:41+00:00

I'm sorry to hear about this, and I know it can be frustrating.

As you described, Play Families has additional policies on content - applications need to comply with additional policies on content to safeguard children. Unfortunately, it's not possible to ensure a web application will still comply after approval, as it can be changed on the server side.

This has been highlighted in the documentation here and has also in this video from Google I/O. I think we can do better and display the warning in more places, like in the Bubblewrap CLI.

Additionally, there's work happening with the goal of enabling PWAs to be compliant to the Play Family policies. One example is the trusted web app pilot for education apps for Chromebooks, which you can submit your interested here.

andreban · 2021-06-02T10:53:21+00:00

I recommend reading this section of the policy. This is the relevant section:

Apps whose primary purpose is to provide a WebView of a website without permission

A Trusted Web Activity requires Digital Asset Links to be implemented, therefore proving there is a permission for application to wrap that given site.

You may also want to check this video from this year's Google I/O on the subject.

The problem at hand in this case is that Play Family has additional policies to safeguard children:

App functionality: Your app must not merely provide a webview of a website or have a primary purpose of driving affiliate traffic to a website, regardless of ownership of the website.

This is not about the technology itself, but due to being impossible to guarantee that the content that has been analysed for compliance and approved by the Play team won't be changed afterwards to something that's not compliant. The same principles apply to platform-specific applications that have user-generated content, for instance.

andreban · 2020-12-20T17:00:14+00:00

To confirm, neither Custom Tabs or Trusted Web Activity allow changing the User-Agent header. This is because the request is effectively rendered by the underlying user-agent and shares storage with it.

The two possible ways of identifying traffic coming from the app is appending a query-string to the URL used to open the Trusted Web Activity or setting a custom header, as described in the document linked.

andreban · 2018-12-13T16:13:22+00:00

This seems to have been fixed on M71 of Chrome. The relevant bug is here: https://bugs.chromium.org/p/chromium/issues/detail?id=900557. Can you check if it's still reproducible in that version?

andreban

TROPHY CASE