For several years, the product remained unchanged, leaving it vulnerable to active competitors. This stagnation allowed competitors to gain ground by offering more features that better met user demands.
NEW FEATURES
Adding features currently offered by competing services to meet user demands: Search, Downloads, Multiple Profiles, Watch List, and Favorites. Updating features that were causing user complaints.
PRODUCT REDESIGN
Redesigning the product across all platforms with a fresh, contemporary look and feel. Creating a component library to ensure consistent growth, scalability, and automated workflows.

SBuilding on previous user research, the company conducted interviews and surveys with real and potential users, and collected data from customer service reports and app store reviews. These insights informed five user personas that guided design decisions based on user characteristics.

Delivering real value requires clearly defining what we're building and why users need it. We broke down the product into functional building blocks, defining each unit's purpose to align the team and establish the foundation for the Product Requirements Document (PRD).

Opportunities for the "Search Feature".
I presented the analysis results for each feature in a journey map highlighting user and business goals. This facilitated discussions around solutions and implementation while identifying pain points and improvement opportunities. It served as a foundational step for understanding functionality, mapping user tasks, and developing initial flows.

Mapping of user and business goals during the "Search".
We defined features through a continuous process throughout the product lifecycle. This allowed us to evolve our offering as customer needs changed and adapt solutions to user behavior through incremental improvements. Building features in phases enabled faster results, reduced costs, and simplified tracking implementation impact.
SEARCH PHASE 1
Phase one focused on core functionality: search-as-you-type, typo tolerance, search history, results display, and failed search handling.
KEY METRICS:
- Daily & Weekly Uses
- Task Success
- Task Time
- Search No Results
SEARCH PHASE 2
Phase two added a collections catalog, transforming Search into an alternative content discovery experience distinct from the standard VOD flow.
KEY METRICS:
- Search or Catalog Choice
- Task success
- Customer Preferences
- Popular Catalogs
SEARCH PHASE 3
This phase integrated the recommendation engine, improving the experience based on watch behavior, watch lists, and other user signals.
KEY METRICS:
- Recommend Success
- Customers Prediction
- Recommendation Strategies
- Enrich Algorithms
Iterating through previous phases provided insight into resource and time requirements. I assisted product managers in establishing a prioritization framework focused on features delivering maximum value to users and the business. This collaborative effort aligned teams and identified cross-functional dependencies.

An initial product architecture outline guided the design of individual screens and larger systems. The diagram illustrated flows between functions, helping anticipate timelines and coordinate exploration and design activities.

Iteration steps were determined by solution complexity and included wireframes, page flows, user task diagrams, competitive benchmarks, prototypes for testing complex solutions, and other research activities.







We analyzed competitive services to identify user habits and patterns formed through their features.





Clarifying the function's complexity provided insights into the flows and screens needed for design.






Rapid solutions for feature content design that helped identify and define component performance and product standards.



Prototyping showcased the final solution's look, feel, interactions, and functionality while generating valuable feedback from team members and test users.
Blim TV's component libraries were built to achieve consistent results while scaling the design process. The libraries included three modular systems: Mobile and Tablet, CTV, and Web. These libraries enabled faster iteration across teams, maintained visual consistency across devices, and provided comprehensive documentation for engineering handoff.

Mockups flow during the "Search".









































































































