THE CLEANUP EPISODE
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
This stream documents a broad TalkStore refinement phase for a Shopify merchant assistant designed to move from questions and store diagnosis to user-approved actions. Practical work focused on redesigning the chat interface, navigation, conversation history, structured findings, messaging, Markdown rendering, and loading states, with a restrained dark visual direction that communicates value without clutter or decorative excess. Product-description flows were tested and layout, navigation, and Findings defects were reviewed; some improvements were implemented, but the Findings 500 error and slow startup and navigation were not conclusively resolved. SSR, hosting architecture, sequential requests, and N+1 queries remained hypotheses requiring better measurement. Luqman also discussed keeping V1 deliberately scoped and shipping before over-polishing, followed by backend, security, and compliance reviews before Shopify submission, while reporting defensible impact such as time saved and catalog quality instead of revenue attribution. Other useful discussions covered model selection and routing through OpenRouter, Crisp support integration, early review and trust challenges, historical Build for Shopify badge requirements shown during the recording, and validating future product ideas with ads and landing pages. In response to audience questions, he described the Arabic-focused channel as a step-by-step record of taking projects from idea and validation through building and marketing, while agent conversations are conducted in English.
69 moments from the stream
- 4:05:35
Support Chat Options for a Shopify App
A research question is raised about the best way to add support chat inside a Shopify app: whether to build it in-house or use an external service, and which companies provide suitable solutions.
- 4:09:03
Integrating Chat Support into a Shopify App
A discussion of support options for an embedded Shopify app, proposing that Shopify’s native “Get support” action be wired through App Bridge to open the same Crisp messenger. The suggested approach is to begin with a lightweight third-party solution offering real-time replies, notifications, email fallback, and message continuity instead of building a custom chat system that would not differentiate the product.
- 4:13:27
Diagnosing Slow Navigation Beyond Server Processing
The initial theory was that network round trips between Egypt and servers in the US West were the bottleneck, leading to a proposal to render the interface and a loading skeleton immediately while data loads in the background. Restarting the development environment and performing a hard refresh produced almost no improvement, while other Shopify apps appeared fast from the same location. That weakened a geography-only explanation and pointed toward measuring the interval from iframe opening to the first visible UI; an N+1 query fix was still considered worthwhile later.
- 4:19:15
Interface Speed as a Core Part of UX
The discussion frames navigation speed not as cosmetic polish but as a practical requirement for working efficiently on the interface and an important part of UX quality. A comparison with a larger, responsive app is used as evidence that the application or its hosting may have a more specific issue requiring deeper diagnosis.
- 4:21:31
A Channel Documenting Projects from Idea to Market
In response to a question about where to begin with the channel, the streamer explains that it is not organized as conventional standalone videos. Instead, the streams document project work step by step—from finding a potential idea through building and marketing the product—from the perspective of a vibe coder and operator.
- 4:22:14
Building and Testing Products Publicly with a Project Command Center
He describes a practical workflow of testing an idea in the market, building it, and marketing it publicly while tracking the work and exposing both problems and positive developments. He also emphasizes establishing an organized project command center before accelerating implementation.
- 4:23:16
Diagnosing SSR Latency: Hosting Regions or Deployment Architecture?
The discussion examines why latency remains after client-loader changes when the server loader still runs through SSR. It considers keeping Railway and Supabase in the same region, the migration cost of moving the database, and the performance difference between a single-origin server and globally distributed edge infrastructure. Cloudflare and Vercel are raised as possible approaches, and a VPN is suggested for testing another region’s user experience; these were discussion-stage recommendations, not verified test results.
- 4:32:36
Preparing a Shopify App for Review and Submission
A plan to finish UI/UX polish and backend work, then conduct agent-assisted reviews and a line-by-line compliance check using the submission checklist. The historically stated aim was to submit before April 17, with acceptance by late April and marketing in May presented as possibilities, not guaranteed outcomes.
- 4:34:33
Testing App Ideas While Awaiting Review
A discussion of using the Shopify review waiting period to test demand for other app ideas through landing pages and advertising, then using market response to decide what merits building in parallel. The review period was estimated at two weeks to a month, not stated as a certainty.
Got a question about something in this stream?
Ask in the group