04 / Messaging product, Android & relay infrastructure
ChatNU — Lightweight Deployable Messenger
A simple Android messenger built around WebSocket and relay communication, designed for fast deployment, low-friction use, and constrained connectivity environments.
ChatNU is an R&D product focused on three problems: a client that non-technical users can operate without training, real-time communication that can recover across unstable networks, and a deployment package that turns an ordinary machine into a relay with minimal setup. The architecture is still being validated and is deliberately presented as a product in development.
Existing tools are either too complex for end users or make independent, controlled deployment difficult.
Simple, controllable communication needs to work without specialist deployment steps or a crowded interface.
A sound system is designed around real constraints.
GOALS
- Relay setup with minimal configuration
- Fast and simple Android interface
- Automatic connection recovery
- Clear message-delivery state
CONSTRAINTS
- Unstable or constrained networks
- Non-technical host operators
- Low resource use
- Predictable behaviour during disconnection
Product definition, communication architecture, experience design, Android and relay prototyping, and deployment validation.
- Product research and design
- Android development
- Real-time communication architecture
- Deployable infrastructure
ChatNU is an R&D product focused on three problems: a client that non-technical users can operate without training, real-time communication that can recover across unstable networks, and a deployment package that turns an ordinary machine into a relay with minimal setup. The architecture is still being validated and is deliberately presented as a product in development.
- WebSocket communication with heartbeat and reconnect
- Independent relay with a simple deployment package
- Separate local message state from server acknowledgement
- Keep the client native and resource-conscious
Interaction followed the workflow and content model—not a prefabricated template.
Code, data, and deployment are one deliverable.
- Android client architecture and core conversation flows
- WebSocket protocol and reconnect handling
- Relay model and connection-state reporting
- Simple host package for non-technical operators
- Offline, retry, and message-delivery states
- Interactive interface prototype and usability validation
A simple Android messenger built around WebSocket and relay communication, designed for fast deployment, low-friction use, and constrained connectivity environments.
No approved numerical metric has been published. The outcome is stated only through observable delivery and the project’s real status.
The next phase is defined from operational evidence and real use.
No roadmap or result is presented as fact without project-owner approval.
Working through something similar?