david.delagneau
374991a568
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md - Updated opencode.json to remove references to deleted files. - Revised profile.md to clarify the status of legacy paths and communication evidence. - Adjusted prompts to reflect new file paths and improve clarity. - Enhanced daily logs with focus, work-items, and blockers properties. - Updated work-item notes to include systems, workstreams, people, and related properties. - Improved context maintenance guidelines to ensure accurate and durable project knowledge. - Refined base filters to exclude template files and ensure only relevant notes are displayed. - Updated daily templates to ensure proper formatting and consistency. - Modified workflows to align with the new vault structure and improve context synchronization.
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.
|