Konnect is a mobile-first platform designed to improve accessibility and reliability in parking for people with mobility challenges. The goal was to create a seamless experience that allows users to find, reserve, and pay for accessible parking with confidence.
This project focuses on scalable UI design, system thinking, and accessibility-first interaction design.
UX DESIGN CHALLENGE:
Iterate UX
TEAM:
Four creative individuals:
Mythili Ravishankar, Tania Verma, Bhupinder Bath, and myself.
MY ROLE:
UX Designer, Project Manager, UI Design & Visual System, Component Design & Design System Development
DURATION:
August 14th – September 17th 2023
Out of 24 teams, our team was selected as one of the top 6 to showcase our work in front of the judges.
About the organizer:
Iterate UX is a non-profit, community-centred platform for hands-on learning. They organize different Virtual Events, Design Challenges, Portfolio and Resume Reviews, Whiteboard Challenges, and Interview Mockups.
UX Design Challenge:
Our project came to life by participating in the UX Design Challenge organized by IterateUX. We were given five industries to choose from:-
We opted for the Accessibility Design Challenge.
Accessibility Design Prompt given by IterateUX:
Develop a parking app that caters to diverse users, including those with disabilities. Design features such as reserved accessible parking spots, real-time availability updates, and a seamless payment process that considers various user needs.
Reasons why we choose the Accessibility Prompt:
Project Goal:
Design a comprehensive parking app meticulously tailored to address the distinct requirements of physically challenged people, ensuring accessible and hassle-free parking experiences.
Problem:
Accessible parking today is:
Users need a system that is:
Solution:
Designed a mobile app experience supported by a scalable UI system, enabling:
The focus was not just on screens—but on building a consistent, reusable design foundation.
The app guarantees a stress-free parking experience for both drivers and passengers. Drivers can relax knowing they’ll find a parking spot, while passengers are assured of being dropped off at a reserved location.
Rather than designing isolated screens, Park Allways was approached as a scalable product system.
Core experience layers:
👉 Designed as a connected system, not separate features.
Four Main Features:
2. Report a Violation for the Misuse of an Accessible Parking Spot
3. Reserve an Accessible Parking Spot before Time.
4. Book an Accessible Ride
100% of our users complaint about the misuse of the parking spot.
Reporting violations helps ensure fairness in parking. It discourages individuals from wrongly occupying accessible spots, which can lead to frustration and inconvenience for people with disabilities. In many regions, parking in accessible spots without proper authorization is against the law. Reporting violations can contribute to enforcing these regulations and holding violators accountable.
How does it work?
“Reserve a Parking Spot” is a hassle-free option that ensures you have an accessible parking space waiting for you at your chosen location. This feature is designed to make your parking experience convenient and stress-free.
It has two options. There is a common feature in both options that they choose what kind of vehicle they will be needing, regular or assisted.
Key Benefits:
– Cost Sharing: Split the fare with another user, making transportation more affordable.
– Community Connection: Meet and interact with fellow users travelling to nearby destinations.
– Environmental Impact: Contribute to a more sustainable environment by carpooling.
Dark mode has gained popularity among a broad range of users, including those with disabilities, for the reasons, such as reduced eye strain, improved readability, and reduced sensitivity to light. To ensure inclusivity and accessibility in our design, we provide the option for our users to switch between dark and light modes. This way, users can choose the mode that best suits their needs and preferences, regardless of disability status.
USER EXPERIENCE DESIGN:
Focused on:
Every interaction was designed to:
👉 minimize hesitation
👉 increase user confidence
DESIGN SYSTEM & COMPONENT LIBRARY:
Designed reusable UI components to ensure consistency and scalability:
Each component includes:
👉 Shifted approach from screen-based design → system-based design
The system was designed to:
👉 Result: a flexible and scalable product foundation
Unlocking Potential:
Creating a parking application designed to cater to users with disabilities requires careful planning, prioritizing the needs of the user, and a firm commitment to accessibility. This involves addressing technological, design, and regulatory challenges to ensure that the application is functional and user-friendly for everyone, irrespective of their abilities.
In this UX Design Challenge, two team members were from Canada and two from the USA. To better understand the problem, we analyzed data and perspectives from both countries.
What is a disability?
Physical or mental impairment that substantially limits one or more major life activities.
The next step in our initial research was to define our target audience. To address this concern we decided to target both drivers and passengers with some kind of disability.
We analyzed the competition to know how to stand out in a specific need. In our search, we discovered a total of seven applications, and during our evaluation process, we identified both positive and negative aspects within each of these apps.
We identified two primary competitors and five secondary competitors, and then we did research on the tertiary competitors in the market targeting the disabled population.
Additional organizations, interest groups, influencers, etc. that have vested interest in our market.
We conducted user interviews to gain valuable insights into their needs, preferences, and pain points. This deeper understanding of our target audience allowed us to create more effective and user-centric solutions.
We needed to first gain a comprehensive understanding of the problems. Hence based on our user interviews we first listed the key problems our users are facing and the impacts it had on them.
After the interviews and key findings, all our hypotheses were validated.
While formulating our problem statement, we employed an iterative interrogative approach known as the “Five W’s.” This technique delves into cause-and-effect relationships that underlie a specific issue, aiming to ascertain the root cause of a problem and identify potential solutions. The fundamental objective of this technique is to uncover the core reasons behind the challenge and develop strategies to effectively address it.
From the insights gained from our interviews, we developed two personas that represented our core users.
ALEX: “An Independent Professional”
Who thrives on independence and efficiency. He navigates life in a wheelchair due to a spinal cord injury.
TAYLOR: “A Vibrant Explorer”
Who exudes independence despite her congenital mobility impairment. She resides in an assisted living facility, relying on caregivers for transportation.
To better understand the different categories under which our users had their pain points, we created affinity map from the raw data gathered from the user interviews. This map enabled us to identify recurring patterns and shared aspects among our participants.
To better understand Information Architecture and the different features we will include in our App, we did a card-sorting activity with the data that we got from our participants. Based on all the data that we gather from our affinity mapping and card sorting we filter different key features that we will be including in our App.
Real time updates
Services
Activities
Customization
To ensure that we have a comprehensive grasp of the app’s flow, we developed a flowchart to gain a thorough understanding of our app’s features and functionalities.
We then created the low-fidelity wireframes to outline the basic structure and layout of our app interface and continue to iterate our user flows and features.
We were asked to use an existing design system as we’ve only a few days to prototype. We chose Alaya a Figma UI kit by Allan as our design system. The main reason to choose this kit is that it has both light and dark modes. To create an inclusive and accessible user interface, it’s essential to offer both light and dark mode options and allow users to choose their preferred mode based on their specific needs and preferences. This flexibility ensures that users with disabilities can customize their digital experience to suit their comfort and usability requirements.
For our primary secondary and tertiary colours we choose the bright colours because these visible colours can provide good contrast against many backgrounds, making it potentially suitable for users with visual impairments or those who require elements to stand out.
We make sure that our design should prioritize a balance of colors and consider factors like contrast ratios, user preferences, and the overall user experience.
We wanted to make sure that our app follows the wcag.
Jost is a San Serif Google Font which is designed with accessibility in mind. It adheres to web accessibility standards, ensuring that text is readable by users with various disabilities, including those who use screen readers.
The Alaya design system has many components for both modes which we use to make our App consistent and visually appealing.
Park + Always
Park + All + Ways
Park AllWays
The name “Park AllWays” was chosen to convey the idea that the app provides parking solutions for everyone, in all situations, and at all times.
So, “Park AllWays” was selected to reflect the app’s mission of making parking accessible and convenient for everyone, regardless of their mobility or disability status.
I created some sample logos
This was the final Logo, we aimed for simplicity and cleanliness to effectively communicate our brand’s message.
Lessons learned:
We encountered some challenges during this project. Some of the lessons learned during our journey were:
What I’d do differently next time:
Next steps: