How netcoresolutions/smartech-ios-sdk works
Core Components
• • SDK Framework (Smartech.xcframework): Represent this as the central library that iOS apps use for integration. Note that the framework includes headers for various protocols (e.g., HanselProtocol, SMTAppInboxProtocol, SMTBackendAPIRequest) that expose its key functionalities.
• • iOS App (Client): Mark an external “iOS Application” component that integrates the SDK.
• • Backend/External Services: Although not contained in the repository, the README and usage context indicate that the SDK communicates with Smartech’s backend services (e.g., for push notifications and in-app messages).
• • Podspec: Represent the podspec file as the distribution configuration, which is used by CocoaPods to manage integration in iOS projects.
Interactions and Data Flow
• Interactions from the SDK framework outward to the “Smartech Backend Services” (even if abstract) to show that tracked events, push notification tokens, or in-app message interactions are transmitted over the network.
Architectural Patterns and Key Design Principles
• Modularity provided by the framework. The SDK’s adoption of .xcframework makes it platform-agnostic (supporting multiple architectures like ios-arm64, maccatalyst, and simulator).
• Protocol-based design (as seen from the headers such as SmartechProtocol, SMTServiceOperation) — a design choice that allows developers to easily extend or customize behavior.
• Point out the clear separation of concerns: The SDK encapsulates communication with the backend, event handling, and notification management from the client app.
Following Elements
• The “iOS Application” that integrates the SDK.
• The “Smartech SDK Framework,” with internal modules (e.g., PushNotificationAdapter, AppInbox, Backend API, etc.).
• “Smartech Backend Services” as an external dependency that receives data or commands.
• API calls from the iOS app to the SDK.
• Data/command flow from the SDK to the backend.
• Any callback/response paths or event propagation.
Additional Recommendations
• Overlap architectural layers where appropriate — for instance, group all messaging and notification-related functionalities within one segment of the SDK.