r/ADSB • u/RepresentativeNice61 • 4d ago

Project Showcase: Software - Mostly AI Generated SkyTrace: a free ADS-B map project — looking for feedback

I built SkyTrace to experiment with browsing aircraft and airport information in one interface, rather than running an existing viewer. It’s free and needs no account.

For ADS-B users, I’d love feedback on the map controls and whether observed, estimated and missing data are clearly distinguished. Coverage depends on third-party feeds.

AI disclosure: I used Claude and Codex extensively for code, debugging and tests.

Site: https://opensky-flight-tracking.vercel.app/

Public repo, screenshots and commit history (since October 2025): https://github.com/amassias/OpenSky-Flight-Tracking

0 Upvotes

25% Upvoted

12 comments sorted by

8

u/elmarkodotorg 4d ago

what does your system do that, say, tar1090 or one of the commercial site frontends doesn't?

3

u/DontRememberOldPass 3d ago

Well for one it’s vibe coded…

0

u/maltesepricklypear 3d ago

Looks modern for one, tar1090 is great. But dates back to teletext 😂

1

u/elmarkodotorg 3d ago

I mean, there is retar by Jack Sweeney, and airplanes.live modded it too. It can look great with skins. And the features are pretty great.

Also now I'm sad that teletext is dead, thanks ☺️

8

u/Falcuun 4d ago

"I built"
"I used claude code extensively "

How are people this clueless and this deep into AI psychosis?

-3

u/Bob_Ross3346 4d ago

Beating your chest as in “I did everything manually” isn’t the flex you think it is.

6

u/rocksuperstar42069 3d ago

Yeah but ai slopping a knockoff that offers nothing new isn't useful. There are 10 of these posts a week. We can all do this too. Cool.

3

u/Bob_Ross3346 3d ago

Ok, but it would be just as annoying if someone built the same shit by hand.

1

u/badDuckThrowPillow 3d ago

The thing that's wrong is to make something that is basically a copy of something else and passing it as original.

Using AI to create something isn't bad on its own. All the people calling it "slop", could they actually be presented with source code and identify what makes the AI one worse? It takes a decent sw person to do that.

1

u/Fast-Aspect-2406 4d ago

Since you asked specifically about observed vs estimated vs missing: from the list and the map I couldn't tell how old any position is. Every row gets the same green "Airborne" dot whether the last fix was 2 s or 2 min ago. A small "seen 4s" on each row, and fading or hollowing the marker once a fix is older than 30-60 s, would answer that at a glance. If you interpolate between polls, drawing the estimated part differently (dashed track or outline icon) makes it obvious which is which.

Two other things I hit:

  • First load showed plane icons with callsign labels. A reload over the same area (northern France, ~1100 aircraft) showed plain dark dots with no labels. If that's a level-of-detail switch by count, a hint like "zoom in for labels" would help. If not, the icons didn't load.
  • At the same moment the bottom-left said "Live 1076 aircraft" and the panel said "In view 1134".

The list itself is nice. Reg, type and the climb/descent arrow in one row is a lot of info that stays readable.

1

u/maltesepricklypear 3d ago

That's actually pretty neat, thanks for sharing the source code. As that for me puts me off entertaining anything AI created, as it's always great to see the underpinnings 👍

1

u/wirelessnetizen 3d ago

Is there a way to dismiss the:
“Zoom in for more aircraft labels.
Outlined aircraft = estimated position • faded /
hollow = fix older than 60s or age unknown.” message?