Good shout! I can probably do a super quick fix by just shoving a big space below the gallery/camera options, but might be an area worth revisiting properly at some point.

I've been playing around with backup/restore and it's melting my brain! It works, but after doing either the database doesn't restart properly without killing the app...

I'll figure it out though!
Oh, and a wee bonus, iCloud is integrated right into IOS, so think those on Apple get a quick cloud backup option for free! Android is a right pain in that regard...turns out that if the user wants to save a file anywhere other than in 'Documents' (or a sub-folder of it) then I need to request a permission that'll likely result in the app having no chance of store approval! Reckon I just need to manage that via messages to the user too, which isn't great:(

To give me a break from a busy Monday at work I thought I'd pop in a wee update on progress over the weekend.

Since no issues were highlighted from the Android beta users, and the developer dashboard shows no crashes I released the Android app to live yesterday, meaning it's now available to anyone wanting to download it! (I've added links in the first post).

From analytics I can see there are already a few people finding and downloading the app, which is pretty cool (especially as I reckon it's still missing some key functionality - I don't intend to try to drive anyone to it until I get a couple more things in there!)

On the build front, I'm still plugging away at getting backup and restore working as I'd like it (didn't get much time to work on it this weekend)- as mentioned before as a proof of concept I've got it working, but there are some very rough edges to it that I wouldn't be happy releasing.

I've initially mainly focussed on refining the UI before I add a bit more defensive code around the functionality itself - including adding in a couple of artificial delays in the process (essentially, everything happens instantly when a button is pressed... but that looks wrong when doing something like this, so I've added a couple of loading spinners that run for a second or two before confirming completion... it may be an illusion, but I think it gives more confidence in the process.

This is one of the places in the app where errors of various types can be thrown, so in parallel I'm going to build in an error framework, so that if the app does error in some way I can give the user meaningful instruction on what to do, or at least provide clear messages that they can pass back to me to help debug issues.

I reckon I'll spend any free time I get this week on this one, then see if I can get ads and possibly notifications done next week, so that I can get v1.1 out by the end of the month!

Great work Grant. I've been using the Android version by simply adding each watch as I wear it. It seems to be working quite well. I can't see a way to submit feedback from within the Android version, so I will leave it here. Just a couple of minor appearance suggestions:
- I'd like to be able to have 2 photos for each watch, so I can have a photo of the dial and one of the caseback or serial number.
-A thumbnail beside each watch on the collection list, rather than the generic watch icon.

I haven't had a ton of time to use the app, but I've had no functional issues with the Android version.

Thanks for that!

On photos, I'd like a caseback picture too (and the survey suggested about half of those responding would like additional pictures), so that's something I'll tackle in a future update (was actually thinking of making them larger - the material design spec does banner images, so a large screen wide image that hides as you scroll up... Keen to investigate that!)

Adding thumbnails to the list view should also be fairly easy, although my main concern there is performance - might well be fine on a well specced phone with decent RAM, but I worry it'd slow things down on lower spec devices.
Again though, I'll experiment with that in the future - I can always make it togglable in settings!

Glad you're enjoying it so far:)

Okay, okay... sure this doesn't look like much, but it's the culmination of a mountain of pain

For anyone wondering, that's a test version of the app running on an iOS simulator on my laptop on the left (with an entirely made up list of watches), and on the right a Google Pixel 4, showing the exact same watch box after backing up to iCloud via the simulator, saving across to Google Drive, and then loading directly from Drive on the Android phone!

So, the ability to Backup and Restore the database isn't quite finished, but I'm finally close!

Honestly, this has been a right pain in the behind to get working, and I was half convinced I was going to have to throw away half of what I'd done and write something far more detailed to make it work . I still need to tidy up some user facing messages, but this proves that backup/restore does actually work!

Anyway, I'm ranting - I'm off to pour myself a nice cold beer... WristCheck v1.1 is back on track

Hi Grant,

Just wanted to share a couple of more suggestions / wish list items with you:

1) I'd like to be able to "wear this watch today" from the main list of watches. I feel that having this function on the main list would be more valuable than the "add to favourites" button on the list

2) A field that allows you to track the timing of each watch would be valuable. It can be done using the free text Notes box, but a separate field would be beneficial. Many owners don't service on a schedule, but only when performance degrades. I'd like to be able to enter my timing results for each watch and track them over time.

I've popped those onto the backlog to have a think about - I could easily make a long press of the watch in the main view trigger the 'wear today' call.

Timing is an interesting one, i could probably put something together similar to the dates implementation, and just track a date/reading pair, then throw some graphs together based on that so that you could see when watches were starting to trend towards too fast/slow.

Once v1.1 is out I've got some plans for what will likely make up v1.2, and I'll try to get the backlog published to allow voting on things to help shape how it progresses going forward.

I think it is brilliant!

Couple more suggestions that I think would make it even better. Of course, feel free to ignore!

1) Ability to sort the watch view according to preference - e.g. A to Z or most/least recently worn
2) A button for Wear this watch yesterday as well as the today one. I sometimes get round to logging the watch of the day, but it is usually every other day.

Many thanks

Thanks for the feedback, great to hear you like it

On 1 - happy to add this to the backlog - I've got a wee sub-list of navigation improvements that I might try to do together (using it myself I think being able to order by last worn date would be useful too!)

On 2, you can currently go in and add yesterday (or any date) if you've missed one by clicking the wee calendar icon > click the padlock icon to 'unlock' > click the plus and pick any date to add in (in v1.0 this includes the future too, but that's fixed in the upcoming v1.1 already ) - I'm hesitant to add a button for 'yesterday' as the UI already isn't too pretty, but I'm currently working on an optional daily push notification to remind you to go in and update it

So this definitely falls into the category of picking nits (which I think highlights how good the app already is):

When I'm entering a new watch into the database I'd like to see automatic capitalization of the first word for brand and model. I don't know how hard this is to implement, but I've seen it in a number of apps.

Looks like I can write and assign a formatter method to individual form fields, so that shouldn't be too hard

Just loaded a fresh test build on my phone and it wiped the database :'(

Not super unexpected (I'm still keeping a spreadsheet!) but annoying nonetheless! Frustratingly I wanted to get the latest debug build on there so that I could do a backup and test the daily reminders 'in real life'.

Anyway, reminders are (I think) functionally complete and just need the copy updated (and a wee confirmation message created to confirm they've been turned on).
I've not put ads in yet, but if these trigger ok then I think I'll do a production build of v1.1 and get it out to the beta test group, then do a v 1.1.1 with ads afterwards, it'd be good to get some feedback on backup/restore and the daily reminder over a week or so I think!

In terms of reminders, these are currently daily but you can select the time (morning, afternoon, evening or custom) - I'd like to go back through the code with a fine toothed comb though as there's a fair amount of individual setup across Android and iOS, hence the desire for real world feedback!

I'll update again once I've got the builds going, probably towards the weekend.

Incoming!

Version 1.1 has been submitted to the Google and Apple for review (in fact, the Android version auto-approved almost instantly so is already available!) Changes are as in the below screenshot!
For those in the beta test groups, if you're on Android you should see it in the Play Store now (and it'll auto update if you have that on). On iOS Apple should approve over the next couple of days and you'll get a test flight email as before.

(and if anyone wants to join the beta test groups please feel free to drop me a PM!)

This version is still ad-free as I'd love to get some feedback over the next week or so on backup/restore and the daily reminders - in the meantime I'm working on the ad implementation which I may pop out as a quick point release once ready.

Hope you enjoy it folks!

I got the TestFlight version. All data is intact.