The objective of this bounty is to bring the PrepOwl Mobile App closer to feature parity with the existing production web application by implementing all pending mobile features identified in the comparison report.

The developer must implement the missing features, integrate them with the existing backend APIs, maintain consistency with the web application's business logic, and ensure a smooth, reliable mobile user experience.

The work will be delivered in three milestones:

1. Milestone 1 — Urgent fixes: Pricing, usage limits, and free-plan behaviour.
2. Milestone 2 — Core learning features: AI Tutor, voice, revision notes, roadmaps, and mock tests.
3. Milestone 3 — Growth and engagement: Account settings, offers, group passes, notifications, games, and analytics.

2. Scope of Work

Milestone 1: Pricing & Free-Plan Behaviour

Priority: Critical

Target release: v1.0.13

Estimated duration: 1–2 weeks

Features: 4

The objective of this milestone is to align the mobile app with the current pricing and free-plan restrictions enforced by the live backend.

Feature IDRequirementExpected Implementation33Server-driven pricingFetch and display the latest GST-inclusive prices from the server, including the Exam Pass at ₹299.35Daily usage meterDisplay the remaining daily usage to free users, such as the number of tutor messages left.36Free-plan limit messagesShow clear, user-friendly messages when a free user reaches a daily usage limit.37Free-user test reportsDisplay a shorter test report for free users with a locked preview of restricted content and a clear upgrade prompt.

Acceptance Criteria

• Mobile pricing matches the current server-provided pricing and GST-inclusive amounts.
• The Exam Pass price is displayed correctly.
• The usage meter reflects the user's actual remaining allowance.
• Daily limits are handled gracefully, with clear messaging rather than confusing errors.
• Free users see the intended restricted test-report preview.
• Upgrade actions guide users to the appropriate subscription or purchase flow.
• Existing payment flows continue to function correctly.
• All changes are tested against the live backend APIs.

Deliverable: A tested mobile release containing the pricing and free-plan fixes.

Milestone 2: Core Learning Features

Priority: High

Target release: Next 1–2 releases

Features: 16

The objective of this milestone is to implement the pending learning capabilities that are already available on the web application.

A. AI Tutor — 4 Features

Feature IDRequirementExpected Implementation8Tutor memoryAllow the tutor to remember learner context, with controls to view and delete stored memories.9Daily MentorImplement the Daily Mentor card and follow-up questions.10Maths and code formattingCorrectly render mathematical expressions, equations, code blocks, and related answer formats.11Web search answersSupport web-search-based answers, including the Pro allowance of 20 advanced searches per day.

B. Voice Features — 2 Features

Feature IDRequirementExpected Implementation12Read-aloudEnable answers to be read aloud in English, Hindi, and Hinglish, with voice settings.13Speak a questionEnable microphone input so learners can ask questions by speaking.

C. Revision Notes & Mind Maps — 2 Features

Feature IDRequirementExpected Implementation14Revision notesGenerate or access revision notes for each session and support PDF downloads.15Mind mapsProvide mind maps associated with learning sessions.

D. Roadmap & Study Planner — 4 Features

Feature IDRequirementExpected Implementation20Progress engine and calendarImplement the updated progress engine with a calendar-based study planner.21Missed-day recoveryAllow learners to recover missed study days and re-plan their schedules.22Milestones and celebrationsDisplay learning milestones and achievement celebrations.23Exam-date planningSupport any exam date and display a study-plan brief card.

E. Mock Tests & Test Series — 4 Features

Feature IDRequirementExpected Implementation25SSC test seriesAdd SSC test series with previous-year papers.26NEET/JEE test seriesAdd NEET and JEE test series.27Pre-test instructionsDisplay pre-test instructions and implement section-lock behaviour.28Report a wrong questionAllow learners to report incorrect questions from a test.

Acceptance Criteria

• All 16 features are accessible and usable on supported mobile devices.
• Existing backend APIs and web-equivalent business logic are used wherever applicable.
• Tutor answers render correctly, including mathematical expressions, tables, and code.
• Voice input and read-aloud work with the supported languages and voice settings.
• Revision notes, mind maps, and PDF downloads work as expected.
• Study plans update correctly based on progress, missed days, and exam dates.
• Test series, section restrictions, and question-reporting flows function correctly.
• The implementation preserves existing mobile features and authentication.
• Relevant loading, empty, error, and success states are implemented.

Deliverable: A tested mobile release containing the pending core learning features.

Milestone 3: Account, Growth, Engagement & Analytics

Priority: Medium

Features: 12

The objective of this milestone is to complete the remaining account-management, monetisation, community, engagement, and tracking features.

A. Login & Account — 3 Features

Feature IDRequirementExpected Implementation4Edit usernameAllow users to update their username.5Profile and security settingsAdd profile-management and security-settings pages.6Hindi app languageSupport Hindi as an app language.

B. Payments, Offers & Upgrade Prompts — 3 Features

Feature IDRequirementExpected Implementation31CouponsSupport coupon entry, validation, and applicable discounts.32Spin-wheel offerImplement the first-purchase spin-wheel offer.34Contextual upgrade promptsDisplay upgrade prompts inside tutor, tests, and voice experiences.

C. Study Together — 1 Feature

Feature IDRequirementExpected Implementation38Duo, Trio and Squad passesImplement group passes, invite links, and refer-and-earn functionality.

D. Notifications & Support — 2 Features

Feature IDRequirementExpected Implementation39Notification centreDisplay study reminders, missed-day reminders, and alerts.40Support ticketsAllow users to raise, view, and reply to support tickets.

E. Play & Learn Games — 2 Features

Feature IDRequirementExpected Implementation42New and accessible gamesAdd Energy Odyssey, MathVerse, MoleForge, BioVerse, and Play for Everyone.43Leaderboards and challengesImplement game leaderboards, challenges, and game alerts.

F. Usage Tracking — 1 Feature

Feature IDRequirementExpected Implementation45Analytics eventsSend the same usage and purchase events as the website.

Acceptance Criteria

• Username updates and profile/security settings work correctly.
• Hindi language selection is available and reflected throughout the supported app interface.
• Coupons and promotional offers follow the applicable backend validation and pricing rules.
• Group passes, invitation links, and referral flows work correctly.
• The notification centre displays the supported notifications.
• Users can create and manage support tickets, including replies.
• All specified games are accessible, with their associated engagement features working as intended.
• Mobile analytics capture the same agreed usage and purchase events as the website.
• Existing account, payment, and learning flows remain functional.

Deliverable: A tested mobile release containing the remaining account, growth, engagement, and analytics features.

3. Overall Deliverables

The developer is expected to deliver:

1. All 32 pending mobile features identified in the comparison report.
2. Integration with existing backend APIs and services.
3. Mobile UI implementation consistent with the existing PrepOwl product experience.
4. Correct loading, success, empty, and error states wherever applicable.
5. Testing of all implemented features on supported devices.
6. Regression testing of existing login, tutor, roadmap, mock test, search, and payment features.
7. Resolution of bugs introduced by the new implementation.
8. Updated source code, build configuration, and any necessary implementation documentation.
9. A testable build for review and acceptance.
10. Release-ready code following the team's existing development and deployment process.

4. Out of Scope

The following are not included in the 32-feature implementation scope unless separately approved:

• Rebuilding features already marked as complete on mobile.
• Developing new backend APIs for features that already have working APIs.
• Redesigning the entire mobile application.
• New features not identified in the comparison report.
• Phone push-notification infrastructure requiring new backend work. The report specifically identifies this as additional backend work if required.

Any additional scope must be discussed and approved before implementation.

5. General Acceptance & Quality Requirements

The bounty will be considered complete when:

• All assigned features pass functional testing.
• The implemented behaviour matches the relevant web functionality and business rules.
• Pricing, subscription status, and usage limits are consistent with the backend.
• No critical or major bugs remain in the delivered scope.
• Existing mobile functionality has not regressed.
• The team has reviewed and approved the deliverables.
• Source code and build artefacts are handed over through the agreed workflow.

6. Milestone & Payment Structure

MilestoneScopePayment1Pricing & Free-Plan Behaviour — 4 features₹[Amount]2Core Learning Features — 16 features₹[Amount]3Account, Growth, Engagement & Analytics — 12 features₹[Amount]Total32 pending features₹[Total Amount]

Payment for each milestone will be released after the corresponding features are delivered, tested, reviewed, and approved.

7. Important Implementation Notes

• The reference report compares mobile app v1.0.12 (code 13) with the production web application as of 12 October 2026.
• The 32 pending features should be implemented according to the feature definitions in the report.
• Backend APIs are reported as live for the planned steps; any API gaps discovered during development must be documented and raised before additional backend work begins.
• The developer should confirm the existing mobile framework, current codebase, supported OS versions, and release process before starting.

The report's Step 3 grouping includes account settings, offers, group passes, notifications/support, games, and analytics. The three milestone scopes above follow that grouping.