You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Translate It already has parts of the original dictionary plan implemented through a different architecture, so the old blueprint should not be treated as a current implementation plan.
The remaining product/research question is whether to expand richer dictionary/linguistic behavior further, for example:
richer definitions, examples, synonyms, and parts of speech;
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Context
Translate It already has parts of the original dictionary plan implemented through a different architecture, so the old blueprint should not be treated as a current implementation plan.
The remaining product/research question is whether to expand richer dictionary/linguistic behavior further, for example:
Research references
Decision to make
What dictionary experience should Translate It provide beyond the current implementation?
Any future work should fit the current single-provider/shared-display architecture rather than revive the obsolete HybridCoordinator/component plan.
Migrated from the former dictionary/backlog documents.
All reactions