iOS migration to Swift UI

Cash efficiency

This new feature ROI was high for both the company and it clients. By giving more clarity on how efficient a clients money is this enables the client to use their money to make them money and also gave the business an opportunity to advise them on how to invest this money.

 

Background

This project required thinking how to logically visualise how well a user cash health was this needed to be simple to understand but also give clarity .

 

The Challenge

There was also some backend limitations that had to be considered in the project.

- All users would have bespoke targets for their cash health
- Visual complexity - It is easy to make UI complex for explain cash health I wanted to make the UI as accessible as possible as this is customer facing.
- It is very hard to define parameters as User could be over 300% or even more above or below there cash efficiency so UI needed to be flexible for this.
- Development graphic limitations


Solution

Deliverables are completed so far as the application is still being worked on.
- Using RAG status: colour gives user fast context on if a action is required
- Arrow indicator give additional detail on how extreme the status is i.e if they are just under / above or significantly under / above
- Amount over/under stated to add context - the statement gives added context to this of possible actions to give reassurance.
- Further detail available for users wanting more context

  • Colours

    This feature involved updating the existing cash section in the app to notify users of how much liquid cash they have available.

  • Textstyles

    This project required thinking about how to logically visualise and organise collative financial data of all a users financial assets. This project required updating the homepage and most used screens in the app.

  • Native components

    The current feature for company options was very complex and was only used by a handful of individuals, I was able to get feedback from these user to simplify and improve the feature.

Financial asset list

Old design system

Whatever it is, the way you tell your story online can make all the difference.

New design system

Whatever it is, the way you tell your story online can make all the difference.

  • Empathise

    The user could be any employee working in DB. This could be someone working in reception to the CEO of the company. Some will be using this software once a year. Others once a week… Managers also needed to use the application to monitor their teams.

  • Define

    What are we trying to achieve?
    Staff side: To create an application that allows a user to declare any outside business interests they may have and track the status of the disclosure.

    Private side: to vet through and respond to disclosures and track the status and history of any disclosure.

  • Ideas

    Most ideas for outside business interests were around refining the tools and features used within the disclosure itself such as a learn more feature for understanding complex terminology and making the user flow as simple as possible.

Profile

Old Screen

Whatever it is, the way you tell your story online can make all the difference.

New Screen

Whatever it is, the way you tell your story online can make all the difference.

  • Empathise

    The user could be any employee working in DB. This could be someone working in reception to the CEO of the company. Some will be using this software once a year. Others once a week… Managers also needed to use the application to monitor their teams.

  • Define

    What are we trying to achieve?
    Staff side: To create an application that allows a user to declare any outside business interests they may have and track the status of the disclosure.

    Private side: to vet through and respond to disclosures and track the status and history of any disclosure.

  • Ideas

    Most ideas for outside business interests were around refining the tools and features used within the disclosure itself such as a learn more feature for understanding complex terminology and making the user flow as simple as possible.

  • My Role

    To create a new feature which involved updating cash feature and creating new cash efficiency section to help user quickly understand if they are holding a healthy amount of cash in all there accounts.

  • Software

    Agile - Work framework
    JIRA - organise tickets
    Figma - Designs, Prototypes,
    Mobbin - Competitor research
    Workshops - Miro and Figjam

  • Stakeholders and Team

    Stakeholders:
    Head of Product
    Product owner
    Head of Tech

    Team:
    Teams of developers
    Product owner
    Head of iOS
    Head of android

  • Duration

    Designed and built in on 1 quarter whilst working on other projects.

User testing

User testing carried out throughout the feature however mostly in house with advisers who work closely with clients due to the type of client we have it is hard to find appropriate people to do testing with, we also review analytics on existing features and collate trends in feedback we receive form real client throughout the design process.