Yet Another Digital Logbook Thread — Except I Built This One

This is awesome. From a developer tech-nerd side, what did you build this with? REACT, Bootstrap? Just curious, it looks fantastic.
 
This is awesome. From a developer tech-nerd side, what did you build this with? REACT, Bootstrap? Just curious, it looks fantastic.
Thanks! Much appreciated!

Windows is Python with PySide6/Qt Widgets and custom styling. The Mac app is Swift/SwiftUI with some AppKit, and the iPhone/iPad version is also Swift/SwiftUI.

They all use local SQLite databases, so the core logbook works offline, with cloud sync between devices. Each platform has its own interface, while I keep the underlying data model and logbook rules consistent across them. On the server side, a shared cloud backend handles accounts, licensing, and cross-device sync, while each app keeps its own local logbook database.

I wanted the desktop versions to feel like desktop applications and the phone version to work comfortably on a phone. Getting imports, historical time zones, flight-time calculations, and syncing to behave has been the bigger adventure. Standardization between all three has also been an "interesting" challenge. There’s a surprising amount hiding behind a logbook!
 
Is this for United Airlines only?
Not at all. Like K said, focused on United for airline schedule importing, but it’s certainly an all purpose logbook. ACARS picture capable, a good historical importer, and multi-platform sync capabilities. FC VIew/ Flica integration planned in the near term.
 
Not at all. Like K said, focused on United for airline schedule importing, but it’s certainly an all purpose logbook. ACARS picture capable, a good historical importer, and multi-platform sync capabilities. FC VIew/ Flica integration planned in the near term.
What is ACARS picture capable?

Congrats on the app. I’m thinking about it.
 
I can't import my logbook because my logbook does not use separate columns for departure airport and arrival airport. It's one column.

I could be doing it wrong by the CCS+ calendar sync doesn't seem to import any details about the flight like crew member names or tail numbers?
 
I can't import my logbook because my logbook does not use separate columns for departure airport and arrival airport. It's one column.

I could be doing it wrong by the CCS+ calendar sync doesn't seem to import any details about the flight like crew member names or tail numbers?
For CCS, calendar sync absolutely won't provide those things because United deemed fit not to provide them. There's a Help button in the CCS area that brings you here: Digital Pilot Logbook User Guide | Blue Deck. It explains United's limitations and how I've designed around it. Next to the Cal Sync tab you'll see two others - Flight Time History and CCS Logbook. Either of those will bring in the rest of the data.

I know it s a pain in the butt, but it truly is the only way with what UA IT provides. There's also a link in the Help area that shows a video where I demo how you can log an entire UA trip in under two minutes. Once you get used to it, it's pretty painless and efficient.

For the one column only route type logbooks, I'll reach out to you via PM - easy fix.
 
Back
Top