Five
April 2013
The fifth version of forScore was the culmination of a lot of threads, continuing forScore 2's pursuit of strategic restructuring, forScore 3's quest for unimagined advances in ease of use, and forScore 4's relentless focus on performance.
It was also the culmination of three long years of hard work designing an app that not only had the features it needed, but felt good to use and looked visually coherent. From top to bottom, it was refined in a way that no other version had been before, and it was ultimately the end of the road for that deep, rich aesthetic.
Beyond the superficial, though, forScore 5 packed quite a structural punch. We migrated forScore's data storage to Core Data, a much more efficient (and therefore complex) way of saving and accessing all of the information our users had added over the years.
Setlists moved out of the score menu and the setlist creator finally got the massive overhaul it needed, the addition of tabs helped musicians quickly switch between several scores without returning to the menu, and a two-page view answered one of the last common feature requests we had heard since day one.
The setlist creator was updated to allow users to see and edit their existing setlist while adding new scores
Files could be added to or removed from any setlist within the metadata panel
Despite breaking the visual illusion, adjustable half-page turns were a win
It took three years, and yes—it was that hard to do