the91455/zerowawe

Purpose and delivery model

Zerowawe is an anonymous peer-to-peer messaging client: users receive/share a nickname, establish direct WebRTC connections, and exchange messages and media without a central message server. It is a React single-page application, packaged for mobile through Capacitor.

Application bootstrap

The browser app starts at src/main.jsx, which mounts the React root and global styling. src/App.jsx is the primary application-level composition point; given the compact source tree, it likely owns the main screen/state transitions for landing, identity, connection, sharing, and chat. index.html is the Vite HTML host.

Paths: src/main.jsx, src/App.jsx, index.html

P2P communication boundary

The intended transport is WebRTC via PeerJS. PeerJS/WebRTC is the critical external boundary: connection negotiation may require PeerJS infrastructure, but chat payloads are designed to travel directly between peers rather than through an application backend. The client must treat peer availability, connection lifecycle, message delivery, and media transfer as asynchronous network state.

Paths: src/App.jsx, package.json

Identity and privacy primitives

Anonymous identity is nickname-based rather than account-based. Nickname generation is isolated in src/utils/nicknames.js, making it the boundary for the “infinite identity” algorithm and shareable peer identifier format. Cryptographic behavior, if used for client-side identifiers or payload protection, is isolated in src/utils/crypto.js; it should remain separate from UI state and transport wiring.

Paths: src/utils/nicknames.js, src/utils/crypto.js, src/App.jsx

User interaction and sharing flow

The primary control flow is: initialize/generate a nickname, expose it for QR or native sharing, accept or target another peer nickname, establish a P2P session, then render and exchange chat/media events. UI implementation is concentrated in the app component and custom CSS, rather than a component-heavy design system.

Paths: src/App.jsx, src/App.css, src/index.css

Mobile runtime integration

Capacitor provides the native mobile shell and platform bridge for the web application. Native Share and device-oriented distribution are architecture-relevant capabilities, while the React/Vite build remains the core UI runtime.

Paths: capacitor.config.json, package.json, vite.config.js

Assets and deployment surface

Static branding and runtime-served assets are under public/; design reference screenshots live separately under assets/screenshots/. The Vite build produces the web bundle consumed directly in browsers or embedded by Capacitor.

Paths: public, public/logo.png, assets/screenshots