FOR REFERENCE ONLY · Always subordinate to your TMs, AMMs, Work Cards, and approved procedures.
§ SupportBuild 27iOS 17+

Support

It's a one-person project. Bug reports and feature requests go to GitHub Issues — include build number and a screenshot if you can.

Issuesgithub.com/wightout/fro-app/issues Build27 · v1.0.0 · iOS 17+ GitHub@wightout

Common questions§ 1

Where is my data stored?
In FRO's sandbox on your device. Nothing leaves unless you export it. See Privacy.
How do I move my data to a new phone?
Use the Export menu to write a backup file to Files (or AirDrop to the new phone), then Import on the new device. There is no cloud sync, so you do this on your schedule.
What's the difference between .frojob and .frotool?
.frojob is a single logged job — aircraft, tools used, hazmat, notes. .frotool is a tool or kit definition. Both are exportable and importable.
Will FRO sign off on a Work Card or audit a procedure?
No. FRO is not authoritative maintenance data. It does not produce sign-offs, approvals, or audit trails. Your TMs and Work Cards are the law.
Why no Android version?
It's an iOS solo build right now. Android is not on the roadmap.
Does it work on iPad?
Yes. iPhone and iPad, iOS 17+.

Reporting a bug§ 2

Open a GitHub issue with: device model, iOS version, FRO build number (Settings → About), what you did, what you expected, what happened. A screenshot helps. If it crashed, include the time it happened so I can match crash reports.

Feature requests§ 3

Same place. Be specific about the workflow you're trying to support. "An export option for X" is more useful than "make exports better."

Refunds§ 4

Refunds are handled by Apple, not by me. reportaproblem.apple.com is the path.