Actually I think Microsoft is partly responsible for the sense of self-righteous indignation that developers have when they get displaced. They deliberately held back on introducing even basic features into Windows for a remarkably long time. Things like anti-virus, paint programs, text editors, photo management - even opening zip files - were left with token or no support for 5 to 10 years after they were no brainers in terms of expected or useful functionality. Of course, MS had (and still has, though less so) a regulatory threat to worry about that nobody else does.
I'm not sure it's that. I think it's just that their strategy of only ever targeting the top 20% most profitable customers means they never broach market shares that make them a threat to competition by the conventional measures used by regulators.
That's... odd.
There's sort of a point there but MS dropped that approach a good many years ago (look at security centre, movie maker and so on) so I'm not sure it's really relevant today.
Even still, anti-virus and movie maker are not default installs (and not even delivered on the install media) which is at least partly attributable to MS still being hesitant to cross that line.
Possibly it came down in a Windows Update (I tend to just say "everything") but if that's the case it's surely only the finest of whiskers away from being a default install.
> because he felt he could bring more to it
> than Apple would
Until his next update is rejected because it duplicates functionality that iOS already provides and would 'confuse' consumers (so could you please stop attempting to compete with us, please?).Checkmate!
If you are willing to be more agile than the vendor you'll always have something, but if all you do provide something basic which can be simple replaced by the vendor, then yes, all you can do milk it as much as you can until vendor get there. (and for small project, one-man shops even this makes a lot of sense)
He described certain applications as grabbing nickels from the path of an on-coming steamroller. Effectively what he was saying was that there are things which are going to be added to products eventually and while there is money to be made by getting there first, the developer needs to accept that it's inevitable that they're going to be ploughed down eventually.
But this isn't just Apple and it's not just iOS, it's software and in particularly operating systems everywhere (or does someone want to tell me that the differences between Windows 1.0 and Windows 7 hasn't impacted on any developers anywhere?).
If your business model is taking what someone else does and doing it just a tiny bit better this comes with the territory. You either need to live with that or keep doing it better so they don't catch up.
Marco Arment wrote a piece on how he didn't care about a rumoured forthcoming addition to iOS despite it competing with Instapaper because he felt he could bring more to it than Apple would and in fact it might bring him new customers by raising awareness of this sort of feature.
If you're not thinking that then I'm sorry to say that your product really wasn't strong enough or different enough in the first place for it to be anything other than a short term venture.