KVR Audio

zvon · Post by **zvon** » Fri Jun 21, 2013 2:22 pm

Apple wants to remove Orphion from the App Store because of the way its innovative articulation gesture is implemented.

Read more about this here:
http://createdigitalmusic.com/2013/06/h ... -936053401

Petition to Apple to let Orphion using its "articulation gesture" API:
https://www.change.org/petitions/apple- ... e_petition

Karmacomposer · Post by **Karmacomposer** » Fri Jun 21, 2013 3:00 pm

I signed the petition. How dare they pull an app because they don't 'like' how the author programmed it.

I assume they are coming out with an update to IOS that will make this 'feature' Orphion uses incompatible.

That's my guess.

Mike

martygras · Post by **martygras** » Fri Jun 21, 2013 3:31 pm

This could set a very bad precedent. Although it seems like the devs may have wandered into forbidden territory.

steffe · Post by **steffe** » Fri Jun 21, 2013 4:33 pm

Karmacomposer wrote:I signed the petition. How dare they pull an app because they don't 'like' how the author programmed it.

I assume they are coming out with an update to IOS that will make this 'feature' Orphion uses incompatible.

That's my guess.

Mike

by using private APIs this developer broke the license agreement he signed with Apple. removing such violations from the appstore is common procedure and in general has nothing to do with the nature of the app or the developer as a person.
and no, he used Apple' private API - so it is not about his code, but about Apple's IP.

Dewdman42 · Post by **Dewdman42** » Fri Jun 21, 2013 5:34 pm

That's good to know but equally annoying that Apple cripples their public API's to the extent that cool features like this can only be created by accessing private API's. And annoying that Apple won't just let innovative things live free and prosper. App Store is Big Brother.

ZenPunkHippy · Post by **ZenPunkHippy** » Fri Jun 21, 2013 5:45 pm

Dewdman42 wrote:That's good to know but equally annoying that Apple cripples their public API's to the extent that cool features like this can only be created by accessing private API's.

APIs are usually marked private because the feature is experimental, or it's not full tested and ready for public use yet.

There is nothing sinister going on here, the app developer has used a private API that may or may not be deprecated in the future. The app being pulled is just one of the consequences of making the decision to go ahead and release the app knowing the API is "private".

Apple can do some evil things, but this is not it.

Peace,
Andy.

the_only_real_lala · Post by **the_only_real_lala** » Mon Jun 24, 2013 10:00 pm

what a bad move from the developer of the app

1st he uses stuff he isnt supposed to use and now he is trashing apple publicly with the help of other ppl, that's going to help

and yes i think the function is cool

v1o · Post by **v1o** » Mon Jun 24, 2013 10:07 pm

To quote the comments section. It's because the developer broke the rules by using a private API. It's nothing to do with use of gestures.

There are two cases for why private APIs exist:

1) they are not finalised and it might change at any point as they refine the SDK. Apple uses them internally in some apps, but doesn't feel they are of enough quality to be made public just yet. Think of it as a prototype car. Ford might test it in the premises, but it won't give access to it to consumers. If developers are using a private API then when Apple changes it (e.g to improve it or do it differently) all apps that rely on it break.

The "public" part means "this stuff will not change, you can use them and be assured your app will work with iOS updates".

2) the company wants to only itself use those APIs.

Reason 1 is far more prevalent. Every platform or library has tons of internal (private) APIs. The distinction between private and public APIs is also important for several styles of programming, because it's believed to make programs more robust and easier to change in the future.

Reason (2) can also happen, but that's not in play here, or the case usually.

Karmacomposer · Post by **Karmacomposer** » Mon Jun 24, 2013 10:11 pm

Then WHY did Apple approve the app to begin with, hmmm?

They should have seen that he went into their No-Man's Land and not approved it.

Don't they have some culpability at this point.

People paid money for this - now they get screwed because Apple 'discovered' their mistake and his bad judgement.

There needs to be accountability here - by either party.

Mike

the_only_real_lala · Post by **the_only_real_lala** » Mon Jun 24, 2013 10:22 pm

he could have informed his customers, hey before u buy - this is a test, i am not sure how long this is going to last
but he didn't

mummy told me not to eat all the cookies now i have to go to bed without supper

steffe · Post by **steffe** » Tue Jun 25, 2013 5:47 am

Karmacomposer wrote:Then WHY did Apple approve the app to begin with, hmmm?

They should have seen that he went into their No-Man's Land and not approved it.

Don't they have some culpability at this point.

People paid money for this - now they get screwed because Apple 'discovered' their mistake and his bad judgement.

There needs to be accountability here - by either party.

Mike

Of course you can blame Apple - but, everyone who bought something from the App store also agreed to some agreement.

it is definitely obvious when you use private APis - as a developer you know and you also know that your app will get removed or not admitted .... With a couple if hundred apps or more per day in the review process - things slide through or a let through (like this social media stuff that transfers contact data which is also a violation of the developer contract - but sadly those do obviously not have to fear consequences)

AppStore as all business related things are not about fairness, but about success and profit - those are the rules applied by Apple.

and if you look at the price of an app and compare ot to a coffee or a meal - well, you also do not get full satisfaction with each coffee and it does not last very long ...

best

plastic · Post by **plastic** » Tue Jun 25, 2013 6:48 am

So, as a customer, if it stops working, can I return it, to get my money back?

the_only_real_lala · Post by **the_only_real_lala** » Tue Jun 25, 2013 7:55 am

plastic wrote:So, as a customer, if it stops working, can I return it, to get my money back?

i returned one app i bought the next day to apple, it was an app that only worked with a newer os - i mean i could open it, it didnt crash or something, i just couldn't use the function the app was made for
i got my money back after a 2 mails back and forth - in the last mail they said something that meant like don't try this again

but in this case, i don't think so

Wormhelmet · Post by **Wormhelmet** » Tue Jun 25, 2013 12:34 pm

I hope there is an uproar about this from consumers that sets a precedent to not allow apps with private API's into the App Store.

What if this was some $50 app with a ton of in-app purchases available?

Don't release apps that aren't going to be supported. If its public API, then the chances are great that Apple will support it in their iOS updates. If this was a public API used, then all consumers could go to Apple to protest with good cause.

A disclaimer should have been done so it pops up and is easily recognizable stating this was released with private API and might not be supported with further iOS version releases.

At any rate, the purchasers of this app were unaware of the risk and both Apple and the Developer are to blame for this being in the App Store released as is with this risk.

Orphion discontinued by Apple