Ask HN: How should pricing work for my app?
Hi,
I posted before on HN about this, but at the moment I'm working on a series of sound toys for Android. Each one is 'organic' in its design, and resembles more an organism that produces sound than an instrument.
Initially I was planning on pricing them at $1 each, but maybe this is too steep for something that isn't a game, or has value that increases measurably over time. Should I package several of them into one app and sell it for $1? I've read somewhere that if people are given too much choice they have a hard time making a decision, so would it be best to package the organisms into one app? Also, is it an evil marketing trick to set a price when there is buzz around a product and say it only exists for a 'limited time'?
An open Ask HN community consultation from 2011 where @Banekin convened hundreds of developers and bootstrappers to share real experiences, hard numbers, and tactics.
Hundreds of active indie hackers contributed case studies, pricing heuristics, and pitfalls to avoid when moonlighting on side projects.
Human psychology 1.0 :-)
YMMV, but 'too many choices' can be a strong deterrent to impulse buying which, imho, is your best friend, given the kind of apps you have.
HTH
Sell them both ways, apart and in a bundle. Keep the price of the bundle lower than the sum of all parts and somehow link to the parts from the bundle. This will show the user that hes getting a good deal.
Maybe sell the less quality ones for 10c a piece, but the really cool ones for a buck. That's my vote.