I did not begin Glyph because I had a polished theory about language learning. I began it because there were conversations in my own family that I could not join.
My mom's side of the family is Armenian Egyptian. My dad's side is Coptic Egyptian. I grew up in Southern California, but Egyptian culture was never some distant fact about me. It was in the food, weddings, humor, stories, and family dinners around me. The language was there too. I could hear it, recognize pieces of it, and still stay quiet when the conversation moved faster than I could follow.
That distance became harder to ignore as I got older. I had spent years treating the Egyptian and American parts of my life as if they belonged in separate rooms. Eventually I realized that I did not want to choose between them. I wanted to participate in both.
The missing piece was conversation
I have only had a handful of real conversations with my grandmother. She prefers Arabic. I did not have enough of it.
That is a simple sentence, but it carries a lot. I was not trying to read a newspaper or pass a grammar exam. I wanted to sit at the same table as my family and carry part of the conversation. I wanted to ask a follow-up question instead of smiling because I had lost the thread.
In January 2026, I started taking Egyptian Arabic lessons. They helped me become more familiar with the language, but I still did not have a clear path from learning a word to using it under pressure. I could study a list and recognize every item on it. Then someone would speak to me and the list would disappear.
That gap became the problem I wanted to solve.
Glyph started as my own practice
The first version of Glyph was not a product. It was a daily tool for me.
I used it to organize the next thing I needed to learn, bring older material back before I forgot it, and push myself to answer out loud. I rebuilt it more than once because some ideas looked good on a screen but did not help me speak. Every rebuild pulled the product closer to one question:
Can I carry more of a real conversation than I could yesterday?
That question changed what mattered. A lesson could not end when I recognized the right answer. I needed to hear the language, build with it, say it, and use it in an exchange that moved.
Why Egyptian Arabic
Glyph focuses on Egyptian Arabic because that is the language of the conversations I am trying to enter. It is not a general Arabic course with an Egyptian label added later. It is a spoken path built around the Cairo-leaning language learners hear from Egyptian family, friends, and media.
The site and app use Franco Arabic because it lets a beginner start speaking before Arabic script becomes another barrier. Franco is not standardized, so Glyph chooses consistent learner-friendly spellings and acknowledges common variations when they matter. Script can still become part of the journey. It just does not have to delay the first conversation.
What I want Glyph to become
I am not promising instant fluency. I am building a foundation that becomes useful in real life.
For me, success is sitting at a family dinner and participating instead of spectating. For someone else, it may be talking with a partner's parents, visiting Egypt, or finally answering a friend without switching to English.
The reason can change. The standard stays the same: the language should leave the lesson with you.
You can try the real Day 1 lesson in your browser or read why I decided to build my own Arabic app.
Editorial note
This article describes my own family and learning experience. It was originally published on April 4, 2026, and substantially revised on August 31, 2026 for clarity and accuracy.