Aviate 1.0.0 Prelease 6
In short
✈️ Aviate 1.0.0 Pre-Release 6
Pre-Release 6 is probably one of our biggest releases
New features
- Gate predictions for Aviate Pro when we don't have an official gate yet
- Import up to 25 boarding-pass screenshots at once on Android
- Keep aircraft, registration, seat, and cabin class from supported CSV imports
- Fill in missing aircraft or tail details on flights you own
- Search more than 8,250 airports by IATA, ICAO, name, city, or region
- In-flight trivia is now available to every signed-in traveler
Improvements and bug fixes
- Live tracking is matched against the exact date and route more carefully
- Home, widgets, and notifications move on from completed flights properly
- Check-in reminders no longer arrive too early for some travelers
- The turbulence card no longer calls a flight "Smooth" when we don't have enough data
- Missing seat data no longer appears as
undefined
Removed
Expense tracking and trip budgets have been removed. Updating also removes their locally stored records and receipt images. If you still have an older build with anything important in Expenses, save it before updating.
✈️ Aviate 1.0.0 Pre-Release 6
Pre-Release 6 is a big one. A few features are completely new, a lot of the flight-tracking work was rebuilt, and importing old flights should be much less annoying.
Gate predictions
Aviate Pro can now show a likely departure or arrival gate when we don't have a confirmed one yet. It is clearly marked as Predicted, and the confirmed gate replaces it the moment we get one.
If one exact gate would be misleading, Aviate can show a small group or range instead. If there isn't enough useful history, it shows nothing. An empty field is better than a confident guess based on bad data.
Import more than one boarding pass
You can now pick up to 25 boarding-pass screenshots and import them in one batch. Aviate processes them one by one, catches duplicates, asks for a year when an older pass needs one, and gives you a summary at the end.
CSV imports also keep more of what was already in the file: aircraft type, registration, seat number, and cabin class. Re-importing an existing flight fills only missing details instead of creating another copy or replacing something you edited later.
A much better airport database
The airport database now covers more than 8,250 airports. Search works with IATA codes, full ICAO codes, airport names, cities, states, and regions. Results also have better city and country formatting, which should mean fewer blank or confusing rows.
This new data also covers recent airport renames; you know which one we're talking about.
It will also give Aviate a much wider coordinate and timezone coverage. That matters for local departure times, cross-midnight flights, widgets, notifications, and matching the correct flight when the same number operates more than once.
Flight tracking that is less willing to make things up
Flight status and position data are now matched using the exact date and route. This reduces the chance of a return leg or another day's flight appearing as yours.
Tracking can also distinguish a live position from a last-known or unavailable one. On the main flight map, Aviate keeps the last real track when fresh data is unavailable. Time-based progress in live notifications is now labeled Estimated instead of looking live.
Completed flights also stop hanging around on Home and in widgets, and check-in reminders now stay inside the intended 24-hour window.
Smaller fixes
- The turbulence card no longer defaults to "Smooth" when useful data is missing
- Missing seats no longer show up as
undefined - Cross-midnight and timezone handling has been tightened up
- Repeating flight numbers are matched more carefully
- In-flight trivia is now available to every signed-in traveler
Expenses have been removed
Expense tracking and trip budgets have been removed from this pre-release. The update also removes their local records and saved receipt images during migration.
If you still have an older build with expense data you care about, save it before updating. I don't want that hidden at the bottom of a changelog after the fact.
Enjoy 😉