PesaTrack Release History

This document tracks all Play Store releases of PesaTrack, including version codes, release dates, and changelogs.

Release Summary

v1.4.1 (versionCode 11) — 2026-06-24

Focus: Patch release on top of v1.4.0 — four polish items that landed after v1.4.0's release commit. Closes the loop on income tracking (self-transfer noise, scroll regression) and finishes the "month starts on" alignment across the rest of the app (Analytics Monthly charts, CSV export).

🐛 Bug Fixes

• Bank → M-PESA self-transfers no longer count as income — When you move money from your NCBA bank account to M-PESA via the bank app, the SMS pair is two halves of the same self-transfer. The M-PESA half (You have received Ksh… from NCBA BANK…) was being saved as UNCATEGORIZED income, inflating monthly income totals and triggering a stray "Income received" notification. MpesaSmsParser.tryParseIncome now keeps a bank-self-transfer sender list (currently NCBA BANK / NCBA) and rewrites matching rows to source = TRANSFER_IN, isExcluded = true before persisting. Side effects: the notification stays silent (only UNCATEGORIZED rows notify), the row is filtered out of every total, and the row still appears on the Income screen (dimmed, struck-through) so you can audit or restore it via long-press.

• Income screen no longer jumps back to the top on refresh — Returning to the Income screen from CategorizeIncomeScreen kicked the list back to the top because the entire LazyColumn was being unmounted whenever uiState.isLoading == true. Gated the spinner branch on isInitialLoad = isLoading && transactions.isEmpty() && totalInflow == 0.0 — refreshes with existing data no longer rebuild the list, preserving scroll position.

• Analytics Monthly charts now respect your "month starts on" setting — The Charts → Monthly tab was still using calendar months while Budgets, Income, Home, and the savings-rate card had already moved to your monthStartDay preference. A salary-on-the-25th user would see "May 2026" data on the Analytics tab even though the active budget period was "Apr 25 – May 24". The period selector label ("Mar 25 – Apr 24, 2026" when offset), arrow navigation, totals, previous-period comparison, By Category / Top Spenders / Payment Type breakdowns, recipient search, the 6-period trend chart, the 6-period category trends, and the days-for-average computation now all use the same offset-aware period as Budgets.

• CSV export now includes income — Settings → Export Data emitted only expenses; income transactions were nowhere in the file. The export now bundles both into a single CSV ordered by date, with a new leading Type column (Expense / Income) so you can filter or pivot. The empty-state toast and Settings row subtitle were updated accordingly.

📦 Technical

• New unit test: MpesaSmsParserIncomeTest."NCBA bank to MPESA self-transfer is excluded TRANSFER_IN". Extend the bank-self-transfer sender list in MpesaSmsParser as new banks appear in the wild.
• New shared utility MonthPeriod.kt — centralises offset-aware period bounds, keys, and labels used across IncomeRepository, AnalyticsViewModel, and (already) BudgetRepository.
• New ExpenseRepository range-based wrappers (getCategoryTotalsInRange, getTopSpendersInRange, getPaymentTypeBreakdownInRange, searchRecipientSpendingInRange) so analytics surfaces can pass explicit period bounds instead of (year, month) tuples.
• New IncomeTransactionDao.getAllIncomeForExport() query; DataManagementService constructor takes an IncomeTransactionDao (4th param).
• Removed unused AnalyticsViewModel helpers (buildMonthKeys, fillMissingMonths, formatMonthLabel) and the stale private val calendar field.

🏪 Play Store Release Notes

What's New:
• Analytics → Charts → Monthly tab now follows your "month starts on" day, so the period selector and all monthly charts match your budget cycle
• CSV export (Settings → Export Data) now includes income transactions alongside expenses, with a new "Type" column
• Bank → M-PESA self-transfers (e.g. NCBA app to M-PESA) no longer count as income — they're auto-excluded but still visible on the Income screen for audit
• Income screen no longer jumps to the top after categorizing a row

v1.4.0 (versionCode 10) — 2026-06-22

Focus: Income tracking — passively detect and categorize money coming in, surface it across Home / Budget / Analytics, and give users a way to exclude one-off transfers from totals.

✨ New Features

• Income tracking — full pipeline (DB v16 → v18) — M-PESA and bank SMS now produce income transactions in addition to expenses, end-to-end:

  • New income_transactions table + IncomeTransaction domain model + IncomeRepository (insertIfNew with dedupe, sourceBreakdown, effectiveMonthlyIncome(yearMonth) reconciliation against the manual override).
  • Parsers — MpesaSmsParser detects salary / business / funds-received / peer receive / M-Shwari → M-PESA / agent deposit / Offnet B2C; NcbaBankParser detects bank credits. MpesaStatementParser emits income rows during PDF imports. New sealed ParsedSms result type (ExpenseResult / IncomeResult / NotARelevantMessage).
  • CategorizeIncomeScreen — pick a source (Salary / Business / Refund / Interest / Family / Transfer in / Other), optionally mark as "Not income", and optionally remember the sender → source mapping (income_sender_rules table) so future income from the same sender auto-categorizes.
  • Income screen — Month / Quarter / Year segmented period picker, header card (total + reconciliation chip + weighted source breakdown bar + legend), tappable rows, manual income entry via Extended FAB.
  • Home secondary income line on the monthly summary card — "KES X received · Y% saved" — tap to open the Income screen.
  • Budget allocation — new "Detected this month: KES X" sub-line + "Use detected" button on the income allocation card, reconciliation chip footer ("Using detected income / your override / override — KES X higher than detected").
  • Monthly Review — new "Where your income came from" card between Headroom and Pace; investment-illustration disclaimer now cites the income source ("Based on detected income of KES X" / "Based on the income you set").
  • Analytics — new Savings Rate insight card on the Insights tab (this-month rate, 3-month rolling rate, expandable "Assumptions" block) and a 12-month Income vs Spend overlay line chart on the Monthly Charts tab.

• "Not income" affordance — Long-press any income row to mark it as excluded (or restore it); excluded rows render dimmed with strike-through on the amount and "Not income · sender" subtitle. Same toggle available as a "Not income" FilterChip on CategorizeIncomeScreen. Excluded rows are filtered out of every total, source breakdown, savings rate, and analytics surface — useful for one-off transfers, refunds you already counted, or rounding noise.

• Create categories from the picker — A "+ Add new category" entry inside the category picker on the categorize / batch-categorize / manual-entry / excel-import flows now opens a small dialog (name + emoji) so you don't have to bounce out to Category Management mid-flow.

• By Category card on Home — Compact "spending by category this month" card that links straight to the Analytics → Categories tab.

• Income received notification (low priority) — A new pesatrack_income_received channel posts a single low-importance notification when an UNCATEGORIZED income arrives, deep-linking to CategorizeIncomeScreen. Respects the "nudge, don't nag" principle — known sources never notify.

• Notification deep links — Tapping a Monthly / Quarterly / Year-in-Review notification now opens the corresponding review screen directly instead of dropping you on Home.

🐛 Bug Fixes

• Income / savings rate now respect your "month starts on" setting — Previously the Income screen, Home "received this month" line, and Analytics savings-rate card all hard-coded a calendar month (1st to last day) while the Budget screen used your monthStartDay preference. A salary-on-the-25th user would see their budget period as Mar 25 – Apr 24 but their income shown for Mar 1 – Mar 31, making the savings rate compare numbers from different periods. Aligned all three surfaces (HomeViewModel.loadIncomeData, AnalyticsViewModel.loadSavingsRateCard + loadIncomeVsSpendChart, IncomeViewModel MONTH tab) on the same offset-aware period via a new shared MonthPeriod helper that mirrors BudgetRepository's existing convention (period named after its start year/month, key "yyyy-MM" when offset is 1 else "yyyy-MM-dd"). Also fixed a latent crash-then-swallow bug where IncomeRepository.monthBoundsFor threw IllegalArgumentException whenever BudgetViewModel passed an offset key like "2026-03-25" — the surrounding try/catch was silently hiding the user's manual income override from the budget income card.

• Live income SMS now triggers the "Income received" notification — SmsReceiver was gating the M-PESA branch on the legacy SmsParser.isTransactionSms, whose keyword list (sent to / paid to / withdrawn / of airtime / Fuliza / bought) only matched expense SMS. Every live income SMS was silently dropped before the parser ran, so no row was saved and the notification never fired. Replaced with body.contains("Confirmed") — the universal M-PESA transaction marker the parser already uses — and the parser strategy now decides expense vs income vs irrelevant.

• Feedback email body now pre-populates in Gmail — The structured Stage 1D/1E feedback drafts were opening with an empty body/subject because Gmail (and several other Android mail clients) ignore EXTRA_SUBJECT / EXTRA_TEXT when the mailto: URI has no query string. Built the URI with ?subject=…&body=… query params and kept the extras as a fallback.

• Home "By Category" tap target — Tapping the card now reliably navigates to Analytics → Categories (previously the click was being swallowed by the chart container).

• ImportScreen income counts — Bulk SMS + statement imports now show newIncomesImported and incomeDuplicatesSkipped alongside the expense counters on the import-result screen.

📦 Technical

• DB v16 → v17 — Added income_transactions table (unique transactionId, source enum, parserSource, isExcluded column, indexed by (sender, source)).
• DB v17 → v18 — Added income_sender_rules table (sender PK, source enum name, learnedAt). Both migrations are non-destructive.
• New screens / routes: Income, CategorizeIncome.
• About + privacy policy copy updated to reflect that both incoming and outgoing SMS are read (the policy still says nothing leaves the device).
• New unit tests: MpesaSmsParserIncomeTest (8 cases), NcbaBankParserIncomeTest (4 cases).
• Removed unused Switch / HorizontalDivider / wrapContentWidth imports + private Row wrapper from CategorizeIncomeScreen after the chip refactor.

🏪 Play Store Release Notes

What's New:
• Income tracking — your salary, business payments, refunds, and other income are now detected from SMS automatically and shown on a new Income screen
• Savings Rate insight on the Analytics tab and an Income vs Spend overlay chart
• Long-press any income to mark it "Not income" (useful for one-off transfers or refunds you already counted) — it's excluded from totals
• Add new categories without leaving the categorize / manual-entry flow
• "By Category" card on Home
• Low-priority notification when new income arrives, so you can tag the source
• Income and Savings Rate now follow the same "month starts on" day as your budget — salary-cycle users get a coherent picture
• Fixes: feedback emails now pre-fill in Gmail, "By Category" tap target on Home, import-result counts include income

v1.3.2 (versionCode 9) — 2026-06-02

Focus: Honest analytics — remove projections that were lying, fix monthly review investment illustration, polish charts.

🐛 Bug Fixes

• Monthly Review Investment Illustration showed wrong principal — The "What your savings could become" card was rendering principal = total monthly spending minus fees (e.g. ~KES 353,000) instead of the user's actual investment for the month (e.g. KES 55,000). Root cause: when a persisted monthly snapshot was re-hydrated from ReportSnapshotEntity, InsightsRepository.toMonthlyDomain() was fabricating the illustration locally with principalAmount = periodTotal − feesTotal and source = HEADROOM because the entity doesn't store the illustration. Fix: re-query the live investment total and stored income, then call MonthlyReviewGenerator.buildInvestmentIllustration(...) — the same path used at generation time.

✨ UX Improvements

• Investment illustration copy now honest about lump-sum math — Headings and body text across Monthly, Quarterly, and Year-in-Review reviews previously implied a recurring "habit" / "X per month" contribution but the math was a single deposit grown for 5 years. Rewrote: HEADROOM heading "What your savings could become" → "Your unspent income this {month/quarter/year}"; body now reads "If invested at 10% p.a. for 5 years it could grow to KES X"; NUDGE_TARGET copy stopped claiming "20% of income" when income isn't set; disclaimer updated to "Assumes a single deposit … left to grow at 10% annual return compounded monthly."
• Forecasting feature removed — Per the product principle "no projections without showing assumptions," the entire budget-forecasting subsystem (ForecastService, BudgetForecast model, ForecastProjectionChart, forecast cards on Home, forecast notifications) was removed. The projections it produced were faulty for typical irregular income/spend patterns. Replaced with a neutral "KES X remaining for N days" line on each BudgetProgressCard.
• Daily spending bar chart removed — Was redundant with the monthly trend line and frequently rendered as a single-bar ambiguity at the start of a month.
• Trend chart point markers — Added visible point markers (Vico LineCartesianLayer.point + pill ShapeComponent) to the monthly trend line and the 12-month year-over-year overlay so individual data points are readable.
• Category breakdown rewritten as a table — CategoryBreakdownChart in Insights changed from horizontal bars to a tabular layout (Category / Amount / %) with a colored category dot, divider rows, and right-aligned numeric columns.

📦 Technical

• Deleted: domain/models/BudgetForecast.kt, services/ForecastService.kt, ForecastCard composable, forecast notification throttle and DataStore keys, all forecast call sites in HomeViewModel, BudgetViewModel, AnalyticsViewModel, BudgetService, SmsReceiver, NotificationHelper.
• New: domain/models/BudgetRemaining.kt — neutral remaining-amount + days-remaining model used by BudgetProgressCard.
• data/repository/InsightsRepository.kt: toMonthlyDomain() is now suspend, re-queries ExpenseDao.getInvestmentTotalInRange(periodStart, periodEnd) and IncomeDao.getByYearMonth(...) (with headroomAmount + periodTotal fallback), then delegates to MonthlyReviewGenerator.buildInvestmentIllustration(...).
• domain/insights/MonthlyReviewGenerator.kt: INVESTMENT_DISCLAIMER updated to disclose the single-deposit assumption.
• presentation/screens/{monthly_review,quarterly_review,year_in_review}/*.kt: rewrote investment illustration heading + body strings.
• New plan file: plans/income-tracking-plan.md (scoping document, not shipped behavior).

🏪 Play Store Release Notes

What's New:
• Monthly Review investment illustration now uses your actual invested amount, not a derived figure
• Honest copy: "If invested once at 10% p.a. for 5 years, it could grow to…" — no more misleading "per month" framing
• Removed budget forecasting that produced inaccurate month-end projections
• Cleaner charts: visible data-point markers on trend lines, tidy table for category breakdown
• Daily-spending bar chart removed (it was redundant with the monthly trend)

v1.3.1 (versionCode 8) — 2026-05-29

Focus: Onboarding activation — reduce drop-offs from ambushed SMS permission prompt

🐛 Bug Fixes

• Onboarding SMS Permission Ambush — Removed the auto-launch of the system SMS permission dialog that fired the instant users landed on onboarding page 3 (added in v1.3.0). Users were being prompted before they could read the context, triggering reflexive denials. Play Console data showed uninstall ratio rising from ~35% pre-auto-prompt to ~49% after v1.3.0. Now uses the standard primer pattern: page 3 shows context and a "Grant SMS Permission" button that the user taps to initiate the dialog.
• Live SMS Auto-Categorization Gap — SmsReceiver was skipping the keyword rules engine entirely, so expenses like NCBA card payments to OPENAI, UBER, KPLC, NAIVAS etc. landed uncategorized even though KeywordRulesEngine had explicit rules for them. PDF statement imports had always worked because StatementImportService calls CategorizationService. Wired CategorizationService into SmsReceiver.applyAutoCategorization as a third fallback step (after deterministic rules and recipient mapping), restoring parity. Live SMS now gets the same auto-categorization treatment as PDF imports.

✨ UX Improvements

• Explicit Skip Path on SMS Page — When SMS permission isn't granted, the page 3 "Next" button is relabeled "Skip — I'll add manually" (outlined style) so users see the alternative path instead of feeling stuck.
• Reassurance-First Permission Copy — Page 3 body rewritten to lead with what matters: "Nothing leaves your phone — PesaTrack has no internet permission, so it cannot send your data anywhere." Explicitly mentions the manual-entry fallback.
• Encouraging Skip Copy on Import Page — Page 4 fallback copy (when SMS is skipped) rewritten from scolding ("permission is needed… grant on previous page") to forward-looking ("No problem — you can add expenses manually as you spend. To import past SMS later, grant access from Home or Settings anytime.").
• Tighter Low-Engagement Feedback (Stage 1E) — Reduced friction-prompt thresholds from 24h/72h to 30min/15min so the prompt actually reaches churning users in their first session. Converted from inline card to a Material 3 modal dialog so it's visible regardless of scroll position. Title rewritten to neutral framing: "Quick question — what's blocking you?"

📦 Technical

• OnboardingScreen.kt: removed LaunchedEffect auto-prompt, removed smsAutoPrompted saveable state, removed unused rememberSaveable import, removed delay import
• HomeViewModel.kt: LOW_ENGAGEMENT_SMS_GRACE_MINUTES=30, LOW_ENGAGEMENT_FIRST_VALUE_GRACE_MINUTES=15; condition B no longer gated on hasSmsPermission
• HomeScreen.kt: LowEngagementFeedbackCard (LazyColumn item) replaced by LowEngagementFeedbackDialog (AlertDialog) rendered outside Scaffold
• SmsReceiver.kt: added CategorizationService injection; applyAutoCategorization now runs the user-rules + keyword engine as a third step after recipient mapping
• New scripts/analyze_playstats.ps1 helper for parsing Play Console CSV exports

🏪 Play Store Release Notes

What's New:
• Smoother onboarding — SMS permission is now requested when you're ready, not the moment the page loads
• Clearer "Skip — I'll add manually" option for users who prefer to enter expenses by hand
• More honest, reassuring copy: nothing leaves your phone, ever
• More expenses auto-categorize on the spot (OpenAI, Uber, KPLC, supermarkets, etc.)
• Better in-app feedback prompts to help us fix what's not working

v1.3.0 (versionCode 7) — 2026-05-20

Focus: Smarter investment illustrations + NCBA duplicate fix

✨ New Features

• Tier-Based Investment Illustration — Replaced naive "what if all expenses invested" with intelligent approach: detects actual investments from Savings & Investments category, shows headroom when income is set, or nudges 20% target as fallback. Progressive milestones (20% → 30% → 50%) encourage higher savings rates. 5-year projection horizon.

🐛 Bug Fixes

• NCBA Duplicate SMS — Fixed duplicate transaction detection for NCBA bank SMS messages that could create multiple entries for the same transaction.

📦 Technical

• New InvestmentSource enum (ACTUAL_INVESTMENT, HEADROOM, NUDGE_TARGET) with tier logic in shared buildInvestmentIllustration() helper
• Added getInvestmentTotalInRange() DAO query for Savings & Investments category group 18
• Updated UI cards in Monthly/Quarterly/Year-in-Review screens with tier-aware copy
• All unit tests updated (33 passing)

🏪 Play Store Release Notes

What's New:
• Smarter "What if you invested" section — now shows your actual savings rate and personalized investment targets
• Fixed duplicate transactions for NCBA bank messages
• 5-year investment growth projections with progressive milestones

v1.2.1 (versionCode 6) — 2026-05-01

Focus: Analytics UX improvement — weekly spending moved to dedicated card

✨ New Features

• Weekly Snapshot Card (Analytics) — Moved weekly spending info from the Home screen to a richer card in the Analytics monthly tab. Shows: this-week total, daily average, week-over-week % change (color-coded ↑/↓), and top spending category for the week.

📦 Technical

• New WeeklySnapshotCard composable in Analytics; new getTopCategoryInRange DAO query + TopCategoryResult data class; loadWeeklySnapshot() in AnalyticsViewModel
• Removed totalLast7Days from HomeUiState / HomeViewModel / MonthlySummaryCard (moved to Analytics)
• Fixed TrendingUp/TrendingDown deprecation warnings (migrated to Icons.AutoMirrored.Filled)

v1.2.0 (versionCode 5) — 2026-04-29

Focus: NCBA bank parser fix, budget notification fix, user feedback & engagement system

✨ New Features

• In-App Review Prompt (Stage 1B) — Google Play In-App Review triggered for engaged users (≥5 qualified sessions + key milestones reached); throttled to avoid annoyance
• Structured Feedback Prompt (Stage 1D) — Home screen card asking "What would make PesaTrack more useful?" with 6 predefined options + free text; response saved locally and opens prefilled email draft
• Low-Engagement Feedback (Stage 1E) — Home screen card for users who haven't completed setup, asking "What blocked setup for you?" with 6 reasons; captures friction points locally + email draft
• Usage Summary in Feedback Emails — Contact & Feedback email from About screen now includes anonymized usage context (install date, session count, feature usage) to help diagnose issues
• Share PesaTrack — New share button in Settings screen to tell friends about the app
• Usage Metrics Snapshot — Local-only tracking of milestones (first SMS parsed, first import, etc.) and feature usage counters for improving the product; data never leaves device unless user explicitly shares

🐛 Bug Fixes

• NCBA Bank SMS Not Importing — NCBA changed their SMS format: Till messages no longer include the till number, and Paybill messages no longer include the "account" keyword. Added tillPaymentPatternB (name-only) and paybillPatternC (name-only) to handle the new format. Old patterns kept as fallbacks for backward compatibility.
• Budget "Exceeded" at Exactly 100% — Budget notification incorrectly said "Budget exceeded!" when spending was exactly at 100%. Now correctly says "Budget fully used!" at exactly 100%, and "Budget exceeded!" only when spending goes over 100%.

📦 Technical

• New UsageSummaryGenerator utility (text + JSON output, Hilt-injected)
• New AboutViewModel for Hilt dependency injection in About screen
• AppPreferences: added review prompt, feedback, low-engagement, and usage metrics snapshot keys
• DataManagementService: embeds usageMetrics JSON in backup metadata
• Google Play In-App Review dependency (review-ktx:2.0.2)
• NcbaBankParser: renamed tillPaymentPattern → tillPaymentPatternA, added tillPaymentPatternB + paybillPatternC
• Privacy policy: removed misleading usage tracking paragraph

v1.1.0 (versionCode 4) — 2026-04-17

Focus: Budget forecasting, notification improvements, stability fixes

✨ New Features

• Budget Forecasting (4 phases) — Linear burn rate projections across the entire budget system:
  • Home Forecast Card — Top 5 at-risk budgets with color-coded status (🔴 exhaustion imminent / 🟡 projected over / 🟢 on track), safe daily spend amount
  • Budget Per-Card Forecast — Each budget card shows projected % by period-end, exhaustion date warning, safe daily spend
  • Forecast Notifications — Fires when projected ≥110% with ≥7 days remaining OR exhaustion <5 days; 24-hour per-budget throttle
  • Analytics Projection Chart — Cumulative actual spending line + projected extension to month-end + budget ceiling reference line (Vico 2-series chart)
• Deep-link Notification Taps — Tapping expense notifications opens the categorize screen; tapping budget alert notifications opens the budget screen

🐛 Bug Fixes

• Excel Import Crash — Fixed crash when importing Excel files with large SMS datasets for matching
• Home Screen Budget Reactivity — Budget summary data on the Home screen now properly reacts to budget deletions via Room Flow (previously stale data persisted until manual refresh)

📦 Technical

• New ForecastService (@Singleton, Hilt-injected, pure Kotlin — no DB tables, no schema migration)
• BudgetService.checkForecastsAfterExpense() triggered from SmsReceiver after each SMS expense save
• Forecast notification throttle stored in AppPreferences DataStore (24h per-budget cooldown)
• ForecastProjectionChart composable using Vico 2-series line chart
• No database migration required — forecasting is pure computation on existing data

v1.0.2 (versionCode 3) — 2026-04-02

Focus: Onboarding fix, SMS permission recovery

🐛 Bug Fixes

• Onboarding "Import Now" Navigation — Fixed the "Import Now" button on onboarding page 4 navigating to the Home screen instead of the Import screen. Root cause: onImportNow callback called both onImportHistory() (no-op) and onComplete() which finished onboarding and showed Home. Fix: pendingImportNavigation flag in AppEntryPoint → LaunchedEffect navigates to Screen.ImportHistory after onboarding completes.

✨ New Features

• SMS Permission Recovery (Home Banner + Import Gate) — Two new surfaces for users who skipped onboarding SMS permission or later revoked it:
  • Home Screen banner — Shown when SMS permission is missing and not permanently dismissed. Three actions: "Enable" (launches permission request), "Not now" (session dismiss), "Don't ask again" (permanent dismiss via DataStore)
  • Import Screen gate — Full-screen explanation card with "Grant SMS Permission" / "Open App Settings" buttons when READ_SMS not granted; Excel import remains accessible

v1.0.1 (versionCode 2) — 2026-04-01

Focus: Post-launch cleanup, data safety

✨ New Features

• Database Backup & Restore — Full database backup/restore via SAF (Storage Access Framework):
  • Backup creates a .db file with embedded _backup_metadata table containing settings (month start day, bank tracking preferences)
  • Restore validates SQLite header, closes current DB, replaces files, restores preferences, restarts app process
  • Users can save backups to Downloads, Google Drive, etc.

🐛 Bug Fixes

• Sample Data Hidden — Removed SampleDataService visibility from production users (was accessible in debug builds and leaked into release)

v1.0.0 (versionCode 1) — 2026-03-31

Focus: Initial Play Store release — full-featured passive M-PESA expense tracker

🎉 Launch Features

Core — SMS Parsing & Tracking

• M-PESA SMS parsing (8 expense types: Send Money, Buy Goods, Pay Bill, Withdraw, Airtime self/other, M-PESA Card, Fuliza)
• NCBA Bank SMS parsing (3 types: Send Money, Till Payment, Paybill)
• Transaction cost auto-extraction and tracking (saved under category 606)
• Non-expense SMS filtering (Receive Money, Deposit, Reversal silently skipped)
• Multi-part SMS concatenation
• Duplicate detection via transactionId uniqueness constraint

Data & Categories

• Room Database v14 with full migration chain
• 18 category groups with 90+ sub-categories (hierarchical)
• Investment & Savings as separate top-level group (13 sub-categories)
• Custom categories + sub-categories with icon/color pickers
• User-defined auto-categorization rules (EXACT/CONTAINS/STARTS_WITH)
• KeywordRulesEngine with 100+ business name matches + PaymentType heuristics

Import & Entry

• Historical SMS import (M-PESA + enabled banks) with date range picker
• Excel .xlsx import (match to SMS + standalone) with 55+ category mappings
• Manual expense entry form (amount, recipient, payment type, date, category, notes)
• Batch categorization by recipient with multi-select mode

Budgets

• 3-tier budgets: Total Spending, Group-level, Sub-category-level
• Weekly / Monthly / Yearly periods
• Global month-start-day setting (1–28) for salary-aligned budgets
• Budget alerts at 80% (warning) and 100% (exceeded) — notification channel
• Monthly income tracking with allocation summary
• Period-first Budget screen with searchable hierarchical category picker

Analytics

• Monthly tab: trend line, daily columns, category bars, top spenders, payment type breakdown, MoM comparison
• Yearly tab: YoY comparison, 12-month overlay chart, yearly category/recipient/payment breakdowns
• Variable-spend category trends (CV-based detection, ≥3 months, KES 100 minimum)

Security

• PIN lock (4-digit, SHA-256 + salt, never plaintext)
• Biometric unlock (fingerprint/face via BiometricPrompt)
• Brute force protection (5 attempts → 30s cooldown)
• Configurable background lock timeout (immediate/30s/1min/5min)

UX

• First-launch onboarding (4-page HorizontalPager)
• Notification system (expense alerts, budget alerts, tap-to-categorize)
• Category-aware expense cards with color coding
• Exclude pass-through expenses (long-press toggle)
• About screen + Privacy Policy (GitHub Pages)
• Data management (CSV export, category reset)
• Settings (bank toggles, security, budget month, categories)

Distribution

• Application ID: com.pesatrack
• Signed AAB: 13.9 MB (R8 minified + resource shrunk)
• Privacy Policy hosted via GitHub Pages
• Data Safety declaration (all data on-device, no collection/sharing)
• SMS Permission Declaration approved

Version Naming Convention

• Major (1.x.x): Breaking changes, major redesign, or architectural shift
• Feature (x.1.x): New user-facing features (forecasting, cloud sync, new bank parsers)
• Patch (x.x.1): Bug fixes, UI tweaks, stability improvements

Play Store Release Checklist

When publishing a new version:

1. Update versionCode (increment by 1) and versionName in build.gradle.kts
2. Build signed AAB: ./gradlew bundleRelease
3. Test on physical device (install from AAB or use bundletool)
4. Update this document with the new version's changelog
5. Upload AAB to Play Console → Production track
6. Write release notes in Play Console (max 500 chars)
7. If Data Safety changes: update the form before or alongside the release
8. Consider staged rollout (10% → 50% → 100%) for feature releases
9. Commit version bump + release notes: git commit -m "v{version}: {summary}"