<?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"><channel><title><![CDATA[Welcome to the Earmarkr]]></title><description><![CDATA[<p dir="auto">Thanks for trying Earmarkr. You're among the first people using it, which means you'll see rough edges before anyone else — and your reports are what get them fixed.</p>
<p dir="auto">Earmarkr is zero-based budgeting that shows its math. Every headline number, including Ready to Assign and the credit-card reserve, can be traced back to the transactions behind it. If a number ever looks wrong, that's exactly the kind of thing we want to hear about.</p>
<p dir="auto"><a href="https://earmarkr.app" rel="nofollow ugc">Open Earmarkr</a></p>
<hr />
<h2>Where to see updates</h2>
<p dir="auto">There's a What's new page in the app — look for it in the left-hand menu. It lists every change as it ships, with step-by-step instructions whenever something moves on screen. You'll see a small marker next to it when there's something you haven't read, and a banner at the top of the page after a release.</p>
<p dir="auto">That's the fastest way to find out what changed; these emails will be occasional summaries.</p>
<hr />
<h2>Found a bug? Have a question?</h2>
<p dir="auto">Use the Get help form inside the app. It's the best channel because your message reaches us with the context we need to reproduce the problem.</p>
<ol>
<li>Click Get help at the bottom of the left-hand menu.</li>
<li>Write what happened.</li>
<li>Send. We reply by email, so just hit reply and we can keep talking there.</li>
</ol>
<p dir="auto">What helps most in a bug report:<br />
•	What you were doing, and what you expected to happen instead<br />
•	The screen you were on<br />
•	If a number looks wrong: the number you saw and the number you expected</p>
<p dir="auto">Please don't include passwords or full account numbers. We never need them, and the form will remind you.</p>
<p dir="auto">Feature ideas and "this was confusing" notes are just as welcome as bugs — the confusing parts are the ones we most need to hear about, and they're the easiest for us to miss.</p>
<p dir="auto">Thanks for testing,<br />
Bradley</p>
]]></description><link>http://community.earmarkr.com/topic/2/welcome-to-the-earmarkr</link><generator>RSS for Node</generator><lastBuildDate>Sat, 29 Aug 2026 22:08:35 GMT</lastBuildDate><atom:link href="http://community.earmarkr.com/topic/2.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 29 Aug 2026 20:03:23 GMT</pubDate><ttl>60</ttl></channel></rss>