top of page

F-Secure KEY

Client -


Year -


Role -

GUI and UX design

F-Secure Key app running on iPhone
F-Secure Key app wireframes
F-Secure Key app screens
F-Secure Key app lock screen
F-Secure Key app screens
F-Secure Key app screens
F-Secure Key app screens
F-Secure Key app screens
F-Secure Key app flow

F-Secure KEY is a password manager app that stores and protects all your passwords, credit card numbers, and PIN codes.

F-Secure KEY offers an effortless method to guarantee that the account credentials for your online services, credit card details, and other essential information remain safe and conveniently available.

Which function would it be a good idea for us to incorporate and test in the application? To find a harmony between the Security versus Usability. Data engineering: how best to organise 100s of things on a small amount of screen estate, regardless of whether that be records, gatherings, classifications and so forth.
Users and audience

User demographic: 20–70, carefully mindful. with extra cash.

Roles and responsibilities

I was a Senior UX Designer, my team was formed by the two UX Designers, three web application developers.

Scope and Constraints

To design the mobile, web and desktop applications to fulfil the user’s requirements in storing and using of their online credentials. My key contributions in this project: 

• Participation in Research Strategy Direction • Service Blue Prints • Participation in user Interviews • Product backlog / Feature prioritisation • Wireframes / Hi-Fi Prototype Disciplines: UX Research, Design Thinking, Agile, Lo-Fi and Hi-Fi Prototype, Usability Testing. 

Team’s approach for this project: An Agile UX, Lean-Start Up, Design Thinking coined by Dave Landis. Total of 7 sprints were ran in the 60-day period.


An initial proto persona workshop helped define our personas: 20–70, carefully mindful, with extra cash.

However to accomplish an increasingly adjusted perspective on the clients and their dispositions/practices we required to led 12 client interviews.

User Interviews

After the interviews we conclude some helpful fundamental discoveries: The big part of Clients come up short on the thought of what could occur them if one of their records gets hacked; they additionally need the consciousness of the situations which could prompt an information break.

Most clients have three passwords or less that they use for contemporary records, and some have 1 ‘universal’ one. Comfort beats security: clients would prefer to be less secure than need to use 2-factor validation to login.

From these discoveries, we had the option to create an essential persona and user journey.


To design a good user experience, we needed to select some critical flows. We have specified a list of features we wanted to include in the app, and now the task was to sort them into the three essential patterns.

Having decided on features, we did workshops to create some flows that would be essential to our persona Martta and settled on:

1 Adding an account manually

2 Applying passwords

3 Changing the password


We, at that point, ideated these critical flows in a workshop to make a paper model. We started usability testing the wireframe flows in low-fidelity, then in high-fidelity.

At each round, we were collecting our notes and synthesise our findings to iterate the user experience, making improvements at every stage.


This app is a part of F-Secure portfolio and helping users to make their online experience secure.

The stakeholders were particularly happy with the layout of the accounts page and the adherence to the F-Secure brand, look and feel.

My group and I all thought that it was illuminating and agreeable working on this project and feel happy with the work we delivered.

bottom of page