Platform Differences: iMessage on macOS vs WhatsApp on iOS

Clear breakdown of what differs and what stays the same between Mimoto platform workflows.

Short answer: iMessage runs through the macOS app using local `chat.db` access, while WhatsApp runs through iOS with user-selected chat exports; both keep local-first processing and shared core analysis logic.

Which platforms are currently supported?

• iMessage: macOS app
• WhatsApp: iOS app

How does iMessage ingestion work on macOS?

The macOS app reads local Apple Messages data from chat.db after user permission is granted. This path can analyze full available iMessage history.

How does WhatsApp ingestion work on iOS?

The iOS app analyzes chats users explicitly choose to export from WhatsApp. This is a selective chat-by-chat flow, with optional multi-export steps inside WhatsApp.

Why can’t iMessage be analyzed directly on iOS?

iOS does not expose direct access to chat.db, so the iMessage data path is not available for direct iOS ingestion.

Are permissions different?

Yes.

• iMessage on macOS: Messages folder access + Contacts access
• WhatsApp on iOS: no broad contact-sharing permission required for this flow

What stays the same across both platforms?

The privacy and scoring fundamentals are shared:

• local-first processing
• no message-content upload
• shared business-logic layer for scoring and conversation assessment

What feature difference should users know about?

A notable current difference is media display in message history: macOS supports showing images there, while iOS currently does not.

Worked example

If a user wants full iMessage history analysis, they use the macOS path. If they want specific WhatsApp chats analyzed on iOS, they export and choose those chats directly.

Not a fit

If someone needs every messaging platform in one unified pipeline today, Mimoto may not fit until additional platforms are added.