Thanks all - as I've said before, genuinely blown away that people like my wee app and find it useful!

In terms of the graphs, issue - I've had a play around with a very quick fix - before and after pictures below:
I'm not sure if the black on blue makes it harder to read? I've got this lined up on a branch so can bundle and release easily - I've only made the change in 'light mode' as it isn't an issue with the dark theme.

I'll get it bundled up and out soon!

@Stif I got a notification that the beta has expired. If you pulled me from the beta that’s totally fine but I’m wondering if I can get my wear data so I can migrate to the standard store version.

Actually just downloaded the production version and the data was all there when I opened it. All set!

@NationOfLaws sorry, I've just seen this message! It'll probably be because I've not released an update for 90 days (the betas are time limited by Apple) - works been keeping me on my toes so I've barely touched the app build for a while :'(

Glad to hear that the data 'just worked' when you moved over to the production release though!

Stif wrote: ↑Thu Nov 02, 2023 9:36 pm Thanks for the update Tim - did you set a new notification on the app? (I think you'd need to turn them off and on to ensure its registered with the new time - but it does sound like you did!).

I wonder if it'll only work with a genuine time change (and maybe not with a location change?)

It definitely now works on Android as I was pleasantly surprised that my notification continued to fire at 9:15 despite the clock change!

In slightly related news, I think in the past you also suggested you'd prefer to see the charts on a rolling 90 days, like OnMyWrist does, rather than monthly... and as part of the rework I'm doing on the wear charts I've now got that up and running.

So far I've rebuilt the page, much as it was before but with the filters separated out (similar to the way the way I implemented the collection ordering) and implemented a series of 'quick filters' that you can instantly flick between.

I'm going to put some 'advanced' filter options in place next...

The location time zone change is still not working for moving between time zones. I’m in Europe this week and my 19:00 notifications are firing at 20:00.

Sorry @timor54 I thought I'd replied to the above (I can see I did 'thank' it!) - did you notice if the time updated successfully with the clock change at the end of March?
It worked as expected in that regard on my Android device - I suspect the library isn't using the devices location but rather the locale settings (so it may update if you set your device to French when in France... not much use I know!) I'll keep a wee note on the backlog for this, but I suspect I'd need to completely rebuild notifications to make it work when on holiday

In other news - I've been fairly quiet on the forum and elsewhere for a while (I think I partially hibernate over the winter, and I took over some new teams at work in December which has lead to a busy few months during the work-day, so haven't spent a lot of time on my own laptop!)

BUT - I felt the urge to get back to things this week (I swear it's the sunshine) so I've been working away on a long planned calendar view for the app, and as always this has led me down a massive rabbit hole!

First, here's a design suggestion @NationOfLaws Jameson shared with me around the time I first began working on WristCheck back in September 2022(thanks again!)
I always loved this suggestion, and feel that the current servicing schedule view is one of the remaining weak points of the app...so I used this as a basis to improve things!

Firstly, I implemented a calendar widget - when loaded, it cycles through the database and maps:

• The wear date records for each watch

• The next service date for each watch (if it has one)

and adds each one of these as an 'appointment' record in the calendar, which I can then display in the below 'appointment view' - all of this was surprisingly easy! So, the calendar (as it currently stands) let's you see at a glance if you've tracked everything recently... but what if you haven't? I couldn't leave it at that, so wanted to give the ability to add wear information directly on the calendar if you see a gap... this was a bit more challenging!

First - picking a date on a calendar is easy, but picking a watch (from a potentially huge collection!) is more challenging - I prototyped a few options, including a pop-up bottom sheet (similar to the chart filters), but in the end opted for a painfully simple solution!

When you press the 'track wear' button, you get a simple pop up that confirms the date selected, and presents a drop down menu, with in built search! So you can quickly scroll to find your watch, or you can type it's name! (Something I've still to do is make the list order in the same order as the watch box settings, just to keep things easy and consistent!)

There was lots of additional fun and games with this - in the background, separate to the page itself I track the state of anything currently selected and fire errors if you try to add wear info without first selecting the watch etc.

I've also added a little button in the bottom right, that'll toggle back to a view that'll show upcoming service dates (like the current page), which I'm going to enhance with warranty expiry dates too.

I'm pretty happy with how this is progressing so far although I've still got a fair bit to do (whilst the code all works, it's not currently very tidy!) and building this also highlights how bad the existing per-watch history looks (just a big page of dates!) so I'll be updating that next (possibly in a separate release though, as that might also be a good time to work on some per-watch stats - I really want to know if I'm more likely to wear a particular watch on a Monday or a Saturday!) - and that page potentially has more space to align more to Jameson's original design suggestion of a calendar plus a few graphs together.

Anyway - that's a wee update and preview of the current app progress - as always, really interested to hear your thoughts!

Thank you, Stif.

For your info, I changed my phone after close to 6 years (to a Pixel), and am pleased to note that the direct transfer between the phones of files/data via USB cable worked great with your app.

I didn't need to restore data and pics with my .hive backup file, since everything carried over to the new phone.

That's great to hear, thanks @asqwerth

Something I've not done yet with the new build is try it out running on a smaller screen (or rather anything smaller than my old Pixel 4), but it's on my to do list to make sure the experience isn't terrible on smaller phones!

I've toyed with the idea of buying a second hand iPhone SE (I think I that's the smallest one) for testing, but anything the app brings in at the moment (which isn't a lot ) is being set aside to go towards a new laptop later in the year - my old 2019 Intel MacBook is really showing its age

Stif wrote: ↑Sat Apr 27, 2024 12:26 pm Sorry @timor54 I thought I'd replied to the above (I can see I did 'thank' it!) - did you notice if the time updated successfully with the clock change at the end of March?

It did, so it’s only seems to be time zone changes that don’t work.

I’m starting to suspect that this might be an iOS ‘feature’ (Apple clearly don’t have bugs…) as I’ve seen a couple of reports of similar problems with calendar notifications going off in similar situations at the wrong time. I can’t remember where I saw these, probably on one of the many iOS forums, but there were no conclusive answers/solutions other than a general frustration with Apple support.

Keep up the good work, I’m interested in the new calendar functionality and still hold out hope for a data export function in the future.

With the calendar looking ok, and build submitted, I thought I'd turn my attention to something a little different...

@timor54 you might like this... (still a VERY early prototype!)
and a proof of concept, actually working extract: As always, keen for some input here - my current plan is to give a couple of options:

• A full extract - a line for every single wear record (as the wear dates are a list within a list, that means a line for each date, so a watch worn 100 times will have 100 matching records in the CSV with different dates

• A simplified record - one line per watch, with a wear count total

I could potentially offer others (such as a super simple - watch details + value, to quickly share with insurance for example, but given how easy it is to tidy up a csv file I suspect that's covered by the second easily enough?)

Not sure how notes will behave if users have things like commas in them - I may make toggling their inclusion possible, but I'll run some tests!

Hey Grant, seeing this post reminded me to try the backup on my iOS mini 13 again, and you have it working perfectly! Thanks again.

Great news! I've found it far better since I rebuilt it - I make fairly regular backups and often transfer them between devices and simulators for testing.

Stif wrote: ↑Wed May 01, 2024 5:27 pm
@timor54 you might like this... (still a VERY early prototype!)

As always, keen for some input here - my current plan is to give a couple of options:

• A full extract - a line for every single wear record (as the wear dates are a list within a list, that means a line for each date, so a watch worn 100 times will have 100 matching records in the CSV with different dates

• A simplified record - one line per watch, with a wear count total

I could potentially offer others (such as a super simple - watch details + value, to quickly share with insurance for example, but given how easy it is to tidy up a csv file I suspect that's covered by the second easily enough?)

Not sure how notes will behave if users have things like commas in them - I may make toggling their inclusion possible, but I'll run some tests!

I’ve been giving this some thought. My view is this functionality would be of interest to those users that wish to do their own post processing of the exported data for analysis and graphing etc. Therefore I envisage two separate categories of export data that would be useful:

• Collection meta data. A full export of the watch data without any wear statistics. This would include all the information describing the watches including their status, i.e. in collection, sold, etc. Although I’m not sure why you’d want to export wish list watches? I can however see some challenges in exporting this as a CSV due to the free form nature of the data. A possible solution could be to export as an XML file?

• Wearing statistics. A single line per wear entry to just include four fields: manufacturer, model, wear date, watch status. I’m assuming that you’re time stamping the wear entries so that you can differentiate multiple wear entries for a single day? By default the entire wearing data but a nice-to-have addition would be the ability to select by watch status and within a date range, e.g. all current watches worn this year, all sold watches worn in the last twelve months, etc. Basically reusing the filters you’ve already implemented with the reporting. A CSV would work fine for this or again XML but I can imagine this adding a layer of complexity if importing into a spreadsheet (which I do).

So no pressure… I’ll expect to see it soon

Thanks Tim!
Over the past couple of days I've actually finished this as it turned out to be far easier than I expected! I've given two options in the end:

• Simple extract: This gives a line per watch, with all details including notes, with a total wear count value

• Complex extract: This gives a line per wear record, but doesn't include the notes, and also won't include any watches not worn.

When I played about with it I realised, even with a big collection with lots of watch swapping, nobody will have crazy numbers of records, and once it's out in Excel/Numbers/whatever it's easy enough to trim the data yourself (I did think of only doing dates + basic details as you suggest, but it was easy enough to include it and it gives anyone using it more flexibility).

It all works surprisingly well - will look forward to some feedback once you get your hands on it!
I'm working on adding a couple of other things to the next release before I start to package it up - the first is the per-watch calendar view (to replace the Big Date List...) I've got the calendar working and showing key dates for the watch (wear/warranty/service etc) so just need to implement a way to add/delete dates now - thinking through the UX of that at the mo!

Then I've been asked to include a second daily reminder - that should be easy enough, and thinking of making that a 'pro' feature - I think the core app is now pretty good, so going to try to just expand on what it does with some wee extras for the real nerds (like me)
In time I'll further expand that with more granular stats like case dimensions/winder settings/extra graphing options etc - things casual users might not care about, but will hopefully add value to those that really want them.

I meant to add - I like the idea of extracting the data with a date range, or other filter like you suggest - I'm going to keep a wee note of that!