Keep the users you worked hard to acquire
Most apps lose a large share of new users within the first days. The causes are usually specific: an onboarding that asks too much too early, a core feature people never find, notifications that feel like noise. We use cohort analysis and funnel data to find where users leave, then improve the product and the messaging around those moments. Because we build apps as well as analyse them, we can redesign the onboarding or ship the fix ourselves, not only recommend it.
What we deliver
Retention analysis
Cohort and funnel analysis that shows when users drop off, which behaviours predict staying, and how retention differs by source.
Onboarding optimization
Shorter paths to the first meaningful result, well-timed permission requests and onboarding variants tested against each other.
Push notifications
Notification strategy, permission timing, segmentation and frequency limits, implemented with APNs and Firebase Cloud Messaging.
Lifecycle messaging
Triggered push, in-app and email messages for activation, habit building, reactivation and win-back.
Churn reduction
Cancellation and inactivity signals tracked, with targeted responses such as save offers, reminders or product fixes.
How we approach it
Find the value moment
We identify the action that separates users who stay from users who leave, then shape onboarding and messaging to get more people there sooner.
Fewer, better messages
Notifications should be useful enough that people keep them on. We favour triggered, relevant messages over broadcast campaigns that train users to opt out.
Retention starts in the product
Messaging cannot fix a product that does not deliver. When the data points to a feature or usability problem, we treat that as the first fix.
Technologies
- Firebase
- Amplitude
- Mixpanel
- OneSignal
- Braze
- APNs
- Firebase Cloud Messaging
How we work
- 01
Discovery
A short call to understand your goals, users and constraints. You get a clear scope, timeline and estimate.
- 02
Design
User flows and high-fidelity screens that follow Apple’s Human Interface Guidelines — reviewed together before a line of code.
- 03
Build
Iterative development in Swift and SwiftUI with regular TestFlight builds, so you can try the app on your own iPhone as it grows.
- 04
Launch
App Store assets, submission and review handled end to end. Your app goes live under your own developer account.
- 05
Support
Bug fixes, iOS version updates and new features after launch — based on real user feedback and analytics.
Questions
What is a good retention rate for an app?
There is no single number. Retention varies widely by category, platform, country and how users were acquired, and a daily habit app should not be compared with a utility used once a month. Public industry reports are a useful reference, but the most reliable benchmark is your own cohorts over time and how they change after each improvement.
Which retention metrics should we track?
Start with day-1, day-7 and day-30 retention by cohort, plus the activation rate for your key action. For subscription apps, add trial conversion and renewal rates. We set up these metrics with consistent event definitions so they can be compared over time.
When should we ask for push notification permission?
Usually after the user has seen value and understands why notifications help, not on the first screen. On iOS, you only get one system prompt per user, so a short explanation beforehand and good timing matter. We test timing as part of onboarding work.
Do we need a tool like Braze or OneSignal?
Not on day one. Firebase Cloud Messaging and a simple trigger setup cover many apps. A dedicated engagement platform makes sense when you need detailed segmentation, multi-channel journeys or marketers who can build campaigns without developers.
Have a project in mind?
Tell us about it. Our team in Istanbul replies within one business day with next steps and a free intro call.
Start a project