Daily iOS
Networking

Priorities in an API-to-list exercise

In a one-hour exercise you're asked to build an app that calls a public API and shows the results in a list, and you'll be graded on architecture, error handling, and UI performance. As a senior engineer, what would you build, in what order?

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

Get a working vertical slice running within 20 minutes: a thin API client behind a protocol, Decodable models, an @Observable view model with loading/success/failure state, and the list. Then add error UI, cancellation, and an image cache in that order.

Share a question