The advice to keep the app's screen labels as they are unless the app itself is localised is the one most teams get wrong. A German voiceover pointing at a button that says "Export" is fine, but a demo with translated captions over English UI can confuse people when they open the real product and the words don't match. The timing point is real too. German and Spanish often run longer than English, so a scene cut that fits the English voice can end mid-sentence in another language.
Yes, the timing one is the hardest to catch by eye. The fix I'd suggest is cutting scenes to each language's narration instead of to the English edit, so every language gets its own scene lengths, with a minimum hold on any screen the viewer needs to read. On labels, if the UI isn't localised, keep the captions in the target language but write button names exactly as they appear in the app, in quotes. Then the words in the caption match what people will actually click.
StackShortlist
Proof Over Promises.
The advice to keep the app's screen labels as they are unless the app itself is localised is the one most teams get wrong. A German voiceover pointing at a button that says "Export" is fine, but a demo with translated captions over English UI can confuse people when they open the real product and the words don't match. The timing point is real too. German and Spanish often run longer than English, so a scene cut that fits the English voice can end mid-sentence in another language.