41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# PDIAP-14859
|
|
|
|
## Status
|
|
|
|
- Active
|
|
- Current focus on April 10, 2026
|
|
|
|
---
|
|
|
|
## Current Framing
|
|
|
|
- This work is currently framed in the workspace as a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically 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`.
|
|
- Include validation expectations in `XQ1`.
|
|
- 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 workspace does not currently hold an approved final title for this ticket beyond the Jira ID.
|
|
- 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.
|
|
|
|
---
|
|
|
|
## Related Work
|
|
|
|
- Related consumer rollout thinking should stay aligned with `PDIAP-15836`.
|
|
- `PDIAP-15838` should not be framed as part of this UIKit-removal spike.
|