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:00:14
Website Build Progress and Feedback
He reviewed progress on a software product’s website, planning to finish the remaining polish and then share it with the community for quality feedback. He said the site was coded directly without Figma or Replit, and that Claude contributed most of the current work.
- 0:02:01
Dividing Claude and Codex Roles in a Coding Workflow
He compared his practical experience with the Claude and Codex apps, finding Claude better suited to the website interface and design while Codex performed well on backend and application-engineering work. He favored focusing on a small number of sessions and organizing chats to preserve context, expecting later work to shift from intensive building toward debugging, analysis, and research.
- 0:06:37
Homepage, Visual Identity, and Footer Architecture
He reviewed remaining homepage work, including pricing, the call-to-action area, and visual polish. He described using a floating 3D logo to create a distinctive impression and designing a footer that suggests a broad site map even though several planned pages will be built gradually.
- 0:08:41
Routing Website Edits to the Appropriate Tool
He discussed assigning website tasks to Codex or Claude according to the nature of the work, judging that some simple edits could be handled by Codex without Claude. Caption gaps make further workflow details uncertain, so none were attributed.
- 0:10:41
Moving Pricing-Page Copy from a Banner into the Footer
A practical edit to remove a banner above the pricing-page footer and reuse its sentence beneath the footer heading.
- 0:12:06
Building a Landing Page Where Every Section Has a Clear Purpose
A walkthrough of a website still in development, built largely through coding, with the principle that each section should serve a distinct purpose. The design includes a problem–solution section, a visual treatment of channels, and a zoom transition into the logo, while acknowledging that some effects and details still need refinement.
- 0:14:32
Structuring a Pricing Page and Its Final Polish
A review of a pricing-page structure with recurring options, feature comparisons, and a general early-reservation mechanism before marketing. The speaker says the page is nearing completion but still needs small CTA and effects refinements, while the homepage requires more work.
- 0:16:28
Honesty in Scarcity and Reservation Indicators
The speaker argues that displaying misleading reservation or scarcity indicators may appear harmless at first but causes longer-term damage, so he prefers openly representing the real state.
- 0:17:46
Critiquing a Navigation Bar That Feels Empty and Off-Brand
An audience comment prompts a critique of the navigation bar. The speaker acknowledges that a design inspired by another site works better in its original context, while here it feels empty, poorly matched to the brand, and in need of cleanup and redesign. He concludes that refinement becomes easier once the intended result is clearly defined.
- 0:20:54
Floating or Sticky Navigation?
A comparison of floating and sticky navigation, noting that sticky navigation appears common in this field while a floating treatment may look better. The discussion considers corner radius, opacity, bar size, and suitability for a multi-page site.
- 0:22:57
A Product Page Focused on Customer Outcomes
An explanation of designing a page that lets visitors understand the product within seconds: present the problem and solution, then use language centered on customer value and business outcomes rather than showcasing the technology. A visual Shopify interface example demonstrates work on descriptions and tags without requiring lengthy reading, with each section carrying a specific message.
- 0:26:04
Planning a Programmatic SEO Blog
A brief plan to add a blog built with a programmatic SEO approach.
- 0:26:46
Comparing SEO, GEO, and Demand Trends
A discussion of the overlap between SEO and GEO services and how direct versus indirect competitors can differ by the market they serve. The speaker observes apparent SEO demand and a visible rise in interest during 2025, while explicitly saying he does not know the cause and is not claiming market expertise. The group also discusses articles designed to surface in AI answers and cites 1997 as the start of the term SEO according to the discussion.
- 0:31:53
An Opinion on B2B Opportunities in the Arabic Market
The discussion offers the opinion that the Arabic market may suit B2B products because companies can be willing to pay and direct competition may be limited in some areas, while distinguishing this from the challenges of B2C.
- 0:34:12
Specific AI Instructions Improve Results
The speaker explains that more specific instructions generally produce better results when working with AI tools, presenting this as a broad principle rather than one tied to a particular tool.
- 0:35:17
Connecting the Burnish Page Journey to the Shopify Dashboard
The discussion reviews the visitor experience as a guided journey that should maintain pace and strong content. It considers presenting three to five value wedges, then compares that with showing the Shopify dashboard more specifically or combining both approaches, while noting that repeating the dashboard may be redundant because it already appears near the top.
- 0:39:16
Polishing the Pricing Page and CTA Consistency
The work shifts to finishing pricing-page modifications, including matching a button to the “Scan My Store” navigation CTA in shape and corner radius.
- 0:41:31
Providing a shop dashboard
A discussion of how to provide a shop dashboard, either by generating one from scratch when needed or extracting a suitable example from the existing shop-dashboard section.
- 0:43:41
Moving from React to Polaris Web Components
The speaker explains that using React would not, in his view, cause the project to be rejected, but Polaris Web Components is preferred and better suited to the project, so he decided to add the migration as a separate work milestone despite the prior effort.
- 0:45:29
Refining the landing-page showcase and calls to action
A review of a landing-page experience that reveals product interfaces in stages controlled by user scrolling. Feedback included separating production of the visual elements from the effect discussion where possible, fixing text overlap without disturbing card placement or the glimpse of the next section, and adding a secondary button for another plan while keeping the primary call to action emphasized.
Got a question about something in this stream?
Ask in the group