forScore mini

As some great developers once said, some ideas don’t make sense until suddenly they do. Today we’re very excited to give you a first look at a project we’ve been working on for quite some time now: forScore for iPhone.

Since forScore was first introduced we’ve heard from people who, while recognizing the obvious limitations of viewing sheet music on a tiny screen, have wondered if there was a way to combine the ultimate portability and connectivity of an iPhone with the full feature set and speed of the iPad. That’s exactly what we’ve done, and forScore on the small screen is no compromise when it comes to either. It’s lightning fast, and it replicates every single feature of forScore for iPad (except the storefront, due to in-app purchase limitations). It’s not a read-only app, not a mobile companion, it’s the complete forScore experience in your pocket. This was our most important goal when designing forScore mini, and we couldn’t be more proud of the results.

Of course, the 4-inch elephant in the room is the iPhone’s tiny screen size. Thankfully, Apple answered that question for us (as we were hoping they would) with the new iPhone 6 and 6 plus. Suddenly, this idea makes sense. The 4.7 and 5.5-inch screens used in the latest generation of iPhones are a huge step up and really make this a viable product. We won’t be requiring an iPhone 6, but we’ll be strongly recommending one.

Finally, our incredible new layout feature that we introduced with forScore 8, Reflow, is a key part of this mobile experience. Reflow, if you missed our recent post, is an accessibility feature that finds and lays out each system of music in a score end-to-end, creating a sort of horizontal teleprompter experience that lets you significantly increase the size of music on a device. On the iPad, it’s a great enhancement for our customers with vision problems, but on the iPhone it’s essential. It’s what turns a tool for casual review into a full-blown music reader.

This is new territory for us, and we couldn’t be more excited. We’re going to need some help, though, so we’re asking for beta testers to try it out and give us feedback on what works and what doesn’t. If you’re interested, let us know. Otherwise, be sure to check back here as we finish it up and release it later this year.

Update: We have reached our beta tester goal for this version, but we’re working hard to finish forScore mini so everyone can try it out as soon as possible. Thanks for your interest!

Small App Updates

Our three apps for the iPhone and iPod Touch have been optimized today for the iPhone 6 and iPhone 6 Plus’ bigger screens. Cue 1.1, Pitch, Please! 2.2, and Beat Keeper 3.1 will now look great on these latest iPhones without scaling up, and we’ll be taking another pass at them once we actually have an iPhone 6 Plus in hand to see what else we can do to take full advantage of its huge new screen. These three apps updates are free, so be sure to check them out if you’re upgrading!

forScore 8.0

Today we’re proud to announce the release of our latest major update to forScore, version 8.0. Over the past several weeks, we’ve taken an in-depth look at some of its key features and enhancements: an updated media box, a brand new tuner, integration with select Bluetooth Smart devices, a completely redesigned annotation experience, and innovative new accessibility features.

It’s also compatible with iOS 8 and includes a few other features that we didn’t get a chance to unveil, such as the ability to export your setlists as one long merged PDF, the ability to batch export annotated PDFs, and a widget that lets you access forScore’s pitch pipe from iOS 8’s “today” view.

This great update to forScore is completely free for existing users, as always, and now just $9.99 (USD) for everyone else.

iOS 8 Compatibility

With iOS 8’s release coming this Wednesday, we wanted to take a moment to discuss some important things forScore users should be aware of.

First, forScore 7.1.2 is not compatible with iOS 8, so if you upgrade your iPad to iOS 8 you’ll also need to install our forScore 8.0 update. Otherwise, forScore 8 works great with both iOS 7 and 8, so you can continue to use iOS 7 and still get forScore’s latest and greatest features if you like.

Unfortunately, we’ve discovered that iOS 8 breaks forScore’s “force virtual keyboard” feature which allows users to type with the virtual keyboard even when a keyboard-style Bluetooth page turner is connected. In short, we don’t expect to be able to fix it. If you’re using an AirTurn BT-105, PageFlip Firefly, or certain newer revisions of PageFlip’s Cicada, however, you can take advantage of hardware features that work around this problem. Otherwise, you’ll need to turn off the page turner every time you want to type. The iRig BlueBoard, which uses Bluetooth Smart, is completely unaffected.

We know this will be a big issue for some of our customers, and we won’t stop looking for other potential ways of working around this limitation. Until then, please help us spread the word by letting your colleagues know so everyone can make an informed decision about when to upgrade. Regardless, we’re very excited about the upcoming release of forScore 8.0, and we’ll be announcing it right here very soon.

Update: Edited to include new information about PageFlip’s hardware workaround.

Developers

Our next big update to forScore is coming soon, but we wanted to take a moment today to announce something a little different: a new Developer initiative that we’ve been working on over the past few months and a set of forScore SDKs.

SDKs, or Software Development Kits, allow developers to share functionality without revealing their code (we use Dropbox’s SDK, for instance, to allow our users to share files with their cloud storage service). This creates a safe way for developers to collaborate without worrying about their code being altered or exploited. When we began to consider creating our own SDKs, we identified three unique situations where customers might want this kind of collaboration: remote control, publishing, and sharing.

Cue, forScore’s remote control protocol, has proven to be a big hit with musicians. It allows one person to use forScore just as they normally would, and allows other nearby forScore users to follow along automatically. It’s a great feature, but it’s just one implementation of a common idea. Several music readers have similar features, but none of them work together, and our new CueKit SDK aims to fix that. With it, other apps can connect to forScore and send or receive program changes, page turns, and more.

ScoreKit, our second SDK, lets other apps export PDF files using forScore’s 4SC format, so they can share their scores with additional metadata and annotations. Music composition apps might use this tool to help their musicians transition from creating to performing their own music. ScoreKit can also read 4SC files sent from forScore, with one important rule: any app that can import 4SC files must also export them. After all, we want to improve collaboration, not give our competitors a one-way advantage.

We work hard to make forScore the best app it can be, but we know that people have many choices and we want them to be able to use the best app for them without feeling locked in or left out. We know this is just a first step, but we’re very excited to continue this initiative and find other ways we can work with our colleagues to elevate the ecosystem for all musicians. If you’re using an app that you think could benefit from one of our SDKs, let their creators know! Both of our SDKs are completely free, so there’s no reason for them not to take a look.