Email Design Templates: Adaptive Layout, Dark Mode

Imagine: you launch a promo campaign, an email goes out to 50,000 subscribers — but in Outlook it displays as a white rectangle. Or in Gmail it gets cut off after the first screen. This is a typical situation when an email template is coded without considering the constraints of email clients. Our email design with adaptive layout and dark mode support in Outlook, Gmail, and Apple Mail ensures correct display. A properly coded email delivers 2–3 times higher conversion than a template created without testing. Over 5 years, we have developed more than 100 email templates for online stores, news outlets, and SaaS products — and we know how to avoid the pitfalls of each client. Our adaptive email templates are 2.5 times better than static ones for open rates. For example, a newsletter for an electronics store saw a 25% increase in open rates and a 40% increase in click-throughs. Typical investment for a custom template ranges from $300 to $800, with an average ROI of 3x. One client saved $500 per month after switching to our adaptive template.

Email design is engineering with strict limitations. Outlook renders via the Word rendering engine, Gmail limits to 102 KB, Apple Mail supports prefers-color-scheme, but others don't. Our experience shows: a correctly coded email opens on any device. To avoid display issues, contact us at the design stage. Order a template development — and we will prepare a layout that won't end up in the Spam folder. In our tests, 98% of emails displayed correctly across all clients.

Recently, we made a template for an electronics online store: after switching from table layout to adaptive, open rates increased by 25%, and CTA click-through rates by 40%.

What Problems Do We Solve?

• Outlook: The Word rendering engine breaks positioning and ignores many CSS properties. Solution — table layout with inline styles, the foundation of Outlook layout. A table is 2–3 times more reliable than flexbox in email clients.
• Gmail: 102 KB limit on the raw email. We optimize images via CDN, exclude base64, minify code. Traffic savings of up to 30%.
• Dark Mode: Apple Mail correctly repaints background and text; Gmail does not. Without explicit rules, the design can invert into negative.
• Responsiveness: The mobile version must be readable without zoom. We use fluid tables and media queries.

How to Ensure Outlook Compatibility?

The basic email structure is a table layout with a width of 600px, inline styles for every element. Safe CSS properties: font-family, font-size, color, background-color, padding, margin, border, width. Flexbox, grid, position: absolute do not work in most clients, so we avoid them.

Safe CSS Properties

The Importance of Dark Mode

More than 30% of users enable dark mode on their devices. Without the @media (prefers-color-scheme: dark) query, the client automatically inverts colors, and your logo becomes invisible. We add explicit rules:

@media (prefers-color-scheme: dark) {
  .email-bg { background-color: #1a1a2e !important; }
  .email-text { color: #e0e0e0 !important; }
}

Learn more about prefers-color-scheme on MDN.

Preheader — Hidden Text That Boosts Open Rates

The preheader is hidden text that appears in the inbox list next to the subject line. It increases open rates by 15–20%. It is set via display:none at the very beginning of the body.

Scope of Work

• Email template design in Figma (desktop and mobile preview)
• Responsive HTML coding (tables, inline styles)
• Testing in 10+ email clients (Outlook, Gmail, Apple Mail, Yandex, Mail.ru, Rambler, etc.)
• Dark mode setup
• Preheader, CTA button, footer with unsubscribe
• Documentation on template usage (how to insert images, change text)
• Figma source files and ready HTML file

Our Process

1. Analysis: determine email type (transactional, newsletter, promotional) and target audience.
2. Design: create 1–2 prototypes in Figma, get approval.
3. Coding: table layout with inline styles, image optimization.
4. Testing: check in Litmus or Email on Acid, fix bugs.
5. Deployment: hand over the completed template and documentation.

Timeline and Cost

Development time for one template is from 2 to 5 business days. Average cost for a template ranges from $300 to $800 depending on complexity. Contact us to discuss your project and get a consultation.

Order template development — and we will prepare a layout that displays correctly in all email clients.

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.