Parkly - Prototyping & Development Blog

Adam Sandell, Alex Tilly Morina, Marina Radic, Hampus Persson, Louisian Boltner, Hong Quan Odin

I. Sketches & Wireframes, 1

December 20, 2024

As a team we sat down and started to individually sketch up rough wireframes for the app, how the app presented the map , different menu options and how and where the user would navigate through the different “pages”. Our motivation for this exercise was to spark a discussion on each individual vision on how the app should look, feel and behave. After each team member had presented their own idea of the app we started to discuss what the goal of the app was, which in short is showing the user where they can park and/or when they should move their car. During a discussion where we put ourselves in the shoes of our user stories, we realized that almost all of our sketches included a login page. For users who are already skeptical about digitalization, we found it appropriate not to force them to sign up in order to use the app (Nielsen's Heuristic, user control). Instead we went with the approach that the user could simply just download the app and start using it right away with the basic GPS navigation needed to find parking. The interested user would be able to sign up for an account to use functions like “save my spot” and “My cars”. With this in mind we discussed other of Nielsen’s heuristics that would be appropriate to implement to our project.

We also explored other relevant Nielsen heuristics to enhance our project's usability. For example, the user could search for a street, the app instantly provides parking notifications through an intuitive color-coded system:

This visual system aligns with Nielsen's heuristic of recognition rather than recall, enabling users to quickly understand the parking status without needing to interpret complex instructions. Upon noticing these colors, new users are likely to interact with the information box, which then expands to display detailed explanations about the parking rules for that location. This step-by-step approach ensures clarity and allows users to plan their parking and routes more efficiently.

I. Sketches & Wireframes, 2

December 20, 2024

We came to a conclusion from our sketches that the navbars and different pages were unnecessary and that our approach should be a minimalistic design and efficient system, but also taking recognition into consideration. The reasoning behind this is that we found we had far too many different pages and navigating through the app would have been either frustrating for the user and/or confusing. There was no point in having different pages for everything when we could utilize icons on the map to perform actions.

The result was a large map that utilized the user’s coordinates to display streets, allowing navigation with a pin that could be moved by scrolling the map. At the bottom, a “Login” button was available if the user was not signed in. Once signed in, this button was replaced with two options: “Home” and “Settings,” both featuring recognizable icons. We also sketched icons to be placed on the map for signed-in users, including:

This design choice focused on simplicity and ease of use while maintaining an intuitive and recognizable interface.

1 1 1
1 1 1
1 1 1

II. Why & How We Came-up With Design Choices

December 20, 2024

At its core, our interaction model is one which users can internalize quickly if they have not already done so from using other map based applications. The focal point is for the user to be presented with familiar icons, concepts and an intuitive interface with which our users can quickly become familiar with in accordance with the Nielsen heuristic idea of matching the system together with the real world. E.g. the car icon in the interface takes the user to the list of vehicles that the user has registered.

The glue that holds our application together and the way we ensure that our users always stay oriented is the fact that the visuals are clear and offer our users quick and total mastery of the application. This is in line with the Nielsen heuristic idea of consistency and adhering to standards since our users, most likely will have certain expectations from previous experiences with other applications. These previous experiences should provide a smooth transition with a very low learning curve into our application and a certain level of continuity is assured.

Corresponding with the Schneidermann heuristic idea of reducing short-term memory load for our users we have scaled down the amount of features for our application to a minimum of buttons and icons. There are four icons from which one (the car icon) will have a drop-down menu and two main buttons in the footer.

III. Selection of Interface Elements & Controls

December 20, 2024

In order to achieve a higher user experience for our product we had efficiency and effectiveness in mind. We aspire to have an application that requires very little effort when using the app. It should be easy to understand and navigate regardless if you are the most technical or not, because our user-group has a wide age-span. Upon discussion where we had both our personas in mind, we decided that when you just download the app you come straight to the map where you have a GPS function and a sign in button. The sign in button is optional to use, but is required if you wish to unlock functions like favorite streets and where your car is parked at the moment.

The symbols we chose to display on the map are simple and easy to understand.

Back to Home

Parkly Icon Copyright, Parkly 2024