2890b6cb6f
Analysis cache redesign: - Remove Hive persistence from AnalysisCacheService entirely - Use Map<String, SakeAnalysisResult> in-memory instead of Hive boxes - Cache now lives only for the duration of an app session; restart always produces a fresh analysis — no stale misidentifications can persist - Remove Hive init(), TTL/cleanupExpired(), getCachedByBrand() dead code - API surface unchanged: callers (gemini_service, dev_menu) need no edits - main.dart: delete legacy Hive boxes (analysis_cache_v1, brand_index_v1) from disk on startup for existing users - dev_menu_screen: update cache description text to reflect new behavior Rationale: - Camera captures always produce unique files -> cache hit rate was ~0% - Each user supplies their own Gemini API key -> no shared cost benefit - Persistent wrong results (e.g. misrecognized brand names) could survive up to 30 days under the old design - Different sake editions photographed separately have different hashes and were never affected by the cache in the first place Made-with: Cursor |
||
|---|---|---|
| .github/workflows | ||
| android | ||
| assets | ||
| docs | ||
| ios | ||
| lib | ||
| linux | ||
| macos | ||
| scripts | ||
| test | ||
| tool | ||
| tools | ||
| web | ||
| windows | ||
| .cursorrules | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| .metadata | ||
| AI_CONSULTATION_PROMPT.md | ||
| AI_MASTER_ROADMAP.md | ||
| README.md | ||
| SECURITY_SETUP.md | ||
| analysis_options.yaml | ||
| build_4_apks.sh | ||
| build_business.sh | ||
| build_consumer.sh | ||
| build_consumer_apks.ps1 | ||
| flutter_native_splash.yaml | ||
| l10n.yaml | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| release_to_gitea.ps1 | ||
| screenshot.png | ||
README.md
ponshu_room_lite
A new Flutter project.
Getting Started
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter development, view the online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.