Nic Hubbard

Darn that lame API. I should have known! 

Wherever the official app had the advantage (really a feature that Cachly couldn't provide) it's where Groundspeak doesn't  provide a viable mechanism for apps like Cachly that must conform to their API to provide the feature - messaging, "live" view as you drive, etc. 

She posted another review. Cachly stacks up nicely.
https://thegeocachingjunkie.com/2017/02/10/looking4cache-vs-cachly-a-comparison-review/

No argument there. 

I too would appreciate a download icon instead of an arrow… that screens looks similar enough to Offline Lists that I sometimes mistakenly tap a query.  Then have to wait and delete the duplicate download.

Your right, looks like in Preview mode it isn't scrolling. Will get this fixed.

Agree. I will get this fixed in our upcoming version.

Ah, well spotted.  I have that option turned off because I can't handle the main map being zoomed and moved out of my control.
But I'd expect looking at a COs subset of caches — not on the main map — would zoom and scroll automatically regardless… in the same way as first going into an offline list.  Can't think of a reason not to?

Yes, you are right! I was originally referring indeed to bringing the maps INTO Cachly--and that's where the sandboxing comes in. I just tried Google map navigation with airplane mode, and it works great! Being new to Cachly, I had the concepts or map layers and navigating by map mixed up in my mind.  Now I understand.
Good news on expanding the URL scheme! Will be on the lookout.
Thanks again!

FYI:  https://thegeocachingjunkie.com/2017/02/05/cachly-vs-geocaching-app-a-comparison-review/
 

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

Yeah that was a rough addition to smooth out in geosphere. The confusion was because the PQ data is as-of PQ generation date, whereas if using the API, the caches contained in the PQ are still as of generation but the data itself downloaded from the API is current. That is to say, if you generated a PQ 3 days ago, and new caches are published that weren't there 3 days ago, they won't show in the PQ if you download it (via any method) today - even though you get logs on those older caches that were posted today.
It was GS's combining of temporal PQs with current API functions that makes it confusing   That was one reason I like the ZIP download - no confusing data, as long as you realize that all the data is only as of the generation date. If you want current data in a PQ, you need to generate the PQ right now, then download it (by zip or api). No way around that in any app. At least until the API allows generating the PQ and downloading it together (or maybe just uses the PQ search parameters to do a current API search and download).
But anyway.
I haven't used the ZIP pq download for a while. That import ability was good mainly for downloading the My Finds PQ, which as I recall isn't provided by the API - have to generate the PQ then manually download the ZIP from the web and import into the app.

I would personally prefer the current sort order over alpha. It matches what I've been recently doing with those most recently used bookmarks at the top of the Cachly list.  Putting them in Alpha wouldn't kill me but it would be less productive for me in how many I have and how I work with them.  Just one person's opinion.

Many thanks for the replies.
It seems that they will not transfer to the new 'official' app either. I can understand technically why, if not logically.
I'll just have to bring forward my planned visit to North Wales!
Cheers.

Just a follow up on my questions and your replies. Went for a caching test drive today with another cacher and we both used Cachly all day and loved it. Outdoors I think the screen was much easier to read. Maybe because I wasn't holding the phone so close to my face.  The directional arrow took some getting used to but I eventually got the hang of it. We really had it down after a couple of caches and only have good things to say about our experience. Keep up the good work!

Just tried it. OK, now that is cool! I didn't need to initiate any kind of an upload or anything else. It's practically immediate.

The 27k cache GPX file is too large for the current version of Cachly. The developer is working on supporting larger GPX files in an upcoming release. Until then, you can load multiple GPX files so split the GPX you have if you really need 27k caches loaded on the device at the same time.

Thanks, will look into it and get it fixed.

Great feature. I can see how this could be easily integrated into the various screens such as the Add Waypoints screen. Will bump it up in priority. 

This advanced filtering isn't something that is in the current version, but we are working on adding it in 2.1. You will be able to filter by a large number of parameters in Offline Lists.

The reason we don't support landscape is that it imposes additional UI layout challenges. I do realize there are advantages to having landscape, so it is something we are looking into as well as improved iPad support.

I would like these features as well. I have a trackable that I visit at every cache I find and would like an option to have this done automatically when I log a find on a cache.
Also agree with having an add waypoint button from the "Navigate to cache" map

As a prior "other app" refugee (and I do still go back to that app for some things still - especially with its ability for me to carry around my regular 30k+ caches with logs and info in my pocket), I'm now using Cachly as my primary app.
The view of how many cache logs you have done each day is one of those "other app" features that I do miss, although it's just a "nice to have" feature and not high on my wish list of improvements that I want to see in Cachly.
For reference: the "other app" it's quite easy to see a tally of how many cache logs of each type (found, DNF, needs Maint/write note, etc) you have done each day.

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.