This engagement is for a production-grade product spanning native iOS, native Android, and a responsive web application, backed by a secure cloud architecture, a content-operations portal, and commercial billing that must survive App Store, Play Store, and web checkout rules at the same time. The work is not a simple quiz wrapper. It requires a coherent system that synchronises learning state, language, payments, and media across devices while remaining fast on current and reasonably older hardware.
The commercial brand is Practice My Citizenship, operated by Happy Migration. Functionally, the product should help people prepare for Australian citizenship through structured practice, timed simulations, audio, and progress tracking. A useful reference for the general interaction model is https://mycitizenshiptest.com/, but that site is a United States product and is cited only as a type of experience. The delivered system must have original branding, original visual design, and original code. It must never present itself as an official government service or imply government endorsement.
Commercial proposals should quote three scopes as distinct commercial offers written in prose rather than a matrix: native iOS and Android together; the responsive web application on its own; and a complete package covering iOS, Android, and web. The administration portal is part of the complete package and should also be priced clearly if it is offered as a standalone line.
The first technical demand is genuine multilingual delivery, not a string-swap. English, Arabic, and Farsi/Dari must ship in the first release, with an in-app language switch that is immediate and persistent. Arabic and Farsi require a complete right-to-left layout, including navigation, typography, input, audio controls, and result screens. The localisation layer must be data-driven so further languages can be introduced later without a full rebuild of the client applications.
The knowledge corpus is a structured, administrable question bank drawn from official study materials and supplied by the client. Questions must be organised by topic and category, support more than one acceptable answer where that is pedagogically correct, randomise both stems and choices, and show explanations after a response. Administrators must be able to create, edit, translate, activate, and retire items without developer intervention. Bulk import through CSV or Excel is required. Dedicated Australian values material and a full simulation that follows the current official structure and pass rules are part of the learning surface, as are category practice, random practice, timed mock sessions, review of incorrect items, saved or favourite items, and a flashcard mode. Results must be explicit: score, correctness, and explanations. The product must remain clearly unofficial.
Access is commercially gated. A visitor may complete only a small number of practice items without paying; the default is three, and that number must be changeable from the administration area. After the free allowance is exhausted, registration and payment are mandatory. The free-allowance rule must be enforced server-side and should resist trivial reset across sessions and devices as far as is reasonably possible. Users purchase either a subscription or a one-time unlock. Billing must integrate Stripe on the web and, where store policy requires it, Apple and Google in-app purchase on the mobile clients, including restore-purchase and subscription management. Prices should be editable from the administration area wherever platform rules allow.
Voice is a first-class subsystem, not an afterthought. Questions and answers must be spoken in English, Arabic, and Farsi/Dari, with play, pause, repeat, and playback-speed control. Speech recognition must let a learner answer aloud. An optional mock-interview mode should ask items aloud and evaluate spoken replies. Microphone permission must be requested with a clear explanation of how recordings or transcriptions are processed. Proposals must state whether speech synthesis, recognition, or related cloud APIs create recurring third-party cost, and must estimate that cost.
Identity and continuity must be treated as a distributed-systems problem. Learners register with email and password, sign in, reset credentials, and verify email. Optional Apple and Google social sign-in may be quoted separately. A signed-in user must see purchase or subscription status, completed items, scores, strengths and weak areas, and must resume progress on another device. Preferences for language, audio, and notifications belong to the account. Account and personal-data deletion must be available as a user-initiated flow. A dashboard should present study progress, correct and incorrect statistics, performance by category, a daily streak, test history, a readiness indicator, reminders or push notifications, and achievement badges or milestones.
The administration portal is a secure web application used by operators rather than learners. It must support user management, the full editorial lifecycle of questions, answers, explanations, and translations, category management, bulk import, subscription and payment review, free-trial and access settings, push notification dispatch, usage and performance reporting, management of marketing and support pages including FAQs, and export of important business data.
The public marketing and support website is responsive and must include a home page, a features narrative, pricing, frequently asked questions, contact and support, privacy policy, terms and conditions, a disclaimer, and links to the iOS and Android applications.
Design must be original, modern, and professionally calm. It should work for people with mixed literacy and English confidence: large readable type, clear navigation, mobile-first composition, accessible colour and controls, and complete right-to-left behaviour. Happy Migration branding applies. Visual design and a clickable prototype must be approved before full engineering begins.
The architecture is expected to be serious. The backend must be secure and scalable, with hashed credentials, encrypted transport, protection of payment and personal data, privacy consent, and data-retention controls. Error monitoring, backups, and basic analytics are required. Development or testing environments must be separated from production. The clients must meet Apple App Store and Google Play requirements, perform well on current and reasonably older devices, and remain extensible for later languages and features. Applicable Australian privacy and consumer law must be respected. A high-complexity stack is expected: strongly typed native or near-native mobile clients, a responsive web client, a well-indexed backend with real-time or near-real-time progress sync, a localisation pipeline that includes bidirectional text, a media pipeline for text-to-speech and speech recognition, and a payments layer that correctly reconciles Stripe with store billing. Proposals should name the recommended stack and justify it against these constraints rather than offering a generic template.
The successful vendor delivers the agreed iOS, Android, and web surfaces, the administration portal, original design files, complete source code, database and backend configuration, technical documentation, assistance with store submission, deployment into accounts owned by the client, pre-launch testing and defect correction, at least sixty to ninety days of post-launch defect support, operational instructions for questions, users, and subscriptions, and a written schedule of ongoing hosting, API, voice, payment, and maintenance costs.
Ownership is non-negotiable. All source code, designs, databases, store listings, domain configuration, and intellectual property created for the project transfer to the client on final payment. Hosting, payment, analytics, store, and other third-party accounts must be registered in accounts the client owns or controls. The vendor must not reuse copyrighted designs, text, questions, or code belonging to another product.
A proposal should therefore read as an engineering offer. It should include examples of comparable educational, assessment, or subscription products, links to published iOS and Android applications, a recommended technology approach and the reasons for it, a fixed-price quotation structured by milestones, separate commercial figures for the mobile clients, the web application, and the administration portal, an estimated calendar, the people who will actually do the work, inclusions and exclusions, third-party services and their recurring cost, warranty and maintenance options, and explicit confirmation that source and ownership transfer, that Arabic and Farsi right-to-left layouts will be implemented properly, and that the team has shipped Stripe together with mobile in-app purchases.
Work is expected to move through a sequence of gated stages: requirements, architecture, and project plan; interface design and a clickable prototype; backend, database, and administration portal; practice content, languages, and audio; registration, free-access enforcement, and payments; testing and security review; store and web deployment; then source handover and post-launch support.
This is a preparation product for Australian citizenship. The reference site is American and exists only to illustrate the class of experience. The finished system must remain original in brand, design, and code, and must not suggest affiliation with or endorsement by the Australian Government.
