> Having components with lifecycle methods called at known times by the framework is a perfectly straightforward mental model. It's worked just fine since the b

> Having components with lifecycle methods called at known times by the framework is a perfectly straightforward mental model. It's worked just fine since the beginning of time. iOS still uses it. Android, too.