Case Study
SynchroCity
Digital SynchroCity
Bluetooth-powered social discovery. Matches compatible people within 50 meters using over 30 psychological frameworks of resonance — computed locally, never transmitted. Real encounters instead of swipe theater. Built for builders, introverts, and neurodivergent thinkers.
The Problem
An epidemic of loneliness in cities of millions
The US Surgeon General called it an epidemic. More than half of adults describe themselves as lonely. One in four have zero close friends — double the rate from 1990. Time spent at "third places" — the cafes, bookstores, and bars where strangers used to become friends — has collapsed. And the apps built to solve this have made it worse.
Dating apps reduce human compatibility to a photo and a swipe. LinkedIn reduces it to a job title. Algorithmic feeds reward performance, not presence. The person who could become your cofounder, your mentor, your closest friend was in the same cafe as you last Tuesday. Neither of you knew.
The technology to fix this has existed for a decade. Bluetooth Low Energy in every pocket. Enough compute power on a mid-range phone to run real psychological models locally. What didn't exist was the will to build something that respects the user instead of farming them.
By the Numbers
30+
Psychological Frameworks
49
Service Modules
50m
Proximity Range
6
Feature Categories
5
Depth Layers
15 min
Beacon ID Rotation
0
Location Data Transmitted
E2EE
All Communication
$0
Free Tier, Forever
The Solution
Proximity, not profiles
SynchroCity inverts the social app. No profile to curate. No photos to rank. No feed to scroll. You set a transmission — what you're working on, what you're curious about, what kind of connection you're seeking — and your phone broadcasts an encrypted fingerprint over Bluetooth Low Energy. Other phones running the app within 50 meters do the same.
When two transmissions resonate, both devices compute it at the same time, independently, on-device. If the score clears the threshold, you each feel a haptic pulse. Look up. They're across the room. You decide what happens next.
This is the oldest form of human connection — being in the same place at the same time — finally given the technology it deserves. Real encounters instead of swipe theater. Chemistry instead of curation.
How Matching Works
Over 30 frameworks. None of your data on our servers.
The resonance engine draws on over 30 psychological frameworks that span fifty years of validated research. Big Five personality. Schwartz values theory. Jungian cognitive functions. Attachment theory. Kegan developmental stages. Polyvagal theory. Flow theory. Broaden-and-build. Self-determination theory. Interpersonal circumplex. Complementarity hypothesis. Optional astrology for the synastry-curious.
Most apps ask you to describe yourself. People are unreliable narrators of their own personalities. SynchroCity also watches how you actually engage — which pings you respond to, which glyphs you leave, when your attention deepens — and builds a behavioral fingerprint that reveals the parts of you that don't fit neatly into a bio.
Every inference happens on your phone. Every comparison happens on your phone. The server never sees your personality, your location, or who you met. The math runs where you are. The frameworks themselves sit on top of a broader on-device services layer — proximity, signaling, safety, memory, surfacing, and monetization all isolated into their own modules, so the resonance engine stays a single focused responsibility rather than a tangled monolith.
Privacy as Architecture
Safety isn't a feature — it's the foundation
Beacon IDs rotate every fifteen minutes so no one can follow a device across a city. Resonance scoring happens on-device, so the server has nothing worth subpoenaing. Communications use X25519 key exchange for end-to-end encryption — meaning Moonlit Social Labs can't read your messages even if compelled. Metadata gets stripped before anything leaves the device.
A buddy beacon lets a trusted friend monitor encounters in real time. Boundary normalization makes "not right now" feel natural instead of confrontational. The glyph reputation system surfaces signal without storing a surveillance record. Every one of these decisions sits in the architecture, not in a privacy policy that could quietly change next quarter.
The design rule is simple. If a feature requires the server to know where you are, who you are, or who you met, the feature doesn't ship.
Privacy engineering. Not privacy theater.
Progressive Disclosure
Five layers, earned over time
SynchroCity doesn't dump your personality on a screen. It unfolds in five layers: Surface (interests, current project), Context (skills, domain expertise), Character (values, thinking style, communication), Shadow (behavioral patterns, growth edges), and Resonance History (glyph patterns, encounter outcomes). Each layer is revealed only as two people choose to go deeper, and only to each other.
The app grows with you because it's measuring you growing. A connection made at the Surface layer looks different six months later at the Character layer, because by then the behavioral fingerprint has been sharpened by a hundred small interactions neither of you had to think about.
Progressive disclosure is also a safety mechanism. Strangers don't need access to your shadow the first time they're in your range. Depth is earned in a way that mirrors how humans already decide who gets to see more of them.
The Hard Parts
What made this difficult
- BLE mesh that survives mobile background mode iOS and Android both aggressively kill Bluetooth activity when an app is backgrounded. Building a proximity experience that keeps detecting, scoring, and pinging while the phone is in a pocket — without draining the battery in an afternoon — meant designing a duty-cycled scanning strategy that negotiates between radio wake-ups, OS-level constraints, and the user's reasonable expectation that their phone still works tomorrow.
- On-device personality modeling without melting the battery Over 30 psychological frameworks, inferred from behavior, compared across every nearby transmission, in real time, on consumer hardware. The whole thing has to stay within a thermal and energy envelope that doesn't announce itself to the user. The win was making the expensive computation lazy and the cheap screening aggressive — most candidates never make it to the full scoring pass.
- Rotating beacon IDs without losing connection continuity The privacy requirement says every device reshuffles its identifier on a fifteen-minute clock. The usability requirement says an in-progress encounter shouldn't suddenly forget who it was talking to. Threading that needle meant a handoff protocol that preserves an ephemeral session identity across rotations without ever exposing a long-lived one to the network.
- Privacy-preserving safety infrastructure Buddy beacons, boundary normalization, glyph reputation, and panic flows all have to work without a central server that knows who is where. A platform that treats abuse as a real problem normally leans on a surveillance stack to catch it. Building equivalent protections with zero server-side visibility into location or identity is the research problem, not the feature list.
- Accessibility-first UX for neurodivergent thinkers The target user is someone whose best conversations happen when small talk isn't the price of admission — the introvert, the neurodivergent builder, the person in transition. That shapes every micro-interaction. Haptic intensity scaled to resonance strength. Progressive disclosure that never demands a bio. Consent prompts phrased so "not right now" carries no social cost. Design decisions as accessibility engineering.
- Relay fallback without giving the server anything worth having Bluetooth LE is unreliable — iOS backgrounds it, crowds attenuate it, and two phones across a noisy bar might miss each other even at two meters. A WebSocket relay fills the gap for edge cases. The hard part is making a server useful without making it trustworthy: the relay carries sealed traffic between ephemeral beacon IDs, can't decrypt a single byte, can't correlate sessions across rotations, and has nothing to hand over under subpoena except encrypted bytes it couldn't read anyway.
Architecture
How it's built
Bluetooth Low Energy as the discovery layer. Every device broadcasts an encrypted transmission fingerprint with a rotating beacon ID. Every device runs the resonance engine locally, so the comparison never leaves the phone. Communications use X25519 for key exchange and end-to-end encryption; the server is a relay, not a reader.
The whole system is specified as an open protocol — the Tavern Protocol — so proximity-based human discovery can outlive any one app. Adaptive power management handles the battery story. Haptic feedback scaled to resonance strength handles the notification story. A glyph system handles the reputation story without needing a surveillance log. The web experience is live in alpha; mobile apps are in development.
Verdict
The anti-swipe
SynchroCity is a bet that people are hungry for something every existing social app has trained them to forget: that the most important encounters of their life are likely to happen within arm's reach of someone they don't know yet. Not in a feed. Not in a DM. In a room. With signal.
The platforms that profit from attention will never build this. The economics don't work when the product is a two-minute conversation that happens offline. So it had to be built by someone who thinks the loneliness epidemic is a design failure, not a market opportunity.
Launched to web. Mobile in development. The mesh is forming — the only question is whether you're broadcasting.