Browser translation
Status
| In-browser translation | |
| Stage | Definition |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | Feature page placeholder |
{{#set:Feature name=In-browser translation
|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Feature page placeholder }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | ` |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | Yuan Wang |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Yuan Wang |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
This feature will enable in-browser translation of content for users who come across web sites that are not in their native language/locale.
On Firefox desktop application, we aim to support 3 main features including: whole page translation, selected content translation, and in-context translation.
The feature of whole page translation is planned to be supported on Firefox mobile devices too.
2. Users & use cases
Target users: people who need to browse webpages in their non-native languages.
User Research Process: - Interview 6 non-native English speakers in SF to understand their online browsing behaviors, potential needs for translation help.
User Research Findings:
- People who don't speak English neither visit any English websites, nor try to read anything in English.
- Language block access. They still care about things happening in the rest of the world, such as news, travel, also shopping, education. However, searching these content in native language does not help find reliable/official information.
- Non-native speakers still need extra help, online dict, translation add-on, etc.
-I use many social networking websites like Google plus and Twitter. I do follow peoples who are not use English as their main language. When I get their updates my news feed, I need to translate it. The 'Selected Content Translation' feature will come to use here.
A real-world user scenario: Parents are browsing the web, looking for information about traveling to Japan, such as local weather. Their goals are to get most genuine and reliable information from Japanese local content providers before going on a trip.
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
1. Feature Designs across multiple platforms: Windows 7, Mac Lion OS, and Android 4.0. Link: http://cl.ly/0y3Q1Q192m2o0j1J2A10
2. Interaction designs for FX Mobile. Link: http://cl.ly/0S3G2J3b2A38420C0c3F
3. Interaction designs for FX Mobile on android tablet Link: http://cl.ly/2G0j061c0J0G3G0t0832/o
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
`
{{#set:Feature open issues and risks=`
|Feature overview=This feature will enable in-browser translation of content for users who come across web sites that are not in their native language/locale.
On Firefox desktop application, we aim to support 3 main features including: whole page translation, selected content translation, and in-context translation.
The feature of whole page translation is planned to be supported on Firefox mobile devices too.
|Feature users and use cases=Target users: people who need to browse webpages in their non-native languages.
User Research Process: - Interview 6 non-native English speakers in SF to understand their online browsing behaviors, potential needs for translation help.
User Research Findings:
- People who don't speak English neither visit any English websites, nor try to read anything in English.
- Language block access. They still care about things happening in the rest of the world, such as news, travel, also shopping, education. However, searching these content in native language does not help find reliable/official information.
- Non-native speakers still need extra help, online dict, translation add-on, etc.
-I use many social networking websites like Google plus and Twitter. I do follow peoples who are not use English as their main language. When I get their updates my news feed, I need to translate it. The 'Selected Content Translation' feature will come to use here.
A real-world user scenario: Parents are browsing the web, looking for information about traveling to Japan, such as local weather. Their goals are to get most genuine and reliable information from Japanese local content providers before going on a trip. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=1. Feature Designs across multiple platforms: Windows 7, Mac Lion OS, and Android 4.0. Link: http://cl.ly/0y3Q1Q192m2o0j1J2A10
2. Interaction designs for FX Mobile. Link: http://cl.ly/0S3G2J3b2A38420C0c3F
3. Interaction designs for FX Mobile on android tablet Link: http://cl.ly/2G0j061c0J0G3G0t0832/o |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 16 |
| Theme / Goal | ` |
| Roadmap | Firefox Desktop |
| Secondary roadmap | ` |
| Feature list | Desktop |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=P1
|Feature rank=16 |Feature theme=` |Feature roadmap=Firefox Desktop |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}