Product Requirement Document

1. Product overview

Quick Translate is an Android mobile application for translating typed or spoken words, phrases, and sentences between selected languages. It uses MIT App Inventor translation, speech recognition, and text-to-speech components. Users can read a result, hear it spoken, share it, and keep useful translations in a local library. A separate responsive landing page introduces the app, presents actual screenshots, provides the APK download, and makes the project documents available through Help.

Prepared for John Carl Valino. Documentation date: 8 November 2026. Distributed Android release: 1.0 (version code 1). The in-app About label says v2.1; this document uses the APK manifest as the release version. This document describes source-supported behavior and acceptance criteria, not a completed on-device test report.

2. Problem and objectives

People encountering unfamiliar text or speech need a convenient way to understand basic meaning without navigating a complex interface. The product aims to make everyday translation accessible on a mobile device, reduce steps between input and result, and let users revisit useful phrases. Translation quality and availability depend on the external service; results should be checked where accuracy is important.

3. Intended users and scope

Primary users are Android users translating everyday text or speech, including learners and people communicating across languages. The application has one end-user workflow. It has no account system or separate administrator, teacher, or student access levels. The project maintainer manages builds, website content, and submission assets outside the app.

Included: text translation, voice input, spoken results, source/target language selection and swap, sharing, recent history, bookmarks, preferences, and the promotional website. Excluded: offline translation, camera/OCR translation, user authentication, cloud account synchronization, and an asserted Play Store listing.

4. Functional requirements

PR-01 — Select languages: provide English, Filipino, Spanish, French, Japanese, Korean, German, Italian, Portuguese, Chinese, Hindi, Arabic, and Indonesian as source and target choices; allow swapping the pair.

PR-02 — Translate text: accept a typed word, phrase, or sentence; send a request when Translate now is tapped; show the returned translation or an actionable error.

PR-03 — Voice input: Listen & Translate invokes speech recognition for the selected source language; recognized speech is used by the translation workflow. Microphone permission and supported speech services are required.

PR-04 — Playback: Speak result invokes device text-to-speech for the target language. Voice translations support automatic playback; a preference controls automatic reading of typed results.

PR-05 — Library: show recent translations and saved phrases. Users can save a result, reopen an entry, and clear history or saved phrases through the provided controls.

PR-06 — Share and reset: Share opens the Android sharing interface for the result; Clear resets the input workflow.

PR-07 — Preferences: allow users to change typed-result auto-playback and history-saving preferences. Present the connection and local-storage information in Preferences.

PR-08 — Website: provide a responsive landing page, real screenshots, theme persistence, APK links, Android installation steps, store artwork, and Help popup access to PRD, TRD, and the user manual.

5. Primary user journey

Open Quick Translate. Select the source and target languages. Enter text or tap Listen & Translate and speak. For typed input, tap Translate now. Read the returned translation. Optionally listen, save, or share it. Visit Library to reopen recent or bookmarked translations; visit Settings to adjust history saving and speech playback.

6. Acceptance criteria

AC-01 (PR-01/02): changing each language selector updates the selected pair, swapping reverses the pair, and a nonempty translation request displays either a result or a useful error without crashing.

AC-02 (PR-03/04): on a supported device, granting microphone access allows recognized speech to enter the workflow; Speak result uses the target voice. Permission denial and missing voices are handled or documented clearly.

AC-03 (PR-05/07): a saved phrase can be found and reopened in Library; history saving respects its preference; clearing a list removes its entries as indicated by the app. Verify persistence after restarting the app.

AC-04 (PR-06): sharing opens an available Android share destination; clearing input returns the screen to an appropriate empty state.

AC-05 (PR-08): both website APK controls download the supplied release bytes; screenshots load; Help documents open in a dismissible modal; mobile navigation and light/dark mode work with keyboard and touch.

AC-06: verify service errors, empty input, denied permissions, unsupported voices, and loss of internet on an Android device before final release. These device tests remain pending.

7. Quality requirements and limitations

Keep input, language selection, and the result easy to locate. Provide readable labels and a simple three-page app structure: Translate, Library, and Preferences. The website must support small screens, visible keyboard focus, modal keyboard navigation, reduced motion, and relative asset paths suitable for shared hosting.

Translation requires an internet connection. Voice availability depends on the device speech provider and installed voices. History and bookmarks are stored locally and are not a cloud backup. No fixed latency, translation-accuracy percentage, or validated device-compatibility range is claimed.

8. Delivery and completion status

Deliverables: supplied AIA source, signed APK, AAB, store artwork, original screenshots, static website, PRD/TRD Help pages, user manual, and the completed proposal PDF. APK signature and download integrity have been checked; Android runtime acceptance tests are pending. A verified Play Store URL has not been supplied. The hosted website is currently owner-private; public visitor access must be enabled by the owner before public submission review.