FireFlow

A native iPhone client for your own Firefly III server

FireFlow talks to one server: the one you point it at. There is no account to create, no backend of ours in the middle, and no analytics. If your Firefly III instance is on your home network, your finances never leave your house.

What you need

• A Firefly III instance you can reach — on the internet, on your LAN, or through a VPN.
• A Personal Access Token from that instance: Options → Profile → OAuth → Personal Access Tokens → Create new token.
• iOS 26 or later.

Trying it without a server

Tap Try the demo on the first screen. It runs on sample data built into the app, makes no network calls at all, and lets you create, edit and delete transactions to see how the app behaves. Nothing you do in demo mode survives a relaunch.

If something isn't working

"Can't reach your server"

Almost always one of three things. If the address is a local one (192.168.x.x, 10.x.x.x, or a .local name), you have to be on that network — FireFlow says so explicitly when it recognises a LAN address. Otherwise, check the port: leaving it blank uses the scheme's default (443 for HTTPS, 80 for HTTP), which is right for most setups but wrong if yours listens elsewhere. And if you run Firefly III under a subpath behind a reverse proxy, that subpath belongs in the path field.

"The server answered with its login page"

The token wasn't accepted. Firefly III redirects unauthenticated API calls to its web login rather than returning an error, so this is what a wrong, expired or revoked token looks like. Create a fresh Personal Access Token and paste it again — make sure it's a Personal Access Token and not an OAuth client ID.

A certificate warning

If your instance uses a self-signed certificate, FireFlow will refuse it by default and say so. There's a per-server setting to allow it. Consider what that means before switching it on: it disables the check that would otherwise tell you someone is intercepting the connection.

Changes that say "waiting to sync"

You saved something while the server was unreachable. FireFlow keeps it and sends it when the server comes back — it will not be lost, and it will not be sent twice. Settings → Sync shows everything outstanding, and anything the server refused outright appears there with the reason and a choice of retrying or discarding it.

Getting help

Email fireflow@rhouse.mx. Telling me what the app said, whether your server is local or public, and what you were doing at the time will usually get to the answer in one reply.