What’s new in v1.5.11
v1.5.11 connects Money actions to the journey and makes follow-through clearer.
- Money action detail panels use a primary action bar with “Worth pursuing”, “Not for me”, and “Later”.
- Bookmarked actions move into a follow-through state with “Mark as done”, “Snooze”, and “Remove”.
- Distinct Money action responses contribute to journey progress, so repeated interaction with the same card does not satisfy progress requirements by itself.
- Coach and journey prompts can bring users back to bookmarked Money actions when follow-through is needed.
What’s new in v1.5.10
v1.5.10 makes Money actions more specific, better researched, and easier to act on.
- Action cards focus on one clear point, with named counterparties or categories where available.
- Recommendations show quantified impact when the data supports it, usually as an estimated range rather than a guaranteed saving.
- Research-enriched actions can include named alternatives, pricing or comparison context, estimated savings, and source links.
- Detail panels are structured around current cost, alternatives or findings, estimated saving, how to act, and source context.
- Money and Growth recommendations are separated more clearly: cost-saving and money-protection items stay in Money, while revenue-growth ideas belong in Growth.
What’s new in v1.5.9
v1.5.9 makes Money recommendations more practical and better qualified.
- Recommendations are more focused, with clearer action framing, named specifics, quantified impact where supported, and concrete next steps.
- Some recommendations can ask targeted follow-up questions when transaction data alone cannot confirm eligibility or usage.
- Subscription value review helps users assess recurring software and service spend when usage is unclear from bank data alone.
- New transaction-pattern recommendations can surface conservative idle-cash opportunities, late or deteriorating expected payments, and debt cost review opportunities.
- Recommendations that rely on inferred timing, rates, or balances include caveats so users understand the basis for the suggestion.
What’s new in v1.5.8
v1.5.8 gives users more control over Money insights and improves first-load reliability after onboarding.
- Users can snooze Money insights when an action is relevant but not right for today.
- Snoozed items are retained across refresh cycles and can resurface later through the prioritisation flow.
- A dedicated snoozed-items view lets users review and manage recommendations they chose to revisit.
- Newly onboarded users are less likely to see unavailable Money metrics or actions when fresh metrics already exist.
- Optional dismissal reasoning can be captured when users dismiss an insight, improving the feedback loop for future recommendations.
- Scheme-type insights can be surfaced when research into grants, tax reliefs, public finance programmes, and similar SME support opportunities identifies relevant support for the business.
Functional flow
1. Load the latest available Money context
1. Load the latest available Money context
Let the SDK present the latest available Money context on first load. Preserve explicit dated flows only when the user has intentionally arrived from a dated context.
2. Render summary metrics first
2. Render summary metrics first
Load top-level metrics before deeper drill-downs so users get immediate financial context.
3. Present the action queue
3. Present the action queue
Show prioritised recommendations and preserve stable status semantics across refresh cycles.
4. Resolve recommendations that need more context
4. Resolve recommendations that need more context
Ask only for the extra context needed to decide whether a recommendation should be shown as a confirmed action.
5. Persist user intent
5. Persist user intent
Apply pursue, snooze, dismiss, remove, or completion transitions only after server confirmation and keep local UI state synchronised.
6. Resurface snoozed items when relevant
6. Resurface snoozed items when relevant
Treat snooze as a positive “later” signal rather than a permanent dismissal, and make snoozed items manageable from a dedicated view.
Integration considerations
| Area | What to preserve | Why it matters |
|---|---|---|
| Initial Money context | Present the latest available Money context on first load | Reduces stale or missing first-load data after onboarding |
| Explicit dates | Preserve explicit dated contexts only when intentionally supplied | Keeps drill-downs accurate without hiding invalid date requests |
| Action ordering | Stable priority and status semantics | Keeps user focus on highest-impact items |
| Extra context questions | Preserve question, answer, and resolution state | Prevents recommendations from being treated as confirmed before the user provides needed context |
| Snooze lifecycle | Persist snoozed items outside the normal feed refresh | Prevents useful recommendations from being lost |
| Journey progress | Count distinct confirmed action responses and completions | Keeps progress aligned to real user follow-through |
| Update confirmation | Server-acknowledged status changes | Avoids drift between UI and backend state |
Reflect status changes only after confirmation, or include a safe rollback path when optimistic updates are required.