Designing for One Screen

A project screen opens.

It shows:

• the project name;
• twenty tasks;
• each task's assignee name and avatar;
• each task's comment count; and
• the current viewer's permission to edit that task.

The API already has clean resources:

GET /projects/{project_id}
GET /projects/{project_id}/tasks?limit=20
GET /users/{user_id}
GET /tasks/{task_id}/comments?limit=20

Every one of those operations looks reasonable on its own.

The screen built from them can still be unusable.