What's new since build 21
Version 0.2. This is the build where the things you can do about your own data arrive — deleting it, and dealing with somebody else's catch or behaviour.
Settings → Delete my account. It does what it says, and the screen is explicit about the part people assume rather than read: your identifying details go, and the catch itself stays, anonymised — the measurement and where it was taken are kept with your name off them.
Catches tied to a tournament or a challenge are refused rather than quietly skipped, and the screen tells you which and why. A scored contest somebody else fished cannot be unwound after the fact.
You can report a catch or an angler, and you can block someone. Blocking withdraws any invitation of theirs still waiting on you. Both are reachable where you actually meet other people in the app: the standings and the challenge screens.
With the keyboard open, the "Show my name publicly" switch was unreachable. That is the control that decides whether your name appears on a public leaderboard, and it was hidden behind the thing you had just tapped to type. It is fixed.
It is called out here rather than buried in a fixed-list, because a control you cannot reach is indistinguishable from one you did not know existed — and this one governs what strangers see.
Both are now switched on explicitly rather than left to a default, with no advertising identifier, and the app ships Apple's privacy manifest describing what it collects. What that means in practice is written out in full in the privacy policy.
If your iPhone is on iOS 17 or earlier, this build will not install. That is the trade for the frameworks the rest of this list is built on.
Some of the plumbing for paid challenge entry is in this build. Nothing can be charged, no challenge can carry an entry fee, and the server refuses one. It is listed so it is not a surprise when you find it, not because it does anything yet.
This is the first iOS build ever tested on a real iPhone. 324 tests ran on actual hardware. That matters more than the number sounds: 334 tests passing in the simulator had gone straight past the privacy-switch defect above, because a simulator keyboard does not cover a control the way a real one does. Everything before this build was verified on a machine that could not see that class of problem.
0.1 to 0.2 looks like a small step and is not — account deletion, reporting, blocking and the privacy work all landed at once. 1.0 is deliberately being kept for a full App Store release, which this is not. The number is small because the shelf it is aiming at is still ahead, not because the build is.