Building Unfair Advantages
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 follows the ongoing development of Burnish as a GEO application in the Shopify ecosystem. A central workflow uses Claude in Chrome to study competitor products and designs, then passes findings and review feedback to Codex for implementation and debugging, with human inspection still required. Luqman also discusses preparing the go-to-market foundation before spending on ads: analytics and attribution, landing-page, headline, and pricing experiments, lead qualification, and a unified metrics dashboard. He makes clear that many forecasts and experiments were not yet complete. Practical work exposes late-stage difficulties, including a mobile-performance regression after some changes, followed by a clearly measured improvement after a later deployment; whether that gain justified the design compromises remained unresolved. The work also covers deployment and Git-branch friction, pull-request checks, accessibility reviews, and Shopify requirements. Some deployments succeeded, while other technical questions remained open. Audience discussions broaden into multi-agent coordination and usage limits, learning SEO, GEO, and development, the growing importance of marketing and distribution as AI makes building easier, and choosing a familiar market. A substantial secondary thread covers content and audience strategy: batching short-form content or temporarily pausing it to focus on building, building in public, weighing Arabic against North American audiences, YouTube monetization and sponsorships, and livestreaming as both a focus aid and a possible distraction, alongside rest and burnout prevention. The stream documents an unfinished process of development, research, and market preparation rather than a completed launch, with several decisions still requiring measurement and review.
151 moments from the stream
- 6:28:08
Strengthening the Hero and Marketing from Conviction
The homepage hero was considered too dark and in need of slightly stronger treatment. The speaker also argued that genuine confidence in a product’s effectiveness becomes visible in the marketing and the work, and customers can sense it.
- 6:29:45
From Frontend Progress to Backend Wiring
After substantial progress on the design and frontend, the next priority was wiring the application to its backend and continuing frontend and backend development together.
- 6:34:20
An Evolving AI-Assisted Development Workflow
The speaker liked a substantially changed workflow even though its evolution was hard to articulate, using AI tools to hand off development tasks and track them through review.
- 6:36:09
Diagnosing a Mobile Performance Regression Instead of Guessing
The latest version showed worse mobile performance and no longer displayed MP4 videos that had appeared earlier. The speaker called for a deeper investigation into the responsible change instead of further guessing, noting that replacing the video with a CSS-only background had not produced the expected improvement and that the desktop version also needed checking.
- 6:41:03
Reviewing Competitor Websites Before Completing the Ads Work
Before completing the advertising work, the plan was to give the website a final polish informed by comparisons with Shopify competitors. The review highlighted presentation quality and strong customer reviews, while the speaker cautioned against publishing a long video that reveals the entire application workflow in this competitive industry.
- 6:53:58
Giving a Coding Agent Visual Access to a Web App
Luqman explains that he wants Codex to open his web application, inspect its appearance closely, and access the console and development tools so it can diagnose issues on his behalf. He compares this with his experience of a browser extension that lets Claude perform this kind of inspection and explores how Codex might gain similar access.
- 6:56:27
Simplifying a Moving Visual Element on Mobile
Luqman discusses a moving graphic that follows the page while scrolling. Although he likes its appearance, he decides to remove it entirely on mobile, illustrating a responsive-design trade-off for smaller screens.
- 6:58:07
Balancing Reactivity and Proactivity in Coding Agents
Luqman compares the interaction styles of Codex and Claude, describing Codex as more likely to provide information and stop while Claude advances the work at selected moments. He notes that prompting Codex to be more proactive can sometimes produce excessive intervention, highlighting the need for selective, well-calibrated initiative.
- 7:00:51
Measuring a Website Performance Improvement and Its Design Cost
After committing and deploying the change, Luqman compares the mobile performance result with the earlier baseline and observes a clear improvement. He then questions whether the gain justifies the design compromises before moving toward an accessibility audit as the next task.
- 7:13:14
Testing Codex Access to a Specific URL
The speaker started a new Codex session to test whether it could access a specific URL, with a brief comparison to Claude. The captions do not establish the test result.
- 7:19:56
Unapplied Prisma Migrations in Development
A brief fragment reports that two new Prisma migrations had been created but not applied to the development database; the wider issue and diagnosis remain unclear.
- 7:27:00
Listing Social Platforms in Burnish’s Go-to-Market Plan
A request to extract the planned social-media platforms from Burnish’s go-to-market section.
- 7:32:03
Recovering the Workflow After Closing an MCP Group
While restarting the dev process, a request was made to reopen an MCP group closed by accident so a link could be pasted.
- 7:38:34
Checking a Shopify App for WCAG 2.1 AA Compliance
A question is raised about whether Shopify App Store partner guidance means the app itself must meet WCAG 2.1 AA. The captions do not confirm the requirement, but the speaker flags verification as an important task that may have been missed.
- 7:39:34
Recommending Codex for Coding Work
The speaker recommends Codex over an alternative whose name is unclear in the captions, relating the choice to the type of work and usage limits while acknowledging uncertainty about some plan details at the time.
- 7:41:28
Pushing Changes Before the Merge Decision
The discussion selects an option intended to avoid violations, then proposes committing and pushing while waiting for a pull-request merge decision. It also asks whether to merge the current work before the next phase and defer fast-follow items until after launch.
- 7:44:13
Web Accessibility Under WCAG 2.1
The discussion identifies WCAG 2.1 as an internationally recognized web-accessibility standard and notes that website design must account for requirements such as color contrast to avoid accessibility violations. It also stresses that hands-on testing can reveal small details missed by general guidance but capable of becoming problems later, especially when proceeding cautiously in a Shopify context.
- 7:50:17
An Old App Version Appearing After Reinstallation
While troubleshooting an app, it was uninstalled and reinstalled, but the old version appeared instead of the latest work. The speaker asks whether this is a warning sign and what development step to take next; this page provides no confirmed diagnosis or resolution.
- 7:57:15
Safely cleaning up a duplicate development app
He performed a sanity check on an accidentally installed duplicate Burnish app, distinguishing deletion from the app-development environment from affecting its Shopify Dev Store presence before cleaning it up.
- 8:01:26
Balancing pre-merge checks with platform requirements
He discussed the checklist before opening a pull request, clarifying that the build was not a final public release and would receive further audits. At the same time, he noted that platform-requirement violations should not be ignored because they could affect Shopify app acceptance, even when the rules constrain design choices such as colors.
Got a question about something in this stream?
Ask in the group