Skip to content

[NT-3071] Create UIKit reference implementation and target with existing tests#251

Draft
Alex Freas (akfreas) wants to merge 8 commits intomainfrom
NT-3071-create-uikit-reference-implementation
Draft

[NT-3071] Create UIKit reference implementation and target with existing tests#251
Alex Freas (akfreas) wants to merge 8 commits intomainfrom
NT-3071-create-uikit-reference-implementation

Conversation

@akfreas
Copy link
Copy Markdown
Collaborator

Adds a UIKit reference implementation that shows how to implement optimization using UIKit. Functionally exactly the same as the SwiftUI one, which also means that we can target the UIKit binary when running the exact same tests that are run on the SwiftUI version.

  • Add xcodegen for generating project so it's clear how deps are connected
  • Move both targets into shared xcodeproj
  • Update documentation

Still pending in another PR: update docs for integrating SDK into SwiftUI/UIKit

…opt xcodegen project.yml so the project regenerates deterministically and a UIKit shell can sit alongside SwiftUI.
…iew and ViewTrackingController, mirroring the SwiftUI MainScreen entry list, identify/reset, and analytics display.
…and shared ScreenLog so the same back-swipe revisit assertions pass against the UIKit shell.
…EntryUIView sections that rebuild when the global toggle or simulated preview panel flips.
… can install each app on the simulator (CFBundleIdentifier was missing under GENERATE_INFOPLIST_FILE=NO).
…en project restructure, home/navigation/live-updates screens wired through OptimizedEntryUIView and ViewTrackingController, Info.plist CFBundle keys for the test runner) with parity fixes for live-update behavior, retain cycles, deinit cleanup, and tracking-controller finalization.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant