Pre-launch

Talkcan

A programmable walkie-talkie for your tools.

Concept: one familiar talk button, configurable channels, and useful destinations on the other end.

Concept

Talk. Route. Listen.

The selected channel determines the destination or action.

  1. Choose a channel

    Pick the route for this message.

  2. Hold to talk

    Keep voice as the primary input.

  3. Release

    Finish the message and hand it to the channel.

  4. Listen when something answers

    Hear a response without making the screen the live control surface.

Concept

One can. Many strings.

A channel is a user-visible route. It can point a spoken message toward different kinds of outcomes without turning every route into an AI feature.

  • A recorder or personal log
  • An automation or webhook
  • A service or assistant
  • A person or shared conversation
One Talkcan interface connected to four channel destinations A Talkcan symbol on the left branches through colored strings to a recorder, automation, service, and person. Recorder Automation Service Person

In progress

Built around the talk button.

These are design principles for work in progress, not claims of released hardware support or safety-critical reliability.

Hardware-first

Talkcan is being designed to work with practical push-to-talk controls. It does not require proprietary Talkcan hardware.

Eyes-free by direction

The intended live loop minimizes visual attention after configuration. The screen supports setup, monitoring, and review.

User-owned routes

The channel model is intended to leave destinations and complexity in the user's control while the public extension contract remains unsettled.

Pre-launch

Built in public. Not released yet.

No Talkcan-branded public release exists yet. This site therefore offers no download or installation instructions and makes no final plugin-format promise.

In progress

Product work

The Android application is completing its current development leg separately.

Concept

Open extension direction

Channels and integrations describe intended outcomes, not a frozen author API or package format.