I redesigned the Tarjimly mobile request-to-connection experience to reduce the time and friction between opening the app and getting help. The redesign focused on request initiation, translator matching, smart defaults, connection states and session continuity — serving over 700,000 people across 250+ languages.
Context
Tarjimly helps refugees, aid workers and people in crisis connect with translators across more than 250 languages.
In these moments, language is not just a barrier. It can affect whether someone gets medical care, legal help, housing support or urgent case assistance.
The mobile app worked, but it was not optimized for stressful situations. Users were entering the product under pressure, navigating several paths and sometimes leaving before they got connected.
The Problem
The main problem was time-to-connection. Users struggled to:
Start translation requests quickly.
Understand the fastest path to help.
Choose between different support options.
Stay confident while waiting.
Continue after a request had started.
I redesigned the mobile request-to-connection experience. I focused on request initiation, translator matching, smart defaults, connection states, translation history and session continuity.
Research & Findings
The baseline friction showed three major issues.
Users delayed before starting a request.
Some users dropped off before connection.
Stress increased cognitive load and made decision-making harder.
The design challenge was not to remove every option. It was to make the right option obvious based on urgency.
Design Strategy
1. Clear Entry
Users see the most important actions immediately: call interpreter for live support, or request translation for text or documents. This reduced hesitation at the starting point.
2. Smart Defaults
The product suggests or detects language where possible and delays non-critical details until later.
3. Visible Progress
Users can see what is happening while the system reaches translators, estimates wait time or confirms a queued request.
4. Smooth Continuation
Users can move from request to live call, chat, translation, transcript or activity history without starting over.
Key Flow
Open app → Choose urgent call or translation request → Select language → System searches for a translator → User sees wait status → Translator connects or scheduling is suggested → Session happens → Transcript or activity is saved.
Outcomes
The redesigned mobile experience helped users connect to support in under 30 seconds across language pairings. It supported over 700,000 people, enabled over 2 million minutes of translation and interpretation and reduced drop-off for urgent requests.
Reflection
Tarjimly Mobile reinforced that in high-stakes environments, good design is not about adding more features. It is about removing anything that delays action.
Tarjimly Spark AI
Senior Product Designer · Real-time AI interpretation