So, to clarify, the "feature" I was referring to was replacing the system font (Helvetica). Even when we requested Helvetica by name, we'd get the random repla

So, to clarify, the "feature" I was referring to was replacing the system font (Helvetica). Even when we requested Helvetica by name, we'd get the random replacement. Are you suggesting we license and distribute Helvetica with our application? It's just not fast enough (at run-time or code effort wise) if we have to to calculate font metrics for every single static label in the application to make sure it fits in the space allotted. Some assumptions are valid, not lazy or bad. It's simply not possible to account for every possible scenario when all bets are off. [Edit] Note: In this particular case the label flowed over a button on a non-scrollable pop-over dialog. Not being able to click that button in the registration flow kept people from using the app at all. This was ages ago so I can't point you to the reviews, but there were enough of them that it mattered. It was also in the days before we added in-app reminders to leave good reviews, so basically the only reviews were from font-breakers.