<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rokas Ambrazevicius on Medium]]></title>
        <description><![CDATA[Stories by Rokas Ambrazevicius on Medium]]></description>
        <link>https://medium.com/@graphicMeat?source=rss-7ab5ca9bde8b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3hzW_KzIExa0sL5fXIijIQ.png</url>
            <title>Stories by Rokas Ambrazevicius on Medium</title>
            <link>https://medium.com/@graphicMeat?source=rss-7ab5ca9bde8b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:09:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@graphicMeat/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What makes an app great is mostly invisible]]></title>
            <link>https://dispatch.jsipe.com/what-makes-an-app-great-is-mostly-invisible-11d0c547768f?source=rss-7ab5ca9bde8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/11d0c547768f</guid>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[indie-hacking]]></category>
            <category><![CDATA[app-developmentux-design]]></category>
            <dc:creator><![CDATA[Rokas Ambrazevicius]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 01:10:24 GMT</pubDate>
            <atom:updated>2026-11-20T01:10:24.589Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ten habits from building MailVault, an email archiver in nine languages, as a solo developer</h3><p>Most advice about “great apps” is about the parts you can screenshot: a clean layout, a nice colour palette, smooth animations. Those matter. But when I look at the decisions that actually made people trust <a href="https://mailvaultapp.com/">MailVault</a>, almost none of them show up in a screenshot.</p><p>MailVault is a desktop email client for macOS, Windows and Linux whose main job is simple to say and hard to get right: save your email on your own computer as plain files, so you can free up space on the server without losing anything. I build it on my own, under the GraphicMeat name. It has shipped 72 changelog entries since February 2026, roughly one release every four days.</p><p>This is what I have learned about making an app good, using MailVault as the worked example. Each section ends with the habit you can steal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxar_QhseLQMjXWmZVVWsw.png" /><figcaption>MailVault’s unified inbox across three accounts.</figcaption></figure><h3>1. Write down what the product believes, before you design it</h3><p>Before there was a design system, there was a short file called PRODUCT.md. Five lines in it settle more arguments than any mockup:</p><blockquote><em>The user’s copy is the product.<br>Never let the user guess where a message lives.<br>Destructive is fine; ambiguous is not.<br>Free stays whole.</em></blockquote><p>“Destructive is fine; ambiguous is not” is my favourite. Deleting mail from the server is the whole point of the app, so I am not supposed to add friction to it. My job is to add confidence. That one line killed a dozen “are you sure?” dialogs before anyone drew them.</p><p>The same file has a list called “Absences that must never be fabricated”: no invented user counts, no fake testimonials, no awards, no licence claims that have not been decided. It sounds like a legal note. It is really a design note. An app that lies on its website will eventually lie in its UI.</p><p><strong>Habit:</strong> write four or five product beliefs that are specific enough to lose an argument. If a principle can never rule anything out, it is not a principle.</p><h3>2. Make every colour mean exactly one thing</h3><p>The design document for MailVault opens with a sentence I now apply to every project: “Colour here is a claim, not decoration.”</p><p>There are four named colours, and each one states where a message lives:</p><ul><li><strong>Vault Emerald:</strong> the message is on your disk.</li><li><strong>Server Blue:</strong> it is on someone else’s machine.</li><li><strong>Only-Copy Gold:</strong> the server no longer has it, and this file is all that is left.</li><li><strong>Desk Lamp Indigo:</strong> whatever is selected, focused or about to happen.</li></ul><p>Status colours like red and orange exist, but they are deliberately kept out of that vocabulary. They describe an operation, never a location.</p><p>Here is the bug that taught me to be strict about it. The reading pane once showed a band saying “Saved in your vault” above a message whose own row icon said “your only copy”. Two parts of the screen were answering the same question from two different pieces of state, and they disagreed. In an app whose whole promise is “you will not lose mail”, that is the worst possible bug, even though nothing was actually lost.</p><p>The fix was not a patch. It was a rule. Every place that says where a message lives (the row icon, the row tint, the tooltip, the reading-pane band) now calls one function, describeMessageState. Nothing is allowed to work out custody on its own. We call it the One Claim Rule.</p><p>A second rule sits next to it, the Proof Rule: gold, the loudest claim the UI can make, only renders when the server state has actually been checked. Not knowing is not proof. If the app has not verified yet, it shows the calm state and the tooltip says “Server copy not verified yet”. That rule is why switching accounts no longer flashes “deleted from server” across the whole list.</p><p>Gold also gets its own icon shape, not just its own colour, because emerald and gold look alike to people with deuteranopia.</p><p><strong>Habit:</strong> if a colour or icon makes a claim about data, route it through one function. Two sources of truth on one screen will eventually contradict each other in front of a user.</p><h3>3. Motion should explain, not decorate</h3><p>The motion rule follows from the colour rule: “colour says where your mail lives; motion says when it moved.” A row that turns green between two frames cannot tell you anything happened. A row that visibly settles into the vault can.</p><p>So MailVault uses a small ladder of durations (90, 140, 220, 320 and 620 milliseconds) and only two easing curves. There is no scroll choreography on the website. The whole app is wrapped so that it respects the system’s reduced motion setting, with extra CSS fallbacks where that wrapper does not reach.</p><p><strong>Habit:</strong> pick a handful of durations and two curves, name them, and refuse every animation that does not explain a change of state.</p><h3>4. Design for the bad moments: offline, undo, interrupted setup</h3><p>A lot of an app’s quality lives in the moments nobody demos.</p><p><strong>Offline.</strong> When the network drops, MailVault shows a banner, not a modal. The comment above that component says it better than I can: a local-first archive that blocks reading when the Wi-Fi drops “has the story exactly backwards”. Your mail is already on your computer. The banner says what still works and gets out of the way on its own when the connection returns.</p><p><strong>Undo.</strong> Destructive actions get an undo toast that stays for eight seconds, and sending has its own undo. Combined with “destructive is fine; ambiguous is not”, this is how you make deletion feel safe without asking permission every time.</p><p><strong>Onboarding.</strong> Setup is a sequence of short steps: welcome, where to store your archive, add an account, appearance, default mail app, what is free, what is Premium. You can skip it, and if you quit halfway, the app offers to resume. If you replay it later with accounts already set up, the storage and account steps are dropped, because asking again would be silly.</p><p><strong>Keyboard.</strong> There is a shortcuts sheet, because people who live in email live on the keyboard.</p><p><strong>Habit:</strong> list the five worst moments in your app (no network, a mistake, a half-finished setup, an error, an empty screen) and design each one as carefully as the happy path.</p><h3>5. Localize properly: English plus the big 8</h3><p>MailVault ships in nine languages: English, Spanish, French, Italian, German, Brazilian Portuguese, Japanese, Korean and Simplified Chinese. If you only do one thing from this article, do this. When I checked our analytics in August, about one visitor in seven to the MailVault website was from Germany, and the site did not have a single German page yet.</p><p>The trick is to treat localization as a test suite, not a translation job. Every language has 4,708 strings, and the build fails if any of these drift:</p><ul><li>every English key exists in every language, and no language invents keys of its own</li><li>every {{placeholder}} and markup slot survives translation</li><li>nothing is accidentally left in English (a short allowlist covers brand names and the like)</li><li>no translation is more than 2.5 times the length of the English one</li><li>each language supplies exactly the plural forms it uses</li></ul><p>The length rule has the best comment in the codebase: “German runs long and will break fixed-width layout before anyone sees it.” The plural rule exists because English has two forms (one message, two messages) and other languages do not follow that pattern. Plurals go through Intl.PluralRules, and dates and numbers through the browser&#39;s Intl formatters, never string concatenation. A separate test fails if code uses a key that does not exist in English, so you cannot ship a raw key name to a Japanese user.</p><p>The website gets the same treatment. English HTML is the only source; the eight translated versions (129 pages each) are generated, never hand-edited. A check step fails on a missing string or a lost tag, and a verify step confirms every generated page has the same structure as the English one and every link resolves.</p><p><strong>Then localize the screenshots and videos.</strong> This is the step most apps skip. A German page with English screenshots tells the reader the translation stops at the text, and that the app probably does too.</p><p>MailVault’s screenshots and videos are not translated after the fact. They are captured again in every language, from the real app:</p><ul><li><strong>Real app, real window.</strong> Screenshots are taken of the actual app window on a Mac mini with a high-resolution display, so they come out at 2x, with the real window corners and controls. Nothing is mocked up in a design tool.</li><li><strong>The mailbox is translated too.</strong> Every capture runs against one fictional demo mailbox: one made-up studio, three accounts, a consistent cast of senders, served by the same mock mail server the tests use. Every subject line, sender and message body in that mailbox goes through a translation catalog. The German screenshot does not show German buttons over an English inbox. It shows a German inbox.</li><li><strong>Every variant, every language.</strong> Product screenshots come in dark and light and in three sizes, in all nine languages. The German folder alone holds 528 screenshot files.</li><li><strong>Help videos per language, with captions.</strong> The help center has 12 short how-to videos per language (search, the privacy switch, a manual backup and so on), each recorded in a fresh launch of the app in that language, with translated WebVTT captions and 72 matching stills. Longer guide videos and the feature clips on the product pages are localized the same way.</li><li><strong>Every image says what it shows.</strong> Each published still and video gets a small “MailVault version 2.20.0 de” stamp in the padding below the UI, never over it. A manifest records the app version, the commit it was captured from, the source frame and crop, and a hash of every file. The version also goes into each image’s alt text, and a media check rejects any app screenshot with no description, no version label or the wrong version. A separate test fails if a translated page points at a clip that does not exist in its language.</li></ul><p>The payoff is not just polish. When a screenshot shows an older version, the stamp says so, and re-capturing the help media in all nine languages is one queued run on the Mac mini instead of a week of manual work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hl4G_wRb-w-LtofECLC0Yg.png" /><figcaption>The same inbox, captured from the real app in English, German and Japanese. The mail is translated too.</figcaption></figure><p><strong>Habit:</strong> ship at least English plus the big eight European and Asian languages, and make the build enforce parity, placeholders, length and plurals. Then automate your screenshots and videos against a translatable demo dataset, so the pictures speak the same language as the words. Translators are not the bottleneck. Drift is.</p><h3>6. A good FAQ answers the awkward questions</h3><p>MailVault’s <a href="https://mailvaultapp.com/faq.html">FAQ</a> is about 60 questions split across nine topic pages: getting started, storage, providers, backup and restore, search and insights, scheduled send, Premium, “your questions” and troubleshooting. A few things made it useful rather than decorative.</p><p><strong>It answers the questions people are afraid to ask.</strong> “Do you offer a lifetime purchase?” gets a straight answer: no, not today, and here is why. “What happens to my emails if MailVault stops development?” is answered too: your archive is standard .eml files that other mail apps can open, and the source code is public. Those two answers do more for trust than any feature list.</p><p><strong>Each answer has its own address.</strong> Every question is an anchor, so support replies can link straight to it, and each topic page carries FAQPage structured data so search engines can show the answer directly.</p><p><strong>Answers are dated.</strong> Every help page has a footer showing which app version it was reviewed against and when. Screenshots are tagged with the version they were captured from. When the app changes, stale help is visible instead of quietly wrong.</p><p><strong>It is searchable and it degrades well.</strong> The help center has a search index of about 990 entries, rebuilt in CI. The search box stays hidden until its script loads, so a page without JavaScript never shows a broken control.</p><p><strong>Habit:</strong> write the FAQ from your support inbox, not your feature list. Answer pricing, data ownership and “what if you disappear” plainly, and stamp every answer with the version it describes.</p><h3>7. Make privacy a property of the architecture, not a promise</h3><p>Privacy policies are promises. Architecture is proof. MailVault’s privacy story is mostly made of decisions that remove the possibility of doing the wrong thing:</p><ul><li>Passwords and tokens live in the operating system’s keychain, never in a config file.</li><li>Gmail and Microsoft 365 sign in with OAuth, so you never hand the app your password.</li><li>Mail is stored as plain .eml files in a standard Maildir folder, with import and export for MBOX. You can walk away with your archive at any time.</li><li>The app has no telemetry and no account to create.</li><li>There is a published security policy with response targets: acknowledgement within 3 working days, assessment within 10, a fix aimed for within 90 days.</li></ul><p>The pricing follows the same idea: “Free stays whole.” The email client and unlimited manual backups are free. Premium pays for automation (scheduled backups, migration between accounts, cleanup rules), never for access to your own data.</p><p><strong>Habit:</strong> for every privacy claim on your website, find the line of architecture that makes it true. If you cannot find one, the claim is a promise, and promises break.</p><h3>8. Test the way users break things</h3><p>Great UX dies quietly in regressions. As of this week MailVault has around 12,400 JavaScript test cases, about 7,000 Rust tests, and 210 end-to-end test files that click through the real app.</p><p>The part worth copying is not the count. It is that the repository includes its own fake mail servers. A mock IMAP server and a mock JMAP server start fresh for each run, seeded with accounts and an inbox of 700 messages, deliberately bigger than any page the app loads at once, so pagination is genuinely tested rather than assumed. Every run uses a throwaway home folder, so tests never touch a real archive.</p><p>Because MailVault is built with Tauri, its interface tests can drive the app through WebDriver, and the headless suite runs on a free Ubuntu runner in GitHub Actions on every change. The heavier suites run on a Mac mini before releases. I wrote about <a href="https://graphicmeat.com/blog/swiftui-vs-tauri-ui-testing">the cost of that setup compared with a SwiftUI app</a> separately.</p><p><strong>Habit:</strong> build the fake version of whatever your app talks to (a mail server, a payment API, a sync backend) and make it awkward on purpose: too many items, slow responses, odd data.</p><h3>9. Ship small and often, and update automatically</h3><p>72 changelog entries in nine months only works because shipping is boring. On macOS the app updates itself through Sparkle, signed and notarised. There is also a Mac App Store build, a signed Windows installer, Linux .deb packages and a Snap for both Intel and ARM machines, all produced by CI from the same tag. A version consistency check runs in CI so the app, the website and the release can never disagree about which version is current.</p><p>Small releases make good UX cheaper. When a user reports something confusing, the fix reaches them in days, not in the next quarterly update.</p><p>Performance is part of the same habit, and it gets written down with the version it was measured on. From the README, for version 2.16.0: a 53 MB macOS download, about 345 MB of memory with a 10,000-message inbox loaded, offline search across 50,000 messages in under 15 ms in our test, and smooth lists past 17,000 messages.</p><p><strong>Habit:</strong> automate the release and the update so completely that shipping a one-line fix costs you nothing. And when you publish a performance number, publish the version next to it.</p><h3>10. Test your website like you test your app</h3><p>The website is part of the product. It is the first screen most people ever see, so MailVault’s site has its own test suite:</p><ul><li>an SEO test checks that structured data, the sitemap and the llms.txt file for AI assistants match the real pages</li><li>a style test checks every English page shares the same shell, has a main landmark and never exposes a personal email address</li><li>a pricing test fails the build if the early-bird offer is ever described as “limited time” or “lifetime”, because neither would be true</li></ul><p>That last one is my favourite small test. Marketing copy drifts toward urgency on its own. A test is the only thing that reliably stops it.</p><p><strong>Habit:</strong> anything on your website that would be embarrassing if it were wrong (prices, platforms, claims) deserves a test.</p><h3>What we have not solved</h3><p>Writing about your own app is only useful if you are honest about the gaps.</p><ul><li>There is no formal accessibility standard for MailVault yet. There is a lot of accessibility work (focus trapping in dialogs, labelled controls, visible focus rings, reduced motion) but nothing measured against a written target.</li><li>No right-to-left language ships yet, so Arabic and Hebrew layouts are untested.</li><li>Mock mail servers are not Gmail. Real providers have quirks no mock captures, and OAuth sign-in is still verified by hand before releases.</li></ul><h3>The checklist</h3><p>If you want the short version:</p><ol><li>Write product beliefs specific enough to lose an argument.</li><li>Make each colour mean one thing, and derive it from one function.</li><li>Use motion only to show that something changed.</li><li>Design offline, undo, setup and errors as carefully as the happy path.</li><li>Ship English plus the big 8, let the build enforce translation quality, and capture screenshots and videos in every language.</li><li>Write the FAQ from real questions, answer the awkward ones, and date every answer.</li><li>Make privacy a property of the architecture.</li><li>Build fake versions of your backends and test against them.</li><li>Automate releases and updates so small fixes are free.</li><li>Test your website like you test your app.</li></ol><p>None of this is glamorous. Most of it will never appear in a screenshot. But it is the difference between an app people try and an app people trust with something they cannot replace.</p><p>The source code is on <a href="https://github.com/GraphicMeat/mail-vault-app">GitHub</a>. If you build apps too, I would love to hear which of these habits you already follow and which ones you think I have wrong.</p><p>👉 Try it: <a href="https://mailvaultapp.com/">mailvaultapp.com</a></p><p>👉 <a href="https://mailvaultapp.com/demo/?lang=en">Live browser demo</a>, if you want to look before downloading</p><p>👉 Be sure to clap and follow the writer 👏</p><p>👉 Follow me: <a href="https://medium.com/%40graphicMeat">Medium</a></p><p>👉 Follow me: <a href="https://x.com/GraphicMeat">X</a></p><p>👉 Homebase: <a href="https://graphicmeat.com/">graphicmeat.com</a></p><p>👉 Best photo book app: <a href="https://graphicmeat.com/photobooks">graphicmeat.com/photobooks</a></p><p>👉 macOS notes and todos: <a href="https://graphicmeat.com/meatpad">graphicmeat.com/meatpad</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11d0c547768f" width="1" height="1" alt=""><hr><p><a href="https://dispatch.jsipe.com/what-makes-an-app-great-is-mostly-invisible-11d0c547768f">What makes an app great is mostly invisible</a> was originally published in <a href="https://dispatch.jsipe.com/">Dispatch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Email App Is Talking About You. Here Is How to Pick One That Doesn’t.]]></title>
            <link>https://dispatch.jsipe.com/your-email-app-is-talking-about-you-here-is-how-to-pick-one-that-doesnt-3a97b8eb094c?source=rss-7ab5ca9bde8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a97b8eb094c</guid>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Rokas Ambrazevicius]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 00:25:05 GMT</pubDate>
            <atom:updated>2026-11-13T00:25:05.734Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Seven privacy features I now treat as non-negotiable in a desktop mail client, and how to check each one yourself.</em></p><p>Open a newsletter and, in the half-second before you read the first line, a tiny invisible image has already phoned home. The sender now knows you opened it, at what time, and roughly from where. Your mail app did that for them.</p><p>Most email apps market themselves as “secure” or “private.” Very few let you verify it. So instead of trusting the label, I started asking every app the same four questions:</p><ul><li><strong>Where does my mail actually live?</strong> On my disk, or also on the app maker’s servers?</li><li><strong>Who runs my searches?</strong> My computer, or a cloud service that sees every query?</li><li><strong>What does an opened message leak?</strong> Tracking pixels and remote images report back to senders.</li><li><strong>What else does the app send home?</strong> Telemetry and analytics travel even when your mail doesn’t.</li></ul><p>If the honest answer to all four is “my computer” and “nothing I didn’t choose,” the app is private in a way you can prove. Below is the checklist I use, with screenshots from MailVault, the desktop client I build, because it was designed around exactly these questions.</p><h3>1. No account with the app maker, and mail kept on your own disk</h3><p>The simplest privacy guarantee is the one where a company never touches your data in the first place.</p><p>MailVault has no account and no mail server of its own. You sign in with Gmail, Outlook.com, iCloud or any IMAP provider, and the app stores a copy of every message on your computer as an ordinary .eml file in a Maildir folder. Nothing passes through MailVault&#39;s servers. If you ever leave, the files open in any other mail app.</p><p>Passwords and sign-in tokens go to the operating system’s own vault: macOS Keychain, Windows Credential Manager or Linux Secret Service. On macOS, the app runs sandboxed.</p><h3>2. Tracking pixels caught in the act</h3><p>This is the feature that changed how I read email.</p><p>A huge share of commercial mail, and plenty of “personal” mail sent through sales tools, contains a one-pixel image. Loading it tells the sender you opened the message, when, and approximately where. MailVault detects those pixels on every message and labels the tracker right on the row, free for everyone. With Premium, it strips them out of the HTML before the message even renders, so the sender learns nothing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FmH4L9N-UGtq3qBm3TuHQ.png" /><figcaption>The before-and-after: one beacon loading, one beacon removed before render.</figcaption></figure><p>Remote images and other outside content also stay off until you click <strong>Load external content</strong> for that specific message.</p><h3>3. Search that never leaves your machine</h3><p>People underestimate how revealing search is. A list of your queries says more about you than almost any single email: who you’re worried about, what you’re negotiating, what you’re trying to find again.</p><p>MailVault indexes your mail on your own computer and answers every search there. There is no search server in the loop, and saved mail stays searchable with Wi-Fi off. You can still narrow by sender, date or folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*axVBXHF_yNdMLTVfjyu5Rg.png" /><figcaption>Search results come from the vault on the same computer, online or offline.</figcaption></figure><h3>4. Phishing warnings before you click</h3><p>Privacy isn’t only about what the app sends. It’s also about not giving your credentials to someone pretending to be your bank.</p><p>Every message shows whether it passed SPF, DKIM and DMARC, the checks that prove mail really came from the domain it claims. And when a trustworthy-looking sender name hides a completely different address, the app calls it out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrW1u3Pea0OkK7e2ozfZvg.png" /><figcaption>The display name says one thing. The actual sender says another.</figcaption></figure><p>Links get the same scrutiny. Phishing emails love to show you one URL and send you to another. MailVault compares the visible text with the real destination and warns you before your browser opens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YraAVJGDeA1N13jPcEcZSg.png" /><figcaption>What the link says vs. where it actually goes.</figcaption></figure><h3>5. Proof instead of promises: a list of every connection</h3><p>“We respect your privacy” is a sentence. A connection log is evidence.</p><p>MailVault’s Network Activity view lists every server the app and its background helper have contacted, why, and how much data went each way, newest first. The log itself stays on your computer. There’s no telemetry setting to hunt for, because there’s no telemetry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pT68eUa8x0r5V8UUayierQ.png" /><figcaption>Every host, every byte, and the countries they’re in.</figcaption></figure><h3>6. Privacy from the person next to you</h3><p>Not every threat is a server. Sometimes it’s a screen share, a conference call, or a stranger on the train reading over your shoulder.</p><p>Privacy mode (a Premium feature) masks names, email addresses, phone numbers and postal addresses across the whole app with one click on the shield icon, or Cmd/Ctrl + Shift + P. Exports have a matching “Redact sensitive info” option for images and HTML.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qM3t_htvn_OBeKQkLUhw0w.png" /><figcaption>Names and addresses blurred across the app, one click to toggle.</figcaption></figure><h3>7. AI help that can stay offline</h3><p>AI writing tools usually mean uploading your conversations to someone else’s model. MailVault lets you choose: Apple Intelligence, a downloaded model, or a compatible local endpoint like Ollama. Gmail messages are only ever handed to on-device providers.</p><h3>What no email app can do for you</h3><p>To be honest about the limits: an app can’t make your provider forget the mail it already stores. Gmail, Outlook and iCloud still deliver and keep your messages, and the people you write to keep their copies. A local client changes where <em>your</em> copy lives and what <em>your reading</em> reveals. If you need end-to-end encryption, you still need an encrypted service.</p><p>And local doesn’t automatically mean encrypted. Turn on disk encryption (FileVault on Mac, BitLocker on Windows), use a strong login, and keep a separate backup on a drive you control. If your mail folder lives inside a cloud-synced directory, that cloud is now part of your setup.</p><h3>The 30-second checklist</h3><p>Ask any email app:</p><ol><li>Do I need an account with <em>you</em>, or just my provider?</li><li>Where are my messages physically stored?</li><li>Where does search run?</li><li>Are tracking pixels blocked?</li><li>Is remote content loaded automatically?</li><li>Do you send telemetry, and can I see every connection?</li><li>Where are my passwords kept?</li></ol><p>MailVault answers: no account, your disk, your computer, yes, no, no and yes, the OS keychain. It’s free on macOS, Windows and Linux with local storage, on-device search, tracker detection and phishing checks included. Premium adds tracker removal, privacy mode and automation.</p><p>The fastest test is the one I did: connect an account, open a newsletter, and watch the tracker get named.</p><p><em>Originally published on the </em><a href="https://mailvaultapp.com/blog/best-private-email-app.html"><em>MailVault blog</em></a><em>.</em></p><p>👉 Try it: <a href="https://mailvaultapp.com/">mailvaultapp.com</a></p><p>👉 <a href="https://mailvaultapp.com/demo/?lang=en">Live browser demo</a>, if you want to look before downloading</p><p>👉 Be sure to clap and follow the writer 👏</p><p>👉 Follow me: <a href="https://medium.com/@graphicMeat">Medium</a></p><p>👉 Follow me: <a href="https://x.com/GraphicMeat">X</a></p><p>👉 Homebase: <a href="https://graphicmeat.com/">graphicmeat.com</a></p><p>👉 Best photo book app: <a href="https://graphicmeat.com/photobooks">graphicmeat.com/photobooks</a></p><p>👉 macOS notes and todos: <a href="https://graphicmeat.com/meatpad">graphicmeat.com/meatpad</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a97b8eb094c" width="1" height="1" alt=""><hr><p><a href="https://dispatch.jsipe.com/your-email-app-is-talking-about-you-here-is-how-to-pick-one-that-doesnt-3a97b8eb094c">Your Email App Is Talking About You. Here Is How to Pick One That Doesn’t.</a> was originally published in <a href="https://dispatch.jsipe.com/">Dispatch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Email Client Is the One That Still Has Your Email in Ten Years]]></title>
            <link>https://dispatch.jsipe.com/the-best-email-client-is-the-one-that-still-has-your-email-in-ten-years-5329a4df2200?source=rss-7ab5ca9bde8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5329a4df2200</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Rokas Ambrazevicius]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 09:44:41 GMT</pubDate>
            <atom:updated>2026-11-06T17:01:22.751Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Apple Mail, Outlook, Thunderbird, eM Client, Mailbird, Spark, Superhuman and MailVault, compared on the one question most reviews skip.</em></p><p><em>Disclosure: I make MailVault, so I have a stake in the answer. I picked the criterion below because I think it matters most, and I tried to be fair to every client on it. Competitor details come from each vendor’s own documentation, last checked in October 2026. Check the current pages before you decide.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vU8YgC__qFSujBqPH6R5OA.png" /></figure><p>Most email client reviews score the same things: speed, design, shortcuts, AI features, price. Fair enough. You open your client fifty times a day.</p><p>But almost none of them ask what happens to your mail when the server stops holding it.</p><p>That is not hypothetical. Gmail and Outlook.com mailboxes fill up and ask you to pay. Employers close accounts when you leave. Providers shut down, change terms, or expire old messages. And nearly every mainstream client is a mirror: it shows you what the server has, caches some of it for speed, and quietly forgets the rest when the server does.</p><p>So here is the test I use. Four questions:</p><ol><li>Where does my mail live? On the server, or as files on my own disk?</li><li>In what format? Can I open it without the app that wrote it?</li><li>Can I delete from the server safely? Is there a verified local copy first, and can I see it?</li><li>Is a company in the middle? A sync service, an account, an AI that reads my mail in someone’s cloud?</li></ol><p>Plus the question every review asks: is it actually pleasant to use every day?</p><h3>Apple Mail</h3><p>The default on every Mac, and a genuinely good one. iCloud sync is seamless, Spotlight indexes your mail, and Handoff carries a draft to your iPhone. If your mailbox is small and you never plan to leave your provider, you may never need anything else.</p><p>Where it falls short on the test: it stores mail in its own internal format (.emlx files plus a database) that other apps do not read directly, and it has no workflow for &quot;keep a copy, then clear the server.&quot;</p><p>Best for: people deep in the Apple ecosystem who treat the server as the archive.</p><h3>Microsoft Outlook</h3><p>If your job runs on Microsoft 365, the calendar and shared-mailbox integration is the point, and it is hard to beat. If your organization hands you Outlook, you probably already have the right daily tool.</p><p>For keeping mail, the details matter. Microsoft’s own guidance says PST export in new Outlook for Windows lives under Settings, Files, Export, while importing a PST into a mailbox still needs classic Outlook. Which Outlook you run changes your recovery plan.</p><p>Best for: Microsoft-centred workplaces.</p><h3>Thunderbird</h3><p>Twenty-plus years old, extensible, with a calendar and a large add-on ecosystem. For a free, full-featured desktop client it is still a standard answer, and it keeps mail locally.</p><p>On the test it does well on question 1 and mixed on question 2: mail lives in mbox, one big file per folder. Readable, but a damaged file can take a whole folder with it, and there is no built-in “archive locally, then delete from the server” flow. You do the careful part yourself.</p><p>Best for: people who want a customizable, no-cost, do-everything client and are comfortable managing their own archive.</p><h3>eM Client</h3><p>A tidy workspace for Windows and Mac with calendar, tasks, notes and translation built in. Worth a look if those sit next to your inbox all day. Read the licence, though: the free tier is limited to two accounts and personal, non-commercial use.</p><p>Best for: people who want mail, calendar and tasks in one conventional app.</p><h3>Mailbird</h3><p>The pitch is one clean inbox for several accounts. The free plan is limited to a single account per device, so if multiple accounts are the reason you want it, you are evaluating the paid plan.</p><p>Best for: multi-account juggling on Windows or Mac, with a budget for it.</p><h3>Spark</h3><p>Spark is built around attention: Smart Inbox, priority senders, Set Aside, Send Later. Its AI tools draft, proofread and summarize. AI usage has quotas, and paid plans are priced per user.</p><p>Best for: people who drown in newsletters and notifications and want the client to triage.</p><h3>Superhuman</h3><p>Speed and AI for teams that live in Gmail or Outlook: Split Inbox, reminders, auto drafts. It is also the most expensive client here, with plans priced per user per month. Cloud AI means you should read the privacy terms for your plan before pointing it at sensitive mail.</p><p>Best for: customer-facing teams for whom reply speed is revenue.</p><h3>MailVault</h3><p>Here is the part where I tell you why I built it, and why it wins the test above.</p><p>MailVault is a full email client, with threading, search, compose, a unified inbox and a chat view, but it is built the other way round from a mirror. Every message you keep is written to your own disk as a plain .eml file in a Maildir folder tree. One file per message. Readable by Thunderbird, Apple Mail, or grep. When the provider deletes, expires or charges for it, your copy does not care.</p><p>Against the four questions:</p><ul><li>Where does my mail live? On your disk, and every row shows whether a message is on the server, in the vault, in both, or only local because the server no longer has it. You never have to guess.</li><li>What format? Standard RFC 5322 .eml in Maildir, plus MBOX export. No proprietary database standing between you and your mail. Lose the app, keep the mail.</li><li>Safe server cleanup? This is the core idea. Archive first, then delete, in one operation, or thousands at once by year, with progress, cancel and crash-safe recovery. An optional step also copies each message to a backup drive and checks both copies before anything leaves the server.</li><li>Anyone in the middle? No account to create, no sync service, no telemetry. Credentials stay in your OS keychain. AI writing help can run on your own machine.</li></ul><p>And the daily-use question: offline full-text search over everything on disk (50,000 messages searched in under 15 ms in our test), threaded conversations, undo send, templates, Gmail and Microsoft 365 sign-in through OAuth, plus any IMAP server. It is a Rust and Tauri app rather than a heavy web wrapper, and it runs on macOS, Windows and Linux.</p><h3>What MailVault is not</h3><p>I would rather you hear it from me:</p><ul><li>It is a desktop app. There is no phone app.</li><li>It does not try to be a calendar and task workspace. If Outlook or eM Client’s surrounding tools are what you want, use those, and use MailVault to keep the mail.</li><li>No big add-on ecosystem like Thunderbird’s.</li><li>Some automation is paid. The client, search and manual archiving are free, with no storage quota from us. Scheduled backups, one-step archive-and-delete, Time Capsule snapshots and a few other things are Premium. Local data is never held hostage by the paywall, and a lapsed subscription never deletes anything.</li></ul><h3>The verdict</h3><p>If your question is “which client has the best calendar,” the answer depends on your job. If it is “which one triages my inbox best,” try Spark or Superhuman. If it is “which one comes free with my Mac,” that is Apple Mail.</p><p>But if your question is “which client will still have my email when my provider, my employer or my subscription is gone,” there is one answer, and it is the one built around that question. That is why I rank MailVault first.</p><p>You do not have to trade your current client away to find out. MailVault reads your existing accounts, so you can run it beside whatever you use now, archive a year of old mail, and open the resulting folder in another app to see that it is really yours.</p><p>👉 Try it: <a href="https://mailvaultapp.com/">mailvaultapp.com</a></p><p>👉 <a href="https://mailvaultapp.com/demo/">Live browser demo</a> — f you want to look before downloading</p><p>👉 Be sure to <strong>clap</strong> and <strong>follow</strong> the writer 👏<strong>️️</strong></p><p>👉 Follow me: <a href="https://medium.com/@graphicMeat"><strong>Medium</strong></a></p><p>👉 Follow me: <a href="https://x.com/GraphicMeat">X</a></p><p>👉 Homebase: <a href="https://graphicmeat.com/">graphicmeat.com</a></p><p>👉 Best photo book app: <a href="https://graphicmeat.com/photobooks">graphicmeat.com/photobooks</a></p><p>👉 macOS notes and todos: <a href="https://graphicmeat.com/meatpad">graphicmeat.com/meatpad</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5329a4df2200" width="1" height="1" alt=""><hr><p><a href="https://dispatch.jsipe.com/the-best-email-client-is-the-one-that-still-has-your-email-in-ten-years-5329a4df2200">The Best Email Client Is the One That Still Has Your Email in Ten Years</a> was originally published in <a href="https://dispatch.jsipe.com/">Dispatch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>