Version 2.4 send to AppStore (2-Way Calibre sync) - Page 3

petrjahoda · 05-02-2026, 11:50 AM

OK, will be in 2.4.1, because you are right, this makes sense.

pdurrant · Yesterday, 03:04 AM

Quote:

Originally Posted by petrjahoda

Hi, this can be done for Read/Unread, because there is also Finished Date.
So when not Finished Date, this parameter will not be updated back to Calibre. Will this be OK?

That would work. If there's a finished dated, #read should be True, but if there's no finish date, don't change the state of #read on calibre.

petrjahoda · Yesterday, 03:05 AM

Hello pdurrant, I already did it exactly as you described.
I will be pushing 2.4.1 today to AppStore.

gustophersmob · Yesterday, 02:58 PM

I forget if I've already commented, but I love the update that made it so it opens the book in progress when the app is opened!

petrjahoda · Yesterday, 02:59 PM

Hi, so you should thank pdurrant for this idea :-)

pdurrant · Today, 02:49 AM

2.4.1 is live. Just testing it out now.

Docuro · Today, 08:15 AM

I noticed that the speed of syncing the books from calibre to justread.app has gone down a lot, even if you sync only the read/unread status. The app needs at least 1 or 2 seconds per book. If you have thousands of books it lasts veeeeryyyyyy long. I think for me and my kind of using calibre and Justread.app it’s not an improvement.

lbrockmueller · Today, 08:32 AM

I love the update. Syncing did not take so long for me. It is nice to keep my eReader and Calibre library in sync without fiddling back and forth. This app adds to the pleasure of reading.

petrjahoda · Today, 08:42 AM

Hello docuro, nothing changed in that part of code.
So I tested 3568 books now and sync was done in 2 minutes and 21 seconds, which is about 0.03 second per book synced (which is about the same as with original 2.0 Calibre sync)
Is it possible there was a chokepoint in your network (netflix, downloading update somewhere, etc.)?

petrjahoda · Today, 08:45 AM

Quote:

Originally Posted by lbrockmueller

I love the update. Syncing did not take so long for me. It is nice to keep my eReader and Calibre library in sync without fiddling back and forth. This app adds to the pleasure of reading.

Thank you very much for the feedback and a quick information: before adding PDF I will incorporate 'margins' like presentation of books read into statistics.

In the statistics there will be a switcher (just like grid/list in library) to switch between statistics as they are now and 'margins like' statistics.

Docuro · Today, 08:55 AM

Quote:

Originally Posted by petrjahoda

Hello docuro, nothing changed in that part of code.
So I tested 3568 books now and sync was done in 2 minutes and 21 seconds, which is about 0.03 second per book synced (which is about the same as with original 2.0 Calibre sync)
Is it possible there was a chokepoint in your network (netflix, downloading update somewhere, etc.)?

Okay, so the problem seems to be in my network. I have to search….

pdurrant · Today, 10:08 AM

Quote:

Originally Posted by Docuro

I noticed that the speed of syncing the books from calibre to justread.app has gone down a lot, even if you sync only the read/unread status. The app needs at least 1 or 2 seconds per book.

Quote:

Originally Posted by petrjahoda

So I tested 3568 books now and sync was done in 2 minutes and 21 seconds, which is about 0.03 second per book synced

Quote:

Originally Posted by Docuro

Okay, so the problem seems to be in my network. I have to search….

Another data point. I'm also seeing much slowing syncing of my library with 2.4.1 compared to 2.4.0.

A partial sync of the remaining 2577 books is taking a very long time. The first 300 have taken about 14 minutes...

petrjahoda · Today, 10:32 AM

Hi to both and thank you for the feedback.

I analyzed it and the problem seems to be with checking those custom columns for every book in the internal database (the more columns the worse).

The reason why it is noticeable on some devices is the speed of the device (cpu, ram, disc). Speedy devices are so fast, those operations are negligible, but the slower device, the slower those operations are.

So I remade this db data checking and the import should be now almost the same as with 2.4.0.
Quick fix 2.4.2 was just sent for review and should appear in 24 hours (as I see Apple does that for last few versions).

Please let me know if it helps. I tested it with iphone SE simulator, where it is OK now (but it was OK even with 2.4.1), but real world device test will be the best.

pdurrant · Today, 10:38 AM

Thanks again for the really quick turn-around! I'll let you know how a test with 2.4.2 goes.

Docuro · Today, 10:43 AM

Quote:

Originally Posted by pdurrant

Thanks again for the really quick turn-around! I'll let you know how a test with 2.4.2 goes.

I agree. My device is an iPad Pro with an M5 Chip

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Version 2.1 sent to AppStore	petrjahoda	justRead.app	5	04-13-2026 07:22 AM
Version 2.0 sent to AppStore	petrjahoda	justRead.app	31	04-09-2026 05:42 AM
Version 2.0.1 sent to AppStore	petrjahoda	justRead.app	0	04-08-2026 07:26 AM
Version 1.9 sent to AppStore	petrjahoda	justRead.app	19	04-03-2026 05:23 AM
Version 1.6 sent to AppStore	petrjahoda	justRead.app	6	03-19-2026 03:00 PM

05-02-2026, 11:50 AM	#31
petrjahoda Addict Posts: 301 Karma: 123456 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	OK, will be in 2.4.1, because you are right, this makes sense.

Yesterday, 03:05 AM	#33
petrjahoda Addict Posts: 301 Karma: 123456 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	Hello pdurrant, I already did it exactly as you described. I will be pushing 2.4.1 today to AppStore.

Yesterday, 02:58 PM	#34
gustophersmob Enthusiast Posts: 46 Karma: 10 Join Date: Oct 2024 Device: Kindle PW2, Kobo Clara BW	I forget if I've already commented, but I love the update that made it so it opens the book in progress when the app is opened!

Yesterday, 02:59 PM	#35
petrjahoda Addict Posts: 301 Karma: 123456 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	Hi, so you should thank pdurrant for this idea :-)

Today, 02:49 AM	#36
pdurrant The Grand Mouse 高貴的老鼠 Posts: 75,454 Karma: 320197842 Join Date: Jul 2007 Location: Norfolk, England Device: Kindle Oasis	2.4.1 is live. Just testing it out now.

Today, 08:15 AM	#37
Docuro Connoisseur Posts: 58 Karma: 10 Join Date: Jan 2026 Location: Europe - Germany Device: Kobo Libra Color, Kindle Paperwhite, IPad	I noticed that the speed of syncing the books from calibre to justread.app has gone down a lot, even if you sync only the read/unread status. The app needs at least 1 or 2 seconds per book. If you have thousands of books it lasts veeeeryyyyyy long. I think for me and my kind of using calibre and Justread.app it’s not an improvement.

Today, 08:32 AM	#38
lbrockmueller Member Posts: 14 Karma: 10 Join Date: Jan 2007 Device: iPad Pro	I love the update. Syncing did not take so long for me. It is nice to keep my eReader and Calibre library in sync without fiddling back and forth. This app adds to the pleasure of reading.

Today, 08:42 AM	#39
petrjahoda Addict Posts: 301 Karma: 123456 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	Hello docuro, nothing changed in that part of code. So I tested 3568 books now and sync was done in 2 minutes and 21 seconds, which is about 0.03 second per book synced (which is about the same as with original 2.0 Calibre sync) Is it possible there was a chokepoint in your network (netflix, downloading update somewhere, etc.)?

Today, 10:32 AM	#43
petrjahoda Addict Posts: 301 Karma: 123456 Join Date: Dec 2025 Location: Czech Republic Device: iphone, ipad	Hi to both and thank you for the feedback. I analyzed it and the problem seems to be with checking those custom columns for every book in the internal database (the more columns the worse). The reason why it is noticeable on some devices is the speed of the device (cpu, ram, disc). Speedy devices are so fast, those operations are negligible, but the slower device, the slower those operations are. So I remade this db data checking and the import should be now almost the same as with 2.4.0. Quick fix 2.4.2 was just sent for review and should appear in 24 hours (as I see Apple does that for last few versions). Please let me know if it helps. I tested it with iphone SE simulator, where it is OK now (but it was OK even with 2.4.1), but real world device test will be the best.

Today, 10:38 AM	#44
pdurrant The Grand Mouse 高貴的老鼠 Posts: 75,454 Karma: 320197842 Join Date: Jul 2007 Location: Norfolk, England Device: Kindle Oasis	Thanks again for the really quick turn-around! I'll let you know how a test with 2.4.2 goes.

Advert

Advert