thebruce0

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

In Geosphere waypoints are stored in the single unified local database, so it's easier to filter for additional waypoint like parking coordinates over the entire database and include them in a map view result. I don't know how Cachly does its local database search, but theoretically it should be possible to, for example, turn on the option to display additional parking coordinates stored in any list within a distance from some point being viewed, or in the map window.
Personally, I have a category set up into which I've imported many thousands of parking waypoints I exported from GSAK, so if I want to I can toggle that category in the map view filter, and it'll include them all with whatever distance filter I'm currently using. eg, viewing all cache listings within 15km from my location, I can turn on additional waypoints filter, include my parking waypoint category, and then all the filtered caches and waypoints show on the map.
It's a nice feature to be able to have a kind of secondary filter on additional waypoints over all the local data to be seen on the map (trailhead waypoints are also a useful option).  Comes in handy in popular areas, when someone publishes a cache in a forest but doesn't put any additional helpful waypoints. This way you can see what other COs may have added to theirs nearby and make use of that info on the fly.

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

To expand a bit, Geosphere has the ability to display the proximity circles as an overlay on the map, and it's also set to only show on physical waypoints - posted coordinates for physical cache types, and multi-stage and final waypoints. (reference points, parking/trailhead/virtual etc are not relevant for proximity concerns and so don't show the circle).  It's a very useful feature, especially when planning for cache placement in a busier area.

A list that keeps the last n caches I have looked at the details screen for. Tapping an entry from the list would open that cache (including retrieving it from the API if it is not current). On a mobile device this "return to an earlier state" is very handy. 

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.

Or perhaps a "power user" mode
That was a suggestion long ago for geosphere, but it's a significant development as it's essentially creating a new UI layout to cater to those who know the functionality and content so well that symbols and letters, at most, can be used to identify common or repeated information, and quicker access to most common functions can take priority over presentation and explanation... and to remove extra whitespace (*tsk* still @ Groundspeak on that for their web design).
Anyway. Thought I'd chime in