ELI5 AI

What the company appears to be: ELI5 AI is a self-reported Kotlin Multiplatform mobile application for university students, built as a study companion that integrates note-taking, active learning tools (e.g., flashcards, quizzes, mind maps), and planning features. It uses AI to explain notes and supports an "active learning" workflow from capture → explanation → recall → planning.

What changed: During Build Week, the project evolved from an Apache-2.0 base into a product with a defined identity (Axie Scholar mascot, app icons), integrated AI workflows, cross-platform functionality, and a unified UI experience across Android and iOS.

Single most important open question: Is there any evidence of user adoption or usage beyond the author’s own development work?

The description states that ELI5 AI is a Kotlin Multiplatform study companion for university students, designed to connect notes, active recall, AI explanations, and planning. It supports features such as:

• Interactive mind maps
• Quizzes
• Flashcards
• Translation
• Feynman practice
• AI Coach conversations
• Scheduling and task planning

The app is built using Kotlin Multiplatform, with shared domain, data, and UI code between Android and iOS. It uses SQLDelight for local storage and Appwrite for cloud services. AI requests are routed through an Appwrite Cloud Function to keep credentials off the device.

Inference: The app appears to be a single-developer project focused on student workflows, not a commercial product with users or revenue.

The author states that ELI5 AI aims to solve the problem of converting information into understanding and consistent practice — a common challenge for students who already have tools for collecting information but struggle with retention and application.

It positions itself as a unified workflow tool that moves from:

• Capture → Explanation → Recall → Planning

The product identity was shaped during Build Week, including:

• A mascot (Axie Scholar)
• App icons
• Design system (Plum Scholar / Liquid Glass)
• Redesigned onboarding and navigation

Inference: The positioning is based on a personal problem the founder identified, not market research or customer feedback.

The description states that ELI5 AI is built for university students, who are described as having tools to collect information but needing help converting it into understanding and consistent practice.

Inference: The target customer is a single user type (university student), with no evidence of segmentation or targeting other groups like high school students, educators, or professionals.

There is no evidence in the description of any business model or pricing structure. The project is described as a personal development effort during a hackathon and not as a commercial product.

Inference: No revenue model or pricing strategy is evident from the self-reported description.

The app is built using:

• Kotlin Multiplatform
• Compose UI
• Appwrite for backend services
• SQLDelight for local database
• Codex + GPT-5.6 for development assistance

It includes:

• Shared codebase between Android and iOS
• Secure AI proxy via Appwrite Cloud Function
• Onboarding redesign
• Four-tab navigation
• Unified UI across platforms

The author reports using Codex to audit migration work, trace dependencies, implement UI changes, configure Appwrite, and test both platforms.

Inference: The technical stack is consistent with modern mobile development practices, but there is no evidence of production deployment or user feedback loops.

There is no evidence of any traction, customers, or usage beyond the author’s own work. The project was submitted to a hackathon and is described as a prototype built during Build Week.

Inference: No data on adoption, retention, or user engagement exists in the description.

The description does not mention competitors or similar products. It is unclear whether there are existing tools that address the same student learning workflow (note-taking + active recall + planning).

Inference: No competitive analysis or positioning against other apps is provided.

• Single-founder project: Only one team member is listed.
• No commercial traction: No evidence of users, revenue, or adoption.
• Unverified claims: All statements are self-reported and unverifiable.
• Hackathon prototype: The app was built during a 2026 hackathon — not a product in production.
• No monetization strategy: No indication of how the project would generate value or revenue.

Inference: The risk of failure is high if no traction or commercial viability emerges post-hackathon.

1. What specific problems do students face that this app aims to solve, and how did you validate those needs?
2. Have you tested the app with actual university students? If so, what feedback did you get?
3. Is there a plan for monetization or scaling beyond the current prototype?
4. How do you intend to build out the AI workflows and active learning features in the long term?
5. What are your plans for user acquisition and retention after the hackathon?