No code execution
We do not install packages, build the app, or run scripts from your project files.
How LaunchLint reviews apps
LaunchLint methodology
LaunchLint connects deterministic signals in project files to reviewed store rules. A signal never becomes a guarantee of approval.
Last reviewed: July 19, 2026
Supporting detail before conclusions
Every detected risk requires a concrete file, configuration, or store-detail signal and a clear confidence assessment.
Official sources
Store-rule references point to Apple, Google, or Expo documentation and are reviewed when requirements change.
Explicit limits
Usability, real runtime behavior, and the final installable app can require human or additional technical review.
Supported app technologies
What LaunchLint can assess completely
Complete means project structure, shipped dependencies, permissions, store configuration, and statically provable security patterns are assessed together.
ExpoComplete static assessment
CompleteReact NativeComplete static assessment
CompleteIonic / CapacitorComplete static assessment
CompleteFlutter / FlutterFlowComplete static assessment
CompleteNative iOS / AndroidStore and platform configuration
ConfigurationKMP, .NET MAUI, Unity, UnrealNo reliable source assessment
Not yetOfficial store rules
LaunchLint guides