Nic Hubbard

I am trying to figure out the best way to move forward with this. Currently offline lists, pending logs and saved locations are tied to your username. So if you login with another user they won't see these. Recently some users haven't realized/know this and changed their usernames only to login and appear to have lost everything. Should this be removed in 3.0 and these are no longer shown to only the users who created them? I think the official app works how Cachly currently does. To me it seems logical how it works now. But some users don't. Thoughts on this and what to do for 3.0?

You can also press and hold on a map to drop a pin, then drag that pin to a location. Or tap your current location and press the + button. From there you will see an option to Save Location. This can help in placing caches. At least it is helpful for me.

You to go to More, then Settings and turn on the cache radius option. This will show the radius you are looking for.

Yes, you can tap the refresh button (top right) and it will load caches based on the center of the map and in a 50k meter radius. Just make sure that Cachly has found your current location first, or that you tap the current location button (bottom right on map) to center it over your location. Is this what you meant? ** Also tapping the gear icon in the search field will show you all the Search Options available.

Good idea. Will look into fixing this.

Groundspeak/geocaching.com imposes a restriction on the API that all third-party apps use (and their official app has this limitation). They restrict Regular users to viewing 3 full caches per day, which means hint and description. They also limit only seeing Traditional caches. I completely understand that this is a very low number of caches, but we unfortunately are not able to change this. This is NOT a limitation of Cachly, but a limitation that geocaching.com imposes on us. geocaching.com wants users to have a Premium membership, which in turn allows Cachly to display more data and raises the daily cache views to 6000.

I hadn't tested it in the field, only on the computer. So I do agree it would be super annoying.

I did build the feature the way it currently functions. But, I do see your point and will fix this for beta 6.

Are you using the beta version?

I will work to make these stand out more in our 3.0 version. Thanks for bringing this up.

The API has three options, Lite, Summary and Full. Summary might be what you are looking for, but I am quite sure it is only a little bit faster if at all. There isn't a way to cherry pick what data to download unfortunately.

I hold no issues with Groundspeak. I think they get a bad wrap a lot of the time. I do think there is room for improvement with how they did the transition to only having the new app.

I have talked with Groundspeak about the possibility of an API that can handle a live map, but at this time they weren't interesting in doing that.

When we do implement this it would be Local Notifications. But this is for sure something I want to get added.

This is a feature that we worked on and tested, but in the end if was a poor user experience because of the limitations of the geocaching.com API. The API limits 30 network requests per 60 seconds. It also limits 50 caches at a time per request. Which means, some users might have no issues, but some users might want to pan around the map looking for caches, and would end up reaching that 30 network requests (some of which likely would already be used up by other API calls). At this point they would have to wait until that 60 seconds is up to load more caches. In our testing of this, it just was not the experience that we wanted. Apps like the official app are able to load 500 caches at a time and put them on the map (even ProjectGC has special APIs to do this). With the API limitations that would take Cachly 100 network requests. Sadly the API just isn't setup to do a live map. I realize that Looking4Cache has this, but I think the user experience when using the live map isn't that great.

You can swipe the row sideways and you will see a Delete option. You said it wouldn't send, was there an error?

I am very aware of what Geosphere provides. It is a great app. We are working to see when we can get this feature added in Cachly. Hopefully soon!

Do you mean sort by distance from your location to the caches?

Sorting defaults to Cache Type. But once you change it, it saves that as the default.

But we have sorting that comes into play. User might have sorted their list.

I very much like the idea behind this as I too have wished I could quickly find a cache in the list that I see on the map. However my only thought it how I also like to scroll through list view and leave it at a certain place, then browse the map and return to list. If it had been scrolled for each cache I tapped I would be really confused as a user. So, I think there would need to be a user setting to turn this on.

Release version has very poor coordinate parsing as it uses an Apple iOS API to lookup locations. In 3.0 we use our own parser. In the release version coordinates in the format 48.123, -120.123 work the best.

Let me know how that goes and if it seems to fix the issue.

We will look into the issue, although it is hard to debug without getting some more debug info from your device.

Any other apps don't seem to have problems with the compass?