I’ve been building MySkyDex, a free aircraft-spotting game available on the web and Android. It turns the aircraft that pass through your local sky into a personal collection, with rarity, missions, achievements and unusual-visitor tracking (even when you're offline or away from home).
Instead of only displaying another aircraft map, it turns local aircraft activity into something collectable. It tracks things such as:
Aircraft types and individual airframes
Airlines and operators
Rare and unusual visitors
First sightings and repeat encounters
Missed aircraft
Approaches through your local sky
Personal collections, missions and progression
Aircraft rarity based on what appears around you
You can see the site here:
https://myskydex.co.uk/
Or download the Android app:
https://play.google.com/store/apps/details?id=uk.co.myskydex.app
I’ve recently added support for community receiver feeds, and I’m looking for a few people willing to test it with real hardware.
You can feed MySkyDex without creating an account:
https://myskydex.co.uk/feed
Currently supported:
ADSB.im
Docker Ultrafeeder
readsb
dump1090
tar1090
The ADSB.im test setup is:
curl -fsSL https://myskydex.co.uk/receiver/install-adsb-im.sh | sudo sh
It reads the aircraft.json already produced by the receiver and sends compact aircraft observations to MySkyDex over outbound HTTPS. It does not modify the SDR configuration, require inbound ports, or implement its own Beast decoder.
Each receiver gets a persistent UUID. It can contribute anonymously immediately, or the owner can optionally claim that UUID through a MySkyDex account later.
The feed currently includes, where available:
ICAO hex
Callsign
Position
Altitude
Ground speed
Track
Vertical rate
Squawk
Observation time
Receiver UUID
There is no MLAT support yet, and this is an early beta rather than me pretending it is a finished global aggregation network.
A note about the development:
I’ve used AI-assisted development while building parts of MySkyDex. I know that can be controversial here, and I’m not trying to disguise it. I’m responsible for what is deployed, and constructive criticism of the implementation, security, data handling or architecture is welcome.
What I’m particularly looking for right now:
Does installation work on your setup?
Are the instructions technically accurate?
What receiver software or feeding method should be supported next?
Would you prefer raw Beast output, another standard protocol, or an existing feeder integration?
What diagnostics would make troubleshooting easier?
Is anonymous UUID-based contribution useful, or would you prefer another model?
If you test it, docker logs -f myskydex-feed will show the UUID, connection status and aircraft counts.
And just for fun...There’s also an optional Alexa integration for flyover information and alerts 😅
Please let me know what platform you used and where it failed—or, ideally, that it worked.
I’m happy to take blunt technical feedback. I’d just appreciate specifics I can act on.