Health · iOS app

Glutamate Guard

An offline iOS ingredient scanner for identifying terms associated with glutamate.

Compendium article 004 Revision 0.6 · July 2026

Glutamate Guard began with a small but persistent shopping problem: ingredient lists are dense, terminology varies, and checking every label by memory is slow. The resulting app compresses that task into a private camera workflow on an iPhone.

The project takes the form of an iOS app that photographs an ingredient list, reads it with on-device OCR, checks the text against a curated term list, and returns a simple reading. Its purpose is to turn a difficult ingredient-list check into a quick, private phone workflow.

The question behind Glutamate Guard

The narrowness of the problem shaped the product. It did not need accounts, a social layer, a remote database, or a generalized nutrition engine. It needed to capture text, compare it with a curated list, and explain that result without implying medical certainty. People who choose to monitor glutamate-related ingredient terms. The app is not a medical device and cannot determine individual sensitivity or safety.

How Glutamate Guard took shape

Apple's Vision framework performs the OCR on-device, while SwiftUI supplies the capture and result flow. Keeping the entire check offline reduced both latency and privacy exposure: ingredient photographs do not need to leave the phone merely to answer a term-matching question. Josiah chose the problem, designed the minimal workflow, built and tested the app with AI assistance, and submitted it to the App Store.

What the evidence supports

Version 1.1 cleared App Store review. A working MVP ran on a real device and was submitted the same day it was built. Its significance is partly methodological. A one-purpose health-adjacent tool can be useful precisely because it refuses to become a diagnostic product. The remaining work is therefore not feature expansion so much as clearer documentation of the term list, evidence boundary, and visual presentation.

The term-list methodology needs clearer public documentation, and the product must retain a non-medical disclaimer without overstating the science of sensitivity. A fuller public record will explain the term list, current App Store status, available usage evidence, and the product's development story.