Built an end-to-end chat product (Script Chat), leading UX research, interaction design, and usability improvements to enable seamless, real-time communication.
Founder
UX Research
Interaction design
A/B tests
My Role
I spearheaded the product's creation, from initial concept and user research to crafting the final design through iterations and user testing. In addition, I worked alongside a UX researcher, Product Manager,Developer's who analyzed the functionalities, Content Strategist The app launched globally on November 2nd, 2016.
User Research
Recruiting various participants who is representing lie target audience. Developing a research plan with clear instructions and tasks. Moderated the research sessions effectively.Developing a research plan with clear instructions and tasks.
Problem Statement
India has 60 crore non-English speakers facing daily language barriers in family chats, friend calls, local business—can't speak their own mozhi freely. WhatsApp + Google Translate are half-solutions: manual copy-paste, poor slang accuracy, no seamless flow.
Goal of the Product
Enable any age, any language users to chat real-time in Tamil/Hindi/Kannada/5 langs total. Audio message record → instant transcript + translation (pure script or Thanglish option). Privacy-first, English UI, mass-market adoption target.
Target Audience
| Segment | Who | Pain Point |
|---|---|---|
| Primary | 25-45 working adults, migrants | Family abroad, mixed-lang office chats |
| Secondary | 15-25 youth/students | Friends different states, socialise |
| Later | Aunties/Uncles, celebs | Native script pride, fan connect |
Declaring assumptions
Business Assumptions
I believe my customers have a need to chat freely with family/friends in their own language without copy-paste frustration
These needs can be solved with real-time audio-to-transcript translation in native script
I believe customers will pay through ads after experiencing translation value
My product will beat competitors because seamless audio→chat flow vs manual Google Translate
I believe free users will share app virally after first successful cross-language chat
I believe my marketing will work because Tamil pride messaging resonates with target audience
I believe customers are willing to keep parallel WhatsApp + translation app usage
I believe customers will pay through ads after experiencing translation value
User Assumptions
Where does product fit in workflow? (WhatsApp→Translate gap)
Between WhatsApp voice messages and Google Translate copy-paste—faster audio→translated chat
What problems solved? (Lang barrier, slang fail, copy-paste)
Will users trust local-only voice processing?
Will users share translated transcripts?
Will users tolerate 2-3s translation delay?
Budget Android phones smooth experience?
Will users keep both WhatsApp + our app?
Family groups > individual chats usage?
Users understand "optional translate" button?
Youth discover via friends vs ads?
Prioritized assumptions
Market Validated - 60%+pain = build
Privacy green light - NPS above 8 = Safe
Tech validated - 82%+accuracy = go
Growth engine - K-factor>0.3 = organic
UX confirmed - less than 3s equals mass market
UI locked - 70% native script
Onboarding ready - 95% completion
Launch ready - No tutorials needed
Model confirmed - No WhatsApp switch needed
Segment found - Groups first features
Transcript Feature
UX Research
Transcript
Need for accessibility | Improved searchability | Increased efficiency
Brand Awareness
Support
Help
Regular exposure | Interactive communication | Organic reach
Design Thinking
Accessibility
Problem Statement
Use clear and concise labels in the mic settings menu to identify the language options. Include native language names for broader understandability.
Voice in Feeds and Conversations
Settings
Visiblities
Speech Recognition Accuracy | Privacy Concerns | More Natural Interaction
Integrations
Tech stack and DB
Some Interesting Interactions
UI Interactions
Search Contacts
Incoming call alert!
Record Transcripts
User Persona's
Skeleton and Mockup
All works © Surya Narayanan 2025
