david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
48 lines
1.6 KiB
Markdown
48 lines
1.6 KiB
Markdown
---
|
|
type: workstream
|
|
project: fidelity
|
|
status: active
|
|
systems: [xflowsdk, xflowviewmaker, ftframeworks, fid4]
|
|
work-items: [pdiap-14859, pdiap-15836]
|
|
related: [consumer-integration, xflow-debugging]
|
|
updated: 2026-04-16
|
|
tags:
|
|
- workstream
|
|
- fidelity
|
|
---
|
|
# XFlow SwiftUI Migration
|
|
|
|
## Goal
|
|
|
|
Track the durable behavior patterns introduced while moving XFlow from older assumptions toward a more complete SwiftUI implementation.
|
|
|
|
---
|
|
|
|
## Stable Themes
|
|
|
|
- SwiftUI migration was not just a UI rewrite; it exposed contract, lifecycle, and parity gaps.
|
|
- Historical Slack evidence repeatedly referenced:
|
|
- component type expansion beyond simple string assumptions
|
|
- Next-button visibility rules driven by full service parameters
|
|
- markdown link handling and analytics integration
|
|
- navigation and modal behavior in pure SwiftUI environments
|
|
- dismissal delegate lifecycle sequencing
|
|
|
|
---
|
|
|
|
## What Matters Now
|
|
|
|
- When a SwiftUI issue appears, check whether the missing behavior is:
|
|
- parity with UIKit behavior
|
|
- an incomplete service contract interpretation
|
|
- a lifecycle sequencing problem
|
|
- a consumer presentation constraint in Fid4
|
|
- Do not assume a visual issue is only cosmetic; several historical SwiftUI bugs changed flow behavior materially.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- Jeff and Norman repeatedly refined story titles and descriptions around SwiftUI architecture changes, showing that scope wording mattered because the work was often deeper than the first symptom.
|
|
- Historical Slack context also shows that SwiftUI-specific work frequently required cross-team clarification when external dependencies or consumer environments behaved differently.
|