POLISHING UI/UX
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 a Shopify app moving from its core build into the harder pre-launch phase of polish and verification: UI/UX review, turning findings and screenshots into tasks, and manually exercising the app alongside AI agents. Luqman presents a command center that divides work among the human operator and agents, balancing parallel execution against file conflicts, and proposes teaching a lighter version from scratch. Practical investigation of slow loading and navigation occupies a major part of the work; routing, repeated database calls, Prisma, and network distance are considered, and some improvement is observed, but the complete cause and final fix remain unresolved. App-listing requirements, privacy policy placement, GDPR, Railway deployment, and the path toward Shopify submission are also discussed as unfinished work or plans rather than confirmed outcomes. Other useful discussions cover competitor research and positioning in a low-competition market, subjective tradeoffs among Codex, Claude, and other models, usage limits and subscription ROI, plus audience questions about Arabic dictation, email outreach, and channel growth through short-form video. The stream also includes attributed views on AI and cybersecurity and on how operator expertise shapes the value of AI tools.
73 moments from the stream
- 2:01:47
Sharing Code with Claude Instead of Screenshots
The discussion covered downloading a file or an entire project and sending the code directly to Claude instead of a screenshot for UI work. The workflow seemed promising, but Claude’s ability to download the code still needed verification.
- 2:05:15
Investigating Slow Navigation
Switching between application sections was observed to be extremely slow, prompting a codebase investigation to find the root cause rather than assuming a quick change had solved it. The Supabase connection was raised only as a hypothesis, while broader backend review was deferred to prioritize UI polish.
- 2:16:12
Diagnosing Load and Navigation Slowness as a UX Priority
The speaker rejected the idea that the wait time was an unavoidable floor, pointing to Vitals as a faster comparison despite its broader scope. He requested a review of the codebase and earlier tasks to identify the change most likely responsible, while prioritizing reduced Talk Store startup and navigation latency before deeper debugging.
- 2:20:17
Sequencing Polish Work and Adding Voice and File Interactions
The speaker outlined a tentative sequence starting with speed, followed by UI and UX polish and then backend work, while introducing features such as voice interaction, pictures, and file attachments along the way. The stated aim was a selectively polished initial release rather than a large expansion before launch.
- 2:21:04
A Conditional Historical Launch Target
In the recording, the speaker referenced Thursday, April 9 and conditionally estimated a mid-April launch if work progressed well, with possible entry into the Shopify App Store submission process by late April. These were contemporaneous estimates, not confirmed outcomes.
- 2:22:09
The Tradeoffs of Entering a Low-Competition Market
The discussion cautions that having no competitors does not necessarily prove an opportunity: revenue and even an addressable market may be uncertain, while creating demand adds a substantial marketing burden. The upside is that successfully creating that demand can establish market leadership and enable rapid growth; both crowded and uncrowded markets have tradeoffs.
- 2:25:53
Reviewing App Speed Improvements and Remaining Bottlenecks
After trying a loading-performance direction, the review finds a clear improvement: settings are nearly instant, while the plans section remains slower, history slower still, and the application's initial load needs more work. The goal is to keep improving speed without destabilizing the backend.
- 2:29:28
Handling Overlapping Code Changes Sequentially
The interface still needs changes before deeper work begins, but running overlapping tasks in parallel could create conflicts while latency and UI elements are being modified. The chosen approach is to proceed one change at a time, with a structured workspace providing clearer visibility into the work.
- 2:32:20
Reviewing UI and UX Before Launch
The speaker plans to review earlier tasks one at a time, treating satisfaction with Talk Store’s UI and UX as a prerequisite for launch while also addressing items not yet represented in the command center.
- 2:34:14
Researching the Settings Structure with Coding Agents
The speaker assigns coding sessions to examine the codebase, project vision, roadmap, and implementation status, then propose forward-looking subsections for the Shopify app’s currently empty settings area using comparable apps as reference.
- 2:36:45
Diagnosing First-Visit and Homepage Slowness
The speaker examines a caching-related improvement: revisiting pages such as plans and settings becomes nearly instant, but the first visit remains slow. He asks for faster initial loading and investigation into whether an earlier homepage layout update contributed to its slowness or broken behavior.
- 2:41:31
Comparing Two Coding-Session Outputs
The speaker refers to passing a file to another coding session and using its output to judge between two results; the closing implementation details are unclear in the captions.
- 2:42:51
Turning a UI Review into Tasks
The review notes are to be converted into one or more tasks within the review-and-polish milestone, then handled through the regular workflow.
- 2:43:27
Reviewing UI Speed and Navigation
The discussion identifies slow UI behavior, especially on first opening some pages, and plans to expose the task board in the Command Center, improve navigation, then reassess speed.
- 2:47:18
A Structured Workflow for Performance Investigation
The proposed workflow revisits the session history, inventories prior speed fixes, distinguishes what worked from what did not, explores additional avenues with multiple agents, and consolidates findings in a Markdown document for later decomposition into executable subtasks.
- 2:51:07
A Lightweight Command Center Tutorial Concept
A practical tutorial is proposed for building a lighter Command Center from scratch, teaching a foundation that learners can extend independently without reproducing the full system’s depth.
- 2:53:16
Designing a Command Center and Navigation Menu
The discussion notes that a command center’s design varies with the project and designer, then raises a practical question: should navigation contain only chat history, plans, and settings, or expose a larger menu?
- 2:55:51
Managing Coding-Tool Usage Windows
Explains a general approach to pacing work around usage-window resets and keeping a fallback tool available if capacity is exhausted early. Actual account details and usage figures are omitted.
- 2:56:34
AI and the Future of Cybersecurity
The speaker relays an opinion attributed to Sam Altman that cybersecurity will become increasingly important as AI is used for both attacks and defense, and notes the emergence of specialized tools trained for the field.
- 2:59:41
Operator Expertise Shapes AI’s Value
The speaker argues that assessments of AI may depend as much on the operator’s skill as on the technology itself: a domain expert who uses AI well may see it as transformative. He explicitly qualifies that he is not a cybersecurity professional.
Got a question about something in this stream?
Ask in the group