How we're building Falcon
Every logbook starts with some boring decisions about tech. Here's why we picked what we picked.
Why Flutter
We're a small team. We can't afford to write the app twice - once for iPhone and once for Android. Flutter lets us write it once and ship it everywhere: phones, tablets, desktops, and the web.
What that means for you:
- The app works the same on an iPad and an Android tablet
- You can log flights offline, right after you shut down, no signal required
- Updates land on every platform at the same time
About the backend
Running your own server is not for everyone. If you just want to log flights, you shouldn't have to become a sysadmin.
Falcon gives you options:
- Falcon Cloud - managed hosting, works in any browser, no setup
- Self-host with PostgreSQL - you control the database, we'll help you get started
- PocketBase - a lighter self-hosted option if PostgreSQL feels like overkill
The web app at app.falconlogbook.com isn't live yet - we're still building. But the architecture is ready.
Why PostgreSQL?
Because flight records are not grocery lists. You want a database that won't let you log 37 hours in a single day or enter next Tuesday as your flight date. PostgreSQL enforces those rules automatically. It also handles searches across thousands of flights without slowing down, which spreadsheets start doing around page three.
Why not spreadsheets?
Spreadsheets are fine for 50 flights. At 500 they become a liability. One wrong keystroke and a formula breaks. Two people editing at once and things get weird. No mobile app, no offline mode, no backup that you don't remember to make yourself.
A real database handles all that without you thinking about it. You log your flights, it stays organised.
The north star
Quick logging. Accurate totals. Data you own. That hasn't changed. Flutter gets us there faster. The backend gets us there without locking you in.
If you want to help shape this, send intel. Tell us what your current logbook does wrong and we'll make sure Falcon doesn't repeat it.