0 views collected around this technical thread.
Cocoapods‑sled is a lightweight CocoaPods plugin that caches Xcode build artifacts and automatically converts reusable pods to binary form, offering low‑cost integration, local caching, binary handling, and full pod reuse to accelerate iOS development workflows.
The article demonstrates how detailed Mach‑O and LinkMap analysis combined with custom CocoaPods hooks, Swift‑syntax refactoring, and indexed symbol mapping can systematically shrink an iOS app’s bundle—from 289.3 MB to 259.3 MB—while cutting CI build time and simplifying debugging.
This technical guide details how to set up iOS dependencies, publish KMM libraries, build a GitLab CI/CD pipeline, and resolve common integration problems for Kotlin Multiplatform Mobile projects, providing code examples and best‑practice recommendations for mobile developers.
This article introduces iOS componentization using CocoaPods, detailing the drawbacks of manual code copying, explaining the creation of local podspec libraries, configuring source files, resources, access levels, and integration steps, while also covering sub‑specs, resource bundles, and practical code examples for Swift projects.
This article describes ByteDance's cloud‑based CocoaPods dependency analysis service, explaining its background, architecture, caching mechanisms, material pruning, and decision‑making strategies that together reduce iOS build dependency resolution time by over 60% while maintaining correctness and low integration cost.
This article details Beike's comprehensive Flutter integration approach for existing iOS and Android projects, covering official module templates, the challenges of the native integration process, and the company's source‑code and binary‑mode solutions that streamline podspec configuration, plugin handling, SDK automation, flavor support, and build efficiency.
The article introduces ARK, a dynamic development mode for iOS that replaces traditional CocoaPods‑Xcode workflows with a lightweight 2 MB repository and real‑time library conversion, dramatically cutting pod install and compile times, improving build success, and enabling fast, component‑focused development using ByteDance’s MBox tool.
The article introduces ARK, a dynamic iOS development mode that replaces traditional CocoaPods‑Xcode workflows with a lightweight repository and on‑demand component fetching, dramatically cutting pod install, compile, and index times while preserving full development capabilities.
This article describes a complete workflow for iOS UI development that centralizes color definitions in a JSON palette, synchronizes them via a CocoaPods post‑integrate hook, and automatically generates Objective‑C/Swift color constants and Xcode code snippets using Ruby and ERB templates, dramatically improving efficiency and reducing manual errors.
This article shares the Kuaishou overseas client team's practical experiences and solutions for improving compilation efficiency through Swift/Objective‑C binary mixed compilation, covering single‑target and multi‑target strategies, moduleization challenges, binary compatibility, and future directions for mobile development.
This article explains how Swift and Objective‑C can be mixed in iOS projects, covering prerequisite settings, CocoaPods module configuration, name mangling, compilation differences, dynamic features, method replacement techniques, and the underlying Swift runtime metadata that enable seamless inter‑language calls.
This article explains how A‑Station adopted Swift for iOS, details the prerequisites and CocoaPods configuration for mixed Swift‑Objective‑C projects, explores module usage, name mangling, dynamic features, method replacement techniques, and provides practical code examples and tooling references.
This article describes how the iOS team reduced build times by binaryizing nearly 100 CocoaPods components, detailing macro handling, packaging with cocoapods‑packager, storage strategies, dependency switching mechanisms, and CI integration to streamline development and deployment.
This article details JD's transition to Swift mixed compilation, covering ABI stability, module stability, library evolution, the required Xcode configurations, bridging techniques for Swift‑ObjC interaction, component‑level mixing approaches, and solutions to static and dynamic linking issues across iOS versions.
To address the growing build times of the Fire Shopkeeper iOS client caused by nearly 100 components, the team implemented component binaryization using custom CocoaPods plugins, static‑framework packaging, binary storage, and CI integration, dramatically cutting compile duration from forty minutes to around twelve minutes.
This article explains how CocoaPods Core manages Spec repositories, including the structure and initialization of Source, Metadata handling, shard-based indexing, version resolution, CDN migration, and the mechanisms for updating and searching PodSpecs across Git and CDN sources.
This article provides a comprehensive overview of CocoaPods' Podspec file, explaining its purpose, supported formats, core data structures, attribute handling, subspec hierarchy, dependency validation, and practical steps for creating, linting, and publishing pods, with detailed Ruby code examples and best‑practice recommendations for iOS/macOS projects.
The team accelerated the QMusic live‑streaming SDK by converting large source modules and external pods into pre‑compiled binaries, tuning Xcode build settings, and automating CI caching, slashing full‑build times from roughly 400 seconds to 40 seconds and packaging duration from over 50 minutes to three minutes.
The article describes how 58.com evolved from a single‑team iOS app to a multi‑team, multi‑app architecture, introduces the App Factory concept with entry projects and pod pools, defines dependency rules, and presents tooling for dependency analysis, pollution detection, and incremental compilation to enable vertical business migration and rapid innovation.
This article outlines the preparation, framework redesign, and common challenges of integrating Swift into an existing Objective‑C iOS client, covering ABI stability, mixed compilation, module configuration, code standards, and future migration plans.