Mohammad Jowkari(AllergyGuard)

Inspi## Inspiration

Ingredient labels are confusing, Wi-Fi isn’t always available, and allergies are high-stakes. I wanted a fast, offline checker that shows exactly why something might be risky.

What it does

Pick your allergens → paste an ingredients list (or import foods) → hit Check Safety. It highlights trigger terms (e.g., whey, sesame, barley) and gives a simple HIGH / MED / LOW hint—fully offline, no accounts.

How we built it

Vanilla HTML/CSS/JavaScript. LocalStorage for preferences and imports (JSON/CSV). Synonym maps + light regex context (“contains / may contain / shared equipment”). Optional PWA: manifest.json + sw.js for install/offline.

Challenges we ran into

Balancing false positives vs. misses, handling regional terms and E-numbers, staying fast on mobile, and keeping everything explainable without a backend.

Accomplishments that we're proud of

Private, offline checker with clear highlights and risk levels. 1,000-item example packs (US/Canada, Persian). Clean UI with light/dark mode and custom-allergen support.

What we learned

Explainability builds trust more than a black-box “safe/unsafe.” Small UX touches (searchable examples, random demo, timing metric) make judging and real use smoother.

What's next for Mohammad Jowkari (AllergyGuard)

FR-CA/Spanish packs and broader synonyms, optional barcode → offline cache, optional client-side OCR, accessibility polish, and community-maintained allergen lists. ration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for Mohammad Jowkari(AllergyGuard)

Built With

• html
• jason
• javascript