Daily iOS
Networking

REST from the client's side

The interviewer says "explain what a RESTful API is." Going beyond the textbook definition, from the point of view of someone building an iOS client, how does the difference between an API designed RESTfully and one that isn't show up in the client code?

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

REST identifies resources by URI and uses the standard HTTP methods, status codes, and stateless communication as they are. That regularity gives the client declarative Endpoints and a generic client, idempotency-based retries and caching, and shared status code handling.

Share a question