ALMOST 70% BUILT
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 documents the practical development of Burnish, a product beginning on Shopify and exploring how stores can improve their visibility in AI answers and platforms through GEO. Much of the work centers on the website and product message: clarifying the problem, solution, and customer outcome; structuring the homepage and pricing page; routing “Scan My Store” calls to action consistently; and refining cards, contrast, mobile layouts, scroll interactions, and a floating 3D logo. Visual reviews repeatedly led to revisions or removal of immersive effects when they distracted from the product, alongside recognition that excessive polish could delay shipping. The pricing experience advanced, but the homepage and especially the scan flow still required substantial frontend and backend work. The proposed scan collects a native Shopify store address and business email, then leads toward a deeper AI-visibility report. Important questions remained unresolved, including audit cost, the instant result or teaser, brand-name detection, usage limits, protection of shared public infrastructure, report-email delivery, and the terms of a refundable reservation. The discussion emphasized honest scarcity indicators and responsible marketing claims. Lighthouse and browser inspection provided preliminary performance signals, but measurements from an older site were not treated as final evidence for the heavier new version; screenshot and animation problems also remained under investigation. For implementation, Luqman compares Claude and Codex and assigns design, backend, migration, and audit work according to their perceived strengths. The workflow uses separated specifications, milestones, dependencies, a Command Center, coding agents, audits, and human visual review. His practical conclusion is that specific instructions, clean context handoffs, and deliberate sequential work are often more manageable than too many simultaneous sessions. The stream does not establish that every migration, audit, or automated workflow was completed successfully. The broader discussion turns to go-to-market work: validating demand before launch, building a list and organic distribution, warming an email domain, and testing advertising or direct sales in phases. Luqman argues that market response—not personal enthusiasm—is the real test of an idea, and that a strong product still needs marketing and distribution. He presents GEO and AEO as emerging relatives of SEO; based on his reading of trends, he observed growing interest during 2025 and predicted further growth by September 2026, explicitly as an opinion rather than confirmed market evidence. Audience questions also cover whether non-developers can build with AI, learning by doing, Micro-SaaS and B2B opportunities, model and hosting choices, and choosing Telegram or Discord for an Arabic-speaking community. Overall, this is an unfinished build-and-validation journey rather than a completed launch, with product viability and growth channels still awaiting real market evidence.
163 moments from the stream
- 0:50:50
Finishing the Pricing UI Polish
A practical review of the remaining pricing-page work: improve the calls to action and hero, place effects behind cards with suitable transparency, shorten the scroll, and use the logo animation to illustrate the working loop. The speaker feels the polishing has gone far enough and wants to move on to the remaining core pages.
- 0:52:19
Designing an AI Visibility Scan for a Store
An analysis of a scan experience that shows where a brand was mentioned across several AI tools and surfaces citations. The speaker considers its speed, expects his own implementation to take longer, and probes the result logic using a site that has not launched yet. After some uncertainty, he concludes that some signals may be valid while retaining caution about results that appear overly polished.
- 0:54:40
Validating Demand Before an App Launch
A pre-launch strategy that begins by collecting an email address and store URL, then offers a refundable reservation for an early cohort receiving priority and hands-on audit and planning help at launch. The reservation is intended to distinguish serious interest and improve the likelihood of initial users while marketing and list-building continue during the approval wait. The speaker also considers making the availability counter transparently reflect real progress.
- 1:00:39
Improving Button Contrast Against the Background
A visual review notes that some buttons do not contrast clearly with the background and suggests adjusting them so they are easier to distinguish.
- 1:03:18
Adjusting a 3D Logo’s Scroll Layering
An analysis of a floating 3D logo’s scrolling behavior, aiming to move it one layer back in the visual stack and place it behind the front card.
- 1:04:50
Working on Multiple Tasks Across Parallel Sessions
A practical discussion about opening multiple pages or sessions to work on more than one task at the same time.
- 1:05:24
Auditing Calls to Action and User Paths
A task to analyze every call to action on the site, identify the primary CTA, clarify its purpose, and determine where it takes users, with a general note that the work has some connection to the backend.
- 1:06:42
Why Mobile Optimization Requires Layout Rework
An explanation that mobile optimization can take substantial time because it is not limited to small code changes; several parts of the layout may need redesigning and previously tuned elements may need further adjustment.
- 1:07:38
Migrating from Polaris React to Polaris Web Components
The frontend migration from Polaris React to Polaris Web Components is treated as an important application-development milestone, with the work organized into a set of tasks on the project board.
- 1:08:19
Checking Page Load with Lighthouse
In response to a question about site loading, Lighthouse is used to review categories such as performance, accessibility, and SEO and compare results. The speaker suggests that the measured load time should be below two seconds.
- 1:11:16
Analyzing Landing-Page Performance and Purpose
The discussion covers analyzing the site through browser developer tools and keeping the landing page focused on receiving visitors and prompting a simple action. An older, content-light version was measured, with the qualification that its results will change once the real content launches, so the current measurements are only an early signal.
- 1:13:40
Refining Logo Layers and Scroll Effects
The review keeps the logo’s size, position, and effect unchanged while making it pass behind visible cards rather than entire sections. It also addresses an overly fast scroll-driven typing effect, reuses an existing pattern for an e-commerce index, and defines a scroll cycle through measure, fix, prove, and remeasure before returning to the landing page.
- 1:24:30
Planning Implementation with Agents and Dependencies
The work is framed as a phased plan or a task for parallel agents, with sufficient context and explicit dependencies for milestones that may block other work. The review also covers matching scan submission to a local API, refining calls to action, and identifying controls that look like CTAs but are inert.
- 1:29:22
Visual Polish and Its Relationship to Conversion
After confirming that the logo moves behind elements, the review continues with its placement and snap behavior near the footer. These changes are treated as extra polish, but still considered important because the page receives inbound traffic and presentation quality may affect conversion.
- 1:31:05
Separating Product Development from Go-to-Market
He distinguishes product-development progress from go-to-market progress and explains that a product’s final stages can take disproportionately long despite appearing small.
- 1:32:41
Formal Education and Experience in the AI Era
Speaking from personal experience, he argues that formal education has a different role in today’s market and AI era, while explicitly avoiding presenting this as advice to abandon education.
- 1:33:52
Routing Primary Calls to Action Consistently
He works on routing the primary free-scan calls to action to one page while excluding buttons such as pricing, and identifies mobile optimization as a remaining frontend task before shifting focus.
- 1:36:21
Describing the GEO Application in One Sentence
He formulates a concise description of a GEO application for merchants seeking better visibility across multiple AI platforms; the platform name and some details are unclear in the captions.
- 1:37:42
Choosing to Build for an Arabic-Speaking Audience
He explains choosing an Arabic-speaking audience despite seeing possible advantages in an English-speaking or North American audience, attributing the decision to a gap he perceives in serving Arab audiences while considering other marketing channels.
- 1:38:31
A Practical Build Journey, Not a Course
He explains that the stream documents a real working journey rather than a structured course, so viewers need not begin with the earliest recording. He considers practical experience potentially more valuable than theoretical instruction while leaving the journey’s outcome uncertain.
Got a question about something in this stream?
Ask in the group