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.
60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
---
|
|
type: system
|
|
project: fidelity
|
|
status: active
|
|
workstreams: [rest-migration, ao-discourse, xflow-debugging, xflow-swiftui-migration, consumer-integration]
|
|
related: [fid4, xflowviewmaker, ftframeworks, cogstore, consumer-integration, pdiap-14859, pdiap-15765, pdiap-15836, pdiap-15838]
|
|
updated: 2026-04-17
|
|
tags:
|
|
- system
|
|
- fidelity
|
|
---
|
|
# XFlowSDK
|
|
|
|
## Role
|
|
|
|
XFlowSDK is the backend-driven UI engine that renders Fidelity flows from service-provided configuration.
|
|
|
|
---
|
|
|
|
## Durable Context
|
|
|
|
- XFlow behavior depends on backend rules, entry point, and authentication state.
|
|
- SwiftUI migration work introduced recurring behavior questions that were not just visual; many were contract or lifecycle issues.
|
|
- XFlowSDK is developed in the dedicated repository `pr100660-xflow-for-ios`.
|
|
- Historical Slack patterns show recurring topics around:
|
|
- component type expansion in SwiftUI
|
|
- Next-button visibility rules
|
|
- markdown link handling and analytics
|
|
- modal presentation and dismissal sequencing
|
|
- consumer-vs-framework ownership boundaries
|
|
|
|
---
|
|
|
|
## Release Mechanics
|
|
|
|
- XFlowSDK publishing currently uses the Jenkins pipeline `xflow-for-ios-publish`.
|
|
- The publish flow builds the XCFramework, publishes it to internal Fidelity Artifactory at `artifactory.fmr.com`, and publishes the podspec to `ap010981-ios_podspecs_3x`.
|
|
- Once published, the new SDK version can be adopted downstream through `pod install` or `pod update`, but consumer validation still depends on XFlowViewMaker and Fid4 propagation.
|
|
|
|
---
|
|
|
|
## Debugging Implications
|
|
|
|
- Do not treat XFlow output as static UI; backend configuration can change the result.
|
|
- When behavior differs across environments, check whether the issue is:
|
|
- service/configuration driven
|
|
- auth-state driven
|
|
- entry-point driven
|
|
- consumer-integration driven
|
|
- Some apparent XFlow regressions historically turned out to be consumer, pipeline, or environment issues.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- SwiftUI behavior repeatedly needed parity work beyond UIKit assumptions.
|
|
- Next-button visibility logic required using the full set of service parameters, not only label text.
|
|
- Modal, delegate, and lifecycle sequencing became recurring themes in pure SwiftUI environments.
|
|
- XFlow work often had to be validated through consumer repositories, not only inside the SDK.
|