Lolly Beta
Launch App

StartFirst steps

Supported environments

Lolly's web app draws with WebGPU, a graphics feature of current browsers, and checks for it before it opens a tool. This page says where that check has been tested and what to try when your device does not pass.

If Lolly says it requires WebGPU

In a browser with no WebGPU, the card reads "Lolly can't draw in this browser yet" and lists the browsers that work today: Chrome or Edge, kept up to date, Safari 26 or later, and Firefox where WebGPU is turned on. It links to the desktop app and to this page. Try these in order:

  1. Update your browser to its current version.
  2. Turn on graphics or hardware acceleration in the browser's settings, then restart the browser.
  3. Open Lolly in one of the tested browsers below.
  4. On a Mac, iPhone or iPad, install the app instead.
Note: Serve the page over HTTPS

Browsers only offer WebGPU to secure pages, so the page must be served over HTTPS, or from a local development server on localhost. Lolly says so when an instance is served over plain HTTP.

What has been tested

Tested and supported

  • Chrome, Edge, Firefox and Safari on a Mac with Apple silicon
  • The Mac app on Apple silicon
  • The iPhone and iPad app, checked by hand

Not supported

  • The Linux app: the WebKitGTK web view it uses has no WebGPU. On Linux you can try the web app in Chrome or Firefox, though neither has been checked on Linux yet.
  • The Mac app on an Intel Mac: from 1.1.3 the Mac app needs Apple silicon. 1.1.0 is the last Intel build and gets no updates.

Not checked yet

  • The Windows and Android apps on real hardware
  • The same browsers on Windows, Linux, Android, iOS, Intel Macs or other graphics hardware

Web releases since 9 October 2026, including 1.2.0 on lolly.tools, rely on the completed Mac browser checks below. These are results on macOS 27, Apple M4, with the browser's default adapter and graphics settings. They do not establish support for the same browsers on Windows, Linux, Android, iOS, Intel Macs or other GPUs.

Qualification results

EnvironmentWebGPU resultVersions and platformAdapter and backendEvidence
Chrome and Edge (Chromium)Supported: tested on macOS onlyChrome 154.0.8037.99; Edge 155.0.4283.45; macOS 27, Apple M4Default Apple Metal 3 adapter; no software fallback9 October 2026; stock browsers, isolated headless hardware runs; required corpus passed, zero skips
FirefoxSupported: tested on macOS onlyFirefox 157.0.1; macOS 27, Apple M4Default non-fallback adapter; GPU identity not reported by the browser9 October 2026; installed visible browser; required corpus passed
Safari (WebKit)Supported: tested on macOS onlySafari 27.0.1; macOS 27, Apple M4Default Apple adapter; no software fallback9 October 2026; installed visible browser; required corpus passed
macOS app (WKWebView)Supported: qualification buildWKWebView 22625.1.29.11.28; macOS 27, Apple M4Default Apple adapter; no software fallback9 October 2026; compiled qualification app, second execution with its existing isolated profile; startup, tool mount and required corpus passed
iOS and iPadOS app (WKWebView)Supported: manual device checkLolly 1.1.1 app; iPhone 16 Pro Max, iOS 27.2 beta (24B5099f); iPad Pro 13-inch (M4), iPadOS 27.0 beta (24A5424a)Default Apple GPU adapter; adapter identity not recorded15 October 2026; development-signed 1.1.1 app installed on both devices; startup, a mounted tool, editing and export checked by hand; the automated corpus did not run (see Recorded evidence)
Windows app (WebView2)Pending: physical runtime not qualifiedWebView2 155.0.4283.62 on a GitHub-hosted Windows Server 2025 virtual machine with no GPU (see Recorded evidence)No adapter on that machine29 October 2026: the WebGPU API is present and no adapter is returned. A machine with no GPU does not answer for Windows hardware, so the row stays pending
Linux app (WebKitGTK)Not supported: WebKitGTK has no WebGPUWebKitGTK 2.52.6, the version Ubuntu 24.04 ships; the release notes for 2.52.6, 2.54.0 and 2.54.2 do not mention WebGPUNone: the WebGPU API is absent8 and 29 October 2026: the Tauri web view has no WebGPU API at all. The library lacks the API, so the result does not depend on the GPU or the machine
Android app (WebView)Pending: physical runtime not qualifiedAndroid 11 on a device; Android 16 (API 36) in the emulator (see Recorded evidence)No adapter on either15 October 2026: Android 11 has no adapter. 29 October 2026: the emulator's WebView 133 has the API and no adapter. Android 12 or later on a real device has not been checked

The macOS app row speaks for Apple silicon only.

Note: A pending row is not a failure

It means the check has not yet passed on real hardware.

A packaged app is released only once its own row says supported, which is why the Windows, Linux and Android builds on the install page stay at 1.1.0. The Linux app stays there until a WebKitGTK release carries WebGPU.

How the checks work

The browser corpus checks numerical results on the main thread and in a worker, photo baking, cancellation, device recovery and operation chains. Its browser startup measurement covers the device service and tool mount fence, rather than the complete gallery.

The Mac qualification app also checked actual gallery startup, a mounted tool, its embedded content and Content Security Policy. These checks do not certify every presentation clicker, embedded website or native platform.

The release tools read the table above: scripts/webgpu-release-gate.ts refuses a release whose environments are not all published as supported, and its header explains the web and per-platform release scopes. The MCP, certificate service, Penpot service and documentation builds do not depend on this table. The Build Guide covers producing a signed build.

Recorded evidence

The Chrome run used source commit 20843cb22d3ad36dfd3d93e518bfd8ee812527a7. The Firefox, Safari and Edge runs used 26799926739fa58bbbf6a8e081f13ab5a8f74617; the required browser corpus and launcher inputs are unchanged between those commits. The Mac qualification app was built from ed6c32571593dba96b0562b47396ff42e2cf3270; its passed execution is not a new current-main build or a fresh-profile startup result. Original failed attempts remain recorded separately.

The iOS and iPadOS result is a manual check, not the automated corpus. On 15 October 2026 a development-signed Lolly 1.1.1 app, built from 26cf05324f46dc4cacd65d12d6f454ada181fb5e with the unsigned qualification frontend, was installed on an iPhone 16 Pro Max (iOS 27.2 beta) and an iPad Pro 13-inch with M4 (iPadOS 27.0 beta). On both devices the app started without the WebGPU notice, opened bundled tools, edited a tool and exported.

The automated product corpus could not run on either device: its qualification broker reads commands from standard input, which is closed when the app is launched on an iOS device or simulator, and its exit on that input crashes the app (an iOS event-loop fault in tao 0.37.1). The release app does not contain that broker.

The Android 11 result is from scripts/verify-webgpu-android.ts on a TCL T810H (Android 11, Android System WebView 155.0.8059.43, Adreno GPU), source 26cf05324f46dc4cacd65d12d6f454ada181fb5e: the WebGPU API is present and no adapter is returned. Its qualification.json has SHA-256 5b45834fd228a68d14e218531796a4a3302f1a7d063f44e65ff9fa1b94ab59be. Android 12 or later has not been checked, so the Android row stays pending.

The 29 October 2026 checks ran the same corpus in the same Tauri fixture on GitHub-hosted machines. The Android emulator run (Android 16, API 36, Android System WebView 133.0.6943.137) used source b6db266a15b5e34c4cae21cbddfde334ca3acdf5, run 40870902947; its qualification.json has SHA-256 9d0a8f64cccafed61dae82cf15b6b429c82ac7e54c7c0c0ac56f0fb254f72bf9. The Windows, Linux and Intel Mac runs, run 40873602178, used a branch of that source whose probe is pinned to the desktop app's own crate versions and patches; on main the probe stopped before the corpus, because its pins had fallen behind the app's. Their conformance reports have these SHA-256 digests:

ReportRuntime and machineSHA-256
WindowsWebView2 155.0.4283.62; Windows Server 2025 image 20261021, Microsoft Hyper-V Video, no GPUc908370958a2f41aa48dd34df1d1cf5e6cc74a698f4ad6a4292163d065e22cb6
LinuxWebKitGTK 2.52.6; Ubuntu 24.04, Xvfb display, no GPU148c230fee9b6d7cb14b8598e7b256df9dd2759237ae130a1c44a3f57311fb80
Intel MacWKWebView 20621.3.11.11.3; macOS 15.7.9 on x86_64, Apple paravirtual graphics with Metal 2a3793a8d28c27fc93bf86d00cb47511b12d1bced57321baeba90bcb6a9b53f9f

The Intel Mac run has no WebGPU API: that macOS 15 web view predates WebGPU. Intel Macs are not supported from 1.1.3, so no further Intel check is planned.

Retained conformance reports have these SHA-256 digests:

ReportSHA-256
Chrome0c9e9628f215692b00f0eba5eacce1820c31d36dc47a57cef1190619bd66033f
Edge9f04aac38b91bdf70a10f3078c288ebb690ad8d4827572f0810248fed2834a75
Firefox conformance reportbdc263c2268485ce9718d40feff26e993ebf68ebcdc30e55484172bbd9f62952
Safariea8b87aa0f60e763b6ac80b6d0663d83323e47ae8e899d2616ab1d4f28becdac
Mac qualification app9f5ed9cd19f7f522a9a221141ace046b789b556b3085400ebb884c5c3bea7fec