Grey Mirror by JustLayMe

iMessage analysis works best when the full iPhone thread stays intact.

Grey Mirror is designed for exported iMessage-style histories where sender, timestamp, body, and order can be normalized. The goal is to preserve the full relationship timeline rather than judge one blue-bubble screenshot.

Can Grey Mirror analyze iMessage conversations?

Grey Mirror can analyze iMessage-style exports when the file preserves enough message text, speaker labels, timestamps, and sequence. Incomplete or ambiguous exports get confidence labels and participant-resolution prompts.

What does an iMessage export need?

The useful part of an iMessage export is not the platform brand. It is the preserved timeline: who sent each message, when it happened, and what came before and after.

Sender labels.
Timestamps.
Message body.
Conversation order.
Enough coverage to compare relationship phases.

What can Grey Mirror measure from an iPhone thread?

With enough data, Grey Mirror can measure timing drift, repair, effort imbalance, positivity reciprocity, planning, silence gaps, communication shifts, and longitudinal change across later runs.

What affects evidence quality?

Exports can be incomplete. Attachments, reactions, deleted messages, phone calls, and other apps can change meaning. Grey Mirror reflects those factors in confidence labels and alternate-context notes.

What should users check before uploading?

The upload is strongest when the export gives Grey Mirror a clean timeline instead of a scrapbook. The parser can handle messy files better when the basic structure is still present.

Confirm the export includes both participants rather than one-sided copied text.
Keep timestamps if the export tool provides them.
Avoid editing the file into selected excerpts; the missing middle can change the pattern.
If the names are ambiguous, expect the product to ask for participant confirmation before assigning person-specific metrics.

Why does iMessage timing matter so much?

Reply timing is often where the emotional shift becomes visible first. A thread can keep the same words while the rhythm changes: slower repair after fights, fewer follow-ups, shorter replies after vulnerable bids, or longer gaps before future-planning conversations.

Timing drift can support a cooling-read only when it repeats across windows.
Fast replies are not automatically healthy; context and content still matter.
Silence after conflict reads differently from silence during ordinary work or sleep windows.

Frequently Asked Questions

Is one iMessage screenshot enough?

It can support a lightweight scan, but it is not enough for full-thread relationship analysis.

Do timestamps matter?

Yes. Response timing, silence gaps, and drift require reliable timestamps.

What if names are unclear?

Participant resolution should pause or ask for confirmation instead of guessing.