Nic Hubbard

Agreed. Working through some other majors features right now but will for sure add this to our feature list.

I will be leaving it for now, but I do appreciate insight from @thebruce0 as to how others might be using this feature.

Cachly uses the API to gather all cache data for the PQ. This includes favorites, corrected coordinates, etc that the .zip doesn't include. We used to use the .zip but users were confused when it didn't include certain info. Getting the PQ data from the API rather than the .zip doesn't take away from your daily API count.

This is a bug that we have on our list to fix in 2.1. It for sure wasn't intentional.

This is something to take into account. We have worked to follow iOS Human Interface Guidelines for most/all of Cachly. Swiping to show options and tapping to me is extremely intuitive since iOS uses this same UI feature in many other places. I think once you get used to it you will love it.

There isn't currently a way to cancel these. The API handles bookmark lists and PQs much differently, so there isn't a way to make the interfaces work exactly the same.

Cachly does have all of these icon distinctions with the exception of a difference for archived or disabled.

Wow, a lot to digest here. First off, if interested we have a semi-public bug/feature tracker if you are interested in being a part of. It might be easier to discuss individual features there. Just contact me through the support option in Cachly so I can get your email. That being said... Cachly won't show those pins/caches twice, but there is no way in the API to exclude loading of specific GC codes. (This is only relevant with the Clear Map on Refresh option to off) I wouldn't change the default way this works since it has been like this since day 1. But I will for sure consider making it a Settings option. This does sound like an interesting feature. Once you get signed up for the bug tracker it would be easier to flush out the details of this there so I can ask questions about this individual feature. When the ... shows in the refresh icon it is pulling 50 more caches from the previous search. For example, a search might actually return 4000 results but the API only allows 50 at a time to be retrieved from the server. Cachly does have this option. When navigating to the cache there is a button with a target on it.

Bookmark lists are shown in the order that they come from the API, which I am not exactly sure what order that is. I think just having them in ABC order would be best, giving sort options for this might be an overkill.

I can reproduce this. Will get it fixed in the next version. Thanks for reporting!

This is a feature that we worked to develop about 6 months ago, but realized that the API just wasn't suited to do this. Here is why: Official Geocaching app uses private API to load up to 500 caches at a time to fill the map, we can only request 50 API is limited to 30 requests per 60 seconds. If you have already used up some of these requests (submitting logs, other map requests, etc) you will have fewer than 30. Users are limited to 10,000 "lite" caches per day which is what is loaded on the map. This limit could be hit and then users could no longer load caches. Moving the map quickly would use up many requests, even if we only called the API when you stopped moving the map. The user experience suffered because you would use up all allowed requests and get an error, then have to wait until 60 seconds was up. I am willing to revisit this in the future, but at the time when developing this feature it just didn't work very well because of the API limitations.

Glad to hear it was a good experience! Let me know if you have any other questions.

Yes, just go to a cache and write the cache note. That is all, we will upload it automatically.

The Pending Log itself doesn't have anything to do with Personal Cache Notes as they are not uploaded at the same time. However you can swipe the pending log row and choose options, then choose View Cache. From there you can add a Cache Note. You can also add them offline and it will upload them later for you. Does this help?

This is still something we are working on, hopefully it can be fixed in 2.1. There is always room for improvement in the UI and we will be sure to look into this issue and how we can address this concern. Making text larger in Cachly based on your iOS settings is harder though and it causes issues with the user interface and how things are designed and laid out. We are working on it. Go to the More tab then to Settings. You will see a section called "Log Defaults". This is where you can set the various defaults. Glad you are liking it!

Sadly there isn't a way to move saved lists from the Classic app to Cachly. Reason being, there is no provided way in the Classic app to export those lists since they are local to that app. It also does not appear that the Classic app uploads waypoints to geocaching.com. If it had, those would be able to sync back to Cachly. Not sure why they didn't do this...

Yes, in 2.1 this issue should be solved as performance and memory problems for massive GPX files are being addressed.

Not sure what you mean. Can you explain this a bit more?

Thanks, will look into it and get it fixed.

Strange. The text comparison sets strings to lowercase for matching so this shouldn't be an issue, but I will look into what is going on. Do you have a GC code I can test?

Yes, this wouldn't be hard at all. iOS has a UI for choosing different rows.

This is something that will be fixed in 2.1. Stay tuned!

There currently is a memory limit that is based on the device you are using. Trying to load thousands of caches will consume a large amount of memory and will likely crash. This is something we are focusing on in 2.1 and the issue should be fixed at that time.

We appreciate your input!

That sounds like a great feature. Will get this added to our Feature List.