I can see how charging extra for functionality that exists as part of the framework of the device is going to spark Apple's ire. I wish they had done this to the DJ apps that are charging for music library access (i.e. DJ Mixer the people who took down their paid app and replaced it with a new one).
So, they are going to respond by creating a "Pro" version of the app. Meaning, if you already had the current version, now you need to buy it all over again. That, my fellow readers, is called a rip-off.
Instead, the honest thing to do is take the current version, call it pro and raise the price (because they want to make money off of this new feature). Then, release a new "standard" app, that has all the functions except for CoreMIDI and whatever else makes it pro. Then release the free lite version as planned.
If they don't do this, I am complaining to Apple and giving the app a 1 star rating.
""So, they are going to respond by creating a "Pro" version of the app. Meaning, if you already had the current version, now you need to buy it all over again. That, my fellow readers, is called a rip-off.""
Nlog did the same kind of thing, short after I did an around 10 dollar upgrade to the pro version they removed it, and replaced it with only midi added having to pay full price again.
Their website states "CoreMIDI Support coming in March 2011!" and this was the reason I bought the app. Without MIDI support it's useless to me - pretty and a cool idea, yes, but I bought it while it was on sale on their promise that it'd support MIDI soon.
If they are indeed planning to charge extra for that functionality, I'll be contacting Apple for a refund on the app (never do e so before but it is possible apparently) and I'd suggest that anyone else who feels the same also does so, maybe that'll sense them a message.
It is not about in-app-purchases, but the lack of paid upgrades. It is simply not working to deliver lifetime free upgrades for a few bucks app. The result is that 95% of all apps I bought (and I bought many many) never saw a serious upgrade. The bizz model of the App Store is only supporting one-hit-wonders. Fire and forget. I would have given all NLog classic users a crossgrade option to NLog MIDI, but Apple does not allow this. At the end indie developers will only be able to continue their work, if people are willing to pay from time to time some money which is in most places less than a drink. Paid upgrades would be best, but who is able to direct Apple?
GB - although a quite disappointing app compared to the abilities Apple has - will put even more pressure on indie app developers. And they copied a lot of features from indie dev apps. Further Apple does not care about providing a plug-in model. Although: They have all technology in place. The full Audio Unit stuff is already in iOS and we are using it daily.
Fortunately Google is not doing music apps - yet. But Android still has too much fragmentation.
I have no bet where the community will be in 6 or 12 months. But the Audanika story is not very encouraging.
At the end it all depends if we are finding enough creativity and energy to develop music apps which user are willing to pay for. It is in our hands, but Apple is not always helpful.
I'd like to comment on the Anonymous poster who said we were charging extra on functionality that is part of the framework provided by Apple.
This is a huge misconception. The functionality is not there to just activate. It takes multiple developers weeks to implement it in a way that we would be ok with to offer it as a paid feature.
We could have implemented it real cheaply (which a lot of other apps did) but we decided against that and put a lot of hard work into it, months to be exact.
Apple not letting us charge money for it is a huge blow to our plans.
Also: Apps that offer a 'save' function only as part of an In App Purchase are doing the exact same thing. Only they're using other parts of the 'framework'.
There's tons of such apps out there and they get approved by the dozen.
I've removed the statement on our website that SoundPrism will have this feature but to be honest it could still be that we might get it approved. The whole matter is just impossible to predict right now because Apple isn't really talking to us.
@Sebastian Dittmann - It's not just anon, but also Apple who said it.
Just because you had to work on it doesn't really justify your argument either.
For one, every feature you add, every bug you fix requires work. Apple wouldn't let you do an in app purchase for updated functionality or bug fixes either. You won't be able to sell AirPlay, multitasking, iTunes file sharing, GameKit, etc. as in app purchases. And each one of them would require varying amounts of work to implement.
Second, this particular feature was possible through the grace of the latest OS, which is free. So for you to charge for it means you are making money off of Apple's work as well your own. It would hurt Apple's messaging to say that their OS has all these great features, but hold on, you actually have to pay extra if you want to use them in an app.
I like the suggestion about updating the current app with CoreMIDI and raising the price. Your loyal customers are rewarded then.
I have another suggestion though. Release a Pro version, but price it initially for a week at the price that you would have charged for CoreMIDI support. Two things happen, A) your customers don't get too pissed about having to purchase the app twice (you were going to charge extra for the functionality anyway). B) You may get many new users for your app, as we all know that the initial launch of an app is critical on the app store.
10 comments:
Trying to sell us CoreMIDI via in app Purchase? I can see why.
Boo this man.
Seriously though, that should def be a free update.
I would pay 59p for CoreMIDI support... what were they proposing to charge?
I can see how charging extra for functionality that exists as part of the framework of the device is going to spark Apple's ire. I wish they had done this to the DJ apps that are charging for music library access (i.e. DJ Mixer the people who took down their paid app and replaced it with a new one).
So, they are going to respond by creating a "Pro" version of the app. Meaning, if you already had the current version, now you need to buy it all over again. That, my fellow readers, is called a rip-off.
Instead, the honest thing to do is take the current version, call it pro and raise the price (because they want to make money off of this new feature). Then, release a new "standard" app, that has all the functions except for CoreMIDI and whatever else makes it pro. Then release the free lite version as planned.
If they don't do this, I am complaining to Apple and giving the app a 1 star rating.
""So, they are going to respond by creating a "Pro" version of the app. Meaning, if you already had the current version, now you need to buy it all over again. That, my fellow readers, is called a rip-off.""
Nlog did the same kind of thing,
short after I did an around 10 dollar upgrade to the pro version they removed it, and replaced it with only midi added having to pay full price again.
Their website states "CoreMIDI Support coming in March 2011!" and this was the reason I bought the app. Without MIDI support it's useless to me - pretty and a cool idea, yes, but I bought it while it was on sale on their promise that it'd support MIDI soon.
If they are indeed planning to charge extra for that functionality, I'll be contacting Apple for a refund on the app (never do e so before but it is possible apparently) and I'd suggest that anyone else who feels the same also does so, maybe that'll sense them a message.
NLog was a different story:
It is not about in-app-purchases, but the lack of paid upgrades. It is simply not working to deliver lifetime free upgrades for a few bucks app. The result is that 95% of all apps I bought (and I bought many many) never saw a serious upgrade. The bizz model of the App Store is only supporting one-hit-wonders. Fire and forget. I would have given all NLog classic users a crossgrade option to NLog MIDI, but Apple does not allow this. At the end indie developers will only be able to continue their work, if people are willing to pay from time to time some money which is in most places less than a drink. Paid upgrades would be best, but who is able to direct Apple?
GB - although a quite disappointing app compared to the abilities Apple has - will put even more pressure on indie app developers. And they copied a lot of features from indie dev apps. Further Apple does not care about providing a plug-in model. Although: They have all technology in place. The full Audio Unit stuff is already in iOS and we are using it daily.
Fortunately Google is not doing music apps - yet. But Android still has too much fragmentation.
I have no bet where the community will be in 6 or 12 months. But the Audanika story is not very encouraging.
At the end it all depends if we are finding enough creativity and energy to develop music apps which user are willing to pay for. It is in our hands, but Apple is not always helpful.
I'd like to comment on the Anonymous poster who said we were charging extra on functionality that is part of the framework provided by Apple.
This is a huge misconception. The functionality is not there to just activate. It takes multiple developers weeks to implement it in a way that we would be ok with to offer it as a paid feature.
We could have implemented it real cheaply (which a lot of other apps did) but we decided against that and put a lot of hard work into it, months to be exact.
Apple not letting us charge money for it is a huge blow to our plans.
Also:
Apps that offer a 'save' function only as part of an In App Purchase are doing the exact same thing. Only they're using other parts of the 'framework'.
There's tons of such apps out there and they get approved by the dozen.
I've removed the statement on our website that SoundPrism will have this feature but to be honest it could still be that we might get it approved. The whole matter is just impossible to predict right now because Apple isn't really talking to us.
Maybe your recent comment on your site about Apple review opacity didn't help. If it's so, shame on Apple...
@Sebastian Dittmann - It's not just anon, but also Apple who said it.
Just because you had to work on it doesn't really justify your argument either.
For one, every feature you add, every bug you fix requires work. Apple wouldn't let you do an in app purchase for updated functionality or bug fixes either. You won't be able to sell AirPlay, multitasking, iTunes file sharing, GameKit, etc. as in app purchases. And each one of them would require varying amounts of work to implement.
Second, this particular feature was possible through the grace of the latest OS, which is free. So for you to charge for it means you are making money off of Apple's work as well your own. It would hurt Apple's messaging to say that their OS has all these great features, but hold on, you actually have to pay extra if you want to use them in an app.
I like the suggestion about updating the current app with CoreMIDI and raising the price. Your loyal customers are rewarded then.
I have another suggestion though. Release a Pro version, but price it initially for a week at the price that you would have charged for CoreMIDI support. Two things happen, A) your customers don't get too pissed about having to purchase the app twice (you were going to charge extra for the functionality anyway). B) You may get many new users for your app, as we all know that the initial launch of an app is critical on the app store.
Post a Comment