Skip to content
شغّال
Back to the library

BREAKING MY APP TO FIX IT

Day 0225:33:51

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 an AI assistant for Shopify as development shifts from building to review, debugging, and UI/UX polish. Luqman evolves a command center that separates UI, UX, and backend verification from fix tasks, records outcomes, and supports step-by-step retesting, while routing work among Codex, Claude, and other agents according to the task. Practical work includes migrating the interface to Polaris, reviewing the homepage and report card, and diagnosing classifier, routing, conversation-button, image, live-counter, and relative-date issues. Some cases were verified as fixed, while others remained unresolved, including app slowness, conversation-flow problems, and a vision-analysis failure. Audience discussions cover model and coding-tool selection, voice-chat applications, and local versus cloud model access, with the comparisons treated as informal impressions rather than definitive benchmarks. On product strategy, Luqman argues for examining demand, unit economics, pricing, and customer-acquisition cost before scaling, while acknowledging that pre-validation is not the only path and that currency mismatch and purchasing power can complicate sustainability in some Arab markets.

  • agent-workflow
  • debugging
  • testing
  • task-management
  • +4

105 moments from the stream

  1. 5:13:14

    Testing a Live Task-Usage Counter

    A completed task and product-description rewrite were used to test whether the usage counter advanced automatically. It did not change immediately but showed the new value after a page refresh, demonstrating that the live update was not yet working correctly.

    • debugging
    • live updates
    • usage counter
    • task completion
    • +1
  2. 5:18:13

    How Fixing One Bug Can Expose Others

    A practical observation that debugging one part of an application can expose problems elsewhere or introduce side effects, alongside noting layout-cleanliness issues involving Shopify Polaris components.

    • debugging
    • regressions
    • Shopify Polaris
    • UI layout
  3. 5:20:55

    Diagnosing a Broken Conversation-History Button

    The conversations button was unusable and failed to open the previous-conversations pop-up; instead, it shifted the screen and introduced a scroll bar. The requested debugging approach was to identify the cause, reproduce the issue in a browser, capture screenshots, and use multiple agents to assist with the investigation.

    • conversation history
    • UI bug
    • browser testing
    • Playwright MCP
    • +2
  4. 5:27:21

    Why Fixing One Bug Reveals More

    He explains that debugging is not linear: fixing one problem can expose several more, so the process requires a different mindset. An issue with the conversation button was blocking progress, while verification work revealed additional problems and made review and debugging slower than the initial implementation, as he had anticipated.

    • debugging
    • verification
    • code review
    • workflow
    • +3
  5. 5:32:35

    Estimating the Work Needed for Shopify Submission

    He notes that estimating submission work must account for review and debugging as well as preparing a video, polished images, and other Shopify app-submission requirements.

    • Shopify
    • app submission
    • release preparation
    • launch assets
    • +4

Got a question about something in this stream?

Ask in the group