<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ashmik Ragesh on Medium]]></title>
        <description><![CDATA[Stories by Ashmik Ragesh on Medium]]></description>
        <link>https://medium.com/@rageshashmik?source=rss-c0304ea8d450------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5VOjUJStNlD8nchmo3ZN3A@2x.jpeg</url>
            <title>Stories by Ashmik Ragesh on Medium</title>
            <link>https://medium.com/@rageshashmik?source=rss-c0304ea8d450------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:25:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rageshashmik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[HireMate: Rethinking Recruitment Processes for Quality Hiring : a UI/UX case study]]></title>
            <link>https://medium.com/design-bootcamp/hiremate-rethinking-recruitment-processes-for-quality-hiring-a-ui-ux-case-study-4848c32c6e85?source=rss-c0304ea8d450------2</link>
            <guid isPermaLink="false">https://medium.com/p/4848c32c6e85</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[hr-talent-management]]></category>
            <dc:creator><![CDATA[Ashmik Ragesh]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 16:02:38 GMT</pubDate>
            <atom:updated>2023-06-23T09:48:49.337Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hiremate a HR management software for Quality Hiring and recruitment: a UI/UX case study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gElSxkp80yMd-aO2nhIrdQ.png" /></figure><h3>Project Overview</h3><h4>Company Background</h4><p>Cubera is an AdTech and Big Data company, with a focus on bridging the gap between advertisers and brands by automating lead efficiency​. They specialise in the collection and utilisation of Zero Party Data, which refers to data that is voluntarily shared by users​. They have developed a marketing automation platform that is instrumental in achieving this.</p><h4>What is Hiremate?</h4><p>Hiremate is an innovative recruitment and hiring management tool designed to streamline and automate the recruitment process for large corporations. It serves as a comprehensive platform that efficiently manages the volume of applications, making the selection process more effective and less prone to human error.</p><h4>Duration</h4><p>1 month</p><h4>Platform</h4><p>Web platform</p><h3>Problem Statement</h3><p>Cubera Technologies receives a high volume of applications for its job openings, making the recruitment and hiring process quite challenging. The current manual process includes posting job openings on various job boards, reviewing resumes manually, scheduling interviews, and making hiring decisions based on the interviewer’s feedback. This approach is not only time-consuming but also prone to bias and errors, leading to missed opportunities to hire the best candidates. So they found out the need for a HR management software that helps HR managers automate the recruitment and hiring process.</p><h4>Goals</h4><ol><li>Automation of Job Posting: To automate the process of job postings across various job boards, increasing efficiency and reach.</li><li>Effective Resume Screening: To implement an effective mechanism for resume screening, reducing the time spent on manual review and increasing the probability of shortlisting the best-suited candidates.</li><li>Streamlined Interview Scheduling: To streamline the process of interview scheduling, coordinating between the interviewers and candidates, and handling rescheduling if needed.</li><li>Objective Hiring Decisions: To introduce a system that collects and analyses interviewer feedback, promoting objective and unbiased hiring decisions.</li></ol><h3>🔎 Research</h3><p>The first step in my design process for Hiremate is the research phase, in which I will gather information to better understand the context and users of the system. The aim of this phase is to identify the needs and pain points of our users, as well as to gain a deeper understanding of the current recruitment landscape.</p><p>To begin with, I will try to find out the pain points to identify what our users require from a recruitment system. In addition, I will carry out a competitor analysis to see how other HR management systems handle recruitment. This will involve examining the features and functionalities of existing products, as well as identifying areas where they may fall short. I can use this information to identify opportunities for HireMate to differentiate itself and provide a superior user experience.</p><h4>1. Pain-points</h4><ol><li>Time-Consuming: The current process involves manually posting job openings, reviewing resumes, and scheduling interviews.</li><li>Prone to Errors: Manual processes, particularly those involving large amounts of data, are prone to human error. This could lead to overlooking qualified candidates or making mistakes in the hiring process.</li><li>Difficulty Tracking Applicants: Without a centralised system to track applicants through the hiring process, it can be difficult to keep track of where each candidate is in the process and what next steps need to be taken.</li></ol><h4>2. Competitor Analysis</h4><p>In the competitor analysis for Hiremate, we examined three popular recruitment software solutions: <strong>Keka HR, Breezy HR, and Zoho Recruit</strong>. I compared these platforms based on their features and recruitment-specific functionalities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tv85X2MP_j-4m9jYjs5YqA.png" /><figcaption>Analysing differentiating features of each softwares</figcaption></figure><p>Regarding visual design, it’s a bit subjective, but here are some observations:</p><ul><li>Keka’s design is modern with a lot of focus on usability and functionality. It has a clean layout with bright colours that make it easy to distinguish different sections and features. The user interface seems straightforward and intuitive.</li><li>Zoho Recruit’s design is clean and professional. It uses a lot of whitespaces and blue accents. The layout is organised, making it easy to navigate. The user interface might seem a bit packed due to the range of features it offers.</li><li>Breezy HR also sports a modern design with a clean interface. It uses a mix of colours, which makes it visually appealing. The layout is intuitive, with a focus on making the recruitment process as smooth as possible.</li></ul><blockquote><em>After comparing the softwares I concluded that a clean UI, light colour scheme, clear call to action, simple user flow will be the main focus points. Because the app would be used by very diverse users therefore it will have to be designed in such a way that it will be easy for everyone to perform the action/function for which the platform is designed.</em></blockquote><h4>3. User Flow</h4><p>User flows are flowchart diagrams that explain the different processes involved in accomplishing a task from your MVP. It lays out steps &amp; actions in a particular order and sequence that the user needs to undertake to get to the end of the task.</p><p>A typical Hiremate user flow might start with the HR manager logging into the platform, then proceeding to create a new job posting. After filling out the necessary details for the post and publishing it, the HR manager would then navigate to the candidate management section of the platform where they can review incoming applications, screen resumes, and decide who to move forward in the process.</p><p><strong>User flow for posting jobs on different platforms:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gSFdAVYvIAL5kzvvS8CPvA.png" /></figure><p><strong>User flow for scheduling a call :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGIvI6OM_9ncanCO5ues7A.png" /></figure><p>This user flow is designed to streamline and automate the hiring process, making it more efficient and reducing the chance of errors or bias. It also ensures that HR managers have all the information they need at their fingertips, helping them to make better hiring decisions.</p><h3>🧑‍💻 Ideate</h3><p>In the Ideation phase of the Hiremate project, I focused on transforming insights gained from the research phase into potential solutions that could address the identified user needs and pain points.</p><p>Throughout the ideation phase, my goal was not to develop an immediate perfect solution, but rather to explore as many possible solutions as possible, keeping an open mind for continuous learning and improvement.</p><h4>1. Sketching</h4><p>In the ideation phase of the Hiremate project, sketching played a vital role in visualising and refining my ideas. It allowed me to quickly represent the design concepts I had in mind, leading to a deeper understanding of how these ideas would fit into the Hiremate interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5WFsuUyU8znjhauGoh-7wg.png" /><figcaption>Brainstormed my ideas with sketches</figcaption></figure><p>These sketches were a crucial part of the ideation phase, helping me to iterate on these concepts quickly and effectively, and setting a clear path for the high fidelity design and testing stages.</p><h4>2. Mid-fidelity Wireframes</h4><p>In the ideation phase of the Hiremate project, creating mid-fidelity wireframes was a key step in transforming the abstract ideas into more concrete, visualised concepts. This was a crucial part of the design process as it helped to define the structure, layout, and functionality of the Hiremate platform.</p><h4>Dashboard</h4><p>The dashboard is the heart of the application and is the first screen that HR personnel would see upon logging in.</p><p>The dashboard was designed to provide a quick overview of the ongoing hiring processes. It included elements like the total number candidate application, the number of jobs posted and also meeting schedules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ze-VwXmxBd415B3pTyxGlw.png" /><figcaption>The main dashboard</figcaption></figure><h4>Posting a job</h4><p>In the ideation phase, I crafted a mid-fidelity wireframe for the<strong> job posting process</strong> in Hiremate. Users start by clicking “Create Activity” and choosing “Job Opening”. They fill out job details, and then set screening questions to automate initial resume reviews. Candidates meeting the criteria are shortlisted, while others receive a polite automated rejection. The final step allows users to select job portals for posting, broadening the job’s exposure. This demonstrates Hiremate’s commitment to efficient hiring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mOD07SKvkQRfrjWHKWH1Aw.png" /><figcaption>A flow on how to post a job on multiple platform</figcaption></figure><h4>Scheduling Calls</h4><p>For scheduling calls, I implemented a streamlined process. Users begin by selecting “Create Activity” and choose the “Scheduling meeting” option from the dropdown menu. They then input the necessary details, choose the date and time, and a system-generated email with a Google invite is automatically sent to the email tagged in the details section. This feature simplifies and automates the scheduling process, reducing the time and effort required to set up interviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7tezs3wQeeOtD5lvnFnDg.png" /><figcaption>Scheduling meeting</figcaption></figure><h4>Other Screens</h4><p>A separate candidate section presents a comprehensive view of all the candidates and their respective statuses in the hiring process, allowing for easy tracking and management. Furthermore, a section showcasing all posted jobs provides a quick overview of active openings and their details, making it a centralised hub for managing recruitment activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9f63GfaJ4ea4UXkfOyDsA.png" /></figure><h4>3. Visuals</h4><p>This is the most compelling part of the process yet most comprehensive as you need to decide upon the colour palette, typography, so all in all a proper style guide that can represent the brand’s uniqueness and presence.</p><h4>Typography</h4><p>In designing Hiremate, I opted to use SF Pro for the font, primarily for its high readability and versatility. It offers an excellent balance between readability and aesthetic appeal, which is essential for an application with a diverse range of users</p><p>Furthermore, SF Pro comes with a wide range of weights and styles, allowing for nuanced typography design that can help organise information and guide the user’s eye. Its modern and professional look contributes to a clean, efficient, and user-friendly design, making it an ideal choice for Hiremate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jki__l9tgQGwqIQj87GsdQ.png" /></figure><h4><strong>Colour Palette</strong></h4><p>In the design of Hiremate, I chose the colour #2D68FE as the primary colour. This colour is a vibrant and energetic shade of blue, which is often associated with trust, reliability, and professionalism. These attributes align well with Hiremate’s brand identity, as it’s designed to be a dependable tool for recruitment and hiring processes. Moreover, this colour provides excellent contrast against lighter backgrounds and text, enhancing readability and usability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nin_5tY52YKM82UjAU-Yog.png" /></figure><h4>High-fidelity Designs</h4><p>The goal of creating high-fidelity designs for Hiremate was to bring the earlier sketches and mid-fidelity wireframes to life, adding depth and detail to the user interface. This allowed me to visualise and evaluate the user experience more accurately, considering factors such as visual hierarchy, colour contrast, spacing, and typography.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BgIJ5PyxMVeiiMO9q6Xz5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UU1Ap6nlwJNEeVcLsV3yBg.png" /></figure><h3>🧪 Testing</h3><p>In the testing phase, I was able to gather valuable insights into the effectiveness and usability of Hiremate’s design. Given the limited time and resources, I conducted the testing with two individuals who were knowledgeable about HR management software</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bguwVP2OvhJbPD3_MEhtUQ.png" /><figcaption>Testing the high fidelity designs</figcaption></figure><p>During this process, I focused on several key aspects of the platform:</p><ol><li>Navigability: I assessed how easily users could navigate through the platform, find features, and complete tasks.</li><li>Task Completion: I observed how users posted a job, ensuring that the process was intuitive and straightforward.</li><li>Response to Interface: I gathered feedback on the visual design of the platform, including colour choices, typography, and general aesthetic appeal.</li></ol><blockquote><em>Through this user testing, I discovered a notable gap in the functionality: the absence of an option to </em><strong><em>withdraw job postings</em></strong><em> from the various platforms. This was a critical find, as it is vital for HR managers to maintain control over their job postings, including the ability to withdraw them when necessary.</em></blockquote><p>Despite the limited testing sample, this stage was invaluable in identifying an essential feature that was missing from the design. This insight will directly inform the iteration phase, where I will refine and enhance the design based on the feedback received.</p><h3>♻️ Iterate</h3><p>In the iteration phase, the goal was to take the feedback and insights gathered during testing and use them to further improve the design of Hiremate. The main point of feedback was the need for a ‘withdraw job’ feature, which would allow users to remove job postings from various platforms.</p><p>Based on this, I went back to the drawing board and revised the design to include this feature.</p><h4>1. Solution</h4><p>In response to the feedback received, I designed a new feature in Hiremate to address the need for job withdrawal. When a user clicks on a specific job, an app slider appears providing the user with more detailed options for that particular job. Among these options is the ability to withdraw the job posting from its specific platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3EHzLZKcKRoKI30lMh0mA.png" /><figcaption>The new app slider</figcaption></figure><p>This new feature not only resolves the identified issue but also gives users more control over their job postings. They can now modify job details or withdraw the job entirely, directly from the job’s overview, making the process more intuitive and efficient. This adjustment exemplifies the iterative design process, where user feedback directly contributes to the refinement and improvement of the product.</p><h3>Here are some lessons I’ve learned</h3><ol><li>Iterative Design Process: The development of Hiremate underscored the value of an iterative design process. I saw firsthand how each stage of the process, from research to ideation, testing, and iterating, played a crucial role in shaping the final product.</li><li>Testing Limitations: I experienced some of the limitations of testing with a small group of people. While it provided valuable insights, I am sure that broader testing could yield even more diverse and comprehensive feedback.</li></ol><p>And that’s a wrap! If you liked this case study, please give it a clap! :)</p><p>You can connect with me on LinkedIn <a href="https://www.linkedin.com/in/ashmik-ragesh-74aa66217/">here</a>.</p><blockquote><em>Fun fact: if you hold down the clap button, you can give up to 50 claps! Try it! 😉😬</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4848c32c6e85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/hiremate-rethinking-recruitment-processes-for-quality-hiring-a-ui-ux-case-study-4848c32c6e85">HireMate: Rethinking Recruitment Processes for Quality Hiring : a UI/UX case study</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating the Pegasus design system- A UI/UX case study]]></title>
            <link>https://medium.com/design-bootcamp/creating-the-pegasus-design-system-a-ui-ux-case-study-86a1bcaae711?source=rss-c0304ea8d450------2</link>
            <guid isPermaLink="false">https://medium.com/p/86a1bcaae711</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ashmik Ragesh]]></dc:creator>
            <pubDate>Tue, 23 May 2023 18:57:17 GMT</pubDate>
            <atom:updated>2023-05-24T21:16:56.208Z</atom:updated>
            <content:encoded><![CDATA[<h3>Creating the Pegasus design system- UI/UX case study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_OPJjSXeW3WjQAYosUmrfQ.png" /><figcaption><a href="https://www.figma.com/file/rgnhD73pO5XvoxMfJffFax/Pegasus-design-system?type=design&amp;t=OFsxxHIjvhDGxSiK-6">The Pegasus design system</a></figcaption></figure><h3>What is a design system?</h3><p>In summary, a design system is a set of standards to manage design at scale by reducing redundancy and maintaining consistency. A design system is a collection of documents, articles, examples, code snippets, screenshots, design guidelines, components, philosophies and other digital assets for a product design company. It’s usually hosted online as a website.</p><h3>01. Project overview</h3><p>Cubera tech had just launched a new product called Pegasus ( a router configuration app) but it lacked consistency. This happened because all these parts of the apps were designed at different times, by different designers having a different context. There was no unifying design philosophy or principles to guide them.</p><p>These problems got worse when we started designing for any new page, product or feature. Also, because of no underlying specified design principles, a lot of time was wasted in debating and implementing design decisions. User experience also suffered because of lack of predictability and consistency.</p><p>So Pegasus needed a new design language that is unique to this new product but still complements the brand and stays true to its core brand values.</p><h4>Duration</h4><p>3 months</p><h4>Platform</h4><p>Native Mobile App</p><h3>02. Problem Statement</h3><p>We identified the need for a new design system for our new product (Pegasus) to ensure consistency and efficiency across various features and interfaces. We recognised that without a design system, inconsistencies in design and user experience could lead to a confusing and frustrating experience for users and that could hurt brand’s reputation.</p><h4>Goals</h4><ul><li>We wanted to drive consistency in all our products on different platforms and across different businesses which would result in great user experience.</li><li>Work through the basic design system and make it mature and robust.</li><li>We wanted to incorporate the new modern visual design trends in our app so that it looks fresh and is a delightful experience for the users.</li></ul><h4>My responsibilities</h4><ul><li>Lead on all things design system.</li><li>Carry out research and competitor analysis and identify best in class practises for a brand new design system.</li><li>Help create a design system that would help the designers and developers to bring consistency in the mobile app.</li></ul><h4>Team</h4><ul><li>2 Designers</li><li>1 Developer</li><li>1 Illustrator</li></ul><h3>03. Process</h3><p>The process of creating a well structured design system had 3 phases, below is an overview:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sNmFqYZpKlmFb8tFfCQUUw.png" /></figure><h4>1. Research</h4><p>Following a series of interviews with individuals from various departments such as front-end developers, product managers, and marketing managers, we have recognised the need to accomplish two primary objectives:</p><ol><li>Identify and address all the design-related challenges present in our product.</li><li>Learn the common standard and principles of a successful design system.</li></ol><h4>1.1 Benchmark</h4><p>We had to find open source design systems that share common design principles as Pegasus. We picked these 3 as a result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87PEyYcR7NxQcPHCXRsyqw.png" /></figure><h4>1.2 User Research</h4><p>As we had not officially launched the app on the app store we could not get user reviews. So we had to approach a different route. We tested our app (with the old design system) with college students and teachers from the <a href="https://pes.edu/"><strong>PES university</strong></a><strong> </strong>Bangalore.</p><p><strong>Key findings:</strong></p><ol><li>The UI of the app was a bit outdated and needed a revamp.</li><li>The Primary colour looked a bit dull and needed to be a bit more brighter.</li></ol><h4>2. Definition</h4><p>The major problem I faced while creating the design system was “How do I build the UIKit first without knowing how the interface will turn out? But also, how do I make the interface when we don’t even have a defined the UIKit? That’s when I read about Brad Frost, who introduced the <a href="http://bradfrost.com/blog/post/atomic-web-design/"><strong><em>Atomic Design methodology</em></strong></a>.</p><p>Going through all of this I concluded that moving directly to pages to develop a UIkit was not probably the best idea. The answer lied in building both of them parallelly and making changes to them simultaneously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NbRPtPv2qomznJH-U8L3OA.png" /><figcaption>I used the atomic design as assets and reference in the process of making the design system</figcaption></figure><h4>2.1 Building the structure</h4><p>To begin with, we started designing basic atoms of our design system like typography, colours and spacing. Things got more interesting and tangible when we started combining these atoms together to form molecules like buttons, form fields, table cells etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lYr3LBr8PIjM5YC2pgNNgA.png" /><figcaption>Colours</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yVi0gFndQ91Rm-ZFRdMJlA.png" /><figcaption>Typography</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0huUNoyZ8v8YsoBr_RBlvw.png" /><figcaption>Spacing</figcaption></figure><h3>3. Design</h3><p>For the design part, we made sure that each of our components is <strong>Accessible, Intuitive and Aesthetic.</strong></p><p>I decided to lay down a very basic UIKit for the designers to start mocking up designs using the basic components keeping in mind that these components will evolve to accommodate a proper built incorporating all the defined principles but with minimal breaking changes.</p><h4>3.1 Icons</h4><p>Icons are an essential part of any design system as they help communicate visual meaning quickly and effectively. They provide users with visual cues and enhance the overall user experience.</p><p>Our <a href="https://www.behance.net/snehapk08">Illustrator</a> helped us create these beautifully outlined icons :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMvMYEYK-fcWmZtL-L17ag.png" /><figcaption>Icons</figcaption></figure><h4>3.2 Shadows</h4><p>Shadows are another commonly used style property in most UIs. From what I’ve seen, a lot of designers just come up with shadows for their while designing the UI.</p><p>These four shadows should be enough to style every component in our system:</p><ul><li>A subtle shadow to raise interactive components and add affordance.</li><li>A more pronounced shadow for a hover effect on components.</li><li>A strong shadow to give perspective to drop-downs/popovers and other similar components.</li><li>A distant shadow for modal components.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NLldVijoBJQ3Oa5s9N9gA.png" /><figcaption>Range of shadows</figcaption></figure><h4>3.3 The humble button</h4><p>Buttons are fundamental components in any user interface, serving as actionable elements that enable users to interact with your product.<br>When designing buttons, it’s essential to strike a balance between aesthetics and functionality. Buttons should be visually appealing while clearly communicating their purpose.</p><p>Figma’s component system enables you to create reusable button components that can be easily customised and scaled.</p><p>These were some of the variants for the default button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Bt3c68g7MGSqeUKJt8rXw.png" /><figcaption>Buttons</figcaption></figure><h4>3.4 Check box</h4><p>Checkboxes are essential elements in user interfaces that allow users to make selections or indicate preferences.<br>When designing checkboxes, it’s important to focus on clarity, accessibility, and intuitive interactions.</p><p>These were some of the variants we needed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PE3JP_INyjPtzNgJ0kg-ow.png" /><figcaption>Checkboxes</figcaption></figure><h4>3.5 Input fields</h4><p>Textfields are crucial interactive components that allow users to input text or data. Designing textfields involves considering both functionality and aesthetics.</p><p>1 thing we needed to consider was to ensure that textfields have a clear purpose and are easy to understand. Use descriptive labels and provide clear instructions or placeholder text to guide users on what type of input is expected.</p><p>These were some of the variants I came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OWrHMSDzqnsMVnfMzoh4Wg.png" /><figcaption>Textfields</figcaption></figure><h4>3.6 Toggle</h4><p>Toggles are interactive components that allow users to switch between two mutually exclusive states, such as on/off or active/inactive.Designing toggles involves considering clarity, simplicity, and ease of use.</p><p>These were some of the variants we used:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8V82Fq_fFaDJEJskhLF-Hw.png" /><figcaption>Toggle</figcaption></figure><h4>3.7 Radio button</h4><p>Radio buttons are interactive components that allow users to select a single option from a list of mutually exclusive choices.</p><p>Ensure that radio buttons have a clear visual indication of their selection state. We needed to use distinctive labels, or visual cues that clearly differentiate the selected option from the others. This helps users understand their current selection at a glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzlFYTvfp8Dj8d9nAfmsBw.png" /><figcaption>Radio button</figcaption></figure><h4>3.8 Tooltip</h4><p>Tooltips are small information pop-ups that provide additional context or explanations for elements on a user interface.Designing tooltips requires careful consideration of their purpose, appearance, and interaction.</p><p>These were some of the variants we used:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rsyutOJd0qxRlRe2fAvpHg.png" /><figcaption>Tooltip</figcaption></figure><h4>3.9 Tags</h4><p>Designing tags involves considering their purpose, appearance, and usability. My motive was to ensure that tags have clear and concise labels that accurately represent the associated content or category. Use short, meaningful text or visual icons to convey the purpose or context of each t</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0yn-wNkGHDkVz0ZaSElNBg.png" /><figcaption>Tags</figcaption></figure><h3>04. How did this help Cubera and its stakeholders?</h3><p>🎨 <strong>Designers — </strong>It has become a lot easier to create, share and synchronise quite an extensive set of components at a much faster rate. Also, going forward it will eventually help us in easy knowledge transfer to the new team members.</p><p>👩‍💻 <strong>Developers — </strong>The component library they created based on the UIkit helped them maintain the sanity of code and consistency in the final product.</p><p><strong>📟 Company — </strong>We achieved the goal of making all the businesses look consistent across platforms</p><h3>05. Here are some lessons I’ve learned</h3><p>Building this design system took a lot of time and there was a lot of back and forth. But it was definitely worth the effort. It has significantly improved our workflow, consistency across our products, and collaboration across the organisation.</p><p>I was able to collect lots of inspiration from different resources all over the internet. Collecting different UI kits and also using different design systems helped me a lot.</p><p>And that’s a wrap! If you liked this case study, please give it a clap! :)</p><p>You can connect with me on LinkedIn <a href="https://www.linkedin.com/in/ashmik-ragesh-74aa66217/">here</a>.</p><blockquote>Fun fact: if you hold down the clap button, you can give up to 50 claps! Try it! 😉😬</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86a1bcaae711" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/creating-the-pegasus-design-system-a-ui-ux-case-study-86a1bcaae711">Creating the Pegasus design system- A UI/UX case study</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PagePilot — A Figma plugin built with the support of ChatGPT]]></title>
            <link>https://medium.com/design-bootcamp/pagepilot-a-figma-plugin-built-with-the-support-of-chatgpt-2fdc4946f767?source=rss-c0304ea8d450------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fdc4946f767</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[organising]]></category>
            <category><![CDATA[figma-plugin]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[plugins]]></category>
            <dc:creator><![CDATA[Ashmik Ragesh]]></dc:creator>
            <pubDate>Wed, 10 May 2023 14:05:34 GMT</pubDate>
            <atom:updated>2023-05-12T21:55:24.799Z</atom:updated>
            <content:encoded><![CDATA[<h3>PagePilot — A Figma plugin built with the support of ChatGPT</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1Frb3vkqQVaDAvvSPCO6A.png" /><figcaption><a href="https://www.figma.com/community/plugin/1237272529482688041">Click here to access the plugin</a></figcaption></figure><h3>What are plugins?</h3><p>Plugins are third-party tools that you can add to Figma to extend its functionality. They are created by developers and designers and can be installed directly into the Figma editor. Plugins can help streamline design workflows, automate repetitive tasks, and add new features to Figma.</p><h3>Overview</h3><p>AI tools are currently gaining a lot of attention and buzz. It’s nearly impossible to browse through any social media platform without coming across news about the latest AI tool.</p><p>As a designer, I have <strong>very limited knowledge on coding</strong>, so I was curious to see if I would be able to create a plugin entirely with AI.</p><p>In this case study, we will explore the creation of PagePilot, a Figma plugin that organises and names pages to simplify design handoff. We will also delve into how this plugin was built using ChatGPT, an AI language model developed by OpenAI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OTuqQwW8afhMsV_2zrL-Fg.png" /></figure><h3>What is PagePilot?</h3><p>PagePilot is a Figma plugin designed to simplify the process of organising and creating pages in Figma. With PagePilot, users can quickly create and organise pages with predefined templates, making it easier to navigate Figma files, especially during design handoff.</p><p>Overall, PagePilot is an essential tool for anyone working on complex Figma projects and looking to simplify the process of organising and creating pages in Figma.</p><h3>How PagePilot was born?</h3><h4>The Problem</h4><p>Design handoff can be a time-consuming and tedious process, especially when dealing with complex Figma files. Designers and developers often have to sift through multiple pages and layers, making it difficult to find the necessary design elements. This can lead to errors and miscommunication, causing delays in the development process and a decrease in productivity. Additionally, designers may have to spend extra time organising and labelling the pages for easier handoff, which takes away valuable time from the actual design process.</p><h4>How to solve it</h4><p>After brainstorming some of the possible solutions I found out that creating a plugin which would automatically create and organise pages in the Figma file that you are working on, which otherwise is would have been done manually by the designers and leads to delay in the handoff process to the developers.</p><p>So creating a plugin which helps in :</p><ol><li>Organising design files into smaller, more manageable pages, making it easier to locate and navigate specific sections.</li><li>Reduces the risk of errors or omissions by providing a consistent and structured framework for organising design files.</li><li>Divides designs into logical chunks based on their functionality or user flow, making it easier to understand the overall structure of the design.</li></ol><h3>Creating PagePilot</h3><p>The idea was there and now it was time to execute it. Only problem was that I had zero knowledge on how to code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZNBXhjId2BpnVTthY1v9Rw.png" /><figcaption><a href="https://www.supermeme.ai/">AI meme generator</a></figcaption></figure><p>My aim was to create a fully functional plugin with the help of AI tools mainly ChatGPT. But first I needed to learn on how a basic plugin is made on Figma.</p><h4>Sources that helped me get started</h4><ol><li>I had seen a post by <a href="https://www.linkedin.com/in/shaiii/">Shai Krishna</a> on how to setup a new plugin in your file <a href="https://www.linkedin.com/posts/shaiii_create-a-figma-plugin-using-chatgpt-activity-7054314409808064512-xsAn?utm_source=share&amp;utm_medium=member_desktop]">(Post)</a> and also on how to add codes to your plugin.</li><li>The Figma youtube channel had a playlist that also explained on how to create your first plugin (<a href="https://www.youtube.com/playlist?list=PLXDU_eVOJTx5YBAszyuOTyxlgIxkQVyii">Video</a>)</li></ol><h4>Pages to be included</h4><p>My mission was to create a plugin which made it easy for designers, developers, and project managers to navigate and understand the project at a glance. So I had find out a layout and order in which it would be a breeze for people to navigate from one page to other and in the order of importance.</p><p>After a lot of research this is the layout and order I felt would be best for everyone:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*hrt41RlFTeKY6cZenJFmkw.png" /></figure><p>Each of the designers I spoke with used pages within files to separate what was still being worked on, what was ready for feedback, and what was ready to build, while also making space for the iterations along the way. Using emojis in various pages also made it more intuitive and fun to use. So why not ⚙️✅</p><h4>Time to code</h4><p>Since ChatGPT has proven to be valuable in many professions and is only expected to improve going forward, I decided to test its capabilities and limitations.<br>So I got started with hatGPT and entered the below prompt.</p><p><em>“ Give me the codes for a Figma plugin that automatically create pages in a Figma file when run. This plugin will have no UI and will work as soon as it is run. The pages are as follows: ”</em></p><p>and then added all the pages that were required 📑</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ybgr2Ebvmts5-PLj7SbExA.png" /><figcaption>Codes generated by ChatGPT</figcaption></figure><p>I was shocked on how fast ChatGPT had given me the codes for the plugin although the prompt was not fully accurate and this also being my first prompt.</p><p>But when I tested the plugin out it lead to an error 🚨😮‍💨</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CuPoTlpzo7SmUIgdnmAPKw.png" /></figure><p>I had asked ChatGPT not to create a UI for the plugin as I wanted the plugin to run the make the pages in a single click.</p><p>I went on and mentioned the error to ChatGPT and it gave a bit different code this time.</p><p><em>“ There is an error stating that the html is not defined ”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2MFP2L81s_hFSG4iinh-sQ.png" /><figcaption>The updated code for the plugin</figcaption></figure><p>I started to notice that ChatGPT produces different versions of the same code on the same prompt, and after trying it a bunch of times with different prompts and error messages I finally got the output I was looking for 😻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RrUyKXYNyJYc9HwJYF4ZsA.gif" /><figcaption>PagePilot in action</figcaption></figure><h4>Publishing the plugin</h4><p>I had to find out a perfect icon for the plugin which denoted what my plugin did and also had to discribe it properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZspBycoWEf6lGWVO3If_cw.png" /><figcaption>The PagePilot logo</figcaption></figure><p>This logo denoted what my plugin does best, that it divided the file into multiple pages and organised them so that it would help in a smooth handoff between developers and PM’s.</p><p>After completing all the details it was now time to publish it in the Figma community. And after 3–4hrs I got a message stating that my plugin had been approved 🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HbEfN0enhCsXRhaD2fjjQ.png" /><figcaption>Email by Figma</figcaption></figure><h4>Link to the file</h4><p><a href="https://www.figma.com/community/plugin/1237272529482688041">Figma</a></p><h3>User testing</h3><p>User testing is important for PagePilot because it helps to identify any usability issues or bugs in the plugin. User feedback can reveal areas where the plugin may be difficult to use or understand, allowing for improvements to be made before the plugin is released to the public.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*syA5Oy-wNOlYNGJFZGJ2kg.png" /></figure><p>I actually had the opportunity to test the plugin with a bunch of users and designers and these were some of the minor things that can be improved in the upcoming versions</p><h4>User feedback</h4><ol><li>“PagePilot has made it so much easier to navigate through our Figma files. The automatic page generation has saved us a lot of time and effort.”</li><li>“I really appreciate the organised structure that PagePilot provides. It’s now much easier to find what I’m looking for in our Figma files.”</li><li>“With PagePilot, we no longer have to manually create pages and think about the order of pages. It’s all taken care of, leaving us more time to focus on the design work.”</li><li>“As a designer, I have a lot of files to manage, and PagePilot has been a game-changer for me. It saves me so much time and makes it easy to navigate through my files. One suggestion I have is to add the ability to customise the order of the pages. That would be really helpful.”</li><li>“PagePilot has been a lifesaver for me. I used to spend hours manually organizing my Figma files, but now I can do it with just one click. The only issue I’ve had is that sometimes it is hard for the user to understand that the pages have been added in the file”</li></ol><h4>Things to improve in the next version</h4><ol><li>A notification indicating that the pages have been added in the file is necessary as most of the designers where not able to understand that the pages were added.</li><li>A few more pages were requested to be added in the file that would make it easier for the developers and PM’s to understand the flow of the product. Mainly user flow, information architecture and other relating pages.</li></ol><h3>Key Learnings and Challenges Faced</h3><ol><li>Understanding the limitations of AI: While AI can be incredibly powerful and efficient, it is not a silver bullet that can solve all problems. It is important to understand the limitations of the technology and work within its constraints.</li><li>Balancing automation and user control: While automation can save time and improve efficiency, it is important to balance it with user control. Giving users the ability to customise the plugin’s behavior can improve the overall user experience.</li><li>Testing and iteration: User testing and iteration are crucial for developing a successful plugin. It is important to get feedback from real users and iterate on the design and functionality based on that feedback.</li><li>Keeping up with updates: Figma and other design tools are constantly evolving, and it is important to stay up to date with the latest updates and changes. This can sometimes require significant changes to the plugin’s code and functionality.</li></ol><p>And that’s a wrap! If you liked this case study, please give it a clap! :)</p><p>You can connect with me on LinkedIn <a href="https://www.linkedin.com/in/ashmik-ragesh-74aa66217/">here</a>.</p><blockquote><strong><em>Fun fact: if you hold down the clap button, you can give up to 50 claps! Try it! 😉😬</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fdc4946f767" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/pagepilot-a-figma-plugin-built-with-the-support-of-chatgpt-2fdc4946f767">PagePilot — A Figma plugin built with the support of ChatGPT</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marvel’s Snap— UI/UX Case Study]]></title>
            <link>https://medium.com/design-bootcamp/marvels-snap-ui-ux-case-study-9f727d8f3875?source=rss-c0304ea8d450------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f727d8f3875</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[marvel-snap]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[gameux]]></category>
            <dc:creator><![CDATA[Ashmik Ragesh]]></dc:creator>
            <pubDate>Fri, 09 Dec 2022 14:18:31 GMT</pubDate>
            <atom:updated>2022-12-22T06:11:04.991Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gi3OGreFy7GE4BT3J8BR4w.jpeg" /><figcaption><a href="https://www.marvelsnap.com/">https://www.marvelsnap.com/</a></figcaption></figure><h3><strong>Overview</strong></h3><p>Playing Marvel Snap and identifying the core game loop. Deconstructing the home screen and identifying 3 pain points and providing solutions for the same and what KPI’s they’d affect.</p><h3><strong>My Role</strong></h3><p>UX designer</p><h3><strong>Design Process</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcXJE-4rhnXKYko4psPsIg.png" /></figure><h3><strong>Define</strong></h3><h4>About the game</h4><p>MARVEL SNAP is <strong>a fast-paced card battle game</strong>. In the game, you will be able to choose members from the Marvel multiverse to build your own super hero team. MARVEL SNAP unleashes the complete MARVEL Multiverse into a fast-paced, adrenaline-pumping, strategic card battler.</p><h4>Core game loop</h4><p>Marvel Snap’s core gameplay loop is all about playing more matches to get <strong>Boosters and Credits</strong>. These allow you to level up your cards, which allows you to unlock more cards. The in-game purchases don’t do much for progression, so it really is a game that rewards you for playing rather than paying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*dM4SfTyLLFq-DF7w4k1QSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yk49coYLnMqzEfVKRzR2Hg.png" /></figure><h4>Requirements</h4><ul><li>Increase Usability.</li><li>Improve aesthetics.</li><li>Easy Navigation.</li></ul><h3>Research</h3><h4>Pain points ( Home )</h4><ol><li><strong>Navigation menu</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uXf-FZ8D6wIKaAerb1tZA.png" /></figure><ul><li>The bottom Navigation bar ideally has 5 options Shop, Collection, Main, Season pass, News.</li><li>But each of the option can only be identified on clicking them.</li><li>Also the icons that have been used are not universally recognized, so the user might face a lot of problem while starting of with the game.</li><li>Yes the user will learn it by using it 100’s of times ( Which one will ) but initially would face a lot of problems with it.</li></ul><p><strong>2. The News option</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*geD4XqVeafo2XO9_F-7D5w.png" /></figure><ul><li>The news option mainly shows the Inbox, news and the latest videos of the game.</li><li>But it has actually been repeated twice.</li><li>The main menu is already super packed and I don&#39;t see the use of 2 news option with the same motive behind it.</li><li>Unlike the <strong>Season pass</strong> option which also has been repeated twice but both have different use cases. The one on the top indicated the <strong>progress</strong> as well.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XEEz9STxB2fwtHZbLh7pVw.png" /></figure><p><strong>3. Main slide indicator</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7lw69n8cpLjO87mjN7XP0w.png" /></figure><ul><li>The main menu has an image in the center indicating parts of the game and news or new updates.</li><li>But what users don&#39;t notice is that there are images as a <strong>slide function</strong> which the user don&#39;t even notice until an other image comes up after delay.</li><li>A <strong>indicator</strong> for the slide is what is missing here.</li></ul><h4>Twitter Survey</h4><p>Because I only had 2 days to complete the task I had to get the survey answers quick, I posted a question on twitter and the community didn&#39;t fail me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*vLBRhjrzvtPAFS5YcE1Dfg.png" /><figcaption><a href="https://twitter.com/Ashmik19/status/1601099436943630336">Question</a></figcaption></figure><p>The replies came pouring and these were the some that I think were accurate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*umdhCpU3liJ0HJBzegIofg.png" /><figcaption>Answers</figcaption></figure><h4>Pain points ( In- game )</h4><ol><li><strong>Location of the End turn and Surrender options</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ix0j8g-QiocpLZRTgNB70g.png" /></figure><ul><li>Fits law teaches us that targets should be easily accessible.</li><li>The <strong>surrender</strong> and <strong>end turn</strong> options are are placed in a bad spot and most of the users tend to click them by mistake.</li><li>The <strong>Surrender button</strong> are is misplaced for the <strong>left handers</strong> and the E<strong>nd turn</strong> for the <strong>right handers</strong></li><li>This also happens in the case of the <strong>navigation bar</strong> on the <strong>home screen</strong> where the <strong>news</strong> and <strong>shop</strong> options are placed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*cJvnCuaKq_MRxtby4-poow.png" /></figure><p><strong>2. Atrocious timer feature</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*LllAKsHdVyQjp2KYXN09mA.png" /></figure><ul><li>The <strong>timer feature</strong> in the game is just bad.</li><li>People don&#39;t tend to notice the timer feature that is right on the e<strong>nd turn button.</strong></li><li>The <strong>light purple</strong> moving out from the <strong>darker one</strong> is not a visible. It took me 3 days to even find out that the game had a timer in it.</li></ul><p><strong>3. Who’s turn is it to play?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vvpcy2ZDanC22EXvQh4x4g.png" /></figure><ul><li>The highlight for the user who has to play next is also a bit confusing.</li><li>A small beam of light on the frame of the name is what indicates it.</li><li>Though the user gets a hold of it with multiple use. It is a bit confusing at first.</li></ul><h3>Ideate</h3><h4>User flow ( Starting a game )</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kit63v98SngXcwSz2ihqrQ.png" /><figcaption>User flow to start a game</figcaption></figure><h4>Sketches</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBtDZ6Ams4WxICxIw2H4JQ.jpeg" /><figcaption>Sketches of the home screen</figcaption></figure><h4>Wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stY0TAW58QNYuU-D9lQ_JQ.png" /><figcaption>The home and the In-game Wireframes</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Ffile%2FJTWqFpUbLUHdrNRtGbzgDs%2FMarvel-Snap%3Fnode-id%3D0%253A1%26t%3DLKTD92qOjkLOhHxB-1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Ffile%2FJTWqFpUbLUHdrNRtGbzgDs%2FMarvel-Snap%3Fnode-id%3D0%253A1%26t%3DLKTD92qOjkLOhHxB-1&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Fa1ef8dd6-5819-4468-923e-f5c0447b9ee7%3Fheight%3D43%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/6029d1bf92a957d3237861e23ec4babc/href">https://medium.com/media/6029d1bf92a957d3237861e23ec4babc/href</a></iframe><h4>Solution explanation</h4><p><strong>Home page</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B2TIljJA5utTEUY82VH-4g.png" /></figure><ol><li>The problem faced was that the user has to click the Bottom nav bar option to identify. But by <strong>naming each option</strong> the user can get an idea before clicking it and intern it also makes the navigation smooth.</li><li>The problem was that the <strong>news option</strong> has been repeated twice even while having the same function. The home menu is already a bit intimidating to the user, so by removing the top news option and rearranging, it looks a bit cleaner now.</li><li>The images in the center of the home page is actually slider and on swiping other images come up. But there is no indication for that. So by adding an <strong>indication</strong> the user now is able to or knows that he should swipe to see different images.</li></ol><p><strong>In-game</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vENeCkEx8dyu_1XgjlxNMw.png" /></figure><ol><li>The problem faced was that user tend to click the <strong>retreat </strong>and <strong>end turn</strong> buttons by mistake because they have been a bit misplaced. Keeping this in mind, I decided to use a grid system and use <strong>35px</strong> as margins. Now the user would not click the buttons by mistake.</li><li>The problem faced was that the timer was not visible to most of the users and only after playing it many times would the user get an hang of it. So the solution I did come up was to bring in a timer when only <strong>20 sec</strong> would be left on the clock.</li><li>The problem was that the user does not get to whose turn is it to play next. So the solution was to to create a <strong>pop up </strong>indicating whose turn it would be next.</li></ol><h3>Reflection</h3><p>This was a project made for a design task that I was assigned recently. I had 2 days for the completion of the task and so I had to improvise and conduct the surveys where I would quickly get results.</p><p>Also adding a brief explanation of my case study down below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2Fdfff1ebabe954071b0d916d382e2116f&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2Fdfff1ebabe954071b0d916d382e2116f&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2Fdfff1ebabe954071b0d916d382e2116f-00001.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1920" height="1440" frameborder="0" scrolling="no"><a href="https://medium.com/media/baa1098d9df173295462d4fa21111bd9/href">https://medium.com/media/baa1098d9df173295462d4fa21111bd9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f727d8f3875" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/marvels-snap-ui-ux-case-study-9f727d8f3875">Marvel’s Snap— UI/UX Case Study</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 design systems to learn (and steal) from in 2022 for UX Designers]]></title>
            <link>https://rageshashmik.medium.com/5-design-systems-to-learn-and-steal-from-in-2022-for-ux-designers-2ae34fb991e6?source=rss-c0304ea8d450------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ae34fb991e6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ashmik Ragesh]]></dc:creator>
            <pubDate>Wed, 21 Sep 2022 10:00:22 GMT</pubDate>
            <atom:updated>2022-09-21T14:21:22.315Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ekr9lqsGCQBLpuVp6LUPRw.png" /></figure><h4><strong>What is a design system?</strong></h4><p>In summary, a design system is a set of standards to manage design at scale by reducing redundancy and maintaining consistency. A design system is a collection of documents, articles, examples, code snippets, screenshots, design guidelines, components, philosophies and other digital assets for a product design company. It’s usually hosted online as a website (public or internal).</p><h4>What can you learn from them?</h4><p>So how can you learn from this? Say you’re designing a e-commerce website and the menu needs a dropdown for categories. Not sure what size your arrow should be on the dropdown or how far away from the text to place it ? Well, you can look to a shopping system pioneer like <strong>Shopify</strong> to see how they do it!</p><p>Here is my curated list of 5 design systems that you can steal ideas from:</p><h4><strong>1. Google Material Design System</strong></h4><p>In terms of design, Google’s publicly shared ‘Material Design’ system paved the way for many to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*w-wewpGpDMt3B91wZGqWkw.png" /><figcaption><a href="https://material.io/">https://material.io/</a></figcaption></figure><h4>2. Apple Human Interface Guidelines</h4><p>Needing no introduction, elegant and intentional design is in the very DNA of Apple. Apple’s Human Interface Guidelines is not only a design system but an incredible resource full of downloadable templates and other guidelines that you can use in your own projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uxhpsxTs2VClpJ8P73VYRA.png" /><figcaption><a href="https://developer.apple.com/design/human-interface-guidelines/">https://developer.apple.com/design/human-interface-guidelines/</a></figcaption></figure><h4>3. Microsoft Fluent Design System</h4><p>Microsoft’s ecosystem of design tools and open-source components can help you get the same look as their products quickly and easily so you can create a consistent vision across Web, Windows, iOS and Android platforms and understand the logic and look of Microsoft products</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdw1B5cnvGBDau-bJ2KuXw.jpeg" /><figcaption><a href="https://www.microsoft.com/design/fluent/#/">https://www.microsoft.com/design/fluent/#/</a></figcaption></figure><h4>4. Atlassian Design System</h4><p>Atlassian design system has plenty of design resources to create better and scalable designs. These resources include tools, plugins, and kits. It has patterns that are a reusable combination of components used to solve user problems. It has an intuitive interface that makes it easy to create designs</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*shl6WIE0V1QKXy0nszYoaQ.png" /><figcaption><a href="https://www.atlassian.com/">https://www.atlassian.com/</a></figcaption></figure><h4>5. IBM Carbon Design System</h4><p>Carbon allows teams to build excellent experiences that differentiate IBM from the competition. Products and experiences built with Carbon provide an interoperability of experience and visuals across products. More complex multiproduct stories are easier to tell when product experiences are in lock step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*STf8K1uBB-Zd1touYeVx9w.jpeg" /><figcaption><a href="https://www.carbondesignsystem.com/">https://www.carbondesignsystem.com/</a></figcaption></figure><p>So those are my choices for top design systems and what you can learn from them. Hopefully, this will have you seeing them in a new light.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ae34fb991e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>