A living collection of guidelines and best practices for developing excellent iOS applications.
iOS Handbook is a collection of guidelines and best practices for developing high-quality iOS applications. It provides teams with standardized approaches to coding style, communication, Git workflows, and reusable components to maintain consistency across projects. The document serves as a living reference that evolves with the iOS development ecosystem.
iOS development teams and individual developers working on Apple platform applications who want to establish consistent practices and improve code quality.
It offers a comprehensive, practical set of guidelines curated from real-world experience, with the flexibility to adapt when strict adherence would produce worse results, making it more useful than rigid style guides.
Guidelines and best practices for excellent iOS apps
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The handbook is a 'living document' that explicitly allows developers to ignore guidelines if adherence produces worse results, encouraging adaptation and practical application over rigid rules.
It covers multiple key areas including Swift style, best practices, communication, Git workflows, and reusable components, as listed in the index, providing a holistic reference for iOS teams.
Guidelines prioritize consistency across teams with sections on communication and Git strategies, aiming to improve collaboration and project quality in group settings.
Maintained by multiple contributors and linked to other B&B iOS repos, it invites updates and contributions, ensuring it evolves with real-world usage and feedback.
As a documentation-only guide, it lacks integrated linting rules or automated checks, requiring manual effort to enforce standards, which can be error-prone in larger teams.
Tailored to the maintainers' experiences at Bakkenbaeck, some guidelines may not universally apply to all iOS projects, such as those with legacy codebases or different architectural preferences.
Being a living document means it needs regular updates to stay current with Swift and iOS changes, which could burden teams adopting it without dedicated resources for upkeep.