|
|
| Line 79: |
Line 79: |
| * '''VIDEO''': | | * '''VIDEO''': |
| # Similar to Photo section | | # Similar to Photo section |
|
| |
| == Preparation for Capturing Screenshots ==
| |
| As shown above, overall it is better to take screenshots from a working product rather than creating a screenshot. However, it takes time to set up the environment to take the screenshots. With the right process and proper guidelines and instructions, it is easy to do, especially the data and environment can be easily leverageable from one version of the product to another.
| |
|
| |
| More information will be added as we have more apps developed.
| |
|
| |
| * '''MAPS''':
| |
| # Select the target language
| |
| # Select a well known city, such as the capital of the country and the landmark of the city
| |
| # Make sure the map road signs appear in the target language, not English
| |
|
| |
| * '''CONTACTS''':
| |
| It's important to create an inventory of contact list before taking screenshot. Be sure these are clean and valid ones associate to a test account so it can be reused in the future. By "clean", it means there is no words like fake email domain names, phone number doesn't comply to the correct format, and names sound like native names.
| |
| # Create a list of names common in the target language/country
| |
| # Create a phone number associate with each contact in the ''format'' compliant to the target market [US/CA: (xxx)xxx xxxx; CN: xx-xxxx-xxxx (landline) or 1-xxxxxxxxxx (mobile), TW: x-xxxx-xxxx, PL: (xx) xxx xx xx ]
| |
| # Create an address associate with each contact in the ''format'' compliant to the target market
| |
| # Create a *valid* email address, even though this is a test account. Avoid fancy or "test" sounding user names. Be sure to use one of the more recognizable domain names for email address
| |
| # Verify that the sorting order is correct for the target language
| |
|
| |
| * '''EMAIL''':
| |
| # Create several emails between friends on various subjects: play games, plan for the weekend/vacation, meet at coffee, go to concert...
| |
| # Make sure a single contact has several incoming emails with various subjects.
| |
| # Avoid ''test'' sounding emails
| |
| # Make sure incoming emails have valid sounding names (vs. test sounding).
| |
| # Make sure emails are in target language, with correct spelling and grammar.
| |
|
| |
| * '''CALENDAR''':
| |
| # Create events in target language
| |
| # Create several events in target language, some of reoccurring events and others one time only
| |
| # Create enough events to have a solid 1 week view or 1 month view
| |
| # Make sure events are not several years old so it appears events are still fresh
| |
| # Screenshots are taken in the target language.
| |
| # Is there option in the calendar to chose lunar calendar of a particular culture over Gregorian calendar? If so, lunar calendar may highlight the offering of the product.
| |
| # Date and time format should display correctly.
| |
|
| |
| * '''PAYMENT''':
| |
| # Currency used in the market
| |
| # Other relevant payment options are available
| |
| # Billing info with correct address format, name order.
| |
|
| |
|
| == Guidelines to Capturing the Screenshot/Creating Composite Image== | | == Guidelines to Capturing the Screenshot/Creating Composite Image== |