The version that's there is a slightly version I uploaded last week to test the process (1.1.9.0). The one that's going up now is v1.1.11.0 and has the fix, it also massively speeds up the database interactions, so that's nice. According to the submission page it can take between a few hours to a few days to pass certification. Also it turns out Windows Store App doesn't show version numbers unless you go to the web page directly (https://www.microsoft.com/en-gb/store/p/variant/9plgzn3nlvpk).

The app is already touch friendly! In fact I'd say it's my preferred way to use it. The ability to set the cache location is coming soon(ish). The app is currently up on the Windows store now, it'll take a couple of days, the version number to look out for is 1.1.10.0.

I parse the file name and try and extract the name, issue number and year from that. I suspect it's because I forgot to properly escape out the url special characters, # is encoded as %23 so if your filename is "comic name #003.cbz" ubooquity gives it out as "comic name %23003.cbz" and my parser is picking up on the "230" as an issue number.

I've got a fix that should prevent any special characters causing problems now. I'm going to get an update out for Monday and this bug should be included in that if it passes testing over the weekend.

How are you finding it otherwise?

Well I'm personally working on a reader with Ubooquity support a key feature for Windows/UWP right now which is why I asked in the first place :D. After it's done I plan on porting it to other platforms.

That's great to know. Will you be providing an API for external apps to update read states as well? Or will that be planned for a release after the next one?