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.
3.5 KiB
3.5 KiB
type, project, status, ticket, title, systems, workstreams, people, related, updated, tags
| type | project | status | ticket | title | systems | workstreams | people | related | updated | tags | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| work-item | fidelity | active | PDIAP-14859 | Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation |
|
|
|
|
2026-04-16 |
|
PDIAP-14859 - Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation
Status
- Active
- Rollout draft prepared and sent to Jeff for review on April 13, 2026
- Rollout document approved for publication; publish and close out the spike next
Current Framing
- Approved title:
Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation. - This work is currently framed in the workspace as a dual UIKit/SwiftUI plan that removes
UIHostingControllerdynamically while preserving both flows appropriately. - The remaining deliverable is process-oriented, not just technical implementation.
Current Scope
- Define a consumer-facing rollout plan for the broader UIKit-removal work.
- Preserve both UIKit and SwiftUI paths appropriately while introducing the new path safely.
- Cover risky entry points such as
FTTransfer, while keeping the latest spike finding explicit that consumer-side changes there may no longer be strictly required after the SwiftUI dismissal behavior is applied correctly. - Include validation expectations in
XQ1. - Use a global feature-flag rollout model rather than entry-point-based enablement.
- Include consumer communication expectations.
- Include a 30-day production period with no reported bugs before final removal.
- Include a follow-up release to remove the feature flag and old code after rollout confidence is achieved.
Notes
- The feature-flag and rollout planning guidance applies to the broader UIKit-removal spike, not only to dismissal-sequencing work.
- Jeff suggested sending the process-oriented rollout document to Quy for feedback when ready.
- The draft shared with Jeff already reflects the global feature flag, broad
XQ1validation, and consumer-facing rollout flow guidance. - Additional review feedback from April 13: rename the proposed flag to
xflow-swiftui-enabled, make consumer contact andXQ1validation explicit in the first phase, remove overly technical rollout wording, and avoid implying there are no consumer-side changes without qualification. - On April 14, Jeff asked whether the FTTransfer part of the rollout document also needed updating; David confirmed the document had already been revised to clarify that root-cause section.
- April 15 clarification: do not reuse the existing SwiftUI LaunchDarkly flag for this rollout.
- The new flag name for this work should be
xflow-swiftui-container-enabled. - The document should note that the flag is
to be added in the future as part of implementation. - Late April 14 guidance: the document was approved late in the day; the next step is to publish it, then close out the spike by commenting
Spike Results:with the relevant document links and the new follow-up story link. - The new follow-up story should also be marked as a blocker for the reopened UIKit-removal story.
Related Work
- Related consumer rollout thinking should stay aligned with
PDIAP-15836. PDIAP-15838should not be framed as part of this UIKit-removal spike.