Unit 03 of 03
Bridging
Declarative and imperative interfaces wrapping each other to run in the same app, incremental screen-by-screen migration of legacy code, and which interface framework to choose in which situation.
Published Updated
Lessons
- 01 Declarative and Imperative Interfaces Together Measuring how a screen falls behind the model when the root view is not reassigned while embedding a declarative view in an imperative screen, and when no update is written while wrapping an imperative view in a declarative screen. 13 min read
- 02 Incremental Migration of Legacy Code Measuring that a field not carried over stays missing on the new screen while moving a legacy screen to the new framework one screen at a time, that a field dropped from the model stays leftover on the old screen, and that the rule works per field, not per screen. 14 min read
- 03 Choosing a Framework Measuring two screens, one declarative and one imperative, built from the same model and checked with the same rule, showing that agreement is not a criterion for choosing a framework; the closing table of the course's fifteen lessons. 11 min read