Development Status | FeedMyBudget

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.
Main app navigation for Dashboard, Specials, Pantry, Lists, Recipes, 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.

Disabled or coming soon

Not ready for public use

Budget is removed from primary navigation and direct routes show a Coming soon screen.
Allergen management is disabled in Profile and onboarding.
Dietary preference management is disabled in Profile and onboarding.
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.

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.
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 tightening the data path from backend product matching through to app display: compare the same grocery need across stores, calculate cost per packaged amount, link pantry items through ingredient taxonomy, and show whether a two-store split creates meaningful savings.

Latest verification

The latest app deployment was verified with flutter analyze, the full Flutter test suite, the live /app/ web route, hard-refresh routing under /app/main, and the /fmb-api/health endpoint.