Mobile email rendering study: study protocol

Define the decision

This page is a proposed research protocol, not a completed study or a report of findings. The decision is: Can recipients read the message and identify the intended action across the selected mobile clients? The observation unit is one message version rendered in one client configuration. Define the population and owner before collecting records; do not substitute an available convenience dataset without documenting the change.

Work through the procedure

1. Build a matrix of client, OS, viewport, text scaling, light/dark mode and images blocked. Keep the original MIME artifact.
2. Use controlled inboxes. Inspect text overflow, link target clarity, contrast and reading order with assistive technology where available.
3. Before collection, write the primary outcome, observation window, exclusion rules and stopping conditions. Preserve excluded observations with a reason rather than quietly removing them.
4. Pilot the procedure with fictional or owned test data, resolve ambiguous fields, and freeze a dated protocol version before the main run.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

configuration: narrow viewport and enlarged text; failure: signature table forces horizontal scrolling; attach a redacted screenshot
Suggested record fields: observation_id, condition, evidence_reference, outcome, exclusion_reason, reviewer, protocol_version
Status: illustrative record only; no study has been run for this page.

Read the result

Classify defects by task impact and reproducibility. A screenshot checks appearance but not keyboard, screen reader or link behavior. Keep the numerator, denominator and missing evidence visible. If the available observations cannot answer the registered question, report that limitation rather than selecting a more favorable metric after collection.

Collect the evidence

Observation unit: message-client-configuration.

Original MIME and owned inboxes across the chosen email-client matrix.

Keep the same message version; inspect links and assistive behavior separately from screenshots.

Analysis: Defects by configuration and task impact; website browser screenshots are not email-client coverage.

Download the JSON collection template under Source references. Set an owner, eligibility rules, outcome definition, observation window and sample justification before collecting records. Templates contain no participant data or results; keep original private records outside the public website.

Check before moving on

1. Name the person responsible for collection and review.
2. Check that the evidence can be inspected without exposing private messages or credentials.
3. Record deviations from the protocol and analyze their possible effect.
4. Retain a dated, redacted evidence worksheet with the final interpretation.

Limits and next action

Do not claim all-device compatibility from a small matrix. Publish tested versions and unknown combinations. Publish results only after the evidence, method and limitations have been reviewed. This protocol provides no benchmark, expected lift or completed-study claim.

Source: Method or workflow reference