Launch blockers fixed in README and landing copy
xpenser fixed launch blockers in README and landing-page copy so public evaluation starts with clearer product framing.
The public launch surfaces became clearer for people arriving from GitHub or search.
This release came from PR #31 and is now part of the xpenser release archive. It gives people evaluating an open-source expense tracker a clearer view of how the product has improved over time.
What changed
- Fixed README issues that blocked launch readiness.
- Improved landing-page copy and product framing.
- Kept the messaging aligned with expense tracking workflows.
Why it matters
A strong README and landing page help users understand what the app does before they inspect the code or deploy it.
Where it fits
This release prepared xpenser for broader open-source discovery.
For a broader product overview, start with the xpenser home page. Developers can also explore the personal finance API and MCP tools, while self-hosters can review the self-hosted personal finance tracker page.