How It Works

WhyDidItClose turns low-level termination signals into direct guidance.

Step 1: Observe App Termination

The app monitor captures closure events and records timing and termination metadata around the event window.

Step 2: Correlate Local Signals

WhyDidItClose correlates available local evidence near the event:

• lifecycle notifications
• local unified logs
• local crash/policy clues when available

Step 3: Classify the Dominant Cause

A deterministic diagnosis engine maps observed patterns to a dominant cause and confidence level.

Step 4: Explain and Recommend

The app produces plain-language output so you can act immediately instead of parsing raw diagnostic fragments.

Example Output Shape

{
  "app": "ExampleApp",
  "cause": "force_quit",
  "confidence": "high",
  "summary": "The app was terminated by an external quit action.",
  "next_action": "Check recent user/system quit triggers and reproduce with event timeline."
}

Before vs After

Before WhyDidItClose

• Teams classify events as generic "crash" without confidence.
• Support and QA spend cycles asking for missing context.
• Engineering receives low-signal escalations.

After WhyDidItClose

• Termination classes are explicit and consistent.
• Event context is immediately shareable.
• Next-step guidance reduces triage round trips.