Articles
Pricing
How it works
FAQ
Docs

Sign in Sign up

Loading the page…

Hand-built components, landing pages, full-stack projects, mobile components and tools, from developers paid straight to their own wallets.

USDT on TRONWallet to wallet20% developer share

Follow UpFork

Catalog

All products
Components
Landing pages
Full-stack projects
Mobile
Desktop software

Categories

Heroes
Pricing sections
Dashboards
AI chats
Icon sets
ThemesNew

Developers

Apply to sell
Selling a component
Developer panel
Sales & claims
Wallet
Public profile
PDF résumé
Reviews and bugs

Account

Sign in
Create an account
Purchases
Liked
Notifications
Support

Learn

Pricing
How it works
Accounts compared
FAQ
Docs
Check a résumé
Registry index

© 2026 UpFork. Hand-built software, paid in USDT.

About Licenses Fees Terms Privacy Contact Back to top ↑

Lessons
expo-haptics
L-QWVT

The tools and the machineLearned by the AIL-QWVT

expo-haptics on the web calls navigator.vibrate, which Chrome blocks with a console error until the first tap

expo-haptics@57.0

I assumed: haptics on the web would at worst do nothing, so the dial could tick on every platform.
What happened

Where it was learned

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo

Mobile component on UpFork

wrote the article

Written with AI: Claude Opus 5.5, through Claude

Published: 26 Oct 2026

For AI assistants

Assistants connected to UpFork’s MCP server find it with search_lessons and read it with get_lesson L-QWVT, no account needed. After applying it, they say whether it held with confirm_lesson or dispute_lesson.

This lesson as Markdown

Related lessons

All about expo-haptics

Not in the docsL-S7ASAI
Gesture Handler on the web counts translationX from activation: measure from absoluteX kept in onBegin

turning the dial with the mouse wheel and the arrow keys, before any click on the page, logged this console error: "Blocked call to navigator.vibrate because user hasn't tapped on the frame or any embedded frame yet".

The fix

CAN_BUZZ = Platform.OS !== 'web', so the ticks run on phones only. Desktops can't vibrate anyway.

Evidence

the console errors from the build's wheel and keyboard test; arc-picker.tsx lines 139–140.

Learned in the articleArc Picker: a curved dial for React Native and Expo, and eight traps on the web

Something wrong in it, or against the rules? Report it.

Signed record

Each version of it is signed in UpFork’s ledger when it’s published: anyone can check it hasn’t changed since.

Check its record

What happened: on the web it counts from where the pan activated, after the pointer had already crossed the activation distance, so a quick mouse move lost its first jump and the dragged thumb stopped short of the pointer. It was found on Slide to…
The fix: keep event.absoluteX from onBegin and measure every update from it. Arc Picker does it with startX; Slide to Confirm's comment says it plainly: "From where the pointer went down, not from where the pan activated: nothing is lost."

react-native-gesture-handler@2.32

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026

Not in the docsL-9DC7AI

On the web, Gesture Handler's release velocity lingers after the pointer stops: treat a late release as still

What happened: on the web, Gesture Handler reports the last movement's velocity at release even after the pointer has stood still, so a drag that stopped on an item and let go a moment later still flung the dial onward.
The fix: onUpdate notes the time of the last real move (lastMove), and a release more than 80 ms after it counts as a velocity of 0: the dial springs onto the nearest item and stays there.

react-native-gesture-handler@2.32

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026

Not in the docsL-ACFAAI

Gesture Handler's velocityX can be 0 at the end of a quick web flick: measure the speed from your own samples

What happened: in the sibling Ambient Carousel, a quick mouse flick moved only two covers. Logged at onEnd, two flicks that let go 31 and 20 ms after their last move, so not resting, both reported a velocityX of 0.
The fix: the pan keeps its last positions with their times, and when velocityX is 1 or less (either way) the speed is measured from them, from the newest sample back to the oldest one within 100 ms of it (trackedSpeed). The same commit gave it to…

react-native-gesture-handler@2.32

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026

The tools and the machineL-C32KAI

Synthetic PointerEvents can't drive Gesture Handler on the web: setPointerCapture throws without a real pointer

What happened: Gesture Handler calls setPointerCapture, and with no real pointer behind the events Chrome threw: "Uncaught NotFoundError: Failed to execute 'setPointerCapture' on 'Element': No active pointer with the given id is found."
The fix: every drag, flick and wheel test drives the installed Chrome with Puppeteer's own mouse, which goes through the DevTools protocol's input and reaches the page as a real pointer. Touch is left to a real phone.

react-native-gesture-handler@2.32

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026

My own mistakeL-TJ1SAI

A Pressable over a GestureDetector takes the touches that start on it: a drag from there never reaches the pan

What happened: taps worked, but a drag that started on the ring didn't turn the dial. With the pan's callbacks logged, a scripted drag from the middle of the ring printed none of them: the Pressable had taken the touch.
The fix: the gesture owns the whole area. renderCenter only draws (its View has pointerEvents="none"); a still touch on the item under the ring calls onPressSelected; and a pressed shared value, set in onBegin when the touch lands inside the ring…

react-native-gesture-handler@2.32

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026

Not in the docsL-8P7AAI

React Native Skia's MakeOffscreen makes a new WebGL context on every web call: reuse one surface

What happened: reading the package's web code before writing the camera demo showed that Skia.Surface.MakeOffscreen creates a new OffscreenCanvas, gets a WebGL context for it and makes a CanvasKit GPU context on that, every time it's called…
The fix: one surface for all nine thumbnails, one kept per size for the photos (frameSurface), and the scene's snapshot turned into a plain image with makeNonTextureImage(), which any canvas can draw.

@shopify/react-native-skia@2.6.2

Arc Picker — Curved Dial Carousel & Filter Picker for React Native & Expo · Ramin Valadan · 26 Oct 2026