Sign-in across platforms
From November 2025 to February 2026, I worked as a Product Designer at NoAvaran Bamdad Rahsabz (ZeeVision). With another Product Designer, I designed experiences for mobile, desktop, web, Smart TV, and Android TV. This case study focuses on our design-system collaboration and the differences in sign-in across platforms.
Sign-in, payment, and usage steps were not the same across platforms. Each flow and interface needed to suit how that environment was used. Sign-in is a specific example of those differences in this project.
We built and expanded the design system alongside the product screens. Visual foundations, variables, and reusable components were part of that shared work. Ownership of specific components was not separated into individual responsibilities.
On mobile, the design focused on one-time-password sign-in. On desktop, password sign-in was the main approach.
On TV, users scanned the displayed QR code with their phone and continued sign-in on the phone to access their account on the television.
The method and steps therefore differed between environments. A focus on OTP on mobile or passwords on desktop does not mean those were the only available methods.
The designed areas and design system were implemented and used in the product. The collaboration produced multi-platform experiences with different sign-in flows.
The numerical impact on sign-in success, design speed, or development time has not been recorded.
Have a product problem to work through? Let’s talk about the people using it, what the business needs, and what we can build.
Have a product problem to work through? Let’s talk about the people using it, what the business needs, and what we can build.
