Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a single-screen SwiftUI app in Swift (e.g. a tip calculator, a unit converter, or a counter/checklist). Use state correctly — @State for a view's own local values and @Binding to pass two-way state to child views (keep children stateless and driven by bindings). The UI must be declarative (body describes the UI for the current state), use value types (struct) for your models, and unwrap any optionals safely (no force-unwrap in the happy path). Run it in the Simulator.
Declarative views; @State for local state and @Binding for two-way child state (correct ownership); UI is a function of state.
Value-type models (struct); optionals unwrapped safely (if-let/guard-let/??, no reckless !); idiomatic Swift.
Compiles and runs in the Simulator without warnings; clean view structure.
Reasonable layout, modifiers used well, follows basic HIG conventions.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A SwiftUI app with correct state ## Goal Build a single-screen SwiftUI app in Swift (e.g. a tip calculator, a unit converter, or a counter/checklist). Use state correctly — @State for a view's own local values and @Binding to pass two-way state to child views (keep children stateless and driven by bindings). The UI must be declarative (body describes the UI for the current state), use value types (struct) for your models, and unwrap any optionals safely (no force-unwrap in the happy path). Run it in the Simulator. ## Acceptance criteria - [ ] SwiftUI & state: Declarative views; @State for local state and @Binding for two-way child state (correct ownership); UI is a function of state. - [ ] Swift correctness: Value-type models (struct); optionals unwrapped safely (if-let/guard-let/??, no reckless !); idiomatic Swift. - [ ] Builds & runs: Compiles and runs in the Simulator without warnings; clean view structure. - [ ] Polish: Reasonable layout, modifiers used well, follows basic HIG conventions. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.