Development status

FeedMyBudget is in alpha.

FeedMyBudget is actively being built and tested. Public pricing data, package matching, recipe costing, basket comparison, and split-shop planning are available at different levels of completeness.

Last updated:

Current stage Alpha

The public app and alpha testing builds may be at different versions.

Latest development build 2.0.36

List-aware recipe discovery and separate meal-planning and shopping actions.

Data quality Improving

Manual review labels and product reports are in 2.0.35 testing builds. Coverage is still being refined.

Latest developments and availability

These are development and prerelease milestones, not a claim that every feature is available in the public app. Android testing builds connect to private Pi staging and require the appropriate network access.

Development build · 2.0.36+236

Recipes that complement a shopping list

  • The shopping-list plus button offers Add products or Find meals using this list.
  • Saved recipe suggestions rank by additional checkout cost, accounting for existing packs, pantry stock, and recipe reservations.
  • Add to meal plan and Add ingredients to list are separate actions. A selected date and lunch or dinner slot can be carried into the recipe.
  • Shopping confirmation reviews the destination, servings, products, and quantities. A changed list or price requires another review.
  • Missing prices and package conversions block confirmation for affected linked products; unmatched ingredients are explicitly excluded.

Alpha testing · 2.0.35

Product information and support

  • Current ingredient and nutrition sections can show data before manual verification, with a grey Not manually verified caution label.
  • A green tick and Verified indicate manual review of that section. Changed data can lose its verified status.
  • Product reports support an issue category, photos, notes, and the user's selected store location.
  • Profile → Support Messages shows report statuses and public replies from review.
  • Barcode no-match submissions can create private provisional pantry items while photos and product details are reviewed.
  • Ingredient taxonomy administration is consolidated around the active selection and categorisation workflow.

What alpha means

Alpha means the product is useful enough to demonstrate the direction, but not all workflows are complete or production-polished. Prices and specials can be incomplete, product matches can be imperfect, and some app or website features may fail while the system is being improved.

Feature status

Completed or usable now

Website and app foundations

  • Homepage explaining recipe costing, full-shop comparison, and split-shop savings.
  • Public privacy and account removal pages.
  • Live coverage summary for tracked products, specials, states, retailers, and locations.
  • Product search against tracked grocery data.
  • Current specials display with store and state filters.
  • Package-normalized product comparison for matched grocery needs.
  • Flutter web app deployed under /app/ with authenticated and guest entry paths.
  • Current app navigation for Plan, Recipes, Products, Pantry, Lists, and Profile.

Implemented in the app

Shopping, pantry, and recipes

  • Store and location setup for state/store-aware pricing.
  • Products, specials, product detail, price source badges, and store-aware price comparison.
  • Pantry listing and ingredient-first add flow using the shared product-linking selector.
  • Recipe list, detail, create, edit, system-recipe copy, ingredient linking, and cost-per-serve display.
  • Recipe price lookups now batch current-price requests instead of firing repeated single requests.
  • Shopping lists, recipe add-to-list, list price comparison, persistence, and user sync paths.
  • Dietary preferences and items-to-avoid controls, with product coverage still being improved.

Incomplete or awaiting validation

Not ready for public use

  • Personalized alerts and household recommendation flows are not finished.
  • Public homepage recipe cost-per-serve and price-history demos are still limited.
  • Production-grade Android release flow still needs regular real-device validation.
  • Operation-specific Undo for adding a recipe remains a follow-up; cancellation is available before shopping confirmation.

Active development

Current hardening work

  • Recipe product matching quality, especially common-name, category, and product-equivalence mapping.
  • Cross-store savings calculations for complete baskets and two-store split shops.
  • Price-history interpretation and display quality.
  • Offline and slow-network behavior on mobile and web.
  • Route-level browser refresh and back-navigation coverage for nested app screens.
  • Repeatable authenticated web smoke tests and physical Android smoke testing.

Known risks

What may still be wrong

  • Some products may not have a current state price or special price.
  • Manual verification of food data does not guarantee stock availability or dietary and allergen safety. Check the packaging and selected store.
  • Some package sizes may not parse correctly, which can hide them from normalized comparisons.
  • Comparable products can be missed until their ingredient/category mapping is cleaned up.
  • Counts on the website may describe active catalogue products, not all currently priced products.
  • Live API requests can be unavailable during staging deploys or backend maintenance.
  • Design, navigation, and feature wording may change as the app moves toward beta.

Current priority

The current priority is validating the new recipe-to-shopping flow on real devices, improving ingredient and product coverage, and reviewing product reports. Checkout estimates must account for whole packs and quantities already committed to other meals, without presenting missing information as a saving.

Latest verification

Development build 2.0.36+236, from source caafcd3d, passed code generation, clean Flutter analysis, 1,113 Flutter tests with four existing skips, and web and Android APK release builds using Flutter 3.47.2 and Dart 3.13.2. Physical-device acceptance remains outstanding. Build checks do not confirm public production deployment or the accuracy of every product record.