Aviate 1.2

✈️ Aviate 1.2

Aviate 1.2 is rolling out.

This release is about the travel record you keep after scanning the boarding pass. Trips now follow your account, saved travel stays useful without a connection, and Labs gives me a cleaner way to test features with real users before calling them finished.

Trips now follow your Aviate account

Until now, a custom Trip was still partly tied to the phone where you created it. Aviate 1.2 stores the Trip name and its flight grouping with your account instead.

Existing device-only Trips are migrated automatically. If your account includes Flight History, you can also turn older flights into a Trip, so a journey does not have to be upcoming to stay organized.

This sync is for the core Trip itself: its name and the flights grouped inside it. It does not make every locally attached Trip detail a cloud document. I would rather be exact about that than imply more than the feature does.

Saved travel stays useful offline

Airport connectivity is not famous for being reliable, up until recently Aviate had Offline mode, but it did not work as well as anticipated, so we decided to fix it.

After your data has loaded once, Aviate can still show saved Trips, boarding passes, and Passport. Accounts with Flight History access can also reopen saved History, including durations calculated from the saved schedule. The app clearly says when it is showing saved data instead of pretending that an old value is live.

This is offline viewing, not full offline editing. Adding, moving, or removing server-backed Trip data still needs a connection.

Private Flight Labels, through Labs

Profile → Labs now shows experiments available for your Aviate version. You can opt in or out and leave a simple thumbs up or down in order to gather more feedback from users.

The first big experiment in this release is Flight Labels. They are rolling out through Labs for Aviate Pro members and eligible grandfathered accounts.

You can create private labels such as Work, Family, or Mileage Run, then apply one to any flight you own in Aviate. Labels appear across Trips and Flight History, and each one can handle Passport in one of three ways:

• Keep its flights in your main Passport
• Give the label its own Passport and statistics view
• Leave those flights out of Passport statistics

That means a work-heavy year can stay in your history without taking over the personal Passport you share. Shared and group flights cannot use private labels, and Flight Labels are not currently available on enterprise profiles.

Labels sync with your Aviate account. You can also choose which labels may use live cards and flight updates while the account remains eligible and notifications are allowed.

This was a heavily requested feature to track family flights without adding them in the Passport, or for Crew members to have a separate Passport for their Work flights as to their personal ones. Hopefully you enjoy it!

Labs also includes an optional Material You color treatment for connections. Labs is for testing product ideas, not exposing Aviate's control panel.

Passport and History have a better memory

Passport, Flight History, and Trips now use a more consistent record of completed travel. That matters when the same flight came from a boarding pass, a manual record, or an import.

You can also choose the airport printed as Issued At in Passport. Set one yourself or leave it on Auto and Aviate will derive it from your all-time completed travel. The same airport carries into the Passport card you save or share.

For accounts with Flight History access, large histories no longer have to arrive in one enormous response. Aviate loads older records as you scroll and continues searching those pages when you filter.

Imports and the details on your pass

The CSV importer now recognizes the standard OpenFlights export alongside the formats Aviate already supports.

If Aviate scanned your name incorrectly, or you simply want it displayed differently, you can correct it inside Aviate. This changes how the name appears in Aviate and on boarding-pass cards you save or share, not the airline reservation or barcode. You can restore the scanned name at any time.

Confirmation numbers are also easier to use: choose the copy action beside one instead of selecting it by hand.

Live Flight Updates

Android Live Flight Updates now follow one current personal flight at a time. When an account has Flight Notifications access, including applicable grandfathered access, Aviate checks the selected flight about every five minutes and keeps it in an ongoing notification while active.

Aviate, its ongoing notification, and Wear OS now agree more consistently on which flight is current and how far along it is. Tapping the notification opens the matching flight; if Aviate cannot identify it confidently, it falls back to Trips.

Live Flight Updates remain opt-in. They require the account-level consent and Android notification permission, and they are not second-by-second tracking.

The smaller changes you still notice

These smaller changes matter too:

• Flight-detail actions stay reachable on narrower screens
• The Trip Card widget adapts better to smaller and resized layouts
• Foldable layouts and navigation transitions are steadier
• Flight summaries on the main map follow your selected language
• Connection timing colors are more consistent
• Boarding-pass scanning opens the camera more reliably
• Repeated calendar syncs avoid creating duplicate events
• Phone and Wear OS agree more reliably about the current flight
• Manual and cached flights show more reliable timezone-aware durations
• Airport maps handle more bad data without crashing

Download Aviate on Google Play