01 / The idea

One cat.
Three connected parts.

An advocate with character, a planned pair of devices and care information for each cat. Here is how the BatCat idea fits together.

One cat. Three parts of BatCat.

A personal advocate, a planned device pair and care information for each cat. Explore how these parts fit the product being developed.

3 steps shown. All steps.

The direction and prototype stage are labelled for each part.
  1. Step 1

    A lasting cat identity

    Product direction
    One cat’s identityName · History · Advocate character

    The plan is for your cat’s identity, history and advocate personality to stay with the cat when devices are swapped. The advocate is an AI character.

    Meet the advocate characters
  2. Step 2

    A planned pair of devices

    Planned kit
    Complete device AWorn · planned example
    Complete device BCharging · planned example

    Two complete interchangeable devices are planned for each cat: one worn while the other charges. Swapping their roles is the intended model; the full wearable experience still needs validation.

    Explore your planned kit
  3. Step 3

    Care organised per cat

    Local prototype
    HomeSelected cat’s overview
    CalendarSelected cat’s care

    The local owner-app prototype has a separate Home and Calendar for each cat, with manual care notes and reminders. The website tour uses fictional examples of this approach.

    Try the fictional app tour

These are parts of a product in development. The advocate’s words do not translate a cat’s thoughts. Device specifications, prices and launch timing remain unconfirmed.

01

A voice with character

Talk with your cat’s advocate using the cat’s name. Character voices and expressive meows give the experience its own sense of fun.

Conversation prototype tested on Android
02

A connection to their world

The planned wearable system brings connected devices into the experience. Location and surroundings are part of the product direction.

Wearable integration in development
03

Everyday care, together

The owner app brings each cat’s records, reminders and care information together, with manual entries where connected data is unavailable.

Local owner-app prototype

The advocate is an AI character. Its speech and meows do not translate a cat’s thoughts or prove how a cat is feeling. Real animal monitoring still needs validation.

04 / Explore the possibilities

A little more
to discover.

From everyday owner tools to the connected system we’re developing. Explore the features and see the stage each has reached.

12 features to explore

Android conversation prototype

A personal advocate

A character and voice representing your cat. Speak using your cat’s name, with characterful replies and expressive meows.

Where development stands

Human-tested wake, reply and follow-up interactions on Android. The complete wearable-to-cloud conversation remains a separate validation step.

Owner-app prototype

Help with the everyday setup

A more focused owner assistant explains care, safeguarding and the main app controls.

Where development stands

Grounded setup guides and voluntary chosen-name memory are implemented locally. Owners can edit or forget the name. Guidance leads to controls; conversation does not commission a device or change its settings.

Owner-app prototype

Each cat, their own space

A separate Home, preferences, calendar and care history for every cat in the household.

Where development stands

Multi-cat record separation is demonstrated in the local owner app. Production accounts and customer commissioning still need delivery validation.

Owner-app prototype

A calendar that keeps the story

Browse dated notes, care entries and upcoming reminders in a seven-day calendar.

Where development stands

Local calendar views, entries and reminder completion/cancellation are implemented. The website tour uses fictional examples held only in this page.

Prototype / limited phone testing

A nudge for everyday care

Plan one-off or repeating reminders, with optional phone notifications.

Where development stands

Notification receipt has been demonstrated in limited phone tests. Permissions and synchronisation are required; longer operation, quiet-time and reboot behaviour remain open.

Owner-app prototype

A history you can review

Add observations and owner-entered weight, review changes and correct an entry when needed.

Where development stands

Manual wellbeing records and correction history work locally. Connected clinical sensors, diagnoses and inferred feelings are outside the verified scope.

Owner-app prototype

Care summaries, on your terms

Review daily facts or prepare a summary over a chosen period.

Where development stands

Seven-day, thirty-day and custom reports up to 31 days use the local records. Preparing a summary does not contact a vet or establish a clinical finding.

Planned hardware / simulated app swaps

Two devices. One identity.

One complete unit worn, one charging. The identity, voice and history stay with the cat.

Where development stands

Device-role swaps are simulated in the owner app. Connected commissioning, endurance, fit and real device swapping still need hardware validation.

Prototype settings / tracking planned

Location and safe zones

Define a zone boundary and review location settings, with connected tracking part of the device direction.

Where development stands

Map and zone configuration interfaces exist locally. Live wearable GPS, reliable crossing detection and delivered zone alerts are not established.

Owner-app prototype

Alerts that fit your day

Choose your alert preferences and quiet times in the owner app.

Where development stands

Preferences are saved locally. Wearable battery, offline and zone events still require connected delivery and reliability testing.

Planned connected feature

A cat’s-eye view

The connected brief includes authorised camera and audio sessions from the wearable.

Where development stands

Real wearable camera, remote recording and two-way talk are not connected in the current owner prototype. Media transport, permissions, power use and field behaviour need validation.

Planned / telemetry required

Activity, rest and roaming

The goal is to help owners understand everyday patterns using available observations.

Where development stands

Worn telemetry, individual baselines and accuracy checks are required. Current cat animations illustrate behaviour; they are not a live measurement of your cat.

Prototype — demonstrated within a defined local testPlanned — part of the direction, awaiting connected validation

Your next little adventure

See a little everyday magic.

Explore care records and device swaps in the fictional website tour.