Weekly UI/UX

Date: 2025-07-21 · Duration: 26.1299991607666 min Organizer: Nader Attendees: Mike, Nader, nathan.d.dutoit@gmail.com, Raymond

Summary

• Raymond completed ticket 513 on authentication and authorization, shifting focus from merchant onboarding to enhanced user tab features.
• Team agreed to utilize Facade for merchant flow endpoints; Sparsh is leading this initiative amidst ongoing challenges.
• Raymond’s integration with Facade endpoints has paused due to incomplete implementation, resulting in the work-in-progress being deployed to staging.
• The previous Pay Engine integration was halted due to complexities in data serialization; the new flow allows for a simplified draft-saving process with pre-filling capabilities.
• Alexander modified payload structure from ‘Lego name’ to ‘name,’ necessitating frontend adjustments; all UI components are ready except for the pricing tab.
• A new dual user authentication flow is in place, effectively managing access for regular and partner users while ensuring proper redirection.
• Discussions highlighted the preference for using differentiated routes over separate subdomains for user types to streamline the project under time constraints.
• Nader proposed a future consideration of a separate domain for partners to enhance concerns related to infrastructure and portal separation.
• Alexander advocated for a simplified modal for merchant name entry, while Raymond suggested a full form approach, ultimately settling on auto-generated names for smoother backend communication.
• Martin is supporting dashboard development for the partner portal, with positive feedback from partners about initial mockups and understanding of existing delays.

Action Items

• Raymond Complete authentication, authorization, and users tab implementation by tomorrow (10:32) Adjust frontend payload handling from ‘Lego name’ to ‘name’ based on Alexander’s changes (04:59) Switch back to onboarding flow work once Sparsh completes Facade endpoints (24:17) Investigate Facade’s user type identification system to implement proper user discrimination logic (11:44)

Nader Reply to Alexander’s comments about merchant creation workflow approach (23:07) Revisit tickets tomorrow with focus on production-ready platform rather than demo approach (12:28)

Unassigned Discuss separate domain implementation approach tomorrow for partner portal (12:28)