Study 03 · Inspired by Project Fathom
A little contact.
Can a web control feel tangible? Compare a native switch with a dressed version of the same idea. On a supported iPhone, try a direct fingertip tap.
The control itself.
Visible, native appearance.
Tap the switch directly.
Same control. New surface.
A real native switch receives the tap.
The rounded surface is decoration.
A useful application
Room to think.
Both switches control this one local preference. Quiet mode hides a decorative interruption from the sample workspace. It does not change your device’s settings.
Quiet mode is off in this demo.
Make room for
the next idea.
Inspect the boundary
A tap is not a script.
Fathom’s author reports that direct taps can still produce the system tick after iOS 26.5, while programmatic activation cannot. This comparison deliberately calls click() on the dressed switch.
A browser-trusted event can also come from automation or assistive input. It does not prove a physical tap or a felt haptic.
Local event log
- Tap either switch to inspect its event.
No switch event recorded.
Physical-device check
Did you feel it?
After tapping the dressed switch on your phone, record your observation. This is your report, never an automatically verified hardware result. Nothing leaves this page.
Compatibility, permissions and provenance
- No microphone, camera, motion sensor, credentials or backend is used. The native control does not request a separate haptics permission.
- WebKit documents haptic feedback for iOS switch controls. Other browsers may render a regular checkbox and provide no tactile response.
- The native appearance of the actual input is preserved. No Vibration API fallback is substituted and no custom waveform is claimed.
- Keyboard interaction, reduced motion and the local visual state remain usable without haptic hardware.
- Inspired by m1ckc3s / Project Fathom, inspected at revision
189dcdd. No license file was present. This page is an original implementation, not a redistribution of its source, assets or styling.