Dev Log: 2026-07-04

TL;DR

• Two Laravel backends started serving Flutter apps on the same day — an events platform (auth, orders, offline check-in) and a helpdesk product (ops mode for agents).


• 
  , the Next.js marketing site, dropped à-la-carte feature pricing for three plans and gained a plan comparison matrix. Everything renders from a single plans.ts — the matrix, the pricing cards, the enterprise page — so the marketing site can't drift from what's actually sold. A pricing page is a contract too; it deserves a single source of truth as much as your API does.
  
  
  

  
  
  
  Hardening pass
  

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

  Change	Why
  Bulk email blasts isolated to their own queue	one big send must never delay a payment webhook
  Reconciliation command for stuck pending orders	webhooks fail silently; polling the gateway is the safety net
  maatwebsite/excel → spatie/simple-excel for exports	streams rows instead of building sheets in memory, smaller dependency surface
  Publish readiness enforced on every transition path	one invariant in one place, not per-controller checks

  
  
  

  
  
  
  Takeaway
  

  
  
  

  Everything today was the same disease in different organs: drift from a single source of truth. plans.ts on the site, Resources in the API, one readiness gate in the backend. Same medicine everywhere.

  Vollständiger Original-Bericht

  Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

  ↗ Original-Artikel auf dev.to lesen