Voice-first communication for kids

Walki Kidalki

A parent-supervised push-to-talk app where children send voice clips only to people and groups their parents approve.

See parent controls View app screens

Parent owned Voice clips only Server-enforced permissions

Walki Kidalki child push-to-talk conversation screen

Parent approved Voice clips only move through approved children, active sessions, schedules, and enabled devices.

Made for real families

Kids get a simple talk button. Parents get the controls.

Walki Kidalki keeps the child experience light and friendly while the backend checks the serious parts: family trust, child permissions, active sessions, enabled devices, schedules, group membership, and revocations.

Parent control

Full control stays with parents.

Walki Kidalki treats parent ownership as the product, not an afterthought. Children get a friendly voice experience while parents control people, groups, schedules, devices, and revocation.

Parents own every connection

A child cannot invite friends, approve members, create groups, or change permissions. Parent Mode is the only place those decisions happen.

Trust is not permission

Family-to-family trust only opens the door for parents to review. Each child-to-child path still needs explicit approval.

Schedules and devices matter

Communication can be limited by time windows, active child state, kid sessions, and enabled devices.

Kid experience

Simple enough for children. Restrained enough for parents.

The MVP communication unit is a voice clip. No open chat lists, no child-managed invites, and no live streaming unless the product intentionally expands later.

Push-to-talk voice clips

Kids send short voice clips instead of typing, calling strangers, or managing contacts.

Inbox first

Incoming messages land in a simple inbox where the child taps Listen when they are ready.

Walkie-talkie feel

Conversation mode can auto-play approved clips during an active session without becoming live audio streaming.

Product screens

Real app surfaces from the current build.

These screenshots come from the existing Walki Kidalki mobile web build and show the parent and child modes that the marketing site is describing.

Walki Kidalki Parent Home showing children, pending approvals, and history — **Parent Home** A quick status view for children, approvals, groups, and recent message history.

Walki Kidalki parent approvals screen showing child-to-child permissions — **Approvals** Parents explicitly approve who each child can talk to before messages can flow.

Walki Kidalki parent groups screen showing small approved groups — **Small Groups** Groups are parent-managed and sized for the MVP safety model.

Walki Kidalki kid home showing approved contacts and group options — **Kid Home** Children see approved people and simple talk options, not administrative controls.

Walki Kidalki child conversation screen with a large push-to-talk control — **Push To Talk** The core child action is clear, large, and focused on recording a voice clip.

Walki Kidalki signed out screen with parent sign in and registration — **Parent Entry** Parent Mode requires authentication before child sessions or permissions are managed.

Demo path

The first end-to-end demo is a real family workflow.

The marketing promise matches the architecture: two parents, two children, explicit approval, one voice clip, inbox playback, parent history, and immediate revocation.

Parents create children

Each family starts from Parent Mode. Parents add their own children and keep ownership of kid sessions.

Families connect

One parent sends a family connection request. The other parent accepts before child approvals are considered.

Child permission is approved

Mateo can talk to Ben only after the parent-controlled child-to-child permission is active.

Voice clip is sent

The child records a clip, the audio uploads to R2, and message metadata is delivered to approved recipients.

Parent can revoke

When a parent revokes permission, new communication is blocked immediately by the backend.

Safety model

Designed so frontend hiding is never the real security boundary.

Walki Kidalki is built around server-side authorization. The app can make good choices in the UI, but every communication write still has to pass the parent-owned permission model.

Children cannot create friendships. A family connection is only trust between parents, not child-to-child permission.
Groups stay small by design. MVP groups default to five children and require parent approval for each child.
Audio belongs in R2. The app stores voice files as objects and keeps metadata separate from audio content.
Revocation is immediate. Disabled permissions, devices, sessions, or schedules block new communication server-side.

Early access

Build a safer voice habit before kids need full messaging apps.

Walki Kidalki is for parents who want quick voice connection without giving children open-ended social tools.