Days From Shopify
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
The stream centers on developing a Shopify app for improving merchants’ visibility in AI answers, including reviews of the reputation and discovery sections, presence-score design, intent-based query ranking, and clearer presentation of answers and research. Luqman argues that measurement should use web-grounded research across multiple engines, while provider quality, cost, and policy-compliant access must be verified; the scoring formula, engine selection, parts of the product architecture, and pricing remain unresolved. The work also covers Market Scout planning, an activity log and dashboard, onboarding, quality checks, and Shopify submission preparation, alongside inconclusive troubleshooting of Shopify and Claude outages and YouTube chat auto-translation. Audience discussions include GEO versus SEO, AI coding-tool limits and pricing, livestreams as shared workspaces, professional networking, and cybersecurity careers, while distinguishing responsible vulnerability disclosure from harmful or unlawful suggestions.
59 moments from the stream
- 2:30:08
An Opinion on Cybersecurity Career Opportunities
In a career discussion, the speaker described cybersecurity as a strong computer-science field and argued that limited local awareness does not mean opportunities are absent, including possible contract work abroad. He suggested researching demand more deeply; these were his opinions rather than verified labor-market findings.
- 2:32:04
Cybersecurity Awareness and the Limits of Proving Vulnerabilities
The speaker argued that some Egyptian organizations show less cybersecurity awareness than organizations abroad and discussed persuading clients by demonstrating a vulnerability. The proposed framing relied on unauthorized compromise and fear, making it an irresponsible approach rather than a recommended lawful disclosure process.
- 2:41:29
Claimed University Compromises and Unanswered Messages
A person claimed to have compromised three universities and sent many messages without receiving a response, adding that a promised reward was still pending. The reply joked about threats and retaliation; these were harmful remarks, not legitimate guidance for handling vulnerabilities.
- 2:44:52
How GEO Differs from SEO
The speaker explains GEO by comparison with SEO: AI systems may weigh reviews, source quality, and relevance to the question rather than relying only on what a brand says about itself. In his observation, search-grounded answers are more accurate than answers drawn from model memory but cost more, so he argues that correctly measuring visibility through search-grounded responses should come before optimization. He describes the field as promising but still costly and less mature than SEO.
- 2:50:58
Do Headless Browsers Comply with Service Policies?
The speaker considers a suggestion to use a headless browser for search, but says he has concerns that this approach may conflict with some services’ policies, based on a warning and an inconclusive reading of documentation. He explicitly remains uncertain and says the issue needs further investigation.
- 2:52:36
Access Constraints for Google AI Overviews
The speaker discussed collecting Google AI Overview results and relayed an agent’s response that no official API was available and that headless-browser access could raise policy and reliability concerns. He remained uncertain about some policy details and favored official APIs where available.
- 2:55:14
Measuring AI Answer Visibility and Evaluating Data Providers
The discussion described comparing responses across multiple AI engines and measuring mentions, sources, sentiment, or scores for each answer. It also weighed direct engine APIs against a third-party provider that might add coverage for services without accessible APIs, emphasizing the need to verify quality, cost, and value first.
- 3:02:51
The Value of Broader Search and Answer-Engine Coverage
The speaker considered AI Overview visibility important for search and said an external provider could be useful if it unlocks engines that are difficult to access directly. He tied adoption to economic value and timing, citing Meta AI, Copilot, and Amazon Rufus as possible coverage examples rather than verified results.
- 3:06:27
The Importance of Early Shopify Reviews
The speaker noted that positive reviews are important for Shopify apps and that poor early reviews can strongly affect an app’s reputation.
- 3:08:00
Claude Outages and Impressions of AI Coding Tools
The speaker discussed a Claude outage and a session that appeared stuck, then described a personal trial of a coding tool whose name is unclear in the captions. In his experience it consumed usage limits without finishing the task, although he found it capable at debugging and interaction. He also felt Copilot understood his requests well. These were personal impressions, not benchmark results.
- 3:13:51
Discussion of a Claude Identity-Verification Announcement
At the time of recording, the speaker said the requirement might begin around July 8, with no year stated, using an identity document and selfie. He pointed to an update on Claude’s website and attributed the possible motivation to regulatory pressure, explicitly framing that explanation as his own belief rather than a confirmed fact.
- 3:15:59
Claude Usage Limits and Fair Plan Sharing
The speaker discussed his experience with a higher-usage Claude tier, saying the five-hour limit felt less restrictive while the weekly cap could still constrain heavy use. He also considered two people sharing a plan, warning that unequal consumption could create fairness disputes, while the implications of identity verification and account policy remained uncertain.
- 3:19:49
Regional Pricing Through Mobile App Stores
The group discussed whether a subscription might cost less through a mobile app store configured for Egypt. Drawing on prior experience with apps whose prices changed after switching country and payment method, the speaker suggested that some companies intentionally use regional pricing tied to purchasing power, without claiming it always applies.
- 3:24:02
Country-Specific Pricing for Apple Apps
The speaker discusses how developers may need to set prices by country and how Apple’s automatic conversions can sometimes produce outdated or unexpected local prices.
- 3:25:52
Pricing a Merchant AI Product Around Quality and Cost
The speaker argues that building the frontend before understanding backend economics can lead to unsuitable pricing. In his view, a merchant-focused product should balance output quality, delivered value, model costs, and a sustainable margin while clearly choosing its target segment.
- 3:32:58
Previewing a UI with Realistic Mock Data
The speaker proposes populating the interface with mock figures that resemble a product after some runtime, allowing the compiled results view to be assessed before real operational data exists.
- 3:33:54
Verifying Sources for AI Component Cost Estimates
While estimating the cost of several AI-system components, the speaker asks for the underlying source and questions a search result that appears implausible, emphasizing the need to avoid guessing in cost calculations.
- 3:47:15
Researching AI-engine integration without direct APIs
The speaker asked for reference review and additional research into the feasibility, cleanliness, and risk of connecting several engines, including Meta AI and Copilot, when direct APIs may be unavailable. He considered an intermediary that could operate a headless browser and expose results through an API, then chose to reassess a provider previously rejected through conceptual research rather than hands-on testing.
- 3:57:05
Prioritizing grounded search and answer quality for merchant questions
The speaker compared different configurations for discovery and reputation while using grounded search for both. He argued that merchant questions should be answered from search rather than training memory alone, prioritizing response quality despite higher cost while leaving engine selection as an open decision.
Got a question about something in this stream?
Ask in the group