iOS Textstyle update

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
M3 textsytles update
xxxxxxxxxxx
NEW TEXTSTYLES
xxxxx
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
XXXX
Mapping old with new M3 textstyles
STRESS TEST WITH EXISITNG LAYOUT FIND OUTLINERS AND CHOOSE MOST APPROPRIATE
Stress testing updated to text styles
Coxxxxxx

-
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 TechTeam:
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.