Tahoe Release Spec

Tahoe & Version Roadmap

A Named Annual Release Cycle Committing to Closing the Native Feel Gap.

The Native Feel Mission

Every React UI library today solves the same problem: giving developers pre-built buttons and inputs. But none of them solve a different, harder problem: making web apps feel native.

When you use a phone app and then open a web app in the browser, you feel the difference immediately. The web app feels flat, interactions feel laggy, and swiping left navigates browser history instead of closing drawers. Tahoe is built to close that gap completely.

The Four Pillars of Tahoe

Every component in this release is built to maintain these four core interaction principles.

Physics, not timing

Every animation in Tahoe uses spring physics — stiffness, damping, and mass — not ease-in-out 0.3s. Things have weight. When a sheet slides up, it overshoots slightly and settles. When a button is pressed, it compresses and springs back. Timing curves feel mechanical; springs feel physical.

Surfaces have depth

Tahoe introduces a full surface elevation system: surface-0 through surface-3, glass layers, vibrancy, and a shadow scale. Modals blur what's behind them. Navbars are translucent. Cards have depth. The page feels like it has layers, not like a flat document.

Platform-adaptive behaviour

The same component behaves differently depending on where it runs. A Select on mobile opens as a bottom sheet with a swipe handle. On desktop it opens as a dropdown. A Sidebar on mobile slides in from the edge with a frosted backdrop and can be opened by swiping from the left edge of the screen automatically.

Feedback on every interaction

Haptic feedback on mobile. Micro-scale press animations on desktop. Every tap, every toggle, every sheet opening — the interface responds physically. This is the single biggest thing that separates native apps from web apps in terms of perceived quality.

Annual Releases Roadmap

We release a named, themed major version each year. This modular roadmap makes tracking version additions and upgrading straightforward.

Tahoe Release

2025 • v2025.1.0Active

"Write zero platform code. Feel native everywhere."

Every React UI library today solves the same problem: give developers pre-built components so they don't have to write buttons and inputs from scratch. But none of them solve a different, harder problem: making web apps feel native. When you use a phone app and then open a web app in the browser, you feel the difference immediately. The web app feels flat. Interactions feel laggy. Tapping something doesn't feel like tapping — it feels like clicking. Scrolling inside a modal refreshes the page. Swiping left navigates your browser history instead of closing a drawer. The entire experience signals: this is a website pretending to be an app. That gap is what biibaos Tahoe is built to close. It commits fully to this goal with a named annual release cycle, and a set of principles that every component is held to.

Key Features & Scope:

Glass and vibrancy surface system — CSS variables and utility classes for frosted glass panels, elevated cards, and vibrancy layers

Tahoe radius scale — rounder corners across all components (8/12/18/28px)

System font stack — prioritises SF Pro on Apple devices, falling back gracefully on other platforms

Spring physics tuning — desktop and mobile spring configs tuned to feel more physical and native-like than the previous values

Sheet handle system — a 48px tall touch target with an animated pill handle on every bottom sheet and mobile modal, making swipe-to-dismiss feel completely organic

Pull-to-refresh prevention — built into every sheet component at three layers (CSS, touch-action, and event listeners) so sheets never accidentally trigger browser refresh

Built-in edge swipe — the Sidebar component intercepts left-edge touches and opens itself without any wrapper component needed

Modal backdrop blur — modals now blur what's behind them instead of just darkening it

Four new components — BottomBar, ActionSheet, ContextMenu — the components that most signal "native app" to a user

StatusPage component — full-screen animated status pages (404, 401, 403, 500, offline, success, empty) with sequential entrance animations

Sierra Release

2026 • v2026.1.0Roadmap

"Liquid motion. Infinite layers."

Sierra is the upcoming 2026 release of biibaos, built on the solid foundation established by Tahoe. It pushes the boundaries of web interface feel even further, introducing highly refined fluid mechanics, spatial overlays, and dynamic micro-gestures.

Key Features & Scope:

Advanced momentum swiping and throw gestures across all overlay components

Device tilt spatial parallax effects on glass cards

Dynamic color contrast shifting and multi-tone translucency

Extended charts with responsive physics animations

What Tahoe Specifically Adds

Here is a precise look at the features shipped in the 2025 Tahoe Release:

Frosted Glass Surface

CSS variables and translucency utilities for layered UI depths.

Adaptive Sheet Handles

A 48px touch zone with pill handle for native gesture dismissals.

Edge Swipe Gestures

The Sidebar component intercepts left-edge touches to slide out automatically.

Spring Tunings

Configured stiffness and damping constants built straight into framer-motion.

Swipe-to-Refresh Blocking

Stops native mobile browsers from pulling down sheets.

Tahoe Radius Scale

Pre-set roundings (8/12/18/28px) to emulate native device aesthetics.

What Tahoe Is Not

Understanding focus is as important as understanding features.

It is not a general-purpose component library trying to cover every possible web usecase, nor is it a headless boilerplate. It is a native-feel layer for React and Next.js apps.

Tahoe makes a specific bet: that the most valuable thing a UI library can give developers is not more components — it is the feeling that their web application belongs organically on the device it is running on.

The Annual Release Model

Shipping yearly named versions forces a discipline of delivering unified, tested interaction themes rather than disjointed updates. It offers developer teams a clean upgrade cadence.

Version Scheme: YEAR.MAJOR.PATCH(e.g., 2025.1.0)