Daily iOS
Architecture

Judging third-party libraries

This is a take-home review. You didn't use a single third-party library in the app you submitted, and the interviewer asks why not, and if you had to, which parts you'd swap for which library. Answer with your criteria.

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

The criteria are: is the standard framework enough, does the library solve a problem you actually have, and can you afford the maintenance, security, binary size, and lock-in cost. Networking and JSON are covered by URLSession and Codable; areas that are expensive to build yourself, like image caching and snapshot testing, are where you use one.

Share a question