Preparing for Ad Launch
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
A wide-ranging practical stream combining a Burnish website and mobile review with discussions about product launches and AI-assisted work. Luqman examined content density, spacing, motion, input and CTA clarity, and visual identity, while the mobile audit, landing page, and some template regressions remained unfinished. On launch strategy, he argued against letting perfection delay shipping, but the product, lead funnel, email sequences, and ad creatives still required preparation and testing; conversion costs and projected outcomes therefore remained unknown. He also discussed lead qualification, install-to-paid measurement, entering the Shopify ecosystem after competitor research, and balancing report depth against speed. In audience Q&A, he shared personal views on Claude, Codex, Gemini, context compaction, multiple agents, and CLI workflows, stressing that tool choice is workflow-dependent and that these were not systematic comparisons. He warned against exposing API keys or selecting a cheaper provider without checking privacy and reliability. He advocated incremental learning through building rather than theory alone and framed AI as an amplifier of existing skills, not a replacement for human judgment. The conversation also covered education, freelancing, B2B versus B2C, unit economics, focused work and breaks, plus brief practical suggestions for preparing chicken meals.
159 moments from the stream
- 0:44:47
YouTube for Informative Streams, Short-Form Platforms for Clips
He says he streams only on YouTube and prefers it for informative content, while viewing TikTok and Instagram as better suited to short clips; he had not set up vertical multi-platform streaming.
- 0:45:21
The Falling Barrier to Entry for AI Tools
He says the idea might have become a revenue-generating product, but hesitated because AI tools were making similar concepts easier for many people to build, while other platforms were already incorporating comparable systems. Some platform names are unclear in the captions and are therefore left unattributed.
- 0:48:04
Reviewing a Landing Page Before Refactoring
He prefers not to refactor the entire landing page, suggesting first that margins and padding be fixed across mobile and desktop, missing content be identified, and successful internal pages be studied before brainstorming the page components.
- 0:49:02
B2B vs B2C: Reach, Value, and Price Sensitivity
He expresses a preference for B2B because of potentially higher margins and the ability to persuade companies through delivered value. In his view, B2C can work at volume when there is a large audience or enough advertising reach, but consumers are usually more price-sensitive. This is an opinion-based tradeoff, not a test result shown on the page.
- 0:50:15
Trust in B2C Apps Compared with B2B
The speaker considers the comparison close but slightly favors B2B, arguing that consumers are selective about which apps they install, while the value offered remains an important factor.
- 0:53:41
Moving a Project from Chat to Claude Code
The speaker recommends collecting what was built in chat and moving it into Claude Code to continue development in a coding-focused environment rather than relying on the chat interface alone.
- 0:54:17
Context Compaction and Handoffs Between Coding Models
The speaker discusses compacting context within the same session when continuing the same task to avoid repeatedly creating handoff files, while retaining a Markdown handoff when moving work between Claude and Codex or different environments.
- 0:57:07
Handling API Keys Safely in AI-Assisted Development
The speaker explains that an AI tool may guide a developer to where API keys are obtained, but entering and storing them in an environment file should be handled carefully. He warns against exposing keys in conversations and suggests replacing any key that has been revealed to reduce breach and misuse risks.
- 0:59:09
A Possible Explanation for Different Navbar and Footer Widths
After interpreting the question as referring to the footer and navbar, the speaker says their differing widths are intentional because they contain different elements and he does not want the navbar to become too large.
- 1:00:19
AI Amplifies Skills, but API Keys Need Protection
The speaker argues that AI amplifies existing skills rather than replacing them, while warning that an exposed API key can enable unauthorized usage and lead to large bills.
- 1:02:28
Monetization Alternatives When Licensing and Maintenance Fall Short
In response to a question about an app whose licensing-and-maintenance model is not working, the speaker suggests researching specialist marketplaces or brokers for selling the app. He notes that traction and demonstrated results matter and qualifies the advice because the app's details are unknown.
- 1:03:48
Why Research and Planning May Use More Tokens Than Coding
The speaker describes using an AI tool more for planning than direct coding and says—based only on his experience—that research, application reviews, implementation plans, and specifications may consume more tokens than building a narrowly specified page because the exploration and output are broader.
- 1:05:15
Mixed Experiences Comparing Codex and Claude
The discussion presents user opinions about Codex and Claude regarding perceived intelligence, usage constraints, and workflow fit. One participant preferred Codex's usage flexibility, while the speaker said he felt more comfortable working with Claude; these are personal experiences, not a systematic test.
- 1:07:37
AI App Building Is an Iterative Process, Not a Single Prompt
Responding to concerns that AI may produce only an incomplete interface or leave parts unfinished, the speaker explains that results depend on iterative dialogue and review: identify what is missing, request the next changes, and continue refining. He stresses that the process has obstacles and does not demonstrate a specific security fix here.
- 1:09:16
An Incomplete Observation About Codex's Project Workflow
The speaker begins describing a past concern that Codex felt overly reactive and tended to conclude responses instead of carrying the workflow forward on its own, but the comparison is cut off and he explicitly says he does not know whether that behavior has changed.
- 1:10:21
Choosing a Coding Assistant by Working Style
Drawing on personal experience, the speaker contrasts a more proactive coding assistant that suggests next steps with a more reactive one. He says the choice—and whether to split tools between frontend and backend—depends on the developer’s preferences, noting that he currently uses one assistant for both.
- 1:13:28
An Opinion on Gemini and Google’s AI Potential
The speaker discusses differing views of Gemini’s ability to understand design and coding tasks. Although he does not currently use it, he argues that Google has the resources to compete strongly in coding and potentially general AI if it prioritizes them, clearly presenting this as personal speculation rather than an established result.
- 1:15:44
Ship the Website and Reserve Deeper Polish for the Product
While reviewing the design, the speaker says the spacing and disconnected grid lines still need stronger geometric consistency. He nevertheless does not want website perfection to delay shipping, because the site is only one part of the experience; in his view, pixel-level scrutiny of colors, elements, and their purpose matters more inside the application itself.
- 1:19:58
Inviting Software Engineers onto Live Streams
Responding to an audience question, the speaker says he is open to having software engineers join his live streams and has previously extended invitations. The page ends before his explanation of the reactions he encountered is complete, so no definitive reason can be inferred.
- 1:20:30
Software Engineers Adapting to AI Tools
The speaker invites calm discussion with critics and says he is not opposed to software engineers. In his view, their experience could give them a major advantage if they approach AI tools flexibly rather than resisting them.
Got a question about something in this stream?
Ask in the group