Screenshot (32).png


What happens when a professional must change dialects? They must now learn a new language, but that entails more than just fluency and conversation skills.

Eloqi IOS App. UX/UI Project
December 2016


The Opportunity & Challenge:

To be a multilingual professional, one must know specific jargon and terms associated with the trade in each language, not just cadence and fluency.

This is where Eloqi steps in. Eloqi aims to fix this problem harming our societies globalisation. Eloqi does not only touch on fluency skills via one-on-one student to coach interactions but additionally emphasises on developing multilingual professionals through sessions of teaching jargon and terms, not just the new language. Thus, helping further the Eloqi advantage.


Project Highlights


User Data

Within a three-week timeline, we were to create a meaningful and developed experience for the coaches. By focusing on the coaches, Eloqi will have a strong foundation for any new user. The mentality behind this is that anyone can learn a new language, but not everyone can teach one let alone teaching industry specific terms and jargon.

The coach user was very difficult to conceptualise. This being because the coach will have a user of their own, the student. Just like the movie “Inception”, we would have to think multiple layers down to gain access to a detailed mental model of the coach.


Competitive Comparative Analysis

Screenshot (41).png

We interviewed coaches and students that have used the Eloqi beta or other language learning apps. Allowing us to understand both users and other competing apps. Although the niche of language learning/teaching apps has been explored rather well (Tandem, Italki, Doulingo etc.), most users must go beyond the means of the platform to gain “new language professional skills”. This is where Eloqi wants to fill the gap.




This where we could flex our creative muscles and finally see what our work will look like. And we started with the design studio excersie. Seeing our features and elements were filtered and grouped by the feature prioritization, the design phase was agile and streamlined.


This is just a taste, so I recommend you read the full Case Study!