engineer-legacy-sdks

Assess legacy Braze Objective-C SDK integrations and guide migration to Swift SDKs.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-legacy-sdks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-legacy-sdks
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-legacy-sdks
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-legacy-sdks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides actionable guidance to assess, maintain, and migrate deprecated Braze Objective-C SDK integrations (iOS, tvOS, Mac Catalyst) to current Swift SDKs or to safely sustain legacy deployments when migration is not immediately possible.

Core Features & Use Cases

  • Migration Assessment Checklist: Evaluate deployment targets, installation methods, BrazeManager boundaries, Objective-C/Swift interop, and feature parity to recommend a migration path.
  • Installation & Integration Guidance: Compare SPM, CocoaPods, Carthage, and manual XCFramework approaches and outline initialization, Info.plist, and appboyOptions configuration.
  • Platform Constraints & Customizations: Document tvOS and Mac Catalyst limitations, log level and IDFA/IDFV handling, and runtime startup requirements.
  • Use Case: When a codebase contains a BrazeManager wrapper and CocoaPods-based Appboy integration, produce a prioritized plan to migrate to SPM and minimize runtime risk.

Quick Start

Assess the repository for Objective-C Braze usage, list installed integration methods, and produce a prioritized migration checklist highlighting BrazeManager seams and required platform changes.

Frequently Asked Questions about engineer-legacy-sdks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an Appboy Objective-C SDK to the Braze Swift SDK?

Migrating an Appboy Objective-C SDK to the Braze Swift SDK requires evaluating your BrazeManager boundaries, installation methods, and feature parity. This Skill generates a prioritized migration checklist to navigate SPM or CocoaPods transitions and minimize runtime risk.

What is the best way to maintain a legacy Braze iOS SDK when migration is not possible?

Maintaining a legacy Braze iOS SDK involves documenting platform constraints, verifying Info.plist and appboyOptions configurations, and checking initialization sequencing. This Skill provides actionable guidance to safely sustain deprecated Objective-C deployments without immediate migration.

Can I use Swift Package Manager to install the Braze SDK for tvOS and Mac Catalyst?

Swift Package Manager supports Braze SDK installations across iOS, tvOS, and Mac Catalyst. This Skill compares SPM against CocoaPods, Carthage, and manual XCFramework approaches to recommend the best installation method for platform-specific constraints.

What are the initialization requirements for Braze legacy SDKs on the main thread?

Braze legacy SDK initialization requires proper sequencing on the main thread alongside correct Info.plist and appboyOptions configuration. This Skill outlines startup requirements and compatibility constraints including minimum Xcode and OS versions for stable runtime integration.

Does the Braze Swift SDK support feature parity with the deprecated Appboy tvOS SDK?

Feature parity between the Appboy tvOS SDK and the Braze Swift SDK requires checking platform limitations and customizations like IDFA/IDFV handling. This Skill assesses feature compatibility to recommend a safe migration path for tvOS deployments.

Why does my Braze SDK migration plan need a BrazeManager boundary identification?

BrazeManager boundary identification isolates Objective-C and Swift interop seams to minimize runtime risk during migration. This Skill highlights these wrappers within CocoaPods-based Appboy integrations to produce a structured, prioritized transition plan.