5 ms·
Come on, you spent $5 for an app. For a working app! This is a pretty low price. Actually, it's basically nothing. Of course you can't get support and are not e
by struppi 13y ago
Come on, you spent $5 for an app. For a working app! This is a pretty low price. Actually, it's basically nothing. Of course you can't get support and are not entitled to feature requests at such a low price tag!
- astral303 13y ago$5 is not cheap by app store standards. It's a fair price for an app in that class. As to whether you're entitled to support or feature requests, you can make an argument both ways. One could generate some word of mouth by following up on (simple) feature requests. In one of the apps, Fourier, the reviewers say that the horizontal frequency scale is off by a factor of 2 (but the frequency display elsewhere is accurate). That's a small thing to fix that hasn't been fixed since Apr 2012. I think that at a $5 price point, my expectation is that the app is updated with at least bug fixes of that variety.
- ProblemFactory 13y ago"App Store standards" don't really work for valuable niche software. They can work for games that end up selling 10 million copies, but there's a reason why professional software with few users is usually priced between $500 and $100 000. $5 is worth 3 minutes of developer time at common hourly contracting prices. If a developer receives and reads an email from a customer, they will probably end up with no profit. If they respond to it, let alone are adding new custom features, they are certainly losing money compared to working for someone else.
- eo34 13y agoFirst, wow, I didn't expect any HN readers to actually know about, much less have bought, my work! Thanks. Second, I understand your frustration. I love building things, and sometimes I wish I could do that full time, but grad school is a 70 hr/wk commitment for me. If the app is not useful for you without the missing feature, Apple does allow returns. I'm not quite sure how it works, but I see a few returns a year on my reports. Also, I've open-sourced the hardest part of the app, the audio managing aspect, as Novocaine (GitHub.com/alexbw/novocaine), and along with the great package NVDSP, anybody could replicate the basic functionality of my apps with a few weeks of learning and effort. It'd be great for the audio app ecosystem, too! I'm also interested in hiring a part-time developer to help flesh out the top-requested features, if anybody has ObjC coding experience. That'd make many more updates possible.
- astral303 13y agoThat open source library is awesome. Wow, thank you.
- rgbrgb 13y agoI've used novocaine on a hackathon project. Very fun little library, thanks! It was 10,000 times easier than setting up the audio unit chain, etc. I had done it the old fashioned way for my first app but there was an incredible amount of error-prone boilerplate code when all I really wanted was a callback function to populate output buffers. This thing also looks pretty cool: http://theamazingaudioengine.com/ http://theamazingaudioengine.com/
- coupdejarnac 13y agoNovocaine is wonderful, thank you.