Jelly UI: Tactile Web Components with Soft-Body Physics

Jelly UI is a dependency-free library of 40 Web Components that uses soft-body physics to create tactile user interfaces. It features built-in accessibility with WCAG AA compliance, dark mode, and RTL support, all accessible via a single script tag. The library provides a comprehensive suite of customizable elements for building responsive and engaging web applications.

Key Points

• Jelly UI utilizes soft-body physics to create a unique, tactile aesthetic for web interfaces.
• The library is entirely dependency-free and consists of 40 customizable custom elements.
• Accessibility and internationalization are core features, including WCAG AA compliance and RTL support.
• Implementation is streamlined through a single script tag and standard Web Component syntax.
• A wide variety of components are available, covering forms, navigation, feedback, and layout needs.

Sentiment

The overall sentiment is mixed but skeptical. Hacker News is intrigued by the idea of tactile, framework-independent UI components, yet the strongest consensus is that the implementation and showcase need more restraint. The community generally supports playful interaction only when it remains performant, configurable, and faithful to native browser expectations.

In Agreement

• The components are visually charming and make standard form controls feel more tactile and memorable.
• A dependency-free Web Components approach is appealing because it can be tried without committing to a framework.
• Small, well-scoped animations can be acceptable when they are tied to active interaction and measured performance remains low.
• Some users liked the demo's segmented presentation because each example felt distinct and easier to inspect.
• The effects would be more useful if exposed through customization knobs so teams could tune or disable specific behaviors.

Opposed

• Several commenters worried that the animation engine or demo page was doing unnecessary idle work and could waste CPU, GPU, and battery.
• Many users objected to the original scroll snapping because it interfered with basic browser navigation across different input devices.
• Critics argued that playful motion should not override direct manipulation or make controls feel unpredictable.
• Some users felt the demo page's interaction choices undermined trust in the library's design judgment before they could evaluate the components.
• Commenters warned that custom-feeling controls and scroll behavior are hard to make robust across browsers, devices, accessibility needs, and user preferences.