Early 2017 I was commissioned by Purple Pixel to design an app for a jobs platform. The following is a case study of the app I designed. I called it Kaam (in Hindi, meaning, job).
1. The brief
To design an Android application for connecting a niche segment (grey collared) job seekers with it’s employers.
2. The need
The jobs finding platforms out there are all evidently there to cater to all the worldly needs under the employment umbrella. You could filter out the segment, industry and nature of work and ultimately get to what you are looking for, but the needs for different segments might not fall with-in the one-size-fits-all framework. That is specially true for the grey collared segment where things like screening the right candidate by resumes and cover letter are lesser important than in other segments.
3. The users:
- The job seekers in the segment including: restaurant cooks, waiters, delivery boys, drivers, receptionist among others.
- The Employer: usually agencies that hire at scale for various organisation’s grey collared staffing requirement and sometimes the organisations (including restaurants, bars and small companies) themselves
4. The design framework:
I’m a big fan of the word and the application of designing any product that fits in a framework. A design framework is essentially an overarching guide that allows your design to always remain intact. The idea is to abstract what you are designing to a minimum possible layout and have that framework extend to a maximum possibility scenario within the scope of that project. A design framework makes room for unique scenarios without breaking the overall architecture. It also accommodates for having different user types be able to navigate the app seamlessly by only making relavant information available to them.
In designing the job platform, here on refereed to as ‘Kaam’, the idea was to have a framework that remains unchanged (except for the relevant set of data applicable within) for both the user types, viz. the jobseeker and the employer.
5. The Flows:
The key components that were considered to be a differentiator and also an opportunity in designing for this market type was having a chat component. The idea being; employers would be able to screen potential employees by having quickly meet-up to discuss if it’s the right fit, rather than go through a rather lengthy process of form fillings and scanning through applications to find the right candidate. Along with that was to have the function of finding jobs by an area. Each components were detailed out for each user type to make sure there weren’t any gaps in connecting the app while communicating the flows.
6. Visual Direction
Several different approaches and design direction were taken to get the look and feel of the app just right. Like in the case with most modern app design flow, the final look and feel were designed with having the option to quickly replace the color palette with a range of other colors and styles so the final decision on the app could be taken even at the very last minute without breaking or having to restructure and redesign every component necessary for making the final assets delivery.
7. Putting it together
The problem with the old world approach of isolating the flows from visual direction completely, leads to a lot of back and forth and sometimes a lot of rework. In following a process of iterative visual direction along with seeking completion of the flows, the app continuously evolved both from a UX standpoint and the look and feel leading to completion. So with designing the Kaam app, I designed only few screens from the flow for the initial visual direction and then the completion of the app were designed with continuously tweaking the flows in the visual direction stage.