OpenAI 2026 hackathon

PTE Flow AI Mistake Coach

Turn every missed WFD word into the learner's next targeted listening drill

Solo project by Cao Ky Nguyen · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #6,163 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

The company appears to be a solo developer project named "PTE Flow AI Mistake Coach", submitted as part of an OpenAI hackathon. The author states it is an extension to an existing PTE (Pearson Test of English) learning app, adding AI-powered coaching for Write From Dictation errors. The core functionality involves generating targeted listening drills after a learner's mistake, using local scoring and AI for explanation and drill generation.

What changed

The project description indicates the author built this as part of an OpenAI hackathon, suggesting it is a prototype or proof-of-concept rather than a production product. It was developed using AI tools like Codex and GPT-5.6, with Kotlin Multiplatform for mobile and a serverless backend.

The single most important open question

Is there any evidence that this project has been integrated into a live PTE Flow app or used by learners beyond the hackathon context? The description states it is an extension to an existing app but provides no evidence of adoption, usage, or integration.

Back to contents

What The Product Actually Is

  • The description states: "PTE Flow AI Mistake Coach" is an extension to an existing PTE learning app
  • It focuses on Write From Dictation (WFD) errors in the Pearson Test of English
  • After a learner makes a mistake in WFD, the system evaluates the answer locally and identifies exact missing, extra, or misspelled words
  • AI Mistake Coach returns:
    • A concise diagnosis of the listening pattern
    • A plain-English explanation grounded in the detected error
    • Focus words taken from the correct sentence
    • A short listen-and-repeat micro-drill
    • One practical instruction for the next replay
  • The system maintains deterministic scoring and spaced repetition schedules, with AI only used for explanation and drill generation

Back to contents

Positioning & Claim Evolution

  • The description states: "Turn every missed WFD word into the learner's next targeted listening drill"
  • The author claims this closes a gap between seeing an error and knowing how to train it
  • The positioning is described as addressing a specific pain point in PTE learning where learners understand meaning but miss small words like articles, plural endings, and prepositions
  • The evolution from "normal answer checking" to AI-powered coaching is framed as improving the learning loop
  • The author states they chose not to use a generic chatbot approach, instead constraining the AI output to be specific, explainable, and useful within a ten-minute daily practice session

Back to contents

Target Customer & ICP

  • Not evidenced. The description does not state who the target customers are beyond "PTE learners"
  • No evidence of customer segmentation or ideal customer profile (ICP)
  • The project is described as an extension to an existing PTE learning app, but no information about the app's user base or demographics is provided

Back to contents

Business Model & Pricing Evidence

  • Not evidenced. There is no mention of pricing, revenue model, monetization strategy, or business model in the description
  • The description states this is part of a hackathon project and an extension to an existing app, but provides no information about how it would be sold or funded

Back to contents

Technical & Delivery Signals

  • Built with: azure-openai, codex, compose-multiplatform, gpt-5.6, kotlin-multiplatform, ktor, openai-api, vercel
  • Mobile app uses Kotlin Multiplatform and Compose Multiplatform for shared Android and iOS code
  • The new shared Ktor client sends only the current sentence, learner answer, and machine-detected mistakes to a protected Vercel function
  • The backend never receives learner identity, account data, subscription state, or long-term history
  • Credentials remain server-side, and the mobile build uses a separate judging secret
  • The system is described as having offline-first flow with network feature added without breaking existing functionality
  • The main human product decision was to avoid a generic chatbot approach

Back to contents

Traction & Maturity Signals

  • Not evidenced. No evidence of revenue, customers, user adoption, or traction beyond the hackathon context
  • The description states this is a working prototype built during an OpenAI Build Week hackathon
  • There is no information about whether it has been integrated into a production app or used by learners
  • The author mentions "a live protected backend with automated validation tests" and "a verified end-to-end Android flow with video and runtime evidence", but these are not independent measures of traction

Back to contents

Competitive Context

  • Not evidenced. No mention of competitors, market analysis, or competitive positioning in the description
  • The project is described as an extension to an existing PTE learning app, but no information about the broader PTE learning market or competing products is provided

Back to contents

Key Risks & Red Flags

  • Solo developer project: Only one team member (Cao Ky Nguyen) is mentioned, suggesting limited resources for scaling
  • Hackathon prototype: The project was built during a hackathon, indicating it may be a proof-of-concept rather than a mature product
  • No evidence of integration or adoption: While described as an extension to an existing app, there's no evidence it has been integrated into a live product or used by learners beyond the hackathon
  • Limited scope: The system is constrained to specific error types (WFD) and does not appear to address broader PTE learning needs
  • Dependency on AI tools: Heavy reliance on Codex and GPT-5.6 for development raises questions about long-term maintainability and scalability

Back to contents

Diligence Questions To Ask The Founders

  1. Has this been integrated into a live version of the PTE Flow app?
  2. What is the current user base or adoption rate of the parent PTE Flow app?
  3. How does the AI coaching integrate with existing spaced repetition algorithms in the parent app?
  4. What are the technical challenges in scaling this solution beyond the hackathon prototype?
  5. Are there any plans to monetize this feature, and if so, what is the business model?
  6. How does the system handle edge cases or unusual error patterns not covered by the current implementation?

Back to contents

Investment/Partnership Verdict

  • Not evidenced. The description provides no information about funding rounds, valuations, or investment status
  • This appears to be a hackathon project with no evidence of commercial traction or viability beyond the prototype stage
  • The solo developer structure and hackathon context suggest limited scalability potential at this stage
  • Without evidence of integration into a production app or user adoption, it's unclear whether this represents a viable business opportunity or just a technical demonstration

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.