Nearby, but not trackable
People see that someone is in the same broad radius. They never see a live pin, address, route, or exact venue unless both choose to share more.
Start avatar-first with simple prompts. Reveal names, photos, or places only when both people choose it.
Radius is for people who notice someone nearby and freeze. No swipe deck. No public rejection. Just a smaller first move.
People see that someone is in the same broad radius. They never see a live pin, address, route, or exact venue unless both choose to share more.
Profiles start with a simple avatar, a first prompt, and tone. Photos come later, after interest is mutual.
If one person wants to reveal more, the other person never gets put on a public stage. A no stays quiet.
The app gives people a reason to talk before they judge each other like a thumbnail.
Bars, coffee shops, events, campuses, meetups, and anywhere people are close but not quite talking.
The product should prove one thing: avatar-first nearby conversation can feel easier than walking up cold.
Choose a broad nearby area. The app buckets distance and refreshes slowly to avoid tracking.
Each chat begins from a simple question, not a photo judgment. People can pass without penalty.
Either person can request a photo, first name, or meetup details. Nothing changes unless both accept.
Mute, block, report, and end chat are visible from the first screen. Safety is not buried in settings.
Radius is a full product, not just a chat room. The app needs matching, consent, moderation, and a careful launch plan.
The first build should include distance buckets, pseudonymous avatars, prompt-based chat, mutual reveal, age gate, moderation queue, reporting, and invite-only pilot controls.
Later versions can add event mode, friend groups, audio intros, time-limited visibility, verified venues, and a paid privacy tier.
Pseudonymous social apps fail when safety is added later. Radius needs the guardrails before the invite list grows.
Show broad proximity bands. Never expose exact pins, live movement, or venue-level presence.
Photos, names, and meetup details require two explicit yeses. A declined reveal stays private.
Block, mute, and report should sit in the chat header. Users should not hunt for safety tools.
Start with age gating, invite controls, and a narrow geography before opening to a wider market.
Cap first messages, repeated reveal requests, and low-crowd visibility so one person cannot map or flood the room.
Reports should create reviewable evidence without exposing private location history to other users.
Radius should launch as a tight local test, not a national dating app on day one. The goal is to learn if people feel safer starting with conversation.
Discuss the pilot