It's been expanding ever since the WWDC 2019 release, same with other newer frameworks like Combine, and it mostly goes unnoticed. They should have some way of showing what docs have been updated, currently in the Apple Developer app I think it only highlights new articles.
>They should have some way of showing what docs have been updated
Back when I used wrote iOS crap, I used dash as a quick reference for APIs.That was pretty good at alerting me to documentation changes, since it has to download an update.
https://kapeli.com/dash
I only started using it (never did buy it) because I was used to using zeal, a free-software alternative.
I like Dash, I bought it. But unfortunately the version upgrade from 4 to 5 introduced some mandatory UI changes that made documentation lookup much more cumbersome. Looking up a function now takes several user interaction steps, instead of just one in Dash 4. I'm still on version 4. If anyone have alternatives, I'm all ears.
Yeah, I feel the same way about Dash 5. Eventually had to upgrade to 5 when 4 became incompatible with the latest Apple docets. But I much preferred the Dash 4 search.
The developer of Dash is very receptive to feedback (in fact I think this change was called out as something that he was interested in hearing opinions on).
That's not my experience. I've reported this to him on two occasions, with screenshots and detailed descriptions of how the UX had regressed.
First one took a year before I got a reply (after reminding him), and only partly answered the request.
The second one I'm still waiting for a reply.
I would love for Dash 5 to fix these issues still, and I would upgrade in a heartbeat, but as it stands, I'm stuck with Dash 4.
The issues are:
1. Dash 4's sidebar shows significantly more hits when searching, making it a lot easier to find what you were looking for, compared to the "omnibar" of Dash 5:
2. Dash 4 shows/loads the currently selected search immediately, requiring no extra step. Dash 5 requires the user to press enter to confirm the search. This is especially frustrating when triggering a search from an editor
edit: where did he indicate he was looking for feedback on these features?
