core practice · system design prompt
Design exercise: Web & Mobile Engineering
Web and native lifecycles, rendering, navigation, state, networking, offline behavior, accessibility, and release constraints. Implement designOutline() returning non-empty values for: lifecycle, stateModel, offlineFallback. Each value must name a concrete mechanism or decision.
The mechanism
Client engineering is lifecycle engineering. Model loading, interaction, backgrounding, connectivity, persistence, accessibility, and platform conventions explicitly.
Expected evidence
A design outline with lifecycle, stateModel, offlineFallback plus an explicit failure mode or trade-off.
Try this drill in the practice workspace →
Hints when you need them
- Name the failure mode before selecting the mechanism.