CSE - CCS370 - UI &UX - Manual
CSE - CCS370 - UI &UX - Manual
LAB MANUAL
CCS370_UI&UX LAB
TABLE OF CONTENTS
1. DESIGNING A RESPONSIVE
LAYOUT FOR A SOCIETAL
APPLICATION
2. EXPLORING VARIOUS UI
INTERACTION PATTERNS
CCS370_UI&UX LAB
EX.01: Designing a responsive layout for a societal application
Algorithm:
Program:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Societal Application</title>
<style>
/* Reset some default styles */body, html {
margin: 0;
padding: 0;
font-family: Arial, sans-serif;
}
CCS370_UI&UX LAB
/* Navigation styles */nav {
background-color: #47fff0;color: #fff;
text-align: center;
}
nav ul {
list-style: none;padding:
0;
}
nav li {
display: inline;margin:
0 15px;
}
CCS370_UI&UX LAB
OUTPUT:
DESKTOP VIEW:
CCS370_UI&UX LAB
TABLET VIEW:
CCS370_UI&UX LAB
PHONE VIEW:
CCS370_UI&UX LAB
Figma:
Aim: To design a responsive layout for a societal application.
Algorithm:
Procedure:
Creating a responsive website in Figma:
Result: Thus designing of responsive layout for a societal application hasbeen performed
successfully.
CCS370_UI&UX LAB
EX.02: Exploring various UI Interaction Patterns
Algorithm:
Procedure:
Figma Design:
CCS370_UI&UX LAB
Clicks/Taps:
Users perform a single click (on desktop) or tap (on mobile devices) on buttons, links, or
interactive elements to trigger actions like opening a page, submitting a form, or revealing
additional information.
Hover/Mouseover:
When users move their cursor over an element, it triggers a visual change or displays additional
information, providing contextual cues. For example, buttons might change color or tooltips may
appear.
Swipe/Gesture:
On touch-enabled devices, users use swiping gestures to scroll through content, navigate
between pages, or dismiss items. These gestures enhance navigation and engagement.
Scrolling:
Scrolling allows users to vertically or horizontally navigate through content that doesn't fit within
the visible area. It's a fundamental way to explore lengthy web pages or lists.
Accordion:
Accordions allow users to expand and collapse sections of content, conserving space while
providing a way to reveal additional information or options.
Modal/Popup:
Modals or popups are temporary overlays that appear on top of the main content. They require
user interaction before users can proceed, providing focused attention on a specific task.
Toggle Switch:
Toggle switches represent binary options that users can switch on or off. They're often used for
settings or toggling between modes.
Menu:
Menus display a list of options or actions that users can select, often accessed through buttons
or icons, providing a hierarchical structure to navigate within an app.
Progress Bar/Loader:
Progress bars or loaders indicate the status of an ongoing task or loading process, keeping users
informed about the system's activity.
CCS370_UI&UX LAB
Result: Thus various UI interaction patterns have been explored successfully.
CCS370_UI&UX LAB
Ex.03: Developing an Interface with Proper UI Style Guides
Algorithm:
Procedure:
• Define Goals and Audience: Understand the project's purpose and targetusers.
• Workspace Setup: Organize Figma files and create sections for styleguides and
components.
CCS370_UI&UX LAB
• Wireframes: Create wireframes and user flows for screen layout andinteraction.
Result: Thus an Interface with Proper UI Style Guides has been developed successfully.
CCS370_UI&UX LAB
Ex.04: Developing wireflow diagram for application using open-source software
Procedure:
1. Define Purpose and Goals: Determine the diagram's purpose and goals,
focusing on user flows, navigation, and interactions.
2. Identify User Personas: If applicable, specify user personas for auser-centric
approach.
3. Gather Requirements: Collect project information, including existingdesigns and
functionality requirements.
4. Select Software: Choose open-source design software, such asFigma, for
wireflow creation.
5. Create a Project: Begin a new project in your chosen software andset up the
canvas to match your project's needs.
6. Wireframe Screens: Develop wireframes for each application screen,focusing on
visual structure.
7. Define Interactions: Add interaction notes or links to illustratenavigation and user
interactions.
8. Create User Flows: Connect wireframes to illustrate user journeys,navigation
paths, and interactions.
9. Add Annotations: Include descriptions to clarify elements andinteractions in each
wireframe.
10. Collaborate and Share: Utilize collaboration features to gather feedback
from team members and stakeholders.
11. Iterate and Refine: Revise the wireflow diagram based on -feedback,
ensuring alignment with project goals.
CCS370_UI&UX LAB
12. Finalize and Export: Clean up the wireflow diagram and export it to a suitable
format for sharing and documentation.
13. Document the Wireflow: Create a reference guide to explain the wireflow's
purpose and key notes for stakeholders and developers.
14. Maintain Consistency: Keep the wireflow diagram in sync with the
application's actual design, updating it as needed.
Design:
Result: Thus Wireflow diagram for application using open-source software has been
developed successfully.
CCS370_UI&UX LAB
Ex.05: Exploring various open-source collaborative interface Platform
Algorithm:
Procedure:
1. Needs Assessment: Define your team's requirements and goals.
2. Research Platforms: Identify open-source collaborative tools.
3. Feature Comparison: Assess features and compatibility.
4. Community Support: Check for active communities.
5. Installation: Set up the chosen platform.
6. User Training: Train and encourage team adoption.
7. Security: Ensure data security and privacy.
8. Integration: Check for compatibility with existing tools.
9. Testing and Feedback: Pilot testing and gather feedback.
10.Scalability: Ensure the platform can grow with your team.
11.Documentation: Create user resources and guides.
12.Community Engagement: Utilize community support.
13.Maintenance: Keep the platform updated and secure.
14.Feedback Loop: Encourage ongoing user feedback.
15.Legal Compliance: Ensure adherence to licensing and Legal requirements.
16.Backup and Recovery: Implement data safety measures.
17.Periodic Evaluation: Continuously assess platform suitability.
18.Migration Plan: Prepare for possible platform changes.
19.Success Sharing: Promote successful platform usage.
CCS370_UI&UX LAB
CCS370_UI&UX LAB
Result: Thus various open-source collaborative interfaces Platform has been explored
successfully.
CCS370_UI&UX LAB
Ex.06: Hands on Design Thinking Process for a new product
Algorithm:
Procedure:
Empathize: Begin by conducting user research and interviews to gain insights into potential
user needs and pain points related to smartphone usage.
Define: Analyze the gathered information to define a clear and specific problem statement.
For example, "Users need a more efficient way to track their daily fitness activities."
Ideate: Organize brainstorming sessions with a diverse team to generate a wide range of
creative solutions. Encourage free thinking and open collaboration.
Prototype: Create a low-fidelity prototype of the smartphone app. This can be a paper
sketch or a digital wireframe that represents the app's basic functionality.
Test: Conduct user testing sessions with a small group of potential users. Observe how they
interact with the prototype and gather feedback.
Iterate: Based on user feedback, refine the prototype and make necessary improvements to
address user concerns or suggestions.
Prototype (Again):Create a more advanced prototype, closer to the final product. It should
incorporate the changes and improvements identified during the initial testing phase.
Test (Again):Conduct another round of user testing, this time with a larger group of users.
Gather data on usability, functionality, and overall user experience.
Refine: Analyze the results of the second testing phase and make further refinements to the
app design and functionality.
Implement: Develop the final version of the smartphone app, incorporating all the changes
and improvements identified during the design thinking process.
Test (Final Testing):Conduct thorough testing of the fully developed app toensure it's bug-
free and ready for launch.
Launch: Release the app to the target market, accompanied by marketing and promotion
efforts.
Example:
Let's say the team is designing a fitness tracking app. During the "Empathize" phase, they
CCS370_UI&UX LAB
conduct interviews and surveys with potential users, discovering that users find it challenging
to keep track of their daily physical activities. In the "Define" phase, they define the problem
as "Users need a more efficient way to track their daily fitness activities."
In the "Ideate" phase, the team generates multiple ideas, including features like GPS tracking,
step counting, and customizable fitness goals. They create a low-fidelity prototype that
represents these features. In the first round of user testing, they observe that users have
difficulty navigating the app.
After gathering feedback and identifying navigation issues, the team iterates by redesigning
the user interface to improve user experience.They create an advanced prototype with a
more intuitive interface and test it with a larger group of users in the second round of testing.
Based on this testing, the team further refines the app, making sure it's user-friendly, bug-
free, and meets the needs of the target audience. Finally, they implement and launch the
fitness tracking app to help users easily track their daily activities.
Result: Thus the design thinking process for new product has been studied.
CCS370_UI&UX LAB
Ex.07: Brainstorming feature for proposed product
Aim:
The aim of this process is to generate innovative and practical feature ideas for a proposed
product, ensuring that the final product meets user needs, addresses pain points, and has a
competitive edge in the market.
Algorithm:
Procedure:
Understand the Product Concept:
Begin by thoroughly understanding the proposed product's concept, itstarget audience, and
its unique selling points.
Idea Generation:
Allow team members to freely brainstorm feature ideas. Encourage a "noidea is a bad
idea" mindset. Use techniques like mind mapping, brainstorming software, or post-it notes
on a whiteboard to record ideas.
Categorize and Prioritize:
Group similar ideas together, and prioritize them based on factors likefeasibility, potential
impact, and alignment with the product concept.
SWOT Analysis:
Conduct a SWOT (Strengths, Weaknesses, Opportunities, Threats) analysisfor each
feature idea to evaluate its potential in the market.
Feasibility Assessment:
CCS370_UI&UX LAB
Assess the technical, financial, and resource feasibility of implementingthe proposed
features.
Market Research:
Conduct market research to identify user preferences and gather insightsthat can inform
feature development.
Cost-Benefit Analysis:
Evaluate the expected cost of development against the projected benefits,such as increased
user engagement, retention, or revenue.
Risk Assessment:
Identify potential risks associated with each feature and develop
mitigation strategies.
Documentation:
Document the chosen features, their objectives, and the rationale behindtheir selection. This
document will guide the development team.
Iterate as Needed:
Keep an open line of communication for ongoing feature refinements anditerations, especially
as more data and insights become available.
Example:
Suppose a software company is developing a new mobile messaging app. During the
brainstorming session, the team generates a wide range of feature ideas, including:
End-to-End Encryption: To ensure user privacy and data security.
Message Scheduling: Allowing users to schedule messages to be sent at a specific time.
Reaction Emojis: A feature that lets users react to messages with emojis for more
expressive communication.
Dark Mode: A night-friendly theme for the app.
Polls and Surveys: Integration of polls and surveys within the chat for easydecision-making.
Auto-Translate: Real-time language translation for international communication.
CCS370_UI&UX LAB
Result: Thus brainstorming feature for proposed product has been applied and executed
successfully.
CCS370_UI&UX LAB
Ex.08: Defining the Look and Feel of the new Project
Aim:
The aim is to establish the visual design and user experience for a new project, ensuring it
aligns with the project's goals and provides an appealing, intuitive, and cohesive interface for
users.
Algorithm:
Procedure:
Visual Design:
Develop a color palette, typography choices, and graphic elements (icons, images, logos)
that reflect the project's identity. Create high-fidelity designs using design software.
User Interaction Design:
Define user interactions and behaviors, including animations, transitions, and micro-
interactions. Ensure a smooth and intuitive user experience.
Responsive Design:
Adapt the design to various screen sizes and devices, focusing on mobile responsiveness.
Documentation:
Create design documentation that includes guidelines for developers toimplement the
design.
Development Integration:
Collaborate with developers to ensure the design is implemented
accurately in the project.
User Testing:
Conduct user testing with real users to verify the design's effectiveness.
Finalization:
Make necessary adjustments and finalize the design elements for
deployment.
Example:
Imagine you're tasked with defining the look and feel of a new e-commerce
website. You go through the following steps:
Assess the project's goal: To create a user-friendly, visually appealing online store.
Research e-commerce design trends and competitor websites.
Choose a clear and readable typography for product descriptions and headings. Plan user
interactions like product image zoom and streamline checkout process.
Iterate on the design based on usability testing feedback. Document the design guidelines for
the development team. Collaborate closely with developers to bring the design to life.
Conduct user testing to validate the design's effectiveness. Make finaladjustments and prepare
for the website's launch.
CCS370_UI&UX LAB
Result: Thus the Look and Feel of the new Project has been defined successfull
CCS370_UI&UX LAB
Ex.09: Create a Sample Pattern Library for the product (Mood board,Fonts,
Colors based on UI principles)
Aim: The aim of this project is to create a sample Pattern Library for a product that includes
mood boards, fonts, and color schemes based on UI (User Interface) principles. The Pattern
Library will serve as a design reference for maintaining consistency and cohesion in the
product's user interface.
Algorithm:
Procedure:
Gather Inspiration:
Research existing UI designs, competitor products, and design trends to gather inspiration.
This will help you create a mood board that captures the desired aesthetics.
Choose Fonts:
Select fonts that align with the product's brand and design goals. Consider readability,
hierarchy, and scalability. Choose a primary font for headings and body text, and possibly
secondary fonts for accents.
Document UI Principles:
Document the UI design principles that underpin the Pattern Library. This may include
guidelines on spacing, layout, typography, and interaction behaviors.
Example:
Let's say you're creating a Pattern Library for a mobile app focused on wellness and
meditation. The aim is to create a soothing and user-friendly design that promotes relaxation.
Here's a simplified example:
Mood Board: Create a mood board with images of serene landscapes, calming color
schemes (e.g., blues and greens), and sample UI elements that convey a sense of tranquility.
Fonts: Choose "Poppins" as the primary font for headings and "Roboto"for body text.
These fonts are clean, readable, and complement the app's aesthetic.
Color Palette: Define a color palette that includes calming colors like "#3CBDBE" for primary
elements, "#70C1B3" for secondary elements, and "#EFEFF0" for background. Ensure that
these colors meet accessibility standards.
CCS370_UI&UX LAB
Result: Thus a sample pattern library for a product was created
successfully.
CCS370_UI&UX LAB
Ex.10: Identify a customer problem to solve
Aim: The aim of this experiment is to identify a customer problem to solve effectively, which
is crucial for product development, customersatisfaction, and business success.
Algorithm:
Procedure:
Customer Segmentation:
Begin by segmenting your customer base into different groups based ondemographics,
behavior, or other relevant criteria.
Data Collection:
Gather data from these customer segments through surveys, interviews, feedback forms,
and analytics tools. You can also utilize data from your customer support system, website, or
app analytics.
Problem Identification Metrics:
Define key metrics and indicators to identify customer problems. Examples include high
bounce rates on a specific webpage, low customer satisfaction scores, or a surge in support
tickets related to a specific issue.
Data Analysis:
Analyze the collected data to identify patterns, trends, and common issues reported by
customers. Data analysis tools and techniques, such as data mining or sentiment analysis,
can be useful.
Prioritization:
Prioritize the identified problems based on their impact on customers and your business. You
can use techniques like the Moscow method (Must- haves, Should-haves, Could-haves,
Won't-haves) to prioritize.
oot Cause Analysis:
Conduct a root cause analysis for each identified problem. Understand why these issues are
occurring by delving into the underlying causes.
Solution Ideation:
Brainstorm potential solutions for the identified problems. Encourage cross-functional teams
to contribute ideas and consider how these solutions align with your business goals.
Experiment Design:
Design controlled experiments or A/B tests to validate the proposed solutions. Ensure you
have a clear hypothesis and success criteria for each experiment.
CCS370_UI&UX LAB
Implementation:
Implement the proposed solutions on a small scale to observe their impact. This might
involve website changes, process adjustments, or feature additions.
Data Collection Post-Implementation:
Continue to collect data after implementing the solutions to assess their effectiveness.
Monitor key metrics to see if they improve.
Analysis and Validation:
Analyze the post-implementation data to validate whether the proposed solutions have
effectively addressed the customer problem. Make data- driven decisions.
Feedback and Iteration:
Collect feedback from customers regarding the changes and iterate on the solutions based
on their input. Continuous improvement is key.
Example:
Let's say you're running an e-commerce platform and want to identify a customer problem
related to checkout abandonment. Here's how you could apply the algorithm/procedure:
Customer Segmentation:
Segment customers based on their demographics and purchase history.
Data Collection:
Gather data through customer surveys, web analytics, and feedbackforms.
Problem Identification Metrics:
One of your key metrics is the high rate of customers abandoning theirshopping carts
before completing the purchase.
Data Analysis:
Analyze the data and find that a significant number of customers abandontheir carts at the
payment stage.
Prioritization:
Prioritize the payment abandonment issue because it directly affectsrevenue.
Root Cause Analysis:
Discover that complex payment options and a lack of guest checkout arecausing the
problem.
Solution Ideation:
Brainstorm solutions, including simplifying payment options and adding aguest checkout
feature.
Experiment Design:
Design A/B tests to measure the impact of these changes on cartabandonment
rates.
CCS370_UI&UX LAB
Implementation:
Implement the proposed solutions on a small scale for testing.
Data Collection Post-Implementation:
Collect data on cart abandonment rates after the changes are
implemented.
Analysis and Validation:
Analyze the post-implementation data and find that cart abandonmentrates have
significantly decreased.
Feedback and Iteration:
Collect feedback from customers who completed purchases and continue to iterate on the
checkout process to further enhance the customer experience and address any remaining
issues.
CCS370_UI&UX LAB
Ex.11: Conduct end-to-end user research - User research, creating personas,
Ideation process (User stories, Scenarios), Flow diagrams, FlowMapping
Aim:
The aim of this experiment is to conduct end-to-end user research and design process to
develop a user-centered solution for a specific problem. This process includes user research,
creating personas, ideation (user stories, scenarios), and creating flow diagrams and flow
maps.
Algorithm:
Procedure:
Define the Problem:
Clearly define the problem or challenge you want to address through thisuser-centered
design process.
User Research:
Conduct user interviews, surveys, or observations to gather insights and data about the target
users. Analyze the collected data to identify user needs, pain points, and behaviors.
Create Personas:
Based on the research findings, create user personas. Personas are fictional representations
of your typical users, including their goals, needs, and characteristics.
Ideation:
Brainstorm creative ideas to address the identified problems and fulfill user needs. Develop
user stories and scenarios to articulate how users will interact with the proposed solution.
User Stories:
Create user stories using the "As a [type of user], I want [an action] so that [benefit/value]"
format. User stories should capture specific user tasks and their motivations.
Scenarios:
Develop detailed narratives (scenarios) that illustrate how users will use the solution to
achieve their goals. Scenarios should provide context, user actions, and expected outcomes.
Flow Diagrams:
Create flow diagrams to visualize the user's journey through the solution.
Use symbols and arrows to represent user actions, system responses, and transitions
between different screens or stages.
CCS370_UI&UX LAB
Flow Mapping:
Develop flow maps to provide a holistic view of the user experience. Connect user stories
and scenarios to specific steps in the flow,highlighting decision points and potential pain
points.
Iterate and Test:
Review and refine your user stories, scenarios, flow diagrams, and flow maps based on
feedback from stakeholders or potential users.Conduct usability testing to validate the
proposed user experience.
Implementation:
Work with developers and designers to implement the user-centeredsolution based on the
finalized flow and design.
Evaluation:
After the solution is implemented, evaluate its effectiveness by gatheringuser feedback and
monitoring key performance metrics.
Iterate and Improve:
Continuously iterate on the design and user experience based on userfeedback and
changing needs.
Design:
Flow Diagram:
CCS370_UI&UX LAB
User Personas:
Flow Mapping:
Result:
Thus a user-centered problem was identified to solve through a comprehensive
process of user research, persona creation, ideation (including user stories and scenarios),
flow diagrams, and flow mapping, with the goal of successfully addressing user needs and
delivering an exceptional user experience.
CCS370_UI&UX LAB
Ex.12: Sketch, design with popular tool and build a prototype andperform
usability testing and identify improvements
Aim:
The aim of this experiment is to design a user-friendly mobile app for task management,
create a prototype using a popular design tool, perform usability testing, and identify
improvements to enhance the user experience.
Algorithm:
Procedure:
Define Objectives and User Persona:
Define the objectives of the task management app. Create a user
persona to represent the target audience.
Prototype Creation:
Use the design tool to create interactive prototypes with clickable elements and
transitions.Ensure that the prototype represents the app's core functionalities.
Recruit Participants for Usability Testing:
Identify potential users or participants who match the user persona. Prepare a usability
testing plan, including tasks to be performed within theprototype.
Usability Testing:
Conduct usability testing sessions with participants. The participants are asked to perform
specific tasks within the prototype. Observe and record their interactions and gather feedback
on their experience.
Conclusion:
Conclude the experiment by summarizing the improvements made to theprototype and how
they enhance the user experience.
Design:
Result:
Thus Sketching, building a prototype, performing usability testing andidentifying improvements
has been executed successfully.
CCS370_UI&UX LAB