In reply to John Roberts (JR):
> In general, it's brill and has done a good job of simplifying what is an extensive amount of data!
Thanks =]
> A couple of comments from using it over the last couple of days. These are general usability things rather than crash issues, as so far only had one (which just occurred randomly). Some of these are quite hypercritical - take that as a signal that you've done a great job overall!
> • The whole app design is "flat" (which I like!) but the "Downloads, "My Crags" "Logbook" and "Wishlist" top menu tabs have drop shadow which looks a bit inconsistent.
Yeah, I ummed and ahhed a bit about this one, but it just looks 'wrong' without shadows there somehow. I see what you're saying though, and I've now reduced their opacity as far as I think I can take it in the dev build.
> • The same tabs as above have disappeared twice whilst using the app leaving a whitespace. App close and restart needed for them to re-appear.
This is interesting, as I've never had this happen. Can you give me any more detail on the circumstances? Was it when you brought the app out of the background perhaps? If it happens again can you try typing something that won't return a match into the search box and see if that forces it to appear (which it should).
> • On the downloads tab the individual crag description areas feel big to scroll through when there are a lot of crags under that area, for example Dolomites. I suspect a smaller summary (smaller thumbnail, name, price) which you can tap to expand might be a neater way. I appreciate you can use the search function (but I never do... I like scrolling)
I see what you're saying here, but feel it's useful information to have on that first level (even though some is duplicated one level further if you tap the bundle cell). Making these initial cells expandable doesn't really work because we already have expandable areas in that list, so double-expansion would be a bit confusing.
> • Occasionally I had to authorise my iTunes account a number of times per download (using touch ID), but that seems to have settled. Possibly an issue this end.
As Alan said, this is something to do with the app store sandbox and will not happen in production (so I'm told). It seems to happen more if you start a download, minimise the app, then come back to it later.