An app can be designed to support CoreMIDI for devices running iOS 4.2+, and just disable those MIDI parts if it detects it's running on an older device that won't have access to those libraries. So the older devices will still be able to run everything else in the app, they just can't use those specific features of the newer OS.
It's not too hard to implement when it's just one feature and just one OS version check. When you get three or four different OS versions with five or six features, it gets a lot less fun real quick, especially to test.
Thanks for that info ART. I see all the power is in the devs hands. I guess this is how nanostudio does it. I always thought that was the case but glad you made it clear. I apologize to SJ about calling his idevices fragmented.
5 comments:
On the iTunes page for this app it says, "Requires iOS 3.2 or later" how is that possible if the app supports core MIDI?
It probably just didn't get updated yet..
An app can be designed to support CoreMIDI for devices running iOS 4.2+, and just disable those MIDI parts if it detects it's running on an older device that won't have access to those libraries. So the older devices will still be able to run everything else in the app, they just can't use those specific features of the newer OS.
It's not too hard to implement when it's just one feature and just one OS version check. When you get three or four different OS versions with five or six features, it gets a lot less fun real quick, especially to test.
Great info, Art, thanks for posting it!
Thanks for that info ART. I see all the power is in the devs hands.
I guess this is how nanostudio does it. I always thought that was the case but glad you made it clear.
I apologize to SJ about calling his idevices fragmented.
Am I the only one who finds it slow reacting to touch?
Post a Comment