Flighty Airports

A new “Flighty Airports” web view from the popular iOS flight-tracking app Flighty is drawing both praise for its polished design and detailed delay data, and criticism for limited functionality on the web, aggressive app-upsell, and some confusing UI choices. Frequent travelers and airline staff highlight Flighty’s real value in early, reliable notifications about delays, cancellations, and inbound aircraft, while others question the subscription price, lack of Android support, and gaps such as boarding-time visibility or low-cost carrier coverage. There is also debate over whether broad airport-level disruption maps and TV-mode displays add meaningful value for individual travelers or risk diluting the app’s focus on a user’s specific flights.

Overall reception

  • Many travelers, including heavy travelers and airline employees, describe Flighty as a stand‑out app they rely on regularly.
  • Others find it overhyped or “prettier than useful,” and some prefer FlightAware, Flightradar24, airline apps, or even iOS’ built‑in tracker.

Design and usability

  • Strong praise for the native iOS app’s polish, visual appeal, and thoughtful interactions; some call it a showcase of long‑term craft.
  • Counter‑views say it prioritizes aesthetics over clarity: tiny/low-contrast duration text, no or poor surfacing of boarding time/countdown, aggressive use of red for trivial delays, and “bubbly” fonts that feel unserious for stressful situations.
  • Map behavior is criticized: odd airport label priorities (e.g., smaller airports appearing before major hubs), labels blinking in and out on zoom/pan, and awkward iPad layouts.
  • The web “airports” site is seen as much rougher than the app, with overflowed text, confusing tables, and limited similarity to the core product.

Airports feature and web interface

  • Some like the new global airport disruption view, TV mode, and unified departure/arrival boards, especially for problematic airports or office displays.
  • Others fear it signals loss of focus from “my flights,” or question the practical value of aggregate delay stats.
  • A few point out inconsistencies in how airports are colored (e.g., “normal” vs “minor issues” not matching basic percentages) and that nearby-airport delays may mostly be spillover from a single problem hub.
  • Complaints that the web view hides detail behind the app, shows only a narrow time window, and resets the map on back navigation.

Data quality and notifications

  • Many report Flighty consistently beating airlines on delay/cancellation/gate-change alerts, sometimes by hours, enabling rebooking or better use of layover time.
  • Others cite notable glitches (e.g., flights shown as having departed early or wildly wrong delays) and argue there should be better sanity checks.
  • Some note that reliability depends heavily on airline data feeds; others suggest cross‑checking with airport data.

Use cases and perceived value

  • Heavy or professional travelers (crew, touring staff, frequent flyers) find substantial value: catching cancellations early, optimizing sleep and lounge time, knowing inbound aircraft status on the lock screen.
  • Light or leisure travelers are split: some gladly pay for reduced stress; others see little benefit over “on plane / not on plane” status or find the price excessive for a few trips a year.

Pricing and platform choices

  • App is iOS/mac‑only with a subscription model (weekly, monthly, annual, lifetime tiers). Some see this as justified by expensive data sources and the affluent, travel-heavy iOS user base.
  • Others are frustrated by the lack of Android support or confused by seemingly duplicated in‑app purchase entries.
  • Several argue focusing on one platform keeps quality high and complexity manageable; others believe an Android version should be feasible given reported revenue.

Requested or missing features

  • Frequent requests: boarding time/countdown, more reliable/nuanced delay coloring, hotel reservation integration, longer airport boards, better airport label stickiness when scrolling, improved airport selection logic, and security/TSA wait-time estimates.
  • There is skepticism about the feasibility of accurate security-line tracking without official data or heavy privacy trade‑offs.