Fitlify

Your body is the controller.

A webcam fitness game for PC, in the works at Alfie Software.

Your camera's pictures never leave your PC.

Swing for it.

Empty hands, a full swing. The game puts the bat in them.

Play the rally.

Step in and swing through. No racket to buy, none to break.

Roll a strike.

One step, one swing of the arm, and let it go.

And in the game.

The figures above are drawn for this page. These two pictures are the game itself, as it stands today, in development.

The game's baseball: a red-haired character in dungarees, seen from behind with a bat in hand, stands in a castle yard hung with targets as a ball flies in.
Baseball, in the yard.
The game's bowling: the same character stands at the head of a lane that runs across a field to the pins, a campfire to one side, at dusk.
Bowling, by the campfire.

33 points, read on your PC.

Fitlify finds 33 points of your body in your webcam's picture, from your nose to your toes, and plays the game from those alone.

The pictures are read in memory. They are never saved and never sent.

The picture stops here.

Your webcam's picture goes into the game and no further. The game reads 33 points from it, keeps those, and lets the picture go.

One picture from the camera
921,600 bytes: 640 by 480, three bytes a pixel, uncompressed
One pose
580 bytes

About 1,600 poses fit in one picture. To scale, the pose's bar would be thinner than a pixel, so it is drawn at one.

One honest note: how someone moves can still tell who they are, as a walk can. So Fitlify treats your moves as personal data, and they go only to a friend's PC you paired with by a code.

Try a taste.

Stand back from your camera, put your hands up and punch: a figure of your own 33 points hits the bag. It is a taste, a small pose model running in this tab, and not the game's own tracker.

The camera demo is shown live, on request.

What it promises.

Six classes to earn.

What you practise decides who your character becomes.

Gold is earned by moving and dresses your character. It is never sold.

In the works: the purse is built, the shop is not. The rate shown is an illustration.

How it is built.

For the engineers: one frame's path from the camera to the character, in Unity 6 and C#.

  1. The camera

    A webcam frame is read in memory on your PC. No picture is written to disk.

  2. The pose models

    Models running inside the game find 33 points of the body in that frame.

  3. The datagram

    Each pose is packed into 580 bytes: a 52-byte header, then 33 points of 16 bytes. A recording is a file of these, so a play session can be replayed byte for byte.

    This is what stays light. The pose models before this step still read every picture, and they are where the frame budget goes; the rules, a recording and every test after it work on these 580 bytes and never on a picture.

  4. The core

    Every rule, the counting included, lives in a library that knows nothing of the engine. Its tests run twice: inside Unity, and on plain .NET with no engine at all.

  5. The character

    The engine side stays thin: it reads what the core decided and moves a character.

The hard problems