Improve flight widgets

dreifach

When picking someone up from an airport recently, I thought of a few improvements that Kagi Search's flight widgets could use. See the below screen recordings for reference.

QR016

BA374

Potential Improvements

Do not display the same flight leaving on different days, at least using the current UI. The LLM summary is misleading in that it infers there are two different flights with the same flight number, when in fact there is one flight number with flights leaving on different days. My preference is to only show one flight (the soonest/current one), and then to have an option to click through to other future days (like how you can click through Wikipedia's widget to different Wikipedia pages without leaving Kagi Search).
Stylise the information boxes.
- Make the Departure/Arrival text bold.
  - Change the wording of the scheduled and actual departure/arrival dates/times so that it is clear that the full day and date (e.g. Monday, December 15) refers to the actual departure/arrival. I would change the wording to "Scheduled" and "Actual", and put the day/date next to the Departure/Arrival heading.
  - Add colour coding and +/- signs for delays and early departures/arrivals.
While seemingly a bug, the arrival gate number did not display in the BA374 screen recording.
Remove the LLM summary. It is superfluous in this context, needlessly duplicating the information that is already there (which could itself be displayed more clearly).

All these small improvements would greatly add to the ease of using flight widgets and parsing information quickly. It would also save a few tokens.

GravityMan

I agree with many of the points you make about the UI, especially the LLM summary.

Re: the bug/data accuracy, as someone who uses the Flighty iOS app and follows their changelog closely, aggregating and correctly outlining the data, even with the flight number, can be painful from airline to airline. I doubt the Kagi team will be able to make any significant improvements without sinking serious dev time or paying for data that isn't public.

RoxyRoxyRoxy

We have an overhaul of the flight widget planned, so thanks for the input on this!

dreifach

RoxyRoxyRoxy Out of interest, any indication on the timeline for this?