3 ms·
There are many forms of "crappy". Developer hygiene is one bar; user functionality is another. "Crappy" here refers entirely to developer hygiene, which the u
by Arainach 3y ago
There are many forms of "crappy". Developer hygiene is one bar; user functionality is another.
"Crappy" here refers entirely to developer hygiene, which the user does not care about at all.
If the platform changed and Angry Birds crashed, the customer would not accept "but look at all of these other Angry Birds clone games still available" as an answer, they want the app they are familiar with.
- chrisjj 3y ago> If the platform changed and Angry Birds crashed Angry Birds doesn't print AFAIK. The scenario is an app being run on a platform that doesn't meet its declared system requirements. If an app requires Windows, and customer tries to run it instead on Xbox OS, then he should be surprised it even launches. He should not be surprised if it crashes on print. > customer would not accept "but look at all of these other Angry Birds clone games still available" as an answer, they want the app they are familiar with. Then he'll have to run that app on the OS it requires. He's free to sent to MS his complaint that Xbox does not run that OS.
- Arainach 3y agohttps://en.wikipedia.org/wiki/Metaphor https://en.wikipedia.org/wiki/Metaphor Telling customers "well go use this other platform" is not an effective way to build or grow a platform.
- chrisjj 3y ago> Telling customers "well go use this other platform" is not an effective way to build or grow a platform. Honesty is the best policy. Telling customers they should expect to run apps that don't support your platform is not honest.