[67726e]

Yes, a good programmer writes a robust application, but ignoring the specifics of this case is being entirely disingenuous. If I write an app to use the Play API and only distribute it via the Play Store then there is no good reason for me to spend my time writing `if (foo != null)` all over the place to placate someone trying to circumvent the official way of downloading my application.

You have to balance the tradeoffs of bloated code and pointless error checking with adding features and improving the program. The more error checking code one writes the more one must maintain and the higher the potential for bugs.

[jacquesm]

> The more error checking code one writes the more one must maintain and the higher the potential for bugs.

That's an artifact of the chosen environment. Not checking for errors in that environment is a bug.

[67726e]

Artifact or not, it's still something one must maintain. Not checking for errors is not a bug, it is you choosing to not support a fringe group of users because it is worth your time and effort. You can call it whatever you like, but that is the reality of the situation. There are tradeoffs to be made and code to be maintained.