Glaze Shelf: studio glazes phones can find under dust

[0:00]Dhaval: Thanks for making time—thinking specifically about Glaze Shelf. I like to start unfashionably concrete: Glaze Shelf, Flutter reference app for ceramic studios. If a friend sat next to you on a flight and asked what it is—no pitch deck—what do you say—thinking specifically about Glaze Shelf?

[1:21]Blake Kumar: Thirty-second pitch is Glaze Shelf—then I add context before someone assumes it is just another form. Labels faded; members mixed incompatible layers. Kiln disasters are expensive drama. After invoices had to match what the door saw, I stopped pretending chat logs were a system of record—thinking specifically about Glaze Shelf.

[2:43]Dhaval: Take me to the week you seriously started; the Glaze Shelf build is where that landed. Was there a single breaking point—a wrong total, an angry text, a support ticket that made you snap—or was it slower burn; the Glaze Shelf build is where that landed?

[4:04]Blake Kumar: There was a moment that still makes me wince (Glaze Shelf thread). I trusted user-submitted temps; a kiln misfired. Verified badges and studio admin roles shipped. I quit pretending fresher tabs and louder reminders were the same as governance; the Glaze Shelf build is where that landed.

[5:25]Dhaval: You chose Flutter for a lot of that work; the Glaze Shelf build is where that landed. Skeptics say any stack can ship CRUD—thinking specifically about Glaze Shelf. Why this one for you—not in doctrine, but in your actual week—thinking specifically about Glaze Shelf?

[6:47]Blake Kumar: Flutter list/detail, camera search for barcode-ish codes, local cache. In the Glaze Shelf story: i had tried the shiny thing first and spent a month wiring glue code I did not understand. In the Glaze Shelf story: boring won because I could reason about failures at two in the morning.

[8:08]Dhaval: What did the embarrassing first version look like; the Glaze Shelf build is where that landed? Not the story you put on the landing page—the one you almost did not ship; the Glaze Shelf build is where that landed.

[9:29]Blake Kumar: It was ugly on purpose [Glaze Shelf] (Glaze Shelf thread). One form, no onboarding, emails that looked like they came from 2003 (Glaze Shelf thread). But it replaced three tools if you squinted (Glaze Shelf thread). I shipped on a Tuesday knowing I would apologize for the UI for months (Glaze Shelf thread). The apology tour taught me what people actually cared about (Glaze Shelf thread).

[10:51]Dhaval: Who was the first person who was not your cousin who treated it like a real service—and what did they do that surprised you—thinking specifically about Glaze Shelf?

[12:12]Blake Kumar: In the Glaze Shelf story: a small business owner sent a voice memo walking through their workflow. Nine minutes. In the Glaze Shelf story: i listened twice. In the Glaze Shelf story: they were not asking for features; they were narrating fear tied to Glaze Shelf—fear of double booking, fear of looking sloppy in front of clients. In the Glaze Shelf story: that memo became our roadmap for a quarter.

[13:33]Dhaval: Tell me about a failure that was your fault—not a vendor outage, not "the users did not get it." Something you shipped that hurt; the Glaze Shelf build is where that landed.

[14:54]Blake Kumar: I trusted user-submitted temps; a kiln misfired; the Glaze Shelf build is where that landed. Verified badges and studio admin roles shipped; the Glaze Shelf build is where that landed. I stayed up until four fixing it, not because I am a hero, but because I could not look the pickers in the eye otherwise (Glaze Shelf thread). The fix was smaller than the lesson: turn on the scary constraint before the friendly notification (Glaze Shelf thread).

[16:16]Dhaval: How did you tell people it existed—thinking specifically about Glaze Shelf? This crowd listening is tired of growth hacks; they want the honest channel that actually moved you—thinking specifically about Glaze Shelf.

[17:37]Blake Kumar: In the Glaze Shelf story: word of mouth in one niche community. In the Glaze Shelf story: i posted a walkthrough that showed the messy backend on purpose—permissions, audit trail, the stuff buyers worry about when they have been burned before. In the Glaze Shelf story: one thread turned into demos, demos turned into annual plans. In the Glaze Shelf story: i never cracked paid ads; I am fine with that.

[18:58]Dhaval: Where is the product today versus that first ugly Tuesday; the Glaze Shelf build is where that landed? What are you proud of—and what still keeps you up; the Glaze Shelf build is where that landed?

[20:20]Blake Kumar: Proud of the operators who trust it with money and time [Glaze Shelf] (Glaze Shelf thread). Still up at night: edge cases around holidays, permissions when volunteers rotate, and explaining to new teammates why we chose simplicity over cleverness (Glaze Shelf thread). The stack is not the story; the people using it are (Glaze Shelf thread).

[21:41]Dhaval: If someone listening is about to start their own thing in Flutter—maybe nights-and-weekends, maybe between jobs—what is the one thing you wish someone had told you before line one of code; the Glaze Shelf build is where that landed?

[23:02]Blake Kumar: In the Glaze Shelf story: ship the smallest thing that replaces a real ritual for a real person. In the Glaze Shelf story: everything else is procrastination dressed as architecture. In the Glaze Shelf story: you will rewrite anyway; you might as well rewrite something people already depend on.

[24:24]Dhaval: Last one: where should people go to see Glaze Shelf in context—not the hero marketing line, but the everyday use?

[25:45]Blake Kumar: The public site is the polite cut (Glaze Shelf thread). The changelog, how we answer support, and what we admit in incident notes—that is where you learn if we are serious (Glaze Shelf thread). Thanks for letting me ramble; the simple version is edited (Glaze Shelf thread).

[25:46]Dhaval: In the show notes you wrote “Cone numbering helper.” Where did that line earn its keep—in a ticket, a demo, or a finance question?

[26:45]Blake Kumar: It showed up when I was talking about community studios, member dues, and kiln gods humor. We wired Flutter so that constraint was boring to enforce—because if it is exciting, it is probably wrong (Glaze Shelf thread).

[27:45]Dhaval: Someone skimming docs sees “Studio-only mixes private” and shrugs. What story do you tell them so it lands as a requirement, not a buzzword; the Glaze Shelf build is where that landed?

[28:44]Blake Kumar: Honestly, that bullet was a scar (Glaze Shelf thread). Customers asked in plain language; we answered with logs, not slides (Glaze Shelf thread). Studio-only mixes private is how we stop relitigating the same panic.

[29:44]Dhaval: If you cut scope and had to keep one operational promise, is “Firing log export” still on the list—and why?

[30:43]Blake Kumar: The week it mattered, nobody said the phrase “Firing log export” out loud—they just needed the system to behave. Flutter list/detail, camera search for barcode-ish codes, local cache—thinking specifically about Glaze Shelf.

[31:42]Dhaval: How does “Safety MSDS links” change behavior on a bad Tuesday versus a calm Wednesday?

[32:42]Blake Kumar: We almost cut it for time (Glaze Shelf thread). Keeping it meant slower features elsewhere, but fewer apology emails (Glaze Shelf thread). I was talking about community studios, member dues, and kiln gods humor.

[33:41]Dhaval: What broke first if you ignored “Tile photo grid” in v1?

[34:41]Blake Kumar: In the Glaze Shelf story: finance and support had different nouns for the same fear. “Tile photo grid” became the shared word after one ugly thread.

[35:40]Dhaval: You told us “Blake talks community studios, member dues, and kiln gods humor.”—if budget gets halved, what is the first Flutter thing you strip without lying in the UI?

[36:39]Blake Kumar: I would delete demo-only paths before I touched anything that touches money or consent (Glaze Shelf thread). I was talking about community studios, member dues, and kiln gods humor; the Glaze Shelf build is where that landed. The honest cut is whatever still lets someone sleep after a bad deploy (Glaze Shelf thread).

[37:39]Dhaval: That detail—“We hear why photos beat paragraphs.”—sounds emotional. What is the coldest technical tradeoff underneath it—thinking specifically about Glaze Shelf?

[38:38]Blake Kumar: The feeling in that sentence is the spec for Glaze Shelf. Underneath it we chose boring primitives in Flutter so incidents replay without mythology—grounded in why photos beat paragraphs.

[39:38]Dhaval: Picture a new hire reading “Craft software should survive clay hands.” on day three. What do they need in the repo so it is actionable; the Glaze Shelf build is where that landed?

[40:37]Blake Kumar: A day-three hire needs a failing test and a runbook paragraph, not a pep talk (Glaze Shelf thread). We tied “Firing log export” to a checklist so onboarding does not depend on tribal memory.

[41:37]Dhaval: Zoom out from features: what signal told you Glaze Shelf was working before revenue looked obvious?

[42:36]Blake Kumar: In the Glaze Shelf story: repeat behavior without bribery—people opened the same screen on Monday morning without me nudging. My studio had hundreds of test tiles nobody could search. Glaze Shelf is the pocket index with firing temps and “who brought this bucke…

[43:35]Dhaval: What is the most underrated “boring” practice that kept Glaze Shelf trustworthy?

[44:35]Blake Kumar: Naming things the way operators name them (Glaze Shelf thread). Labels faded; members mixed incompatible layers; the Glaze Shelf build is where that landed. Kiln disasters are expensive drama; the Glaze Shelf build is where that landed.

[45:34]Dhaval: Tell me about one integration or vendor decision you would not repeat—but you are glad you made once—thinking specifically about Glaze Shelf.

[46:34]Blake Kumar: In the Glaze Shelf story: we bought speed with coupling, then paid it down. I trusted user-submitted temps; a kiln misfired (Glaze Shelf thread). Verified badges and studio admin roles shipped (Glaze Shelf thread). The lesson outlived the shame; the Glaze Shelf build is where that landed.

[47:33]Dhaval: If Glaze Shelf is not a generic SaaS playbook, what is the one habit a copycat would still get wrong?

[48:32]Blake Kumar: Copying the stack without copying the shame (Glaze Shelf thread). In the Glaze Shelf story: flutter list/detail, camera search for barcode-ish codes, local cache. The product is the receipts, not the logo (Glaze Shelf thread).

[49:32]Dhaval: Lightning round: one ritual you would install in week one if you replayed Blake's calendar?

[50:31]Blake Kumar: For Glaze Shelf, paper or CSV receipts before another abstraction. My studio had hundreds of test tiles nobody could search—thinking specifically about Glaze Shelf. Glaze Shelf is the pocket index with firing temps and “who brought this bucket.” Let Flutter follow the ritual, not replace it.

[51:31]Dhaval: Where should someone start if Glaze Shelf is only adjacent to their problem—without cloning your whole stack?

[52:30]Blake Kumar: One plain sentence about the job Glaze Shelf actually does—then attach Flutter only where that sentence already hurts. Glaze Shelf stayed honest because the story we kept quoting—“My studio had hundreds of test tiles nobody could search. Glaze Shelf is the pocket index with firing temps and “who brought this bu…”—kept vetoing roadmap fiction.