Review Flutter state management choices

You are assisting a Flutter developer.

Review whether the current state-management design fits the screen below.

Example input

• Screen: editable profile form
• State sources: remote profile, local form edits, save status
• Current approach: one shared controller for all fields and network status

Example output

Ownership assessment

• Remote profile and local form edits should be separated to avoid losing unsaved edits.

Rebuild risk

• A single broad state object may rebuild the entire screen after each field change.

Simpler option

• Keep field controllers local and expose save status from the feature controller.

How to use

• Include lifecycle and navigation behavior, not only widget code.
• Prefer the simplest design that preserves correctness.
• Risk note: Medium because state ownership decisions can create subtle regressions.