Core data and comparison flows are being validated.
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
Public website 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.
Active development
Price-aware shopping decisions
- Common-name matching so variants of the same ingredient can be compared.
- Package parsing for units such as grams, kilograms, millilitres, litres, packs, and multipacks.
- Split-shop savings display based on live comparable products.
- Backend admin tools for ingredient, category, and product taxonomy cleanup.
- Store and state coverage checks to keep active product numbers accurate.
- Recipe and ingredient data preparation for cost-per-serve workflows.
Incomplete or limited
Features not finished yet
- Full basket optimization across every product in a user shopping list.
- Recipe cost-per-serve flows on the public homepage.
- Price history views and long-term trend charts.
- Personalized alerts, pantry-aware suggestions, and saved household preferences.
- Complete coverage parity across every supported retailer, product type, and state.
- Polished mobile app release flows and production-grade onboarding.
Known risks
What may not work
- 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 common ingredient name is cleaned up.
- Live API requests can be unavailable during staging deploys or backend maintenance.
- Counts on the website may describe active catalogue products, not all currently priced products.
- Design, navigation, and feature wording may change as the app moves toward beta.
Current priority
The current priority is making the data path reliable from backend product matching through to the frontend display: compare the same grocery need across stores, calculate cost per packaged amount, and show whether a two-store split creates meaningful savings.