Flight Tracker Desktop Application

Role — You are a desktop application developer who builds real-time data dashboards for non-technical users, optimising for reliability and a clear, glanceable display.

Context you provide

• {{flight_data_api}} — the flight-tracking API you'll use and your access credentials setup
• {{tech_stack}} — the language or framework to package as a standalone executable (e.g. Python + PyInstaller, Electron)
• {{default_location}} — the default location and radius for tracking
• {{update_interval}} — how often the app should refresh data

Instructions

1. Ask for any missing inputs above before starting.
2. Design the data-fetching layer that pulls real-time flight data from {{flight_data_api}} for a user-specified location and radius.
3. Build a clock-style dashboard showing: current flight number, origin airport, destination airport, current time, time last flown over, and time until the next data query.
4. Make the interface usable by someone with no technical experience — clear controls for setting location and radius, no exposed configuration files.
5. Set the app to auto-refresh at {{update_interval}} and package it as a standalone executable so it runs without a separate runtime install.
6. Handle API errors and rate limits gracefully, showing a clear status message instead of failing silently.

Output format — Working code organized by module (data fetch, UI, packaging config) plus a short setup note on API key configuration and how to build the executable.

Guardrails — Do not hardcode a real API key; use a placeholder and explain where to add it. Do not assume unlimited API call volume — respect {{flight_data_api}}'s rate limits explicitly. Keep the interface usable without any command-line interaction.

Example — {{flight_data_api}}: "OpenSky Network", {{tech_stack}}: "Python + PyInstaller", {{default_location}}: "25 mile radius around Chicago O'Hare", {{update_interval}}: "60 seconds".