Product Roadmap

What is live, what is being tested, and what only happens if Zam! proves useful enough to continue.

Updated June 2026: Zam! is in live beta. The current roadmap reflects completed rebrand, auth, Cloud Sync, CSV import/export, gift-card tracker, privacy disclosure, deployment, and support-documentation work. Continued development depends on real user feedback, whether the app is useful enough to keep entering budgets, and whether Premium support can at least cover infrastructure and continued development time.
Live Beta

Core Product

The working budget app: browser-based budgeting, signed-in Cloud Sync protection, and the core workflows needed to enter, review, import, export, and protect a real budget.

  • Income, expense, savings, debt, emergency fund, Add, Recent, and Calendar workflows
    Live beta
  • Categories with edit mode, drag sorting, up/down controls, and position entry
    Live beta
  • CSV transaction import with mapping, duplicate detection, row selection, raw CSV view, strict validation, and expanded preview
    v1.2 RC complete
  • CSV export with custom file names, date ranges, account/category filters, plain decimal amounts, and stable YYYY-MM-DD dates
    v1.3 RC complete
  • Gift-card payment method, Add More gift-card tracker, balance fields, expiration support, and local merchant metadata cache
    Live beta; isolated from core expense/deposit logic
  • Settings dashboard redesign, accent palette controls, reset-form shortcut, and responsive UI polish
    Live beta
  • Privacy-first Cloud Sync protection with a 5-minute no-account demo
    Live beta
  • Google OAuth and email magic-link sign-in with guarded app routes and clean login redirects
    Live; Apple sign-in paused until demand justifies it
  • Required site-data disclosure, storage-blocked guard, no embedded app trackers, and privacy/legal updates
    Live beta
  • Zam! rebrand, zambudget.com marketing cutover, app.zambudget.com app cutover, SEO audit gate, and support/trust/contact pages
    Live
Active Beta

Reliability, Data Safety, and Conversion

This is the current focus. The app needs to stay trustworthy before larger feature work moves forward.

  • Cloud Sync encrypted sync, version history, and sign-in recovery
    Live beta; recovery-key UX remains a core design focus
  • Import/export hardening, QA stress files, post-import details, and import rollback design
    v1.4 hardening
  • Merchant Recognition Lite for local merchant cleanup suggestions
    v1.5 groundwork; false-positive tuning before Premium promotion
  • Graceful sign-out, rough logout, hard refresh, fresh-session recovery, and trusted-browser behavior
    Active beta QA
  • Premium billing and Stripe upgrade path
    Live beta path; keep testing before wider promotion
  • Manual auth smoke checks and future auth canary monitoring for magic-link health
    Manual checks active; automation planned
  • GitLab, Cloudflare, DNS, deployment, disaster-recovery, and rebuild documentation
    Live docs; keep current as infrastructure changes
  • Beta user feedback: is it useful, stable, and worth paying to keep alive?
    Decision input for continued development
Demand Driven

Deferred Enhancements

These are not the priority until the core product proves retention, reliability, and basic cost recovery.

  • PDF exports and printable reports
    Planned after stability work
  • Full Zam backup export/import, account email change, and account-ownership migration
    Security/recovery backlog
  • Recurring transactions, import reconciliation, and smarter category suggestions
    Demand driven
  • Charts, spending trends, mobile apps, Apple OAuth, bank imports, and AI-powered insights
    Only if beta demand supports the work