Coding (Platform)

Android / Kotlin: Validate state transitions for push inbox lifecycle transitions

A device lifecycle boundary exposes stale data when network and local state disagree. The affected area is push inbox.

Repair the push inbox lifecycle transitions implementation so it accepts only declared state transitions and reports rejected requests.

Evidence

Affected surface: Android / Kotlin / push inbox.
Observed failure family: validate state transitions.
Scope policy: zoneState must equal healthy.

What this task practices

This coding (platform) exercise trains the same sequence expected in an interview: understand the prompt, make assumptions explicit, produce a concrete answer, and explain the decisions behind it. The task is marked easy difficulty. The private workspace adds the tools required by this round, such as recording, code execution, diagrams, evidence panels, or structured notes. It also preserves the attempt so later feedback can be compared with previous work. Evaluation is based on task-specific criteria and the candidate seniority selected in the preparation path. Public pages never expose the reference solution, hidden tests, evaluator instructions, or another candidate’s work.