How to evaluate a mobile app before acquisition — app store dependencies, in-app purchase infrastructure, push notification reliability, offline architecture, device fragmentation, and the metrics that reveal real vs. inflated user numbers.
Mobile app acquisitions have risks that don't exist in web software. You're operating inside platforms (Apple and Google) that make the rules, can change them, and can remove your product. The technical due diligence needs to account for platform risk, not just code quality.
This guide covers the specific evaluation challenges of acquiring iOS, Android, or cross-platform mobile apps.
The first thing to check: what is the app's current standing with Apple App Store and Google Play?
Request access to: App Store Connect and Google Play Console before close, not screenshots.
Apple requires apps to use its IAP system for digital goods and services. The 30% (or 15% for small developers) commission applies. This is non-negotiable for consumer apps selling digital content.
What to verify:
An app generating ₹1Cr/month in revenue through a non-compliant payment flow is one App Review cycle away from a forced change or removal.
Mobile apps depend on third-party SDKs for analytics, crash reporting, push notifications, and more. Each is a risk:
Run a dependency audit. Old, unupdated SDKs are a common source of App Review rejections.
If the app has subscriptions:
App store revenue is subject to a 30% platform cut and delayed payouts. Verify:
Mobile user metrics are frequently inflated. Here's how to verify:
Red flag: Apps with millions of downloads and negligible revenue. Downloads without engagement are worthless in an acquisition.
| Architecture | Maintenance overhead | Risk |
|---|---|---|
| Native iOS + Native Android | High — two full codebases | Requires two platform-specialized teams |
| React Native | Medium — shared JS, platform bridges | Bridge maintenance, upgrade complexity |
| Flutter | Medium — Dart codebase | Smaller talent pool than React Native |
| Ionic/Capacitor | Lower complexity, lower performance | Heavy WebView dependency |
For acquired cross-platform apps: Ask specifically how much platform-specific (iOS/Android) native code has been written outside the shared layer. Mature cross-platform apps often accumulate significant native workarounds that reduce the maintenance benefit.
Does the app work offline? This is often a quality differentiator:
A poorly designed offline sync system is one of the most expensive things to retrofit.
Push notifications are critical for retention in most mobile apps:
A 40% push delivery rate indicates stale tokens, poor segmentation, or infrastructure issues.
Request crash data from the current crash reporting tool (Firebase Crashlytics, Sentry, etc.):
A crash rate above 0.5% in a consumer app is significant — users who experience crashes don't return.
Acquiring a mobile app and need a technical assessment covering platform risk, user metric authenticity, and infrastructure quality? Contact us — we conduct mobile-specific technical due diligence across iOS, Android, and cross-platform apps.
If this guide resonated with your situation, let's talk. We offer a free 30-minute discovery call — no pitch, just honest advice on your specific project.
Your developer went silent. Your project is half-built. You don't know what state the code is in. This is the step-by-step guide to recovering your project and getting back on track.
10 min readRescuing SoftwareHow enterprise buyers should evaluate SaaS vendor security — what certifications actually mean, what to look for in security questionnaires, data residency requirements, incident response, and the contract clauses that protect you.
11 min read