Skip to content
VYLDOR

Proposed functions

Three controls, 28 ideas to test

The concept asks three things of you: pull the module out, feel a tap, press once. The list below combines planned core interactions with later research ideas. None has run on Vyldor hardware, because no physical prototype exists.

Uses planned parts
Would use components already considered in the concept; engineering and prototype validation are still required.
App only
Would not require another belt component, but the companion software has not been built.
Needs funding
Would need additional components, certification or an external receiver ecosystem before it could be promised.

Read this list as a design specification, not a changelog. None of it has run on hardware yet, because there is no hardware yet. The first group is what makes this different from a fitness tracker with a screen. The two after it are the everyday functions, in the order they get built.

01 · 8 functions

Research beyond the core

A belt is a long loop around the torso, can hold a large area of skin contact and sits near the body's centre of mass. Those properties create research questions, not validated advantages. Every item in this group is unbuilt and requires its own feasibility test.

  1. 01Needs funding

    Body-coupled authentication research

    Research hypothesis: body-coupled signalling might support deliberate touch-based authentication. Signal reliability, safety, false acceptance, privacy and the required receiver ecosystem have not been tested; it is excluded from the first prototype claim.

  2. 02Uses planned parts

    Gait authentication research

    Research hypothesis: waist-mounted motion data might support gait-based wearer verification. No population data, false-accept or false-reject rate, step count, privacy design or power budget has been validated.

  3. 03Uses planned parts

    Strap antenna research

    Research hypothesis: the strap's length might provide useful antenna geometry. RF performance, body loading, flex life, manufacturing and certification have not been simulated or bench-tested.

  4. 04App only

    Haptic pattern research

    Planned experiment: test whether timing between two haptic zones can communicate more than separate left and right taps. Recognition through clothing and movement has not been measured.

  5. 05Needs funding

    UWB ranging option

    Future option: ultra-wideband could support precise ranging, but it would add hardware, power, integration and security work. No Vyldor ranging or anti-relay implementation exists.

  6. 06Uses planned parts

    Belt-tension sensing research

    Research idea: a strain gauge in the buckle load path might measure changes in belt tension. Signal quality through clothing, movement, fit and temperature has not been tested, and no health claim is intended.

  7. 07Uses planned parts

    Wear-detection research

    Research idea: comparing inward- and outward-facing temperature sensors might help estimate whether the belt is being worn. Reliability and environmental sensitivity have not been tested.

  8. 08Needs funding

    Off-grid messaging research

    Long-term research direction: a separate low-frequency radio and strap antenna might support off-grid messaging. Range, antenna performance, power, regulation and the required user network are all unvalidated.

02 · 10 functions

The first ten

These are what the first version of the app is built around. If the belt only ever did these, it would still be worth wearing.

  1. 01App only

    Waist, tracked

    The number a doctor watches and no wearable reads, because nothing else is pulled tight around your middle.

  2. 02App only

    Meals without logging

    Tension rises through a meal and falls for an hour after. You do not write anything down, which is where every food app loses people.

  3. 03App only

    Breathing, all day

    The signal a sleep lab straps around your abdomen. No chest strap, because the belt is already the chest strap.

  4. 04App only

    Physical confirmation

    One deliberate press to approve anything you would not want happening on its own.

  5. 05App only

    Whisper Queue

    Anything that arrived while you were busy is held instead of interrupting, then read back in one go when you ask for it.

  6. 06App only

    Attention Firewall

    An allow-list for your body. You name who and what is permitted to reach you at all; everything else waits in the queue.

  7. 07App only

    L/R HapticTurn

    The hip nearest the turn taps a short pattern a few seconds before you need it. Left is left, right is right.

  8. 08App only

    Phone Leash

    One pulse if the phone stops answering while you are moving away from it. A reminder, not a tracker and not a security device.

  9. 09App only

    ContextMorph

    The same button and the same taps mean different things depending on what your phone is doing: on a call, in a map, on a camera.

  10. 10App only

    No-cloud mode

    Restrict the belt to whatever your phone can do on-device. Slower and simpler answers, nothing leaving the handset.

03 · 10 functions

Planned after that

All of these are software on the phone side, so they can arrive without changing the belt. They are queued behind the ten above.

  1. 01App only

    A tug nobody sees

    Pull the strap in a rhythm and the gauge reads it. An input with no button, and a silent way to call for help with your hand at your side.

  2. 02App only

    Read it back short

    A long message, email or page summarised out loud instead of read on a screen.

  3. 03App only

    Contact priority

    A named few who can always break through the firewall, with their own tap pattern so you know who it is before you answer.

  4. 04App only

    Media control

    Play, pause and skip without taking the phone out of a pocket or a bag.

  5. 05App only

    Camera shutter

    Trigger your phone's camera from where you are standing. The belt has no camera of its own and never will.

  6. 06App only

    Presentation control

    Advance a slide with one hand at your waist, with no clicker to hold or lose.

  7. 07App only

    Timers and reminders

    Set by voice, delivered as a tap at the hip rather than an alarm everyone in the room hears.

  8. 08App only

    Smart-home scenes

    One press runs a scene your phone already controls, so you are not unlocking a screen to turn a light off.

  9. 09App only

    Profiles

    Work, home, travel. Different rules for who gets through and what the button does, switched by you or by location.

  10. 10App only

    Find my phone

    One press makes the phone ring, for the times it is under a cushion rather than genuinely lost.

04 · 1 function

Would need hardware we have not committed to

Listed because people ask, not because it is planned. It is the one addition we have looked at and left out.

  1. 01Needs funding

    NFC in the buckle

    A tap target in the belt itself, for transit or door access. It is not in the current design and we will not imply it is.

Close view of the Vyldor buckle face: matte anodised graphite with the Vyldor mark etched tone on tone
One belt, three controls. The length of the list above is a software question, not a hardware one.

The app

Every one of these can be switched off

In the planned architecture, the belt itself holds no settings. It would vibrate, charge the module and report a button press. Everything else would be a rule on the phone: which contacts get through, what a left tap means against a right one, how strong the pulses are, what the button does in each app, and which of the functions above exist for you at all.

That is deliberate. A feature you cannot turn off is not a feature, it is an imposition, and a belt that quietly decided things for you would be worse than the phone it is meant to replace.

Body signalling and gait verification are unvalidated research directions involving biometric data. If either is developed, it would start disabled, with a plain explanation of what is stored and where, and a switch you control. A belt that quietly learned to recognise you without asking would be worse than no belt at all.

Being straight about it: we will build the apps if enough people want the product. It is a few months of writing plus ongoing support, and it is not work worth doing for something nobody is waiting for. The waitlist is how we find out, and it is the only reason it exists.

Which of these matters to you?

Join the waitlist and reply to the first email with the one function you would actually use. That is what decides the order they get built in.

Free to join. By submitting you agree we may email you about Vyldor, and nothing else. One click unsubscribes. How your data is handled.

Thinking about backing it instead? Read the investor page