OTWOO · LANGUAGE, TECHNOLOGY, CONTEXT

Otwoo for Android: version 1.0.2 and recovered screens

Two Google Play captures from 2022 preserve the identity of Otwoo 1.0.2 and its original screen references. The listing is now unavailable. No APK or IPA installer has been recovered.

The application identified in the archive

The captures were made on 31 January and 20 May 2022 (UTC). Both identify the same Android package and version. Their update field refers to June 2020: it is not the date of the archive capture. The publisher website points to www.otwoo.com.br. These fields help distinguish Otwoo from similarly named applications.

Historical Google Play identity
Packageotwoostartup.com.otwooapp
Publisher labelOtwoo.app
Version1.0.2
Listing update date28 June 2020
Minimum Android5.0
Listed size37M — listing metadata, not a recovered file

The interface, beyond a promotional badge

The archived listing references eight screen images. Seven are reproduced here, recovered from those original image URLs. They show language selection, photo analysis, weather and the historical CheckCorona conversation. The text visible inside the original screenshots remains in its original language; captions and explanations are translated.

Language selection in the original interface.
04 Language selection in the original interface.
Object recognition in a photograph.
06 Object recognition in a photograph.
Weather query for Recife, dated 23 June 2020.
07 Weather query for Recife, dated 23 June 2020.

CheckCorona screens: a dated record

These screens preserve the interface used during the pandemic. Their medical questions and response wording belong to that historical context. They do not provide a consultation, diagnosis or current health instructions. The record is useful for understanding the conversation design.

View four historical conversation screens
CheckCorona: the start of a Portuguese conversation.
01 CheckCorona: the start of a Portuguese conversation.
Questions in the historical CheckCorona flow.
02 Questions in the historical CheckCorona flow.
A response from the 2020 flow; not current medical advice.
03 A response from the 2020 flow; not current medical advice.
CheckCorona opening screen with voice control enabled.
05 CheckCorona opening screen with voice control enabled.

Where are the APK and IPA?

The exact Google Play address returned HTTP 404 in the 19 October 2026 check. A store page and screenshots are not an APK. We have not recovered a signed binary, signing certificate or an iOS App Store identifier. There is no verified installer to distribute here.

The old App Store badge linked to CheckCorona, rather than an Apple product page. The preserved Firebase link currently redirects to a Google waiting-list form on desktop and iOS. With an Android user agent it returns an intent containing that form and the historical package identifier. No intent was launched and no application was installed.

Choose a route by what it actually does

The local worksheet works in this browser without an app or account. The access-status table separates the old stores, conversation links and external form. The waiting list requests contact details; it is not an app download or a guarantee of a reply.

Open the historical waiting-list form on Google ↗.

Follow the connected projects

Sources, original files and limits

Found in the archive: the two Google Play HTML captures, with original digest verification. Two lower-resolution screenshots were also recovered from Wayback and verified against their archive digests. The larger images displayed here were retrieved now from the URLs referenced in the old listing; historical byte identity is not asserted for these larger versions. One other screen contains precise coordinates and is omitted from the public collection.

Capture inventory and access-check results (JSON) · Download seven original JPEGs, two Wayback JPEGs and the manifest.

Four other shortened links in the recovered pages lead to press references, not installers. In this check, the historical Agência Brasil article was available; another destination returned 404, one redirected to an agency homepage and one could not be resolved by our DNS lookup. The inventory records each observation without treating a redirect as recovered article content.