<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: william lao</title>
    <description>The latest articles on DEV Community by william lao (@william_lao_0c017fe1ee6cb).</description>
    <link>https://dev.to/william_lao_0c017fe1ee6cb</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4156747%2F207c4733-c1d8-44f7-a339-2be7929d1980.jpg</url>
      <title>DEV Community: william lao</title>
      <link>https://dev.to/william_lao_0c017fe1ee6cb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/william_lao_0c017fe1ee6cb"/>
    <language>en</language>
    <item>
      <title>supa_audit is archived. Here's a maintained audit log for Supabase.</title>
      <dc:creator>william lao</dc:creator>
      <pubDate>Sat, 14 Nov 2026 08:44:13 +0000</pubDate>
      <link>https://dev.to/william_lao_0c017fe1ee6cb/supaaudit-is-archived-heres-a-maintained-audit-log-for-supabase-42bc</link>
      <guid>https://dev.to/william_lao_0c017fe1ee6cb/supaaudit-is-archived-heres-a-maintained-audit-log-for-supabase-42bc</guid>
      <description>&lt;h2&gt;
  
  
  "Who deleted this row?"
&lt;/h2&gt;

&lt;p&gt;If you run a Supabase app, you will hear this question. A customer says their order vanished. A teammate swears they didn't touch the pricing table. You open the Dashboard and find… nothing. There is no record of who changed what.&lt;/p&gt;

&lt;p&gt;Supabase has three kinds of "audit" built in, and none of them answers the question:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;pgAudit&lt;/strong&gt; logs &lt;em&gt;which SQL ran&lt;/em&gt;. It does not store the old and new values of the row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Auth Audit Logs&lt;/strong&gt; record logins and sign-ups. Not data changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Platform Audit Logs&lt;/strong&gt; record Dashboard actions. Not app data changes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tool that used to fill this gap was &lt;code&gt;supa_audit&lt;/code&gt;, Supabase's own trigger-based audit extension. As of November 2026, its GitHub page says &lt;strong&gt;Public archive&lt;/strong&gt; — 670 stars, 45 forks, no maintenance. The README also warns against enabling it on tables above ~3k ops/sec, and it never had an actor field, restore, retention, or a UI.&lt;/p&gt;

&lt;p&gt;So I built the smallest correct replacement, and put it on GitHub for free.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Lite version (free, MIT)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Repo:&lt;/strong&gt; &lt;a href="https://github.com/liulewis/supabase-audit-log-lite" rel="noopener noreferrer"&gt;https://github.com/liulewis/supabase-audit-log-lite&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It is a trigger-based audit log, about 150 lines of SQL:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;audit.audit_log&lt;/code&gt; — one row per INSERT / UPDATE / DELETE, with old/new values as JSONB, the acting user's &lt;code&gt;auth.uid()&lt;/code&gt;, and a timestamp.&lt;/li&gt;
&lt;li&gt;It lives in its own &lt;code&gt;audit&lt;/code&gt; schema, so the Data API never exposes it.&lt;/li&gt;
&lt;li&gt;RLS is on, authenticated users get &lt;code&gt;SELECT&lt;/code&gt; only. There is deliberately no write policy, so the log is append-only through the API.&lt;/li&gt;
&lt;li&gt;Two query views: history of one row, and activity of one person.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Setup is three steps in the SQL Editor:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- 1. run sql/01_audit_schema.sql, then sql/02_views.sql&lt;/span&gt;
&lt;span class="c1"&gt;-- 2. turn auditing on for the tables you care about&lt;/span&gt;
&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;audit&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;enable_tracking&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'public.customers'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;audit&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;enable_tracking&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'public.orders'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;-- 3. "who deleted this row?"&lt;/span&gt;
&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;changed_at&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;operation&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;actor_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;old_data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;new_data&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;audit&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;v_row_history&lt;/span&gt;
&lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;table_name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'customers'&lt;/span&gt; &lt;span class="k"&gt;and&lt;/span&gt; &lt;span class="n"&gt;record_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'42'&lt;/span&gt;
&lt;span class="k"&gt;order&lt;/span&gt; &lt;span class="k"&gt;by&lt;/span&gt; &lt;span class="n"&gt;changed_at&lt;/span&gt; &lt;span class="k"&gt;desc&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is a demo script (&lt;code&gt;sql/03_demo.sql&lt;/code&gt;) that inserts, updates and deletes a throwaway row so you can see the three audit entries appear.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Lite honestly does NOT do
&lt;/h2&gt;

&lt;p&gt;I would rather list the gaps than have you discover them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No field-level diff.&lt;/strong&gt; Lite stores the full old/new row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No single-row restore.&lt;/strong&gt; Restoring a deleted row correctly — foreign keys, unique keys, concurrency — is the hardest part and is not in Lite.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No retention management.&lt;/strong&gt; The log only grows. Watch your 500 MB free-tier database.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No tamper-resistance depth.&lt;/strong&gt; Lite relies on RLS + no write policy. No &lt;code&gt;BEFORE UPDATE/DELETE&lt;/code&gt; guards, no &lt;code&gt;TRUNCATE&lt;/code&gt; protection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No admin UI.&lt;/strong&gt; You query with SQL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No actor for background writes.&lt;/strong&gt; &lt;code&gt;actor_id&lt;/code&gt; is &lt;code&gt;auth.uid()&lt;/code&gt; for changes through PostgREST. Writes from &lt;code&gt;service_role&lt;/code&gt;, Edge Functions, cron or direct SQL record &lt;code&gt;NULL&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TRUNCATE is not captured.&lt;/strong&gt; Row-level triggers don't fire on it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The full kit (presale)
&lt;/h2&gt;

&lt;p&gt;I am building the full version as a one-time template — diff views, single-row restore, retention governance, tamper-resistance depth, the admin UI, and actor context for background jobs. Presale is &lt;strong&gt;$29&lt;/strong&gt; (launch price, then $39):&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Presale:&lt;/strong&gt; &lt;a href="https://franklinlewis7.gumroad.com/l/audit-log-kit" rel="noopener noreferrer"&gt;https://franklinlewis7.gumroad.com/l/audit-log-kit&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I need from you
&lt;/h2&gt;

&lt;p&gt;This is a validation post as much as a launch post. If you have ever needed an audit trail on Supabase, tell me:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What was the scenario — compliance, customer support, debugging, or showing history to your own users?&lt;/li&gt;
&lt;li&gt;How many writes per second do your audited tables see?&lt;/li&gt;
&lt;li&gt;Would you pay $29 once for diff + restore + retention + UI, or is the free Lite enough?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Try the Lite, star the repo if it helps, and leave a comment. If enough people need the full version, I will build it. If not, the Lite stays free and I will say so.&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>postgres</category>
      <category>database</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Supabase Free Has No Backups — Here's the Free Way to Add Them</title>
      <dc:creator>william lao</dc:creator>
      <pubDate>Fri, 13 Nov 2026 15:24:17 +0000</pubDate>
      <link>https://dev.to/william_lao_0c017fe1ee6cb/supabase-free-has-no-backups-heres-the-free-way-to-add-them-2f9d</link>
      <guid>https://dev.to/william_lao_0c017fe1ee6cb/supabase-free-has-no-backups-heres-the-free-way-to-add-them-2f9d</guid>
      <description>&lt;p&gt;If your side project lives on a Supabase Free project, here is the uncomfortable fact: &lt;strong&gt;there are no automated backups.&lt;/strong&gt; None. If you drop the wrong table tonight, there is no restore button waiting for you in the dashboard tomorrow. The fix Supabase sells you is the Pro plan at $25/month — mostly, for a lot of us, just to get daily backups retained for 7 days.&lt;/p&gt;

&lt;p&gt;The DIY fix looks trivial: run &lt;code&gt;pg_dump&lt;/code&gt; from a GitHub Actions cron job, upload the result somewhere cheap. It &lt;em&gt;is&lt;/em&gt; about 30 lines of YAML. But those 30 lines hide five traps, and every one of them fails &lt;em&gt;quietly&lt;/em&gt; — you find out your backup doesn't work on the one day you actually need it.&lt;/p&gt;

&lt;p&gt;I hit all five while building my own setup. Here they are, in the order you'll meet them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trap 1: The connection string Supabase shows you first breaks &lt;code&gt;pg_dump&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;In the dashboard (Settings → Database → Connection string), the prominent option is the &lt;strong&gt;transaction pooler on port 6543&lt;/strong&gt;. &lt;code&gt;pg_dump&lt;/code&gt; cannot run through it — it needs a real session, and through the transaction pooler the dump fails or hangs with errors that point nowhere near the real cause.&lt;/p&gt;

&lt;p&gt;Use the &lt;strong&gt;session pooler&lt;/strong&gt; instead: port &lt;strong&gt;5432&lt;/strong&gt;, host &lt;code&gt;aws-0-&amp;lt;region&amp;gt;.pooler.supabase.com&lt;/code&gt;. Same panel, different tab. This one line is the difference between a working backup and a week of debugging.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trap 2: The "direct connection" is IPv6-only, and GitHub runners are not
&lt;/h2&gt;

&lt;p&gt;The other string in the dashboard, &lt;code&gt;db.&amp;lt;your-ref&amp;gt;.supabase.co&lt;/code&gt;, looks like the obvious choice for a dump. On the Free plan that host is &lt;strong&gt;IPv6-only&lt;/strong&gt;. GitHub-hosted runners are IPv4-only. The result is a connection error that looks exactly like a firewall or credentials problem — it is neither. (This is also why the same string works fine from your laptop on an IPv6 network and fails in CI.)&lt;/p&gt;

&lt;p&gt;Session pooler, port 5432. Again. Traps 1 and 2 are the same lesson: the two connection strings Supabase offers first are the two that don't work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trap 3: Your &lt;code&gt;pg_dump&lt;/code&gt; is older than the server
&lt;/h2&gt;

&lt;p&gt;Supabase runs &lt;strong&gt;PostgreSQL 17&lt;/strong&gt;. The &lt;code&gt;ubuntu-latest&lt;/code&gt; GitHub runner ships a PostgreSQL client that tops out at &lt;strong&gt;16&lt;/strong&gt; — and &lt;code&gt;pg_dump&lt;/code&gt; flatly refuses to dump a server newer than itself:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;pg_dump: error: server version mismatch
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;postgresql-client-17&lt;/code&gt; isn't in Ubuntu's default repos, so the fix is to add PostgreSQL's official PGDG apt repository first, then install the 17 client. Three extra lines in the workflow — once you know you need them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Trap 4: GitHub silently disables scheduled workflows in public repos
&lt;/h2&gt;

&lt;p&gt;This is the nastiest one because nothing ever errors. If your backup repo is &lt;strong&gt;public&lt;/strong&gt; and sees no activity for 60 days, GitHub &lt;strong&gt;disables scheduled workflows&lt;/strong&gt; — quietly. No failed run, no red X, just backups that stop happening while you believe you're covered.&lt;/p&gt;

&lt;p&gt;Put the backup workflow in a &lt;strong&gt;private repo&lt;/strong&gt;. (You want this anyway: the repo holds your database connection string as a secret and your backup config.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Trap 5: Daily backups blow straight through the Free egress cap
&lt;/h2&gt;

&lt;p&gt;Every dump pulls your entire database &lt;em&gt;out&lt;/em&gt; of Supabase, and the Free plan includes &lt;strong&gt;5 GB/month of egress&lt;/strong&gt;. The math is unforgiving:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;500 MB database, dumped &lt;strong&gt;weekly&lt;/strong&gt; → ~2 GB/month. Fine.&lt;/li&gt;
&lt;li&gt;500 MB database, dumped &lt;strong&gt;daily&lt;/strong&gt; → ~15 GB/month. Over the cap.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Weekly is the sweet spot on Free. And double-check your cron while you're at it: &lt;code&gt;42 3 * * 0&lt;/code&gt; is weekly (Sundays 03:42 UTC); drop the trailing &lt;code&gt;0&lt;/code&gt; and &lt;code&gt;42 3 * * *&lt;/code&gt; quietly becomes &lt;em&gt;daily&lt;/em&gt; — trap 5, self-inflicted.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One honest scope note:&lt;/strong&gt; &lt;code&gt;pg_dump&lt;/code&gt; covers your database, &lt;strong&gt;including &lt;code&gt;auth.users&lt;/code&gt;&lt;/strong&gt; (they live in the database). It does &lt;strong&gt;not&lt;/strong&gt; cover Storage files — those live in S3, not Postgres, and need a separate approach. Anyone who tells you their pg_dump setup protects "everything" hasn't checked.&lt;/p&gt;

&lt;h2&gt;
  
  
  The free version: the smallest thing that actually works
&lt;/h2&gt;

&lt;p&gt;Once you know the five traps, the working minimum fits in one workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;GitHub Actions cron, weekly, in a &lt;strong&gt;private&lt;/strong&gt; repo&lt;/li&gt;
&lt;li&gt;Install &lt;code&gt;postgresql-client-17&lt;/code&gt; from the PGDG repo&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;pg_dump&lt;/code&gt; over the &lt;strong&gt;session pooler (5432)&lt;/strong&gt;, custom format&lt;/li&gt;
&lt;li&gt;Upload to a &lt;strong&gt;Cloudflare R2&lt;/strong&gt; bucket (10 GB free tier, zero egress fees)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I packaged exactly this as a free lite version — script, workflow, and a 10-minute setup guide:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;→ &lt;a href="https://github.com/liulewis/supabase-free-backup-lite" rel="noopener noreferrer"&gt;supabase-free-backup-lite on GitHub&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It is deliberately minimal: the dump is uploaded &lt;strong&gt;unencrypted&lt;/strong&gt;, there is no validation that the dump is restorable, and if a run fails, nobody tells you. For a hobby project, that's a fair trade. For a project with real users, those three gaps are exactly where backups go to die — which is why I built the full kit.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full kit: encryption, proof it restores, and a watchdog
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://franklinlewis7.gumroad.com/l/jispyu" rel="noopener noreferrer"&gt;Supabase Free-Tier Backup Kit&lt;/a&gt; is the same weekly workflow with the failure modes engineered out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GPG AES-256 encryption&lt;/strong&gt; before upload — a leaked R2 credential no longer means a leaked database&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pre-flight validator&lt;/strong&gt; that rejects the 6543 pooler and the IPv6-only host &lt;em&gt;before&lt;/em&gt; the run, with an error that names the actual fix, and checks your &lt;code&gt;pg_dump&lt;/code&gt; version against the server&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validation on every dump&lt;/strong&gt;: SHA-256 checksum plus &lt;code&gt;pg_restore --list&lt;/code&gt;, so a truncated or corrupt dump gets caught the week it's made, not the day you need it&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A restore drill and step-by-step runbook&lt;/strong&gt; (English + Chinese): spin up a throwaway Postgres, restore into it, prove it works — because a backup you have never restored is a hope, not a backup&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Failure alerts&lt;/strong&gt; via webhook (Slack / Discord), a &lt;strong&gt;watchdog&lt;/strong&gt; bonus workflow that notices if the backup job never runs, and a Healthchecks.io heartbeat&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An egress calculator&lt;/strong&gt; for the 5 GB/month cap, and &lt;strong&gt;90-day R2 retention&lt;/strong&gt; rules (server-side, so CI never holds delete permissions)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's &lt;strong&gt;$29 one-time for the first 50 buyers, then $39&lt;/strong&gt; — no subscription, and a &lt;strong&gt;14-day money-back guarantee&lt;/strong&gt;. Current version is v1.0.7. For scale: Pro is $25 &lt;em&gt;every month&lt;/em&gt;. The kit pays for itself in five weeks, and the lite version above stays free forever if money is the blocker.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one-sentence version
&lt;/h2&gt;

&lt;p&gt;Supabase Free gives you a great database and zero safety net; a weekly &lt;code&gt;pg_dump&lt;/code&gt; to R2 closes the hole for $0 — as long as you dodge the pooler, the IPv6 host, the version mismatch, the public-repo kill switch, and the egress cap.&lt;/p&gt;

&lt;p&gt;Start with the &lt;a href="https://github.com/liulewis/supabase-free-backup-lite" rel="noopener noreferrer"&gt;free lite version&lt;/a&gt; today. The worst backup strategy is the one you were meaning to set up next week.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I'm the author of both the lite version and the kit. Everything in the free version is genuinely free and fully functional — the kit exists for the encryption, validation, and restore proof.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>supabase</category>
      <category>postgres</category>
      <category>backup</category>
      <category>githubactions</category>
    </item>
    <item>
      <title>Show Dev: Agricalc — free science-based agriculture calculators as an offline-first PWA</title>
      <dc:creator>william lao</dc:creator>
      <pubDate>Fri, 02 Oct 2026 07:52:02 +0000</pubDate>
      <link>https://dev.to/william_lao_0c017fe1ee6cb/show-dev-agricalc-free-science-based-agriculture-calculators-as-an-offline-first-pwa-ebh</link>
      <guid>https://dev.to/william_lao_0c017fe1ee6cb/show-dev-agricalc-free-science-based-agriculture-calculators-as-an-offline-first-pwa-ebh</guid>
      <description>&lt;p&gt;Hey devs! I want to share a project I built: Agricalc (&lt;a href="https://agricalc.online" rel="noopener noreferrer"&gt;https://agricalc.online&lt;/a&gt;), a free collection of science-based agriculture calculators.&lt;/p&gt;

&lt;p&gt;What it does:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Covers the full farming cycle — planting, fertilization, irrigation, harvest, and marketing&lt;/li&gt;
&lt;li&gt;Every calculator is built on established agricultural formulas and reference data&lt;/li&gt;
&lt;li&gt;Includes a 53-term agricultural glossary (CEC, GDD, evapotranspiration, N-P-K…)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Why a PWA:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Farms often have poor connectivity — the whole thing works offline once loaded&lt;/li&gt;
&lt;li&gt;No registration, no backend account needed&lt;/li&gt;
&lt;li&gt;Multi-language and mobile-friendly, designed to be used in the field on a phone&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Who it's for: farmers, agronomists, agricultural students, and anyone in crop and livestock production.&lt;/p&gt;

&lt;p&gt;GitHub repo: &lt;a href="https://github.com/liulewis/agricalc" rel="noopener noreferrer"&gt;https://github.com/liulewis/agricalc&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd love feedback — especially from anyone with ag experience. Are the formulas matching what you use in practice? What calculators are missing?&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>agriculture</category>
      <category>pwa</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
