News of latest release of forScore for the iPad has gotten me interested in working with the new generation media slates again. With wedding season heating up, I’ve been scanning and moving my trio music to dropbox in the hopes of ditching that gig bag of books too (as I’ve already ditched most of my teaching bag).
The thing is, I’m not a fan of the iPad. I’m not saying it’s a bad product or anything, just that it’s not my thing; personal preference. It’s still a little small for what I like in a music reader, and lacks active pen input, but I think it could work for our trio music. Most of our books are made from smaller letter sized paper, rather than larger sheet music (A4, I think). With some cropping of the scans, this music comes out an acceptable size for the iPad display. The trio music doesn’t require much in the way of markup, and in my limited use I’ve found the drawing tools in forScore to be much improved.
I’d love to give an Android tablet a try, as I already use an Android smartphone and I love my HTC Flyer, which at 7” is way too small to consider for music reading. I’m not alone, as I’ve gotten a few emails from readers interested in Android tablets for sheet music. So I went looking. There are few enough apps in the Android market that are specifically for tablets anyway, and none of them are PDF music readers.
So, I emailed forScore to see if they might have any plans to break into the Android world and their reply echoed a lot of what I’ve been hearing from other app developers. I do appreciate the time they took to explain. Here is their response:
“First off, the biggest reason why we haven't jumped into the Android ring is simply a matter of resources: we started and continue to run our company during what will probably be considered the worst economic conditions of a generation, so we've always been very deliberate in how we spend our time and resources. We'd rather make a single product that's really solid and gets frequent updates than two products that don't always work well (the latter being the approach that all too many developers take).
Secondly, the iPad commands an overwhelming majority of market share at this point. We'd be spending more than half of our time working on a version that may only yield a small percentage of the sales we see with the App Store, so it's just not worth it at this point.
Finally, and really most importantly, the Android environment itself just isn't as attractive. From a hardware standpoint, there are a bunch of different devices all with varying capabilities (some have cameras, some don't, some are very fast, others can barely keep up). If we have to either ship an untested product or purchase one of every Android tablet out there, then that's a big issue to take into account. From a software standpoint, Apple's environment is just a lot more attractive and easier to work with on the whole. There's a level of integration that Google can't match, and the ubiquity of the platform makes it easier to get help from the community as needed.”
I can’t blame them. It’s one of those catch 22 cycles where there’s not enough adoption of the platform to warrant developing apps for it, but no one is going to adopt the platform if there aren’t enough apps. No one want to write for a platform that people aren’t using, and people don’t want to use a platform that no one is writing for.
Also, while the hardware has become much more standardized on honeycomb (10” 1280x800 screens, Tegra2) there are still plenty of variations even in those (camera? SD card? microSD? full size USB?).
The real killer though is the screen. The 10” widescreen is simply too narrow in portrait mode. I swung by Best Buy to check them out again, and was able load a PDF of music from my dropbox. While there are no specific music readers, there are plenty of tools to read PDF files. The iPad is barely passable in size for me, so the narrower Android tablets were just too small. With their smaller screens and lack of apps, I could not recommend an Android tablet for music reading. Not on the current generation of hardware at least.