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
- 0:58:49
How to Present 18 Use Cases
A clear split between two pages is mentioned, followed by the question of how to present and reorganize the 18 use cases. Some details of the proposal are unclear in the captions.
- 0:59:29
The Market Teaches What Building Alone Cannot
A practical argument that developers should not only build one project after another; they should take what they have built to market and observe user response, because real market exposure provides lessons that technical building alone cannot.
- 1:00:35
AI Product Unit Economics in Some Arabic Markets
The speaker argues that some Arabic markets may contain many problems and opportunities, yet products serving them can face foreign-currency service costs against local-currency revenue. He suggests minimizing variable costs, favoring fixed costs where possible, and relying on broad adoption, while noting that AI and database expenses may still grow with usage.
- 1:04:02
Focused Work and Voice vs Typed AI Prompting
The speaker considers quieter, more focused work sessions and compares voice with typed instructions for AI agents: writing offers more structured context and suits important tasks, while voice is faster but may be less precise. In his view, agents have become better at following overall direction, though careful supervision remains necessary; he also explores prompting in Arabic and translation behavior.
- 1:10:54
Arabic Voice Dictation Instead of Typing
A discussion of using voice input when working in Arabic, including the possibility of creating an Arabic-specific voice or using a multilingual service to work faster.
- 1:14:43
Prioritizing TalkStore Development
A proposed TalkStore work sequence covers logic, impact and home pages, retention and churn measures, and settings, while reserving the chat interface for dedicated attention. It is presented as an ambitious goal, not completed work.
- 1:15:49
Choosing Voice Tools for Workflow Comfort
A personal trial of local Whisper did not produce a major difference for conversational coding; the takeaway is that voice input is optional and users should choose the workflow they find most comfortable.
- 1:18:26
Reviewing TalkStore Billing and Task Weighting
A review of TalkStore’s changing billing strategy compares answers from two models to identify overlap and gaps. It highlights the risk of treating unequal tasks as equivalent units, which could make a merchant overpay for a small change.
- 1:22:18
Pricing and Billing Models for TalkStore
A comparison of simple subscriptions, task-based billing, and credits, including how to handle single items while keeping the pricing table practical and straightforward. The discussion also suggests agreeing on the model before drafting the full table.
- 1:27:47
Tracking Completed Work in the Calendar
Although the work session proceeds flexibly, the speaker wants every completed item recorded in the calendar so progress and outcomes can be reviewed at a glance.
- 1:29:23
Making Settings Functionally Meaningful
The speaker says he likes the settings as they are today, but describes them as largely a gimmick because they do not meaningfully affect the AI or TalkStore, leaving room to deepen their functionality.
- 1:30:40
An Impression of Claude and Usage Monitoring
Responding to a question about the day’s experience, the speaker perceives a noticeable difference and describes Claude as strong, while expressing general concern about checking usage and deferring fuller observations; this segment does not provide a complete comparison.
- 1:31:35
A Personal Comparison of Claude and Codex for Coding Tasks
At the time of the recording, based on his personal experience and comparisons on similar problems, the speaker regarded Claude as one of the strongest models then available and said it sometimes noticed issues Codex missed. He also felt that some single-agent work had become faster, while token consumption remained an important trade-off.
- 1:33:28
How Adaptive Thinking Balances Reasoning and Token Use
The speaker explains that adaptive thinking decides when a problem needs deeper reasoning instead of enabling it for every request. In his account, this is intended to avoid spending extra tokens on simple questions while retaining deeper reasoning when needed.
- 1:34:06
Claude Token-Usage Concerns as of April 16
The speaker says adaptive thinking may consume roughly 35% more tokens and reports that Claude had faced a token-related problem from March 23 through the recording date of April 16. He suggests its persistence may represent a new normal, presenting this as his view at the time rather than a confirmed conclusion.
- 1:35:14
Using “Coming Soon” Labels for Future Settings
While reviewing a visually rich settings page, the speaker proposes keeping useful, nonredundant options even when they are not yet supported, marking them “Coming soon” instead of deleting them. He also notes that the application is not shipping immediately, allowing future planning to remain distinct from current readiness.
- 1:37:33
An Impression of Cursor’s UI-Building Capabilities
The speaker describes Cursor as particularly strong for UI work, based on his impression of a demo he saw. This is a personal assessment, not a documented test on this page.
- 1:38:26
What Would Justify Calling AI a Bubble?
Responding to an audience opinion about pricing and a possible bubble, the speaker distinguishes an individual company from the broader AI market. He argues that calling the field a bubble requires a well-developed rationale, noting that major technologies such as the internet also faced similar skepticism even though real bubbles have occurred historically.
- 1:41:36
Are AI Company Valuations a Bubble?
A discussion of the view that the gap between some AI companies’ valuations and revenue may indicate a bubble, while stressing that this is not conclusive evidence and that confident predictions exceed the limited information available to the public.
- 1:43:36
Building a Product Is Not Enough Without Distribution
A practical opinion attributes a software project’s growth to clear direction and sustained work, emphasizing that marketing the product and building an audience are essential alongside technical development.
Got a question about something in this stream?
Ask in the group