StreetSparrow is a community app for the place you actually live: a feed for your block, groups for your building or street, and private messages with your neighbors.
And when the power or the network fails, it does not go dark. Your phone quietly passes messages to other phones nearby, so the neighborhood can still talk.
Join the list and you will be first in when the beta opens in your area.
StreetSparrow
Neighbors. News. Together.
Lost & found
Reunite a wandering dog in minutes
Outage-proof
Keeps working when the network fails
Private messages are encrypted end to end. What you share stays between you and your neighbors.
A genuinely useful neighborhood app first — everything else works quietly in the background.
Lost dogs, a couch on the curb, the water main on Oak Street, who has a ladder. Posts stay in the area they were written in, so what you see is genuinely near you.
Your building, your street, the school run, the community garden. Small spaces for the people who actually share the place with you.
One-to-one messages, encrypted end to end. You can reach someone whose username you know, wherever they are.
Your feed is sorted by distance, so the closest and most useful things rise to the top. What you see is what your neighborhood is actually talking about.
Four taps at the bottom: what's nearby, the spaces for your area, your messages, and your settings. That's the whole app.

Nearby
See who and what is on your local network right now.

Spaces
Commons plus topic spaces for your area — no joining required.

Commons
The block's conversation: road closures, free firewood, a lost cat.

Settings
Your nine-digit number and your pinned area, in plain language.
The same spaces and the same conversations show up on an iPhone, an Android phone, and on small handheld LoRa devices. A message written on a phone can travel over radio and arrive on a neighbor's handheld blocks away — and back again.




StreetSparrow uses the same path every day, so the version that works in an outage is the version you already know and already have friends on. It simply keeps going when other apps go quiet.
01
Normal days
The app uses the internet like any other app. Fast, familiar, ready out of the box.
02
The internet goes out
Your screen looks exactly the same. Your phone quietly starts passing the same messages directly to nearby phones over Bluetooth and Wi-Fi.
03
Days into an outage
If anyone nearby has a small radio node, messages hop between blocks — and a single reconnected phone can carry the neighborhood's mail out to the world.
In a real emergency, the messages that matter most are between neighbors. The Oak Street bridge is out. We have a generator, come charge your phone. Has anyone seen the Kowalskis?

In a real disaster, most people have a charged phone and little else, so that is the case the app is designed around. Every radio node and solar relay nearby makes it dramatically better — and two phones alone are enough.
One app for the whole neighborhood. What you see depends on how deep you want to go, and you can change your mind at any time.
A local feed, groups, direct messages, lost pets, mutual aid, store and road status.
A friendly neighborhood app that happens to be unusually hard to knock over.
Coverage walks, signal history, heard nodes, protocol paths, diagnostics.
Your existing hardware becomes first-class neighborhood infrastructure.
Node health, airtime, coverage, power, bridge status, drills.
Concrete, measurable neighborhood resilience you can improve.
Recognizable identity, status publishing, priority for genuine life-safety messages.
Recognition is granted by the local community, and priority applies to genuine life-safety updates.
StreetSparrow is in pre-release, and the beta opens by invitation, neighborhood by neighborhood, while the protocol is being settled. Put your name down and you will be invited when a build is ready for your area.
Invitations go out first to neighborhoods on the list.
If your block, building, or school wants to try this, say so now so the pilot can be designed for a real place.
If you already run repeaters or map coverage, your hardware is what this is designed around. Tell us what your area looks like.
Read the schemas, run the conformance vectors, and write a fourth implementation. No permission needed.
Contact details to be published.
Everything below is optional reading. It is here because the design is the product, and anyone should be able to check it.
Every device works out which hexagonal cell of the world it is in (H3, Uber's open grid). Those cells are the neighborhood graph. A public post is stamped with the cell it was written in and a number of geo hops it may travel, and that alone bounds who sees it — a property of geography rather than a follower graph, an algorithm, or a server's opinion.
Internet, Wi-Fi, Bluetooth, and LoRa radio all carry the same signed message objects under the same rules. Addressing stays identical on every transport, and a relay acts as a fast peer — identity and trust live with the sender, so losing a relay only costs reach.
Public posts are addressed by place and stay local. Direct messages are addressed by cryptographic identity, are encrypted end to end, and can cross any distance to someone whose username you already know. The two namespaces stay separate by design. During an outage, one surviving gateway can carry the mail for a whole disconnected neighborhood while every message stays sealed.
The overwhelmingly common configuration in a disaster is people holding charged phones, so that is where the guarantee holds. Every radio and fixed node above that floor makes the network dramatically better.
Losing the internet reduces speed and capacity, while the meaning of nearby stays exactly the same. Cell distance is semantic rather than a prediction of radio range — a single LoRa transmission may jump three cells.
No power, no internet, no LoRa, no prior setup. Message exchange still happens.
An Android phone in range gives the cluster a beacon and an on-demand Wi-Fi island.
One battery-powered node gives the neighborhood a memory: a message left at noon reaches someone walking past at midnight.
A solar node carries that memory through day seven, and more radios give the area a graph.
A trickle to the outside world. Sealed messages leave when a path appears; nobody in between can read them.
Any implementation must reproduce them byte for byte. The vectors are the contract.
T-Deck device firmware (C++), an iPhone client (Swift), and an internet relay (Rust), sharing no code.
Protobuf schemas and wire registries for the Sparrow Object Protocol (SOP). Independently implementable, royalty-free.
Real implementations run against each other as processes and as physical radios on a desk, leaving a folder of evidence per run — including a no-path control.
The Meshtastic and MeshCore ecosystems already provide open firmware, inexpensive radios, and people who install repeaters and map coverage. StreetSparrow turns that infrastructure into visible public value and a much larger community to serve. Existing stock users stay reachable without migrating or reflashing anything.
One transceiver time-shares between Meshtastic and MeshCore with measured, disclosed loss. Continuous dual-network infrastructure uses two radios.
Licensing: reference implementations GPL-3.0-or-later (the iPhone client is MPL-2.0); schemas, registries, and conformance vectors Apache-2.0; documentation CC BY-SA 4.0.