How an iOS application is organised.
WHAT AN APPLICATION CONSISTS OF
An entry point and application delegate Scenes, representing instances of the interface View controllers or declarative views
Resources: assets, storyboards, localised strings
A property list declaring configuration
WHAT THE PROPERTY LIST DECLARES
Permissions and their usage descriptions Supported orientations Capabilities required Application identity and version
WHY THE USAGE DESCRIPTIONS MATTER
Requesting a permission without one causes a crash, and review rejects vague descriptions.
WHAT A BUNDLE IDENTIFIER IS
A unique identifier for the application, used throughout the developer ecosystem.
WHAT ASSET CATALOGUES PROVIDE
Images at several resolutions, app icons, and colour definitions.
WHAT TO PROVIDE IN THEM
Every icon size required, and colours with light and dark variants.
WHAT TARGETS ARE
Build products: the application, extensions, tests, widgets.
WHAT CAPABILITIES ARE
Platform features requiring explicit enabling: notifications, sign-in, background modes, payments.
WHAT TO KNOW
They must be enabled in the project and in the developer portal, consistently.
WHAT THAT CAUSES WHEN MISMATCHED
Builds that fail to sign or features that silently do not work.
