May 2017 Summaries

Working exclusively on mobile apps for years has given me a unique perspective on the challenges of developing an SDK, unlike working on apps that ship to the App Store. One of the biggest differences is dealing with crashes and debugging weird bugs in the codebase used by other apps, where visibility into their code is limited. Developing an SDK also means having stricter constraints, such as minimal dependencies and a focus on lightweight frameworks from Apple, which can be stressful but ultimately makes for a fun challenge when shipping code that runs on millions of devices daily.

Transitioning from developing mobile apps to creating an SDK, the author discusses the unique challenges faced in this new role, particularly in their position as Product Owner and iOS team lead at Luciq, which focuses on bug reporting and in-app feedback. Unlike app development, SDK development involves heightened pressure to avoid crashes, as any failure in the SDK could ironically cause the app it's integrated into to crash. Debugging is more complex due to the inability to see the host app's code, and there are stricter constraints, such as minimizing dependencies to keep the SDK lightweight. Integration simplicity is prioritized to facilitate ease of use for developers, and maintaining support for older iOS versions becomes crucial due to the diverse needs of the apps using the SDK. Additionally, the SDK's UI must be customizable to blend seamlessly with various app designs, presenting a creative challenge. Despite these constraints, the author finds the process rewarding, noting the satisfaction of their work running on millions of devices.