CuRis – How I Designed an App?

Have you ever wondered how designers take an idea and make it come to life?

In this article, I’m going to present to you how I designed the CuRis app. From business requirements to visual design, using the OOUX methodology, atomic design principles, site mapping, and more.

But first – what is CuRis? The CuRis app is a modern technology platform for connecting Healthcare workers directly with Healthcare organizations without the need to work with an agency.

curis app

 

The tasks for this project included:

  • Creating the CuRis brand.
  • Building a mobile app for locums
  • Building a web-based management system for healthcare organizations.
  • Launch a product web page for promoting the platform.

My role in the project:

  • Communicate with the client and understand their vision.
  • Understand the competitors and conduct customer surveys.
  • Create the logo, brand, information architecture, wireframes, component library, and the final designs in 3 months.

I had one more designer on the team. Together we collaborated to meet deadlines and match stakeholders’ expectations. All of this work would not have been possible without the dedicated work of my friend and colleague Margarita Georgieva!

Work process

1. Logo and Branding

We created a variety of Logo ideas and moldboards. The approved idea is a representation of the core intention of the app – to connect people with different experiences and job titles in the healthcare sector to healthcare organizations. We decided on a color pallet that includes 3 different blues as main colors and a peach nuance as a contrast.

curis

curis typography

2. Object Discovery

We used Object-Oriented User Experience as a core methodology. OOUX is used for structuring a problem space that emphasizes on the objects – the things people interact with. You can learn more about OOUX at https://www.ooux.com.

The objects of a problem space are the things that users are there to interact with. In the Discovery phase of a project, with the client and PM, we tried to scope out what are the THINGS that users should think about in the CuRis space. We ended up with the main components – “Locum”, “Healthcare organisation”, “Job”, “Shift”, “Message”, “Certification”

how i designed an app

 

3. Object map

The methodology uses 4 types of meaningful elements. The most important one is the OBJECT. Then we have RELATIONSHIPS between the objects, call-to-action (CTAs), and ATTRIBUTES of the objects (metadata and core content). ORCA for short. 😉

All these elements together create an Object map. This is the first design artifact that represented our idea clearly and gave context to the system. It helped us ask ourselves more questions and dive deeper into the requirements.

For complex systems, this is a great thing to have before going into details. It shows the idea as a whole. Based on it, ask more and more questions so that you and your team can understand the digital monster and fight it!

designing

 

4. System modeling

The RELATIONSHIPS between the objects can be simplified by a system model. In the example below you can see that in the system, everything revolves around the SHIFT. The healthcare organizations add the shifts that they need locums to fill inside the system. Locums can apply for the shifts when both parties are available, given they have the qualifications.

system modeling

 

5. Site map

I wanted to create a sitemap that also includes the core content of the system. Everything has a place where it is nested. I created three site maps – one for the desktop app for organization admins, second sitemap for the mobile app that the locums would use and a third one for the product website.

site map

 

6. User flows

The graph below shows the main flow of actions that both the healthcare worker and the organisation go through and the alternative roads they can take. The green cards represent the action of the user, the blue cards show who does the action, the gray ones show the Objects that are acted upon. It is created by me, the stakeholders and the project manager.

user flows

 

7. Trello information board

The OOUX methodology has many steps, that lead to the creation of one source of truth. All questions that a UX designer might want to get answers about are documented. Trello as a tool could do the perfect job of holding the information and presenting it in a way that all parties (developers, stakeholders, managers) can understand and collaborate. It is an ever-changing organism.

trello information board

 

8. Wireframes

The final piece of digital documentation before going into high fidelity prototyping is the wireframe. In the OOUX world, all information structures are color-coded and the building blocks of each object are prioritized. We should know what is most important and what is less important (the less important stuff, go down the page or can be removed depending on the purpose).

wireframes

This process helps to create components that represent the same object in various places. This is a way to keep the object consistent, no matter where and how it is presented. You can hide the not-so-important information from the smaller-sized cards and the object would still be recognizable as the same THING!

curis app

 

Thank you for your attention!

Check out the website https://curisapp.com

ORCA methodology was developed by Sophia Prater and it works like magic! If you work as a UX/UI designer, you should definitely try it with your team.

object oriented UX

 

Written by Delyanka Sirakova at Motion Software

During the day, Delyanka is a Product designer, passionate OOUX strategist, and an artist! At night she transforms into a huge science geek, writes sci-fi stories, and dives deep into the absurdities of life by reading about conspiracy theories, listening to real crime stories, and… crochet!

x

Motion Software starts operating under the name of its parent company Exadel, taking effect on July 15th.

More Info

Motion Software uses cookies to improve site functionality, provide you with a better browsing experience, and to enable our partners to advertise to you. Detailed information on the use of cookies on this Site, and how you can decline them, is provided in our Cookie Policy Learn more about cookies, Opens in new tab. By using this Site or clicking on OK, you consent to the use of cookies.

OK