# Web & Mobile Engineering

> Web and native lifecycles, rendering, navigation, state, networking, offline behavior, accessibility, and release constraints.

Canonical: https://learn.significanthobbies.com/curriculum/concepts/web-mobile-engineering

Web and native lifecycles, rendering, navigation, state, networking, offline behavior, accessibility, and release constraints.

- Difficulty: core
- Tracks: Application Engineering

## Mental model

Client engineering is lifecycle engineering. Model loading, interaction, backgrounding, connectivity, persistence, accessibility, and platform conventions explicitly.



## Primary sources

- [MDN Web Platform](https://developer.mozilla.org/en-US/docs/Web) (doc)

## Practice

### 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.

**Expected evidence:** A design outline with lifecycle, stateModel, offlineFallback plus an explicit failure mode or trade-off.

## Review prompts

- Why does backgrounding matter more on mobile than on web, and what does it force into the architecture?

## Build evidence

- **Synthesize: Application Engineering** — Turn backend, client, UX, real-time, interactive, analytics, and distribution skills into one complete product. Produce one working system, benchmark, or evidence-backed design that integrates the path.

## Prerequisites

- [API Design](https://learn.significanthobbies.com/curriculum/concepts/api-design)

## Related concepts

- [API Design](https://learn.significanthobbies.com/curriculum/concepts/api-design)
- [UX & Interface Design](https://learn.significanthobbies.com/curriculum/concepts/ux-interface-design)

## Learning paths

- [12-Week Application Engineering](https://learn.significanthobbies.com/curriculum/roadmaps/application-engineering-12w)