Pitchyy : App design
An innovative platform designed to effortlessly connect writers and producers, streamlining script exchange, collaboration, and project initiation.
Role : UX/UI designer
Responsibilities : Product design, usability testing, UX research, visual design.
Stakeholders : Writers, producers, founders and investors of Pitchyy.
Designed for:
Understanding the problem
Lack of collaboration medium for writers and producers in the entertainment industry (OTT platforms).
Hinderance in communication due to the absence of a linear channel.
Risk to confidentiality and potential for idea/concept theft.
Absence of security and legal protection of the writers.
Difficulty in networking and promoting the craft.
Constraints
Very unique product, difficult to create a comparision limiting the baseline research.
No access to practicing writers and producers to interview and understand their personal frustrations.
Short timeline to achieve the mid-fi prototypes.
Project timeline
2 weeks to create the mid-fidelity prototype.
Persona development - Understandinging the users
Due to the limited resources and fundings, I could not conduct real-life interviews. Based on the stakeholder informed decision and hypothetical personas I drafted these personas.
Affinity mapping
I used this tool to systematically organize and categorize the vast ideas, concepts, and user needs identified in the design brief. I understood the overarching themes and user priorities better, helping me identify the core functionalities that must be prioritized in the UI.
Site map
In creating the Pitchyy app, the site map was essential in organizing the platform’s structure to meet the unique needs of both writers and producers. Mapping out key functions, such as secure script exchanges and communication channels, helped us clarify how these features would interact and ensured a seamless user experience despite the project’s tight timeline and research constraints.
What value did it add to my process?
This early-stage blueprint allowed me to effectively communicate the app’s vision to stakeholders and the development team, aligning everyone on the app’s direction before diving into more detailed design and prototyping.
It provides a bird's-eye view of the entire information architecture. A hierarchical representation of the various pages, sections, and features within the app.
By outlining the core pages and their relationships, I could identify potential gaps in the user journey and refine the app’s functionalities to better meet user needs.
Wireframes
Through extensive research, stakeholder meetings, and the development of a sitemap alongside various design processes, I crafted a selection of wireframes, each contributing specific functionalities to the overall design process.
By using wireframes, I could efficiently iterate on the design, gather feedback from stakeholders, and make data-driven adjustments before moving into mid-fi prototypes. This streamlined the design process, providing clarity and a solid foundation for the next steps in developing Pitchyy’s user experience.
Mid-fidelity prototypes
Writer's account view
Find those amazing stories hiding under the new trails of thoughts
Home screen
Collaboration on the finger tips.
Direct access to the creative flair.
Hamburger menu
User's profile
Navbar with options to access 'Your pitches', 'Bookmarks', 'Home', 'Pitch requests', 'Notifications'.
Collection of pitches sent to the producers
Expanded view of the pitch request received by the producers
Pitch requests
Producer's account view
Requesting a pitch on your finger tips.
Designed a 'Hamburger menu dropdown' Using a concept of 'Magic number', from cognitive psychology introduced by George A. Miller, by limiting the number of selections to reduce decision paralysis.
Home screen
The producer must sign a discretion policy and pay to read the story line/ pitches that the writers are sharing. This helps in eliminating the craft offenders and exploitation.
Received pitches
Payment gateway
What's next?
Review: The working prototype was presented to the stakeholders. In this case, there was no major feedback in terms of design.
​
Development: Upon successful review session, the file was handed over to the team of developers where I collaborated with them throughout the development phase until the finishing stage.
​
Quality assessment: A quality check is run upon development. I personally keep a tab on development and ensure the quality matches the original designs, screen by screen.
Usability testing: The design and the testing team, ran usability testing to ensure the users could finish the tasks smoothly.
Iterations: We would have iterated in case there was a need of a change in design.
Launch: We then successfully launched our new website and received good reviews from our user base.