Nimbus Core

---

Overview

Nimbus' Core defines the foundation upon which all other Nimbus features are built.

Within the core you will find common elements used to build iOS applications including in-memory caches, path manipulation, and SDK availability. These features form the foundation upon which all other Nimbus libraries are built.

How Features are Added to the Core

As a general rule of thumb, if something is used between multiple independent libraries or applications with little variation, it likely qualifies to be added to the Core.

Exceptions

Standalone user interface components are rarely acceptable features to add to the Core. For example: photo viewers, pull to refresh, launchers, attributed labels.

Nimbus is not UIKit: we don't have the privilege of being an assumed cost on every iOS device. Developers must carefully weigh whether it is worth adding a Nimbus feature - along with its dependencies - over building the feature themselves or using another library. This means that an incredible amount of care must be placed into deciding what gets added to the Core.

How Features are Removed from the Core

It is inevitable that certain aspects of the Core will grow and develop over time. If a feature gets to the point where the value of being a separate library is greater than the overhead of managing such a library, then the feature should be considered for removal from the Core.

Great care must be taken to ensure that Nimbus doesn't become a framework composed of hundreds of miniscule libraries.

Classes
class	NINavigationAppearance
	Class for saving and restoring the navigation appearance state. More...
Modules
	Common Metrics
	Data Structures
	Debugging Tools
	Device Orientation
	Errors
	Foundation Methods
	In-Memory Caches
	Network Activity
	Non-Empty Collection Testing
	Non-Retaining Collections
	Operations
	Paths
	Preprocessor Macros
	Runtime Class Modifications
	SDK Availability
	State
	View Recyling