Build an app people come back to.
See how people use your iOS app, hear what they want improved, and bring them back to the right screen. Pharen connects analytics, feedback, deep links, and crash reporting so your team can decide what to fix and see what changes after you ship.
See what brings people back.
Track the steps that matter, from a first screen view to a completed checkout. Automatic sessions bring screens, custom events, and crashes into one timeline so you can see what led up to a problem.
Compare adoption across releases, see how many installs come back, and use funnels to find where people drop off.
Explore sessions and analyticsPharen.shared?.track("checkout_completed", properties: [
"order_value": 49.99,
"items": 3
])
Pharen.shared?.screen("Cart")Hear what people need from your app.
Let people report a problem, suggest an improvement, or ask a question inside your app. Screen context and optional pictures help you see what they saw.
Use in-app surveys to measure satisfaction or whether people would recommend your app. Collect feedback on the web with a hosted report page or widget.
Explore in-app feedbackExplore the web report widgetWhat a report shares
- In-app feedback requires content consent before collection.
- People can preview and remove pictures before sending a report.
- A query key needs the report-text grant to read a masked copy of a report. Agent queries exclude pictures and individual survey answers.
Bring people straight to the right screen.
Send people from a campaign or shared link to a specific place in your app. Use your own domain and set a web or App Store fallback.
With behavioral consent, measure confirmed app opens and see which links start a session. Open events report details such as the link ID and campaign. A separate routing lookup can send the URL path and query string to Pharen. The open event omits those raw fields.
See how routing and measurement work// Open the destination in your app
Pharen.shared?.deepLinks.onLink = { link in
router.open(link.targetPath, params: link.params)
}
// From .onContinueUserActivity / your scene delegate:
Pharen.shared?.deepLinks.handle(userActivity)Find the crashes worth fixing first.
See which issues recur, which builds they affect, and when a resolved issue returns. Approved organizations can upload matching debug symbols to get readable stack traces.
The SDK saves fatal crash reports on the device for upload on the next launch. The server deduplicates retries by report ID.
Explore crash reportingPharen.shared?.crashReporting.recordError(
"Checkout failed: payment gateway timeout",
stack: Thread.callStackSymbols,
severity: .error,
breadcrumbs: ["tapped_pay", "network_slow"]
)Get the next fix into testers’ hands.
Run the iOS release lane to archive your app, register the release, upload the build and its debug symbols, and get an install link. Testers can open the link in Safari on a provisioned device.
Set up iOS beta distribution$ bash release/release-lane.sh
→ archiving (Release) · exporting .ipa
→ symbols upload · 3 dSYMs
→ registering release 9.9.9 (999)
→ builds upload
https://install.pharen.ai/install/…See how your app is doing in the App Store.
Follow public ratings and rankings. Connect App Store Connect to bring your app’s reviews, downloads, engagement, and store-measured performance into Pharen.
Imports from your App Store Connect credential are Customer Data scoped to your organization.
Read the Store Data terms// → pharen_store_overview · sample-app · live
rating 4.8 (n=126) · US · v9.9.9
chart_ranks top-free/6008 #38 · US
reviews 3 this week · 1 unanswered
perf launch p50 412 ms · hang rate 0.3%
sync ok · 2h ago
// commerce and engagement: from your own keyAsk your agent about app performance.
Ask which version saw more crashes, where people dropped out of checkout, or how App Store ratings changed. A query key limits read access to the apps and environment you choose. Pharen may withhold small counts from grouped or filtered metrics.
A user or an install, what your app said about a user, and the address a reporter left to be reached at cross only on a key you minted with the grant that covers them and a stated purpose, and every such read is recorded: in your user lookup log, or on the issue's history for a reporter's address.
The agent connection excludes a raw event, a location a device shared, anything from the special-category store, anything under the health purpose.
See what your agent can access// → pharen_query
{ "metric": "crashes.count",
"app_id": "sample-app",
"environment": "live",
"group_by": ["app_version", "device_model"] }
// ← rows (released builds; small counts withheld)
9.9.9 iPhone14,5 14
9.9.9 iPhone15,3 6
9.9.8 iPhone14,5 5
// meta: withheld_rows 1 · small_count_threshold 5Give your agent a stack trace to work from.
Your agent can read issue counts, the latest affected build, and a representative stack with readable frames when matching symbols are available. Use that context to find the relevant code and check which builds are affected.
The issue feed includes development and released builds. For released build counts, use the crash metrics.
// → pharen_issues · sample-app · live
NSInvalidArgumentException · DemoCart.total()
open · 6 crashes · last seen on 9.9.9 (999)
DemoCart.total() → CheckoutView.body → main
SIGSEGV · SampleStore.load(fixture:)
open · 14 crashes · last seen on 9.9.9 (999)
SampleStore.load(fixture:) → SampleStore.init → mainConnect activity across sessions with consent.
Pharen uses pseudonymous install IDs. With identity consent, your app can associate activity across installs using a pseudonymous user ID. Identity traits are stored separately from events.
Explore how Pharen handles app dataPharen.shared?.identify("cus_482", traits: ["plan": "pro"])
// Pseudonymous user ID: cus_482
// Trait stored separately: plan=proTry Pharen with your iOS app.
Individuals in the United States can explore the demo and check availability for private iOS testing with invented data. Test and live keys require organization approval. For larger teams, contact [email protected].