Hi everyone. This is about an app, but I’m not going to write the name here because this isn’t about promoting it; I just want to ask your opinions on its concept.
I’ve just started building an app that uses the iNat API to show the nearest observation to you at any time. It scans every few seconds to find and show the nearest observation to your location, while you’re walking outdoors. It then shows the pics, distance and date, common and scientific names, the observer, identifications, etc. So kind of like the single observation “screen” of the iNat app, but the difference being that it automatically updates every few seconds, and it just does that one thing (so super “light” app).
Do you think this is unique and valuable enough to be worth building?
I posted about it in the iNat subreddit, and a moderator said “iNaturalist already has a very similar capability, if you zoom in on your location in the map and then search the map area for nearby observations.” But to be honest, I can’t see anyone doing that and then keeping it open on that screen and refreshing it every few seconds… so I’m not sure if that’s a good comparison. Let me know if you agree or not.
Update: I realise that I didn’t explain the use case very clearly, resulting in some confusion about who would use this, when, and for what purpose ![]()
The idea is that someone who goes for a walk in a new location (or a location but don’t know much about) might want to know what sort of plants, animals, fungi etc. are seen in that area. They aren’t necessarily going to stop to look for the specimen (to reproduce the observation). Instead, they’ll look at their phone briefly to see the observation, marvel at the biodiversity in the area, then keep walking and look at their phone 10 / 20 / 30 seconds later to see the next one.
In other words, the intended user is a casual walker / hiker; not necessarily someone who has used iNaturalist much in the past. I expect them to use the app to enrich their walk, rather than to engage more thoroughly (at least at that time).
I am planning on adding some filters like selecting the observer, the dates (or at least by recency; e.g. within the past year), the taxon, etc. So even though the casual user might not use these, it might still be useful to you by using those filters.
Lastly to address the questions about traffic to the iNat API; that’s a valid concern, but I’m doing a few things to reduce how often it queries the API. For example, it caches all requests, so that it doesn’t make the same request if the user hasn’t moved much (e.g. if they haven’t moved more than 20m). And I’m planning to add a feature that does a single larger query to the API and just stores all the observations on the user’s device, so that it doesn’t need to re-query the API while the person is on their walk in that area; and that would enable offline use.
So to sum up; I don’t want to replicate anything that the iNat app already does; I want this to offer a new experience using iNat’s incredible data.

