Excellent!
I think I have a good example of the kind of thing that happens on iNatNext due to sluggishness. In this screenshot, most of the thumbnail photos don’t match the taxa text description.
I was looking for an observation I had just uploaded to add a cropped photo. I opted for uploading the observation again and deleting the duplicate via the website.
I had uploaded about 40 new observations from my phone finishing approx 10-20 min prior to this screenshot. I switched between the list and thumbnail view and the problem presented with both views.
Now that more time has passed, the issue appears resolved. The thumbnail grid is still a bit sluggish to load. The list view loads fairly quickly.
I was impressed with CV recommendations as I was adding photos to iNatNext while offline (in an area I arrived at yesterday). There were also options for broad taxa in the recommendation lists which made it easy to put observations at order and family.
Is it possible for the user to change the default date format from mm/dd/yyyy to dd/mm/yyyy for those of us who live outside the US?
The app doesn’t appear to follow iOS’s date format settings, as mine are set to dd/mm/yyyy.
I hadn’t noticed this before, but I would prefer it too. Or I guess it could be standardised to yyyy-mm-dd everywhere since that may be more practical for „archival purposes“, though having a choice is preferable.
I agree, but for everyday use dd/mm/yyyy is probably better.
But now I’m wondering how the date format appears to be dd/mm/yyyy (actually dd.mm.yyyy) in @tiwane’s and @misumeta’s German-language screenshots earlier in this thread.
Ah, changing the app’s “app language” (in the settings) to German changes the date format on individual observations to dd.mm.yyyy, but appears to have no effect on the (US) date format in my list of observations.
Interestingly, changing the app language to “English (UK)” from default English appears to have no effect on date format whatsoever.
Not for us Americans. I do agree with having a choice.
Yes, I was speaking for those of us who live outside the US. It would make sense for the date format for the “English (UK)” language setting to be dd/mm/yyyy. It doesn’t presently seem to be the case. Or better yet, if it could be tied to the phone’s date format setting rather than the app-specific setting.
I realy love the new option to comments and ID on observations of others!
I’ve only started using the new app recently, and have used it primarily to ID other people’s observations. I noticed one step in the Identification process that seemed unnecessary (to me at least). After hitting the “Suggest ID” button, we are taking to the “Add an ID"page. When I click on the ID that I want among the suggestions here, I am then taken back to the observation page (darkened 50% or so) but with a smaller, bright " Suggest ID” box at the bottom of the screen. To finally set my suggestion I then have to hit the dark gray button at the bottom that says “Suggest ID”. This last step seems completely unnecessary to me. What is the purpose of this extra step? I have already chosen the identification I am suggesting on the previous page (“Add ID”) so why am I being asked to confirm it? Is it common for users to accidentally make a suugestion so this extra confirmation step is needed? I find that it unnecessarily slows down the identification process, as I haven’t accidentally made a suggestion so far.
Also, I’ve noticed that when I first mark an observation as not wild in the DQA and then I return to make an ID suggestion the only Suggestion that the CV offers is “Human”. For example, I recently tried to identify a domesticated rose that was clearly growing in a pot, after I first marked the observation as not wild. No suggestions were offered by the CV other than Human. So, I had to type in “rose” manually. This seems like a glitch.
I wonder if the default setting should be applied based on locale instead of language. Even though I’m German I prefer to use iNat in English so that I can more easily find the correct name for features if I want to discuss them in the forum, but I’d still rather use dd.mm.yyyy
Thank you, this is the kind of descriptive feedback we can address, as opposed to “it’s slow.” We have two TODOs intended to address this problem: progressive image loading and list item recycling.
Is it possible for the user to change the default date format from mm/dd/yyyy to dd/mm/yyyy for those of us who live outside the US?
IDK if we’ll ever implement a setting that only controls the date format, but you can change your language / locale to one that supports this kind of date formatting, e.g. English (UK) (we should support Australian and New Zealand variants of English too, need to look into why they’re not showing up). Currently none of those strings are localized yet, though, so someone will need to “translate” them: https://crowdin.com/editor/inaturalistios/724/en-engb?view=comfortable&filter=basic&value=3#q=date%20format
Darwin Core standards (what most natural history museum datasets use) recommend ISO 8601 (which goes year-month-date), and they should be exported that way for GBIF-import so it’s stored somewhere that way already… Seems unfortunate to make Americans who use the science-preferred formats to change their settings to a “different” language. :-/
I really like the new app. I’ve been using the android GitHub thing and I know it’s still in progress but I’m really enjoying it. Just find it very slow to open the camera and take the shot. Sometimes the I need the camera to be ready but I always have to wait AI camera to load and even after the shot I need to wait a few seconds so the photo can be taken. Sometimes I miss the focus or move a little. GPS takes too long to find where I am too. Just this and it’s neat. The flow is fine.
It is slower to change the vied status when l go through my notifications. When I go back to the list it takes a second or so to remove the green dot. Sometimes I have to open a notification two three times to change the status.
Since it is March now and the previous post is from October to December, I thought, it may be time for a new one.
My thoughts: Wow!
I haven’t been using iNat Next that much recently because I have most of my photos on my computer. However, having just uploaded a few observations from my phone, I am impressed how much the app has already improved since I started using it (and it was already very good back then).
What I really like is the amount of choice the user now has, especially for uploading new observations. I feel like that way a lot of the workflows different iNat users may have are supported. (I also appreciated the short YouTube tutorial linked to in the app!)
I think this is a great approach to something like iNat, and it would be amazing if user choice could be implemented in other areas too, wherever it is feasible both logistically and in terms of how much time and resources it takes to create and maintain.
I like it, but I don’t really see the point since the earlier iNat app was good enough for me.
I absolutely love it so far! I just really hope after they’ve checked off every item in their to-do list, that they pick up on some of the great feedback and suggestions from the community.
I merged the above three posts to the original topic which I believe was intended to stay open, and reopened it.