A template for creating new Swift frameworks with pre-configured CI/CD, dependency managers, and project structure.
SwiftFrameworkTemplate is a project template designed to kickstart the development of Swift frameworks for Apple platforms. It solves the problem of repetitive setup by providing a pre-configured project with CI/CD pipelines, dependency manager integrations, and essential development tools. Developers can immediately focus on writing framework code instead of configuring build systems.
Swift developers and teams building reusable frameworks or libraries for iOS, macOS, tvOS, or watchOS. It's particularly useful for open-source maintainers and organizations establishing standardized Swift project structures.
Developers choose this template because it eliminates hours of boilerplate setup with battle-tested configurations for dependency management, testing, and continuous integration. It ensures new Swift frameworks follow modern best practices and are production-ready from day one.
A template for new Swift iOS / macOS / tvOS / watchOS Framework project ready with travis-ci, cocoapods, Carthage, SwiftPM and a Readme file
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Pre-configured deployment targets for iOS, macOS, tvOS, and watchOS ensure frameworks are ready for all Apple platforms from the start, as stated in the README.
Supports CocoaPods, Carthage, and Swift Package Manager simultaneously, saving time on configuring each manager individually for distribution.
Comes with Travis CI configuration for automated testing and deployment, making it easy to set up continuous integration without manual scripting.
Includes SwiftFormat for code formatting and Jazzy for documentation, promoting consistent code style and maintainability out of the box.
Based on Xcode 10 and Swift 4.2, which are several versions behind current standards, requiring manual updates for modern Swift projects.
Requires installing Carthage and Cookiecutter as prerequisites, adding extra steps that might deter developers looking for a quick start.
The CI configuration is tailored to Travis CI, not easily portable to other services like GitHub Actions without significant modification.