Inspiration
You can rewrite an email before sending it. A difficult conversation rarely gives you that same second chance.
RETAKE began with a question: what would it look like to practice the exact moment you wish you could take back?
We focused on new managers preparing for conversations about missed deadlines, promotion decisions, and boundaries with former peers. Rather than building another general-purpose chat interface, we built a focused rehearsal: try one approach, rewind that moment, compare another, and leave with words you have deliberately chosen.
What it does
RETAKE is a native Android prototype for practicing fictional workplace conversations.
Each rehearsal has three turns. You choose a response, see the character’s authored reply, and can select “Rewind this moment” to try a different approach. The comparison preserves both attempts, explains the difference in wording, and lets you choose which version to keep.
For example, in “The missed deadline,” one opening is:
“You always miss the deadline.”
Rewind the same moment and try:
“The handoff was late. What got in the way?”
The point is not to claim that one sentence guarantees a particular reaction. It is to make the difference between a general accusation and a specific observation visible and available for reflection.
At the end of a rehearsal, you can edit a useful phrase and save it locally for later.
The prototype includes three free rehearsals: “The missed deadline,” “The promotion conversation,” and “Yesterday’s teammate.” RETAKE Plus adds “Ask for clearer feedback.”
All character responses and coaching are authored fictional possibilities—not predictions about real people, personality assessments, or measured learning outcomes.
How we built it
The Android app uses Java and native Android views, with an explicit state machine managing the rehearsal flow. This keeps the original attempt, alternative response, comparison, and retained choice distinct.
Saved phrases use local SharedPreferences. RevenueCat handles the prototype’s offering, purchase, entitlement, restoration, and access-refresh flows. The current integration uses the RevenueCat Test Store; test transactions are not real revenue.
The interface uses a restrained paper-and-green palette and readable conversation cards. The central design decision is to keep both attempts available for comparison instead of replacing the first answer and losing the context.
ChatGPT and Codex assisted with research, implementation, debugging, test automation, and documentation. OpenAI image generation was used for the original app icon. The native Android experience does not use live AI-generated dialogue.
Challenges we ran into
Rewinding a conversation is more than going back to the previous screen. The app needs to preserve the first attempt, restore the correct moment, and let the user explore an alternative without confusing the two paths.
Another challenge was separating the practice experience from monetization. The three core rehearsals remain free; the additional scenario depends on the RevenueCat entitlement rather than merely opening the purchase screen.
Preparing the project also exposed a release-management issue: the recovered source archive and the later documented Android build need to be reconciled so that the public repository, demo, and test evidence all describe the same revision.
Accomplishments that we’re proud of
RETAKE makes one interaction concrete: rehearse, rewind, compare, and keep.
The core experience connects a fictional situation to a practical takeaway—a phrase the user can edit and save. The recovered Java practice engine passed 41 behavioral assertions, and five Java files passed syntax parsing during submission preparation. These offline checks are distinct from Android build, interface, and purchase testing.
What we learned
A focused interaction can communicate an idea more clearly than a long feature list.
For RETAKE, the useful output is not a score claiming to measure someone’s confidence. It is a visible comparison and a sentence the user chooses for themselves.
We also learned to keep evidence specific: a source-level test, an emulator run, a sandbox purchase, and a production release demonstrate different things.
What’s next for RETAKE
The immediate priority is to reconcile the final Android source and build, capture the native demonstration, and make the project reproducible from its public repository.
After that, we want to observe new managers using the rehearsals and learn which comparisons they find useful before expanding the scenario library.
RETAKE remains a prototype. Physical-device testing, production billing, cross-device access, and real-world learning outcomes have not been verified.
Log in or sign up for Devpost to join the conversation.