Nobody wants to read an explanation before they can use something. So the first screen says what the app is in one line, shows the three things it will do for you, and asks for one thing back: your location. Give it, and the next screen already knows which lakes are within driving distance. Skip it, and you type a town instead — nothing is locked behind the permission.
The data behind it
Location is used to sort lakes by driving distance and to pick the right bite calendar, because fish start feeding weeks earlier in Florida than in Michigan. It is never stored on our servers and never attached to a person: the coordinates stay on the phone and go out only as “find waters near this point”. That is worth saying plainly on the first screen, because asking for location without explaining why is how apps get refused.
What it calls
GET /api/fishing/near — the nearest published waters for a point · GET /api/fishing/platform — the counts shown on this screen, read live
What you can do here
Tap “Use my location” to let the phone answer for you
Or type a town or a zip code instead
Skip entirely and browse everything we have published
See what the app covers before agreeing to anything
