Home summaries load faster
We added a faster way to load the Home summary so key totals do less repeat work.
Why it matters: This helps the dashboard feel quicker when people come back to review their money.
Latest changes
A plain-language history of product changes since February 2026, based on the project changelog and implementation dates.
Each note explains what changed and why it matters, without internal issue labels or release jargon.
55 updates
We added a faster way to load the Home summary so key totals do less repeat work.
Why it matters: This helps the dashboard feel quicker when people come back to review their money.
We added CSV and PDF exports for transaction history, with date choices and a privacy note.
Why it matters: This helps users save, print, or share their records when they need a copy.
We improved the budget error path so missing database fields are easier to identify.
Why it matters: This helps keep budget fixes focused when an environment is missing a migration.
We added an Insights view that shows how visible family expenses are split by member.
Why it matters: This helps households see who spent what without changing how transactions are saved.
We added saved schedules for paydays and recurring expenses, with edit and delete controls.
Why it matters: This helps families keep upcoming money events organized across devices.
We moved account and transaction work into Wallet and kept Home focused on the big picture.
Why it matters: This helps users find money details without crowding the main dashboard.
We cleaned up the main dock around Home, Insights, Add, Wallet, and Profile.
Why it matters: This helps users move around the app without guessing where to tap.
We made receipt image links survive saves, edits, sync, and reloads.
Why it matters: This helps users keep proof of purchases attached to the right transaction.
We made the Insights category chart follow the active member and date filters.
Why it matters: This helps users trust that the chart matches the range they are reviewing.
We changed visible money groups to plain labels like Income, Bills, Spending, Goals, and Total Value.
Why it matters: This makes Bunga easier to understand on small screens and for new users.
We simplified the add flow around Income and Expense, quieter recurring controls, and a clearer Add button.
Why it matters: This reduces friction for the most common daily action in Bunga.
We added a larger budget builder for custom category budgets, edits, deletes, and hidden defaults.
Why it matters: This helps households build budgets that match how they actually spend.
We tuned demo transactions, shortened the sandbox title, and made top expenses tappable.
Why it matters: This helps people understand the product faster before adding real data.
We added compact Home insights and linked savings details into the Insights page.
Why it matters: This keeps Home simple while still giving users a path to deeper review.
We prepared the iOS and Android shells for the next TestFlight and Play testing uploads.
Why it matters: This keeps mobile testing aligned with the latest web product changes.
We added a transaction-added sound cue with a fallback tone when no audio file is available.
Why it matters: This makes successful saves easier to notice without staring at the screen.
We changed the public landing page into a focused signup page for iOS and Android beta interest.
Why it matters: This keeps the first step clear while mobile testing is getting started.
We added tap-to-expand bucket cards with matching chart and transaction details.
Why it matters: This helps users see what is inside a spending group without leaving the dashboard.
We added an automatic theme choice that follows the device light or dark setting.
Why it matters: This helps the app feel native without forcing users to pick a theme.
We made cash expenses use the real purchase cost while still supporting cash given and change back.
Why it matters: This matches how people think about paying with cash.
We added custom date ranges and a warning before users lose unsaved transaction work.
Why it matters: This gives users more control while reducing accidental data loss.
We added family review requests and protected active merchant edits from background refreshes.
Why it matters: This helps families coordinate while keeping edits from being overwritten.
We improved transaction card layout, category mapping, custom categories, and save feedback.
Why it matters: This makes transaction review easier on small screens and in busy ledgers.
We improved Android sign-in paths, mobile web loading, and receipt autofill behavior.
Why it matters: This keeps mobile testing more reliable for everyday use.
We paused paid-plan gates and billing actions while beta testing continues.
Why it matters: This lets testers use the product without hitting unfinished payment flows.
We added a compact native auth entry and prepared Google sign-in for mobile shells.
Why it matters: This gives mobile builds a clearer path into the app.
We improved keyboard, focus, labels, dialog, chart, and navigation semantics.
Why it matters: This helps more people use the app and gives launch QA a repeatable checklist.
We aligned landing navigation and expanded FAQ coverage for trust, sandbox, setup, and advice limits.
Why it matters: This helps cautious users understand Bunga before signing up.
We hardened account ingestion, production mock boundaries, and beta entitlement behavior.
Why it matters: This keeps launch surfaces more trustworthy.
We added Privacy Policy, Terms of Service, and Contact Us destinations from the landing footer.
Why it matters: This gives users clear trust and support paths before launch.
We added custom transaction categories, exact-payment cash support, and launch quality checks.
Why it matters: This improves day-to-day entry while making releases safer.
We improved receipt OCR setup, billing headers, API-key behavior, and image handling.
Why it matters: This helps receipt autofill fail less often and report clearer errors.
We added monthly budget tracking and subscription reminder behavior.
Why it matters: This helps users plan recurring money events before they become surprises.
We rebuilt family invites with preflight review, duplicate checks, and QR invite support.
Why it matters: This helps families join workspaces without losing track of existing transactions.
We made profile setup lighter and added a skip path before first transaction entry.
Why it matters: This helps new users reach the dashboard faster.
We refined transaction capture, added clearer income labels, and softened Guardian copy.
Why it matters: This makes the product feel less like a spreadsheet and more approachable.
We rewrote the landing page around clarity, trust, spacing, and a calmer product story.
Why it matters: This helps people understand what Bunga does before starting setup.
We adopted the Mango brand mark and added groundwork for future Guardian voice and app sounds.
Why it matters: This gives Bunga a more consistent identity across app surfaces.
We hardened profile bootstrap, transaction loading, refresh behavior, and shared delete handling.
Why it matters: This makes returning to the app and reviewing data more dependable.
We added idempotency and queue claiming so repeated submits do not create duplicate rows.
Why it matters: This protects users from accidental double entries.
We added AI coach preferences, rollout controls, observability, and investment safety rules.
Why it matters: This keeps AI help educational, trackable, and easier to control during launch.
We added family collaboration basics, recurring payday and subscription scheduling, and cash breakdowns.
Why it matters: This moved Bunga toward shared household planning instead of only solo tracking.
We improved Google login, onboarding persistence, rolling dashboard history, and family chart labels.
Why it matters: This made the core app flow more stable before larger feature work.
We added profile API support, account setup syncing, bulk transaction entry, and Google-only auth cleanup.
Why it matters: This made setup and faster data entry more practical.
We added bulk transaction support, updated categories, and introduced an optimistic background sync queue.
Why it matters: This helps users enter more data quickly while keeping saves resilient.
We expanded subscription tiers, Tailwind theme setup, and dashboard value calculations.
Why it matters: This gave the product clearer plan structure and visual foundations.
We added a landing page, account setup, sandbox mode, transaction context, and demo unlocking.
Why it matters: This gave new users a way to try Bunga before relying on real data.
We added the AI Guardian chat, translation support, Supabase setup, onboarding work, and analytics tooling.
Why it matters: This created the early product foundation for coaching, setup, and localization.
We added user filtering in Insights, subscription context, trial status, and more realistic mock data.
Why it matters: This made the dashboard feel more personal and easier to test.
We moved project and budget IDs to UUIDs and improved Budget Manager responsiveness.
Why it matters: This made budget data safer and the budget UI easier to use.
We added an environment example, updated site metadata, and refined type safety and localization support.
Why it matters: This made the project easier to run and prepare for deployment.
We added advanced internationalization utilities and better date display across dashboard surfaces.
Why it matters: This made Bunga easier to adapt for users in different locales.
We added Brankas bank connection work, live transaction display, and a language context.
Why it matters: This connected early dashboard data with a more global app structure.
We added authentication, Prisma data setup, bills, family finance tools, and transaction management basics.
Why it matters: This formed the first working base for household finance tracking.
We added the Insights dashboard and a transaction drawer for memo, flag, and bucket editing.
Why it matters: This gave users the first ways to review and adjust their money data.