This iOS/Android cross-platform app for temporary workers redesign focuses on creating a more user-friendly and modern experience. It addresses key UX challenges by improving navigation, simplifying processes, and refreshing the interface.
Over the 10-month project, the emphasis has been on usability, accessibility, and maintaining a consistent visual design to better meet user needs.
Category:
Android/IOS app
Client:
Adia
Domain:
Pharmacy
Duration:
10 months
Actions
Inspiration board
Prioritizing workshops
Cross-platform mobile design
Figma prototyping
Design system
[PROJECT NEED]
Adia, a trusted platform for temporary job seekers in Switzerland, has connected thousands of users with opportunities over the past few years.
However, as trends and technology evolve, so must the platform. With the current mobile application engine (Microsoft Xamarin) set to expire in 12 months, Adia saw this as a chance to redefine itself.
The goal: modernize the app’s look and feel, improve user experience, and align with current standards to better serve its growing audience.
Target users
Their task
Find and secure temporary job opportunities that align with their preferences, skills, and availability
[IDENTYFYING THE PROBLEM]
Adia faced challenges redesigning their old software
Adia needed to refresh its slightly outdated software to ensure continuous support and robust data security for its clients. Taking advantage of the opportunity, they also wanted to refresh their app's design to better meet the needs of their users.
Struggling to tackle this overhaul with other companies before, they partnered with us to guide the transformation and achieve their vision.
Adia - previous app designs
[WHAT MADE ADIA OUTDATED]
Here’s a quick look at the key challenges we’ve identified and the opportunities we’ve had to improve, thanks to input from users, stakeholders, and a UX audit.
While applying for an offer, users often became confused about the job status
Many job seekers didn’t realize they needed to sign the offer before showing up for the job because it already appeared in the 'My Jobs' section.
On the other hand, some assumed that not signing the contract meant there would be no consequences for not showing up, which posed a significant challenge from a business perspective.
Previous app: Applying for the job offers flow
Overly complex wording on the job-applying confirmation pop up
Users often feel frustrated by dead ends
Users frequently encounter frustration during the process of applying for an offer or updating the job status due to numerous dead ends in the interface.
These moments leave them unsure about what steps to take next or how to resolve issues, creating unnecessary friction and hindering their overall experience.
A lack of clear directional prompts in the UI
Diving deep into UI
A UX audit revealed several key issues impacting the user interface.
Accessibility concerns, such as insufficient color contrast and unclear labels, create confusion and hinder navigation. Inconsistent visual hierarchy makes it difficult for users to prioritize actions, while the outdated design reduces trust and engagement.
Previous app: Issues in the UI, as seen in the job offers example.
[REBIRTH OF ADIA CANDIDATE APP]
After nine months of intense workshopping and countless design discussions, the Adia app emerged with a completely transformed look and feel — a fresh, innovative experience that redefines how users interact with the platform
First, the design foundation
We began with Material Design to ensure efficiency and quick delivery, leveraging its predefined guidelines for consistency.
However, the client’s focus on showcasing a unique brand identity led to the decision to invest in a custom design approach, resulting in a solution that reflected their distinct style and elevated the user experience.
Material Designs first attempts compared with the final design direction
[MATERIAL DESIGN]
Quick implementation with the reliable design system
Confidence in delivering a fully functional application within 12 months
[TAILORED DESIGN SYSTEM]
Unique brand identity building a competitive position in the market
Allows customisation for the design and user paths
Secondly, the skeleton
Knowing the current architecture of the application isn't efficient enough, we checked the existing system's limitations and conducted internal workshops with the client's team. Together with the domain experts, we collaboratively worked out the most sensible solution tailored to their needs.
New app information architecture
Applied jobs got their separate section
Lastly, the other improvements
Knowing the current architecture of the application isn't efficient enough, we checked the existing system's limitations and conducted internal workshops with the client's team. Together with the domain experts, we collaboratively worked out the most sensible solution tailored to their needs.
[CONCLUSION]
So what did we achieve?
A trusting relationship
Adia was so satisfied with the process and the outcomes of our collaboration that, even as the project was concluding, they was already considering further initiatives with us in the coming years.
A brand new identity
Adia was extremely pleased with the modern, tech-forward direction we took the application in, which was beautifully reflected in its visual design. The contemporary look was developed in alignment with their existing brand identity, a key priority for them.
New & improved product
A fresh product that puts smiles on the faces of both users and stakeholders alike.
What we learnt?
What would we do differently?
Optimizing backend alignment
Next time, we’d anticipate the backend complexity more carefully and wait for the final backend spike before fully defining the scope of MVP frontend work, ensuring a more efficient approach to handling even small changes.
Tests with the real users
We had chances to bring in real users, but it needed more time and effort from the business team. Going forward, we suggest focusing more on user engagement to really understand what features people want most.
Testing provided plugins more carefully before implementation
Although we did test the plugins before implementation, we could have done more thorough testing before adding them to the project. Next time, I'd suggest spending more time testing plugins upfront to make sure everything works smoothly on both platforms.
