SyncSense
Ambient interaction layer

The phone was only
the control panel.

SyncSense turns InSync signals into haptics, audio and spatial cues — so connection can stay in the real world instead of pulling people back into a screen.

It does not replace consent. It carries the moment after a signal: subtle cue, wave, accept, shared context, soft reveal and lightweight conversation support.

What SyncSense does See Meeting / Dating See SyncField™
SyncSense concept image with Veyra, Lucas, ambient cues and wearable interaction
System language

Three layers. Three roles.

InSync becomes much clearer when the layers are separated. SyncField detects presence. InSync handles consent and signal logic. SyncSense carries the interaction into the field.

⌁
SyncField™ The proximity layer. It detects anonymous, opt-in overlap before identity, maps or profiles.
◎
InSync The consent and signal protocol. It checks intent, visibility, context and mutual action before reveal.
◌
SyncSense™ The ambient interaction layer. It turns signals into haptics, earbuds, glasses and soft UI so the moment stays in the real world.
Core shift

Not a notification layer. An interaction layer.

SyncSense should not only react at the exact moment of a signal. After a mutual signal, it should gradually take over parts of the phone UI so users do not need to look down again.

Signal cue Wave Accept Shared context Soft reveal Conversation cue
The phone configures the connection.
The wearables carry the moment.
Interaction stack

How SyncSense carries the moment.

📳
Haptics The first layer. Gentle pulses for weak, medium or mutual signal states — without pulling attention into the screen.
🎧
Earbuds Soft audio cues and later spatial audio hints. Enough to feel a change, not enough to become a loud notification system.
👓
Glasses The live interaction layer. They can show wave/accept, first signal summaries, shared tags and reveal cards — without face targeting.
📱
Phone The control panel. Settings, privacy, modes, history and deeper controls remain on the phone — but not the whole moment.
After the signal

What can move off the phone.

Before mutual consent
  • anonymous cue
  • signal strength
  • wave prompt
  • accept / ignore
After mutual consent
  • shared tags or context summary
  • soft reveal card
  • conversation cue
  • lightweight opener support
Guardrail: SyncSense should never become a people radar. No names above heads. No face targeting. No public map. No exact people tracking. Only consent-first, anonymous field cues that gradually unlock more interaction.
Why it matters

Ambient connection instead of more screen time.

Most apps still assume the phone is the whole stage. SyncSense changes that assumption. The signal starts in the field, and the interaction should stay in the field as long as possible.

Real world first Consent-first Screen-light Spatial
InSync should not make people look down at their phones.
It should help them look up at the world.
Roadmap

Build trust in the right order.

MVP 0.1Screen prototype: clickable demo, consent flow, concept validation.
MVP 0.2Haptic prototype: phones translate weak, medium and mutual states into touch patterns.
MVP 0.3Audio cue prototype: earbuds deliver subtle, non-creepy ambient cues.
MVP 0.4Glasses concept: anonymous spatial UI for wave, accept, summary and soft reveal.
MVP 0.5Real proximity: BLE/UWB-backed two-device tests where technically supported.
MVP 0.6Event / venue pilot: use SyncSense in a real density environment.
Site structure

Where SyncSense lives.

/insync/The short overview and routing layer.
/insync/dating/The primary use case: Meeting / Dating through signals, context and consent.
/insync/dating/syncfield/The proximity layer.
/insync/syncsense/This page. The ambient interaction layer.
SyncSense™ — wearables carry the moment.