I do have resist-fingerprinting on, thanks! I'll have to poke at that, I'm curious about the technical reasons. A dialog would help, this is the first I've heard of it and I don't mind exceptions for sites that aren't injecting javascript on billions of unrelated pages.
>and they're on the edges of the map
I don't think they were very edge-y from what I remember... but I'll double check. And will get a screenshot if I disagree - maybe it's something about window size or display density.
>we don't enable category discovery and search at high zoom.
Yeah, I've seen that in a few apps. It's kinda fine when zoomed far out as it's not like you'd be getting a representative distribution, and it might flood more specific (and intended) results out. It broadly makes sense, though I mostly see people confused and frustrated by it in-person (there's rarely any way to tell it has happened). Some of that is just them being overly familiar with only Google though.
But if that category search is not enabled, why doesn't it find business name matches? And why are the results far outside the viewing window?
Also I think that zoom level is almost certainly worth allowing (not necessarily defaulting to) category search. In a dense city it'll overwhelm things, but in much of the USA that might find 2-3 things, if any at all. Maybe it's worth blending in the number of results you'd get if it was enabled when deciding? Like "Prioritisation on search behaviors is super hard, I definitely understand that... but that's why user-controlled options are useful. OSM apps nigh-universally seem to be removing that as the years go by, and the end result is that it's almost unusable because it doesn't let you find things you know exist. Google mitigates it with enormous amounts of ad money and hundreds/thousands of engineers feeding recommendation systems to show 10 decent results out of 100,000 matches (and a lot of learned helplessness by their users), but I don't think that's worth emulating, and they still have a ton of optional controls for filtering. OSM data is convoluted and messy and hard to make convenient, but not having any control at all seems obviously worse to me. Even a `raw-field-name:"value"` seems better, it's passively learnable and fairly easy when tokenized.
---
Lest this all seem like ranting / an upset user: I just have lots of opinions about mapping! And I'm broadly rather unhappy with existing apps. I'm literally always glad to see new attempts, and I don't expect everything to be built for me, so thank you for trying things :) I'm entirely happy to say a ton more or just not be your target audience and stick to technical stuff.