I think it might just be a glitch where its showing all species recorded so far on iNaturalist rather than updated with the observed Tellinella species?
If you include casual grade observations the numbers are essentially the same (given there are hundreds of species added per month the discrepancy could easily be newly observed/IDed species over the last few hours)
Android iNat app version 1.37.2 did not replicate issue.
On latest beta version 1.38.1, did replicate. On Explore, species tab has a total of 563,382, and seems to be the case no matter how filtering on location nor which taxa. The species number noticeably takes a few seconds to load.
Step 1: I search for a taxon (subgenus Chalicodoma) in a given area (Sicily) and get a tile view of observations
Step 2: I go to the card with number of species. It loads very slowly and then shows a number as in the screen (obviously not the number of the searched taxon’s members in the searched area), and the information below is “This is a list of species most often observed by you. Attention: the number of species on Earth is estimated to be 9 million. Go out and observe them”
Step 1:When I access the ‘Explore’ section from the app on Android, the results it shows contain an error regarding the number of species in the area (in this case, the polygon represents what is near me in Mexico City). The total number of species in all of Mexico City is 9,882, and here, just within the search polygon, it shows me over 500,000.
Step 2: When I try to view the species present in this area (the hundreds of thousands it says are there), it gives me a message as if there were none in the search results.
This issue is on our radar, I do apologize for it.
For what it’s worth, version 1.38.1 (645) is a beta release, so it’s not a full public release yet. If you want to stop beta testing, you can opt out at https://play.google.com/apps/testing/org.inaturalist.android Then download the latest public release if you want. You can always opt in to beta testing later using the same link.
As I mentioned above, this is an issue with the beta version of the app. You can leave the beta testing group if you want and install the current public release.