# Pixel Create My Widget: Setup, Supported Phones and the UK Limitation

Start with a simple widget before connecting personal data, because availability and permissions shape what the new Pixel feature can show.

By Paras Madan | 2026-11-11


Google’s Create My Widget lets eligible Pixel users describe a home-screen widget instead of building one manually. Announced in the November 10 Pixel update, it can make everyday information easier to glance at, but the connected-data restrictions matter before you try turning Gmail or Calendar into a personal dashboard.

The [November Pixel Drop](https://blog.google/products-and-platforms/devices/pixel/november-2026-pixel-drop/) is a staged rollout over the following weeks. If the creation option is missing today, that alone does not tell you whether your phone is unsupported or still waiting for the feature.

## Which Pixels can use Create My Widget?

The [official setup guide](https://support.google.com/pixelphone/answer/18835879) specifies Pixel 10 and newer devices, excluding Pixel 10a. Users must be at least 18, with English support in Australia, Canada, India, the US and the UK.

There is an important difference inside that country list: Gemini Connected Apps integration is unavailable in the UK. Personal-data widgets elsewhere require a Google Workspace connection. Google also says some features may need a subscription for higher usage, without stating a universal quota or price on this page.

Treat those as separate checks. Owning a qualifying device does not establish that every data source is supported in your country. Paying for a subscription should not be assumed to remove a regional restriction either.

Before experimenting, decide whether your intended widget needs external information at all. A countdown using a date you provide is a simpler starting point than a widget that must identify a trip in your email, reconcile it with your calendar and decide what to display.

## Build a simple widget first

Hold an empty area of the home screen, then choose Widgets and Create. Describe the widget, send the request, review the preview and add it. The interface also offers templates, and an existing custom widget can be edited by holding it and choosing Edit.

For a first attempt, try this illustrative prompt: “Create a countdown to my product demo on 30 November 2026. Show the event name, the date and the days remaining. Keep the layout easy to read at a glance.” This is a proposed example, not a report of a tested widget.

The fixed date gives you a straightforward way to check the result. Verify the event label and calculation before adding anything more complicated. If the preview contains extra details you did not request, remove them while the widget is still small and easy to inspect.

Once that works, change one thing at a time. Ask for a shorter label or a different arrangement before introducing a new data source. Otherwise, a disappointing result leaves you guessing whether the problem came from the layout, the interpretation of the request or the underlying information.

## Make the prompt describe the decision you need

A useful widget answers a recurring question. “How long until the demo?” has a clear answer. “Make a useful productivity dashboard” leaves the assistant to decide what matters and encourages a crowded result.

For the demo example, the countdown may be enough. Adding a motivational quote, a weather panel and a list of unrelated events would make it harder to find the one number you wanted. A small surface has limited attention as well as limited space.

**Choose one question before choosing the layout.** The widget should reduce the effort of checking something, not create another interface you need to interpret every morning.

You can make the request more precise by specifying what to omit. For instance, ask for the event name and date without an agenda, or a sports result without general sports news. These instructions describe your preferred presentation; they are not guarantees about which data sources the feature can access.

## Add personal data only when it improves the result

Google’s [Gemini Intelligence update](https://blog.google/products-and-platforms/platforms/android/gemini-intelligence-november-features-devices/) describes widgets that draw on services such as Gmail, Calendar and Search. That opens more interesting possibilities, but it also introduces a second question: whether the information shown belongs on a glanceable home screen.

A trip widget might be convenient, yet a full itinerary could reveal more than you want someone beside you to see. Decide the minimum useful detail before granting access. A short event label may serve you better than an automatically generated summary containing names, addresses or message excerpts.

Where connected integration is supported, review the requested access and check the displayed information against its source. Do not assume that a plausible-looking date is the latest date. If an event changes, compare the widget with the original calendar entry before relying on it for a consequential decision.

For UK users, the connected-app restriction changes the plan. Begin with a widget based on information you explicitly provide or another supported capability. Repeatedly reconnecting an account or rewriting a Gmail-based prompt cannot be relied on to overcome an unavailable integration.

## Troubleshoot by narrowing the problem

If Create is absent, check the device, age, language, country and staged rollout first. If the editor is available but a data-dependent widget fails, investigate that data requirement separately. If the information is correct but the widget is cluttered, edit the presentation rather than changing account permissions.

There is no reason to turn every disappointing output into a full reset. Keep a simple version of the widget as your reference, then introduce the smallest change that would make it more useful. This gives you a clearer diagnosis and avoids adding access merely because the first design was weak.

The strongest use of generated widgets is a small piece of software shaped around a repeated personal question. Start with that question, keep the evidence visible enough to check, and let the design remain simple enough that it earns its place on your home screen.

I’m Paras. I work at the intersection of AI, engineering and distribution.

I help technical founders explain new features through useful workflows, clear limitations and stories their audience can follow.

[Book a 30-minute call](https://cal.com/paras-madan/30min).