How do I set up dependency management in iOS with CocoaPods?

The guide recommends using CocoaPods for easy integration: install via 'sudo gem install cocoapods', run 'pod init' to create a Podfile, add dependencies, and use 'pod install' to generate a workspace. It advises committing pods to version control for consistency.

What's the best architecture pattern for iOS apps to avoid massive view controllers?

It suggests MVVM or VIPER; MVVM moves state to ViewModels to slim down controllers, while VIPER offers more structure for large apps. The guide compares these with MVCS, noting MVVM's popularity for testability and separation of concerns.

How can I secure sensitive data like passwords in an iOS app?

Use the iOS Keychain with wrappers like SSKeychain, avoid NSUserDefaults, and set protection levels (e.g., accessible after first unlock). The guide emphasizes clearing data when not needed and using TLS with certificate pinning for networking.

iOS Good Practices vs. Apple's official documentation: which should I use?

iOS Good Practices complements Apple's docs by providing curated, practical advice from community experience, focusing on real-world pitfalls and workflows. Apple's documentation is authoritative for API details but can be less approachable for best practices.

How to debug memory leaks in Xcode effectively?

Use Instruments' Allocations instrument: profile your app, filter by class names, and monitor the Persistent column for increasing instance counts. The guide also recommends setting exception breakpoints to catch crashes early.

What are the key differences between Carthage and CocoaPods for iOS?

Carthage builds dependencies into binary frameworks for faster builds and less magic, while CocoaPods integrates them directly into your project. The guide notes Carthage is simpler but requires manual setup, whereas CocoaPods is easier for Swift projects with Alamofire.

How to localize an iOS app for multiple languages properly?

Store strings in localization files from the start, use .stringsdict for plurals, and set launch arguments like '-AppleLanguages (Finnish)' for testing. The guide advises keeping all user-facing text centralized to simplify translations and updates.

Open-Awesome

Futurice iOS Good Practices

NOASSERTION

A comprehensive collection of iOS development best practices, covering architecture, tools, security, and deployment.

Visit Website GitHub

11.0k stars1.2k forks0 contributors

What is Futurice iOS Good Practices?

iOS Good Practices is a community-maintained guide that curates recommendations and best practices for building iOS applications. It covers everything from initial project setup and architecture choices to security, diagnostics, and App Store deployment, helping developers write more maintainable and robust apps.

Target Audience

iOS developers at all levels, from beginners learning the platform to experienced engineers looking to refine their workflows and adopt industry-standard patterns.

Value Proposition

It consolidates scattered knowledge into a single, actionable resource, saving developers time and reducing errors by providing clear, practical advice vetted by the community and Futurice's developers.

Overview

Good ideas for iOS development, by Futurice developers.

Use Cases

Best For

Learning iOS development best practices from scratch
Structuring iOS projects with clear architecture patterns
Implementing secure data storage and networking in iOS apps
Setting up efficient build configurations and deployment pipelines
Improving code quality with diagnostics and profiling tools
Managing dependencies and project organization in Xcode

Not Ideal For

Developers seeking ready-to-use code libraries or project templates, as it provides guidance rather than executable components
Teams needing interactive, real-time tutorials or video-based learning resources
Projects focused exclusively on cutting-edge iOS features not yet widely adopted or covered in community docs
Organizations requiring formal, vendor-supported documentation with guaranteed updates and SLAs

Pros & Cons

Pros

Comprehensive Practical Coverage

Spans the entire iOS development lifecycle from project setup with Xcode and dependency management to deployment and security, offering actionable advice drawn from real-world experience.

Battle-Tested Recommendations

Provides proven guidance on tools like Instruments for profiling, Keychain for secure storage, and architecture patterns like MVVM to avoid massive view controllers, based on Futurice's expertise.

Community-Driven and Living

Actively maintained through open issues and pull requests, ensuring it evolves with iOS updates and community feedback, as highlighted in the README's call for contributions.

Clear Structural Guidance

Offers specific advice on code organization using MARK comments, localization with .stringsdict, and build configurations with .xcconfig files, reducing common pitfalls.

Cons

Sparse Code Examples

Lacks extensive sample code or full project implementations; for instance, architecture sections describe MVCS or VIPER but don't provide complete, runnable templates, requiring extra effort from developers.

Potential for Staleness

As a community-maintained document, it risks outdated information if not regularly updated, and the README admits gaps like missing testing sections, which could hinder comprehensiveness.

Opinionated Without Alternatives

Some recommendations, such as favoring code over Storyboards for maintainability, are presented with bias and may not suit teams preferring visual tools or different workflows, limiting flexibility.

Frequently Asked Questions

Related Projects

Swift Style Guide by @raywenderlich

The official Swift style guide for Kodeco.

Stars13,164

Forks2,102

Last commit1 year ago

NY Times - Objective C Style Guide

The Objective-C Style Guide used by The New York Times

Stars5,821

Forks1,236

Last commit3 years ago

GitHub - Style guide & coding conventions for Swift projects

**Archived** Style guide & coding conventions for Swift projects

Stars4,758

Forks560

Last commit8 years ago

raywenderlich Style Guide

A style guide that outlines the coding conventions for Kodeco

Stars3,086

Forks615