Web-Native Tools
Use the browser for capabilities the native app does not own.
A web clone should not merely imitate iOS. HYiYH uses browser APIs for capabilities that can be better on desktop and cross-platform devices: installable PWA behavior, keyboard command navigation, screen selection, filesystem access, clipboard and sharing, direct WebRTC transport and selected device sensors.
What it does
A focused surface with connected context.
Command palette
Use Command-K or Control-K to move quickly between supported HYiYH surfaces on keyboard-equipped browsers.
Screen and filesystem access
Compatible browsers can select a window or screen for capture and can accept files or directories directly into supported workflows.
Progressive Web App
Install the static shell on supported devices while private authenticated HTML remains network-first and is not persisted by the service worker.
How it fits into a day
Practical workflows, not feature checkboxes.
Direct peer transport
WebRTC supports direct browser-to-browser messaging and file or backup transfer when both peers explicitly connect.
Use sensors only with permission
Location, orientation, motion, microphone and camera features remain browser-permission-driven and release resources when the tool closes.
Prefer capability detection
The interface checks whether WebXR, wake lock, sharing, filesystem or sensor APIs exist instead of assuming every browser exposes the same platform.
Start from the problem instead
See how this feature fits into a real workflow.
The HYiYH solution guides begin with common friction—digital overload, scattered project context, private Body planning, local-first work, professional operations and cross-device workflows—and show which features work together to reduce it.