Mobile App Design & Development

App marketing is structurally harder than web marketing. App Tracking Transparency, ATT-driven signal loss, store-platform attribution restrictions and SKAdNetwork constraints all degrade the data marketing teams rely on to optimise. Apps that are built without explicitly accommodating these constraints are usually expensive to market once they ship — the right answer is to design the analytics, attribution and lifecycle infrastructure into the build, not to bolt it on after launch.

What we build

The standard programme covers:

• iOS native apps (Swift, SwiftUI) where platform-specific UX, performance or capabilities warrant
• Android native apps (Kotlin, Jetpack Compose) under the same principle
• React Native cross-platform apps where shared codebase economics outweigh platform-native polish (most consumer-facing apps with broad feature parity)
• Backend infrastructure: API, authentication, real-time sync, data layer integrated with the wider marketing stack
• Marketing infrastructure: SKAdNetwork integration, App Store Connect optimisation, deep linking architecture (Branch, Adjust, Singular), attribution APIs
• Lifecycle infrastructure: push notification engine (OneSignal, Braze, Iterable), in-app messaging, lifecycle stage tracking
• Analytics: app analytics SDK + server-side event pipeline, integration with the rest of the marketing measurement stack

Why ATT changed everything

Apple's App Tracking Transparency framework, rolled out in iOS 14.5 in 2021, requires apps to ask explicit permission before tracking users across other apps and websites. Opt-in rates settled around 20-30% for most consumer categories. The implication: 70-80% of iOS users became invisible to third-party attribution and most cross-app audience targeting.

The marketing impact was material. Apple's own documentation is the primary source on what ATT does and doesn't allow. Industry response has consolidated around three patterns:

1. SKAdNetwork integration: Apple's own privacy-preserving attribution API. Required for any app running paid acquisition on iOS. Not optional from a marketing perspective even though it's technically optional from an Apple perspective.
2. Server-to-server attribution APIs: post-install events sent server-side to ad platforms (Meta CAPI, Google Ads SKAdNetwork integration, TikTok Events API). Recovers some of what ATT removed.
3. First-party data emphasis: building audiences from in-app behaviour, email signups, account data — durable to ATT changes because it doesn't depend on cross-app tracking.

Apps built BEFORE these patterns were standard usually need significant rebuilding to support them properly. Apps built AFTER them work cleanly with the modern attribution stack.

How a build runs

The marketing infrastructure layer

The thing that distinguishes a marketable app from a generic one is the marketing infrastructure built into the architecture. Specifically:

• Attribution: SKAdNetwork integration on iOS, Google Play Install Referrer on Android, deep linking via Branch/Adjust/Singular/AppsFlyer for cross-platform consistency. The basic question "which marketing channel acquired this user" should have a defensible answer.
• Event tracking: client-side SDK + server-side pipeline. Events tagged with consistent naming, conversion events flagged for ad-platform integration, all events flow into a central data layer (Segment, Snowflake, BigQuery, mParticle).
• Push notification engine: OneSignal / Braze / Iterable / native APNs+FCM integration. Lifecycle-aware so messages can be triggered by stage changes, not just broadcast.
• In-app messaging: contextual prompts at the right moment in the user journey — onboarding, activation milestones, churn-risk intervention.
• Authentication + identity: durable user identity that links anonymous app behaviour to authenticated user behaviour to CRM record. The infrastructure that makes lifecycle marketing possible.
• ASO infrastructure: keyword tracking, conversion-rate testing on listing screenshots and metadata, integration with paid app campaigns.

Most agencies that build apps treat these as post-launch upgrades. We treat them as foundational — the architecture cost is similar either way; doing them post-launch typically costs 2-4x more in rework than doing them at build time.

Native vs React Native

Default: React Native for most consumer apps. Native when there's a specific reason — gaming, AR, complex media processing, deep platform integration that React Native libraries don't cover well, or brand-experience apps where platform-native feel is critical to perceived quality.

What it costs

App builds are scoped engagements with significant range based on complexity, platform coverage and integration depth. Indicative ranges:

• Lean React Native MVP (consumer app, 6-10 core screens, basic backend): £80-150k
• Standard React Native app (consumer or B2B, 15-30 screens, custom backend, marketing infrastructure): £150-400k
• Native iOS + Android (cross-platform native, complex backend, advanced features): £300-700k+
• Complex apps with significant proprietary infrastructure (real-time sync, AI features, payments): £500k-£2M+

Ongoing development typically £6,000-£25,000/month per active platform.

Where this service wins

• Consumer-facing apps where marketing-driven acquisition matters — the marketing infrastructure built into the architecture pays back in lower per-user marketing inefficiency
• Apps replacing legacy versions built before ATT — usually the rebuild can pay for itself just in attribution recovery
• B2B mobile apps that need to integrate with the broader marketing and CRM stack — the same architectural principles apply, just with different lifecycle patterns
• Subscription apps (consumer subscription, fitness, health, productivity) where retention infrastructure is the dominant value-driver

Where it doesn't fit

• Apps that are essentially mobile-friendly websites — a responsive web app or PWA is usually the right answer at lower cost and faster time-to-market
• Internal tools that don't need ASO, attribution or marketing infrastructure — generic app development is fine and cheaper
• Concept-validation MVPs where the question being tested is product-market fit rather than marketing-channel viability — the marketing infrastructure is premature optimisation

Read deeper on this

• Conversion tracking foundations for AI-led marketing — the cross-platform attribution principles that apply to both web and app.
• Why your CAC is climbing — and what to do about it — including ATT as a structural force on iOS app CAC.
• Email & Lifecycle Marketing — the lifecycle work that pairs with mobile push and in-app messaging for retention.

Sources and further reading

• Apple — App Tracking Transparency — Apple's developer documentation on the ATT framework.
• Apple — SKAdNetwork — Apple's documentation on the privacy-preserving attribution API.
• Google — Play Install Referrer — Google's documentation on Android install attribution.