I think it's easy for me and you to understand that they were acquired for their talent but to ordinary people it just looks like they've bought something, were

I think it's easy for me and you to understand that they were acquired for their talent but to ordinary people it just looks like they've bought something, were promised updates, and they weren't delivered. That reflects badly on all developers and it's something that's been happening a lot in the last few years. Businesses need their customers to trust them and acquihires are making the entire community look bad. Acquihiring is irrelevant. If anything, what's making the app developer community look bad are developers making promises they don't or can't keep. It's simple: if you promise something, deliver it. Know why Apple doesn't pre-announce features? Because announcements are promises, and nothing can be promised until it's done. Heck, even being as careful as they are, they've announced features that never shipped. At my company, we're extremely wary of pre-announcing anything when we interact with our users and, when we do, we go to lengths to emphasize that we can't promise anything until it ships. To be clear, I'm not accusing Sparrow's team of willfully misleading, lying, or misrepresenting anything. I'm certain they were confident their promises were good. Nor do I fault their decision to join Google; I'd probably do the same given the right compensation and opportunities. This is just a great example of why promising features is risky and should be avoided – you never know what the future will bring.