Quote:
Originally Posted by pwalker8
I got wiped out by the update as well. Yea, not happy since my library has around 3700 books in it and it takes a long time to download everything and it's not exactly something you can do in the back ground.
As far as the subscription model goes. I'm a lot more understanding about that. First, Apple is pushing developers to use the subscription model. Second, if you want someone to keep maintaining and updating the program, this is likely the only model that works. Otherwise it's simply a hobby for a developer who either updates it when he or she has time, or perhaps loses interest. $12 a year doesn't strike me as excessive, as long as there are updates, bug fixes and improvements on a regular basis. It certainly beats having to deal with an abandoned App like many apps I've used over the years. Before they announced that the iOS version was being taken over by a new programmer, I had assumed that the iOS version was abandonware and that it would only be a matter of time before I had to figure something else out.
I'm understanding that doing a big rewrite to bring the code of to specs in Swift might introduce some bugs, but generally, that's why programmers do beta testing. Hopefully, this is a lesson learned.
|
When was the announce of the new developer done? I mush have missed it.