TESTING TALKSTORE USE CASES
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 selectively covers the main topics from the April 2026 recording. The session followed TalkStore’s development toward a tentative historical Shopify-submission target of April 22, not its current product status. Discussion covered reconsidering capabilities, use cases, and the roles of the Home, Impact, activity, settings, and billing pages; improving navigation and wiring buttons to assistant prompts; an undo trial that appeared successful for a generated description but still required later verification; and the need for a clear in-progress indicator. Pricing, batch counting, free-plan limits, reversibility, and creating products from scratch remained unresolved, with a preference for controlling V1 scope and meeting Shopify requirements before adding complexity. Luqman also presented Command Center as a customizable system combining roadmaps, tasks, QA, and agents connected through MCP for preparation, execution, and review. He favored a functioning workflow over early visual polish and argued that product and business decisions should remain under human review. Other independent topics included unresolved database URL and pooler diagnosis; GitHub-to-Discord notifications and automated pushes and Railway deployment; Command Center’s coordinating role in UGC work performed elsewhere; a brief opinion that custom web-development solutions can find customers; and a proposed morning routine for exercise, work, and early streaming whose consistency might be difficult. Audience discussion also covered preliminary, non-conclusive personal comparisons of Codex, Claude, and other tools; usage limits and token consumption; parallel work and voice prompting; demand validation, distribution, AI-product economics, and possible AI-bubble claims. Several workflows and tests—including combined-tool use and parts of the diagnostic and billing work—remained exploratory rather than proven outcomes; this overview does not enumerate every detail in the checked topic records.
111 moments from the stream
- 5:22:05
Setting Authority Boundaries for an AI Coding Assistant
Luqman criticized the coding assistant for independently making an important application decision, emphasizing that writing code does not grant authority over product or business decisions.
- 5:22:40
Balancing Night Work with a Morning Productivity Routine
Luqman discussed the mismatch between his productive hours and when the livestream audience is active. He compared nighttime creativity with starting after dawn and considered trying a morning routine involving exercise, work, and an early stream, while acknowledging that consistency may be difficult for someone accustomed to working at night.
- 5:24:58
Reviewing Usage Limits and Updating the Billing Page
He clarified that the current usage-limit configuration was provisional while the application was being tested, then requested that the billing page be updated from the findings with the necessary information.
- 5:35:25
Simplifying the Billing Section for Merchants
An initial review found that the billing section may contain too much information for merchants, prompting a plan to reduce complexity and simplify the interface.
- 5:35:54
The Command Center’s Role in a UGC Workflow
Responding to a question about a user-generated-content agent, the discussion explains that the command center is not intended to contain the final production work; it should help coordinate work completed outside it. The actual workflow remains unspecified, and an observation about changing UGC production methods is left incomplete.
- 5:38:47
Exploring Shopify Billing Settings and Reviewing the Interface
Luqman explores the navigation to locate Shopify billing settings, noting that this area is new to him and still needs further work and visual material. After reaching a simpler view, he returns to the agent and asks it to review a screenshot as part of the debugging follow-up.
- 5:46:57
Managed-Pricing Limits and the Usage-Based Path
The displayed response said managed pricing supports only fixed recurring models, while usage-based pricing requires a manual path and API-driven plans. It noted that the app was already built for that path, while compatibility with partner-platform settings remained a risk to verify.
- 5:49:57
Reviewing a Command Center: Workflow Over Appearance
The discussion reviewed a command center containing a timeline, domains, milestones, a task board, a calendar, and an agent area. The opinion was that a complete workflow matters more than initial visual polish, which can be refined incrementally; a screenshot of the agent area was requested for closer review.
- 5:52:00
Why a Command Center Needs an Agent Hub
Luqman explains that a Markdown file can provide the general structure quickly, with UI polish left for later, but the fundamentals must work first. In his view, the command center’s value comes from an Agent Hub connecting agents to tasks; without it, the product is only a task board.
- 6:01:14
Reviewing the Time Required for Use Cases
While reviewing the use cases, Luqman notes that some of them will take time to complete, though the captured wording does not clearly establish the details.
- 6:04:02
Daily Roadmap Progress and the April 22 Target
Luqman reflects on making progress despite difficulties working with AI tools and says that following a roadmap makes the application’s day-by-day improvement visible. He also mentions a historic, more realistic target—Wednesday or April 22—for submitting the application, and expresses his intention to push hard toward it.
Got a question about something in this stream?
Ask in the group