When the software has to fit the business
Most software does not fail at launch. It fails eighteen months later, when the person who wrote it has left, nobody can change it safely, and every new feature costs more than the last. We build the other kind.
That means readable code, tests that actually run, documentation somebody other than the author can follow, and architecture chosen for the problem in front of us rather than the one on a conference slide. Whether it is a mobile app, an internal platform or an integration between two systems that were never meant to speak, the standard is the same: you should be able to hand it to a different team and have them get on with it.