> It sounds like there’s also a good chance that Yahoo’s apps might get a bit of Artifact’s speed and polish over time, too.
This never happens. Good design isn’t a quality you can spread around. Speed and polish are the result of focus. In an acquisition by a big company, you’re expanding the number of people you have to work with, who all want to carve up your app into little pieces. Once you integrate with the bigco’s security, auth, ops, design language, branding, adtech, billing, matrix management, and this quarter’s initiatives, there’s no “speed and polish” left.
The best case scenario for retaining good design is that you’re bringing enough users/revenue that you get to be a Very Special Snowflake in the org chart. Or, if your acquired company outputs a software artifact for the rest of the company to use, like a search engine or database.
I thought that line was funny too. Speed and polish is rarely an additive change. You don't just copy-paste some "go fast" code over to the other code base!
This never happens. Good design isn’t a quality you can spread around. Speed and polish are the result of focus. In an acquisition by a big company, you’re expanding the number of people you have to work with, who all want to carve up your app into little pieces. Once you integrate with the bigco’s security, auth, ops, design language, branding, adtech, billing, matrix management, and this quarter’s initiatives, there’s no “speed and polish” left.
The best case scenario for retaining good design is that you’re bringing enough users/revenue that you get to be a Very Special Snowflake in the org chart. Or, if your acquired company outputs a software artifact for the rest of the company to use, like a search engine or database.