← Research & specs
AdPilot · Corpus

Research: Product, UX & Tech Patterns for an AI-Agent Ad-Management Mobile App

Research: Product, UX & Tech Patterns for an AI-Agent Ad-Management Mobile App

Prepared: September 2026 · Product-strategy research for a cross-platform (iOS + Android) AI-agent ad-manager for SMB owners and indie developers.

Method note: ~10 targeted web searches plus official-doc fetches (Expo, Vercel AI SDK, Meta Business Help, Apple/Google developer docs). Where a claim comes from general industry knowledge rather than a verified 2025–2026 source, it is marked [directional]. Vendor blogs are marked [secondary].


1) Executive Summary


2) Agent-UX Patterns That Build Trust

2.1 What works across Fin / Cursor / Motion / Notion AI [directional, cross-referenced with agentic-patterns literature]

Pattern Example Why it builds trust
Tiered autonomy (risk-gated actions) Fin grants "system access" incrementally, driven by agent analytics; Cursor runs safe edits inline but asks before destructive/global operations Users calibrate: the agent earns autonomy with evidence
Human-in-the-loop approval gates The standard pattern (Cloudflare Agents docs, agentic-patterns.com): human reviews the proposed action with all inputs; executes only after approval Approval targets high-risk/irreversible actions only; low-risk stays autonomous
"Review context packet" CreateOS: approvals need proposed action + inputs + expected outcome + rollback path, not a yes/no prompt Informed approval; reduces rubber-stamping
Plan-first / prepare-not-submit MindStudio "gate pattern": agent surfaces a complete proposal (dashboard/card), human pulls the trigger Matches Motion/Cursor: always show the diff before it lands
Explanation attached to every autonomous action Fin explains why it took an action; Notion AI shows what it changed "Why did the AI do this?" is the single most-requested trust feature in ad-tech
Recoverability as default Cursor checkpoints/undo; EAS Update republish analogy Users experiment when mistakes are cheap

2.2 Applied to ad management — autonomy ladder (recommendation)

Tier Actions Autonomy
0 — Read Pull metrics, suggest insights Automatic
1 — Create Draft ads, audiences, budgets (never submitted) Automatic, always previewed as a card
2 — Spend-touching Launch campaign, pause, raise/lower budget within pre-set caps One-tap approval with context packet
3 — Irreversible Change payment method, raise daily cap, spend above caps, delete assets Explicit confirmation + re-auth; never batch

Key design rules from the research:

  1. Consequential = anything that moves money or is hard to reverse. Everything else should be autonomous — too many gates destroys the "agent" value prop.
  2. Approval cards, not modals. Show: what will change, why (reasoning), cost impact ("+ $15/day, ~$450/mo"), expected effect, and one-tap Undo availability.
  3. Every AI action writes an audit entry the user can inspect ("AI Actions" feed) — see §4.
  4. Escalate ambiguity. If the agent is unsure (conflicting goals, ambiguous audience), it asks; silent guessing is the fastest trust killer.

3) Onboarding Blueprint for Our App

3.1 Evidence base

3.2 Proposed flow (target: campaign draft ready in < 5 min)

Step Screen Time Notes
0 Value screen: "Your ads, run by an agent" + 1 sample before/after ~20 s No signup wall yet [directional]
1 Connect ad account (Meta/Google/TikTok OAuth) — or "explore demo business" ~60 s OAuth-first; account connect is the real commitment
2 Progressive profiling, 4 questions: business type → goal (leads/sales/awareness) → monthly budget slider (sets spend cap!) → tone/brand voice (or paste website URL) ~90 s Budget answer is the initial spend cap (trust-by-design)
3 Template gallery: pick a campaign recipe ("Local services", "E-commerce promo", "App installs") with real sample creative ~60 s Agent personalizes template to answers
4 First agent moment: agent presents a complete campaign draft as an approval card (creative, audience, budget, reasoning) ~60 s "Do it for me" default; "Help me do it" toggles edit mode per field
5 Approve → agent launches (or schedules) → success screen with what happens next + how to undo/stop — Activation event = first approved launch

3.3 Principles


4) Trust & Safety Feature Checklist

Evidence: HITL approval-gate literature, Fin's incremental system access, ad-tech practice on why lack of control/black-box decisioning/fear of wasted budget are the cited adoption blockers [directional where unverified].

Must-have at launch (v1):

Fast-follow (v1.x):


5) Compliance Risk Register

# Risk Evidence / status Severity Mitigation
1 AI-content disclosure rules diverge by platform; labels now effectively mandatory No single rule: Google requires "AI Generated" labels on synthetic content broadly; TikTok made labels mandatory on all AI-generated ad content (July 21, 2026 update); Meta auto-labels commercial AI ads and mandates disclosure for political/social ads. Enforcement = rejection/demotion [secondary: Novoads, AuditSocials, Virvid] High App auto-detects AI-generated creative and applies each platform's label at submission; block launch when a required label is missing; track policy changes quarterly
2 New ad accounts are spend-throttled and ban-prone when scaled fast Meta sets daily spend limits per account, raised at Meta's discretion based on payment history/compliance; new accounts commonly start ~$25–$50/day [secondary: Meta Business Help; r/FacebookAds]; restrictions appealed via Account Quality portal High The product's ramp plan matches Meta's ramp: start low, increase caps gradually, warm up accounts (page age, payment history), never spike budgets; pre-launch policy checks; escalation playbook for restricted accounts
3 Special ad categories (housing, employment, credit, social issues/elections) carry restricted targeting + certification on Google; Meta has parallel Special Ad Category rules Long-standing Meta/Google policy [directional — standard platform policy, not re-verified this cycle] Medium Category detection during campaign creation; switch to compliant targeting automatically; refuse restricted-targeting combos
4 Storing ad-account OAuth tokens = personal-data processing (GDPR/CCPA) Tokens grant access to accounts tied to individuals; standard obligations: lawful basis, encryption at rest, least-privilege scopes, data deletion on disconnect, DPAs with subprocessors, breach notification [directional — legal review required] High Token vault with encryption + scoped permissions; document deletion flow ("disconnect = revoke + purge"); privacy policy + DPA templates; data-residency decision before EU launch
5 App-store rules for AI apps Apple's 2025 age-rating overhaul (13+/18+ tiers, new questionnaire); AI chatbot-style apps have been rated 17+/18+ since 2023 due to unfiltered-content risk; Google Play's AI-Generated Content policy (enforced since 2024) requires in-app reporting/flagging of AI content and content-safety moderation Medium Ship in-app report/flag UI for AI output (also a Google Play requirement, not optional); conservative age-rating questionnaire answers; content filters on generated creative (no political/NSFW); monitor Apple guideline updates
6 Platform API / ToS risk: acting on user accounts via Marketing APIs Ads APIs require app review, approved permissions, and compliant automation [directional] Medium Use official Marketing APIs only (no scraping); pass app review per platform; keep scopes minimal; rate-limit agent actions
7 AI hallucination in ad claims (health, financial, "guaranteed results") Platform policies prohibit misleading claims; AI copy is a known source [directional] Medium Pre-submission claim screening; prohibited-claims blocklist per vertical; human approval before any launch (Tier 2 gate) covers this

6) Tech Stack Recommendation (with evidence)

Recommendation: React Native 0.87 + Expo (managed workflow), TypeScript, Expo Router, EAS Build/Update/Submit, Vercel AI SDK (server-side agent + useChat client).

Evidence

Requirement Expo/RN Flutter 3.47 Verdict
AI SDK support AI SDK has a dedicated Expo guide (Expo ≥ 52): streaming via expo/fetch, useChat from @ai-sdk/react, server-side Zod-schema tools, multi-step tool chains — first-class mobile support (ai-sdk.dev) No comparable first-party AI streaming SDK; Roll-your-own REST RN+Expo
OTA updates (fast iteration on agent prompts/UI) EAS Update: push JS/assets over the air, gradual rollouts, one-click republish/rollback, adoption & crash dashboards; MAU-based billing (docs.expo.dev) Shorebird exists but younger ecosystem [directional] RN+Expo
Cloud build & release velocity EAS Build/Submit: cloud builds without local native toolchains — fits small/indie teams Requires more Xcode/Gradle housekeeping on native changes [directional] RN+Expo
App architecture expo-router: file-based routing, deep links, universal links — natural fit for approval-card deep links from push notifications GoRouter solid but less integrated RN+Expo
App-store policy compliance for OTA Docs are explicit: OTA obeys store rules; native changes need a new binary (runtime-version policy) — no gray area Same constraints apply Tie
Performance RN 0.87 New Architecture is adequate for chat feeds, charts, cards Impeller 2.0 leads for graphics-heavy apps (Bolder Apps, 2026) This app is form/chat/list-heavy, not GPU-heavy — adequate
Ecosystem/talent React/web code-sharing for a future marketing site & dashboard; large hiring pool; ~12.6% of top-500 US apps [secondary: AgileSoft Labs] ~46% developer market share [secondary] — but our web needs favor RN RN+Expo
When Flutter would win — Animation/graphic-intensive consumer apps, custom-drawn UI Not our case

Supporting architecture notes


7) Monetization Patterns

Evidence: agency-pricing surveys (10–20% of ad spend is the standard agency model; 31% of agencies price by %-of-spend, 42% flat fee, 27% hybrid — Ryze); usage-based pricing is now mainstream (78% of UBP adopters started within last 5 years — Metronome State of UBP 2025); credit models proven in AI tooling (Ahrefs, Clay — Lago/Flexprice); hybrid subscription+usage is the common 2025 configuration (Schematic).

Model Who uses it Fit for us
% of ad spend (10–20%) Agencies, some managed tools ✗ Rejected for self-serve SMB: taxes success, opaque to first-time advertisers, and conflicts with our "start small, ramp slowly" safety posture
Flat subscription Most SMB SaaS ✓ Core model; predictable, sellable in app stores (IAP)
Usage credits (AI generations, agent runs) Ahrefs, Clay, AI marketing tools ✓ Layer on top: protects LLM margin, creates natural upgrade path
Hybrid (base + overage / tiered + add-ons) Common 2025 pattern (Schematic; Datadog-style) ✓ Recommended shape
Free tier Freemium standard ✓ Generous enough to reach activation in demo/sandbox mode; capped by connected-account limit and AI credits

Recommended structure:


8) Sources

Agent UX / human-in-the-loop

Onboarding

AI-ad disclosure & platform policy

App-store rules for AI apps

Tech stack

Monetization