Preparing an iOS or visionOS project brief

Identify the primary audience and the situation in which they will use the app. Explain the problem, the current alternative, and the change you want the product to make. A single primary workflow gives the first release a clear focus.

• Who will use it: customers, employees, or another defined group?
• What should they be able to complete, and how will you know the app helped?
• Where will they use it, and what time, connectivity, or accessibility constraints matter?

List the devices you want to support and why they suit the experience. An iPhone workflow, an iPad workspace, and an immersive experience on Apple Vision Pro can have different requirements. Describe what should be shared and what should be specific to each.

• For iOS, note device coverage, offline needs, notifications, and any hardware features.
• For visionOS, describe the setting, level of immersion, interactions, and expected session length.
• For immersive work, include comfort, readable content, accessibility, and a clear way to pause or leave the experience.

List the essential user journeys from start to finish. Include empty states, errors, and recovery rather than only the ideal path. Separate launch requirements from optional features so tradeoffs are visible.

• Describe what users can create, view, change, and share.
• State whether accounts, subscriptions, purchases, or roles are needed.
• Keep a short out-of-scope list and explain any fixed launch deadline.

Name existing services the app must connect to and who controls them. Identify what is ready, what needs to be created, and who will provide it. Missing content or access can affect the sequence of work as much as missing code.

• List APIs, authentication, business systems, and data that must sync.
• Identify branding, copy, images, audio, and their usage rights.
• For immersive experiences, list 3D environments, models, animation, and sound; say whether editable source assets exist.
• Explain privacy requirements and any restrictions on collecting, storing, or sharing data.

Describe observable results that will demonstrate the first release is ready. For example: “A user can finish the agreed workflow, recover from a lost connection, and find their saved work when they return.” This is an illustrative criterion; each project needs its own.

• Identify who reviews the work and which devices and real-world conditions must be tested.
• Include testing on Apple Vision Pro for immersive experiences.
• Agree on source-code and asset handoff, account ownership, publishing responsibilities, and post-launch support.
• Share a budget range, timing constraints, and decisions that still need discovery.