Build a global discipleship pathway app

KINGDOM HEIRS Discipleship App Developer Build Workflow & Screen-by-Screen Map PHASE 1 MVP — BUILD ONE COMPLETE PATHWAY, TEST IT, THEN EXPAND Pilot Pathway: COME & SEE — 14 Days Primary Goal: Prove the entire member journey end-to-end before building the remaining pathways. The pilot must demonstrate onboarding, language selection, pathway assignment, lesson delivery, Bible access, progress tracking, quizzes, AI-assisted content search, notifications, and administrator content management. Prepared for Kingdom Heirs Foundation Developer handoff specification   1. Build Strategy: One Complete Pathway First Do not attempt to build the entire Kingdom Heirs ecosystem at once. The developer should complete one vertical slice from first app launch through pathway completion. Kingdom Heirs will test and approve that complete flow before the next module or pathway is authorized. 1. Build the core app shell and member onboarding. 2. Build the Come & See 14-day pathway end-to-end. 3. Connect Bible access, progress tracking, two quizzes, notifications, and completion logic. 4. Build a usable administrator content-management workflow. 5. Add the first version of AI-assisted search limited to approved Kingdom Heirs content. 6. Test on both Android and iPhone. 7. Kingdom Heirs approves the pilot in writing. 8. Only then duplicate the proven pathway architecture for Rooted in Christ, Journey into Discipleship & Evangelism, The New Man, Kingdom Heirs Foundations, Counterfeit Gospels / The Truth Stick, children and education programs, leadership/fivefold equipping, and future curricula. New pathways must be addable from the administrator system without rebuilding the app. 2. Product Identity — What This App Is This is a global evangelism and discipleship ministry app, not primarily a local-church management app. It must work for people who encounter Kingdom Heirs through crusades, sports outreaches, churches, schools, missions, prisons, community programs, referrals, and online outreach across multiple nations. • Member-first: help a person know Jesus, grow as a disciple, and discover how to serve. • Global-first: language and country should be first-class member settings, not later add-ons. • Content-first: most ministry material should be editable by administrators without submitting a new mobile app version. • Pathway-first: members should see a clear next step rather than a confusing library of everything at once. • Scripture-first: Bible references and contextual reading should be easy to access from lessons and daily encounters. • Expandable ecosystem: the app must support future pathways, verified church partners, printable church resources, and ministry-event registrations without redesigning the core application. • Safe AI: AI should retrieve and summarize approved Kingdom Heirs content and Scripture resources; it should not invent doctrine or replace pastoral care. 3. Phase 1 Required Outcomes Area Phase 1 Requirement Pass Condition Platforms Android + iOS testable builds Kingdom Heirs can install and test both. Authentication Email login plus practical social login if chosen New user can register, sign in, sign out, reset password. Language Language chosen during onboarding and changeable later UI/content switches correctly for configured language. Assessment Onboarding survey recommends a starting pathway Survey result is stored and recommendation is explainable. Pilot pathway Come & See — 14 days All 14 lessons open, complete, and track progress. Bible Lesson Scripture opens Bible content/link cleanly Member can move from lesson reference to full passage. Quizzes 2 simple 8–10 question quizzes Score saved; user sees pass/review state. AI Search Search approved ministry content by question/topic Answers cite or identify source content used. Admin Non-developer content management Admin can edit/publish lesson text and common content. Analytics Basic member and pathway progress Admin can see signups, starts, completions, quiz results. 4. Phase 1 Member Flow Launch → Language → Welcome → Sign Up/Login → Country/Profile → Discipleship Survey → Recommended Pathway → Home → Come & See → Daily Lesson → Scripture/Bible → Reflection/Action → Mark Complete → Quiz → Progress → Completion → Next Recommended Step The member should always know three things: (1) Where am I? (2) What should I do next? (3) How do I get back home? Avoid deep menu nesting. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test 1. Splash / Launch Fast branded entry and startup checks. Kingdom Heirs logo; short mission line; app version/loading state. Automatic routing based on saved login/language. Loads reliably; returning member bypasses unnecessary onboarding. 2. Language Selection Establish global language before onboarding. Searchable language list; English first; scalable language codes; “Change later” note. Select language; Continue. Selection persists and can later be changed in Settings. 3. Welcome Explain what the app helps the member do. Know the Father • Follow the Son • Walk in the Spirit • Prepare for the Kingdom; short global ministry statement. Create Account; Sign In; Explore limited guest option if approved. Clear ministry identity; not framed as a single local church app. 4. Create Account / Login Create secure member identity. Name, email/phone as configured, password, social login if used, privacy/terms. Register; Login; Forgot Password. Account created; duplicate accounts handled; reset works. 5. Country & Profile Personalize region and member profile. Country; city/region optional; age range; preferred language; timezone; notification permission later. Save; Continue. Country/language stored in profile and visible to admin. 6. Why Are You Here? Warm-up before assessment. Examples: I am exploring Jesus; I am a new believer; I want to grow; I need freedom; I want to serve/lead; I want Bible foundations. Choose one or more. Selections persist and help seed recommendation.   5. Onboarding Survey & Pathway Recommendation The survey should be simple enough to complete in roughly 3–5 minutes. It should recommend, not diagnose. The user may accept the recommendation or intentionally choose another pathway. • Spiritual starting point: exploring Jesus / new believer / growing believer / mature believer / leader. • Bible confidence: rarely read / learning / comfortable / regularly study and teach. • Current need: know Jesus / establish identity / discipleship habits / freedom from addiction or sexual sin / biblical foundations / ministry and leadership. • Prayer and church/community connection. • Desire to share faith and make disciples. • Optional life-stage questions that improve recommendations without becoming intrusive. Primary Need / Starting Point Recommended Pathway Reason Exploring Jesus / unsure what I believe Come & See — 14 Days Encounter Jesus and understand the Gospel invitation. New believer / needs identity and habits Rooted in Christ — 30 Days Establish identity, prayer, Scripture, obedience, and Christlike living. Ready for disciplined growth and evangelism Journey into Discipleship & Evangelism — 90 Days Build daily disciplines and learn to share faith. Seeking freedom from pornography, shame, or sexual addiction The New Man — 90 Days Focused recovery/freedom resource; should include appropriate privacy controls. Needs broad biblical framework Kingdom Heirs Foundations — 120 Lessons Deep biblical worldview and preparation for ministry. Mature believer called toward ministry/leadership Foundations first or verified leadership pathway Fivefold/ministry equipping should sit on top of biblical foundation, not replace it. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test 7. Survey — Step 1 Capture spiritual starting point. 3–5 simple multiple-choice questions; progress indicator. Answer; Back; Next. Answers saved if user leaves and returns. 8. Survey — Step 2 Capture habits, needs, and goals. 3–5 questions; sensitive choices should be private. Answer; Back; Submit. Scoring produces deterministic result. 9. Recommendation Give a clear next step. Recommended pathway card; short “Why this fits you”; expected length; Start button; Choose Another Pathway link. Start Recommended; Browse Pathways. Recommendation matches defined rules and is saved. 10. Home Dashboard Make the next action obvious. Continue Your Journey card; Daily Scripture Encounter; progress; AI Ask/Search; Prayer; Media/Events optional shortcuts. Continue; Daily Scripture; Ask a Question; Menu. Primary pathway is above the fold and resumes at next incomplete lesson.   6. Pilot Pathway: Come & See — 14 Days Build this pathway completely before duplicating the structure. The pathway should be data-driven so future programs reuse the same screen templates and database model rather than requiring a new hard-coded app flow. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test 11. Pathway Overview Orient member before Day 1. Cover/title; 14-day description; purpose; progress 0/14; Start/Continue; lesson list with locked/unlocked policy. Start; Continue; Open available lesson. Progress and lesson states update correctly. 12. Daily Lesson Deliver one discipleship lesson. Day number/title; short teaching; key Scripture references; optional image/video/audio; Today’s Truth; action/reflection. Read Scripture; Play Media; Next; Mark Complete. Content loads from backend/admin; no app release required to edit text. 13. Scripture / Bible View Move from lesson into God’s Word. Reference, short licensed/approved preview if applicable; “Read full passage” action; language/version handling. Open integrated Bible provider or approved web/app deep link; Return to lesson. Correct passage opens in selected language/version where available. 14. Reflection / Response Turn head knowledge into heart/application. One reflection question; one action step; optional private note/prayer. Save note; Mark action; Continue. Private entries are not public by default. 15. Completion State Record daily progress. Completed check; next lesson teaser; streak optional but not manipulative. Next Day; Home. Completion persists across devices. 16. Quiz 1 Retention checkpoint after approximately Days 1–7. 8–10 multiple-choice questions; simple biblical recall; one answer per question. Submit; Review answers. Score stored; incorrect answers can show brief explanation/reference. 17. Quiz 2 Retention checkpoint after Days 8–14. 8–10 multiple-choice questions. Submit; Review; Finish Pathway. Completion logic respects defined quiz requirement. 18. Pathway Completion Celebrate and direct next step. Completion message; certificate/badge if used; summary; next recommended pathway. View Certificate; Start Rooted in Christ; Share optional. Completion recorded and next-step recommendation shown.   7. Daily Scripture Encounter The 365 Daily Scripture Encounters should be scheduled in a fixed Day 1–365 progression rather than randomized. The app should support the fields already prepared in the master workbook: day number, encounter title, Scripture reference, short NIV preview, Today’s Truth, Read in Context, and Bible Gateway NIV URL. • Display the encounter for the appropriate scheduled day. • Show the Scripture preview immediately so the member encounters God’s Word before clicking away. • Show Today’s Truth as Kingdom Heirs application, visually distinct from the Scripture text. • Provide a prominent “Read in Context” button. • Admin should be able to edit/schedule encounters without publishing a new app build. 8. AI Ask / Search — Phase 1 The first AI implementation should be retrieval-first. The member asks a question; the system searches only approved Kingdom Heirs materials and approved Scripture/reference sources, then produces a concise answer grounded in those sources. • Search scope in Phase 1: Come & See, Rooted in Christ, Journey into Discipleship & Evangelism, Kingdom Heirs Foundations, selected FAQs, and approved Scripture resources. The indexing model must later accept The New Man, Counterfeit Gospels / The Truth Stick, sermons, ministry training resources, and every future approved pathway without changing the AI architecture. • The answer should identify which Kingdom Heirs resource/lesson was used so the member can open it. • If the approved library does not support an answer, the app should say it does not have enough Kingdom Heirs material rather than fabricate doctrine. • High-risk pastoral situations should route toward trusted human help rather than presenting AI as a pastor, counselor, physician, or emergency service. • Admin needs an ingestion/indexing process for new approved content. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test 19. Ask Kingdom Heirs Natural-language search across approved ministry content. Question box; suggested topics; clear notice that answers come from approved library. Ask; Clear; Open Source. Known questions retrieve relevant approved content. 20. AI Answer Give concise grounded discipleship answer. Answer; Scripture references; source cards; “Go Deeper” links. Open source lesson/book; Ask follow-up. Source attribution is visible; unsupported questions fail safely. 21. Search Results Allow non-AI keyword/topic browsing. Results grouped by pathways, lessons, Scripture, media. Filter; Open result. Search handles common terms and multilingual strategy.   9. Global Language Architecture Do not hard-code English into the interface or content model. Every user-facing string and every piece of ministry content that may be translated should support a language code and fallback behavior. • UI strings: localization files/keys, not English text embedded throughout widgets. • Content: separate translation records tied to the same lesson/content ID. • Member preference: preferred language stored on profile; changeable at any time. • Fallback: if a translation is unavailable, show the designated fallback language and clearly identify it. • Right-to-left support should be considered for Urdu/Arabic-family interfaces even if not all RTL languages launch on Day 1. • Search/AI indexing should retain language metadata so users receive content in their selected language whenever available. Initial language architecture should be scalable for ministries in Africa and South Asia. The exact launch language list can be staged based on available translated content rather than forcing every language into Phase 1. 10. Administrator Experience Kingdom Heirs must not depend on the developer for everyday publishing. The developer should identify and demonstrate the exact administrator interface the ministry will use after launch. If FlutterFlow is used for front-end development, the operational content should still live in a backend/CMS structure that authorized staff can safely manage. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test A1. Admin Login Secure staff access. Role-based login; MFA if supported. Sign In. Member credentials cannot access admin. A2. Admin Dashboard See content and member activity. Member count; pathway starts/completions; pending content; quiz stats; recent activity. Open Content; Users; Analytics; Notifications. Key metrics load from live data. A3. Pathway Manager Create/edit reusable pathways. Title; description; order; language; status; lesson list. Add/Edit/Reorder/Publish. Changes appear in app without store release. A4. Lesson Editor Manage daily lesson content. Title; body; Scripture references; media; reflection; language; publish date/status. Save Draft; Preview; Publish. Admin can edit Come & See lesson and see app update. A5. Quiz Manager Manage questions and answers. Question; options; correct answer; explanation/reference; assignment point. Add/Edit/Delete/Publish. Quiz updates without mobile rebuild. A6. Daily Scripture Manager Import/schedule 365 encounters. CSV import; day/date; title; preview; truth; context; Bible URL. Import; Validate; Schedule; Edit. 365-row import validates and schedules in order. A7. Member / Progress Support discipleship operations. Profile; language/country; pathway; progress; quiz scores; roles. Search; View; limited admin actions. Permissions protect sensitive/private data. A8. Notifications Send reminders and ministry updates. Audience filters by pathway/language/country; schedule; preview. Schedule/Send. Test notification reaches correct audience.   11. Core Data Objects the Developer Should Plan For Object Minimum Fields Why It Matters User ID, name, email/phone, country, language, timezone, roles, survey result Member identity and localization. Pathway ID, title, description, order, audience, language availability, status Reusable program container. Lesson ID, pathway ID, day/order, title, body, Scripture refs, media, reflection, status All lesson content should be backend-driven. Progress user ID, pathway ID, lesson ID, completed at, quiz state Resume and completion logic. Quiz / Question quiz ID, placement, question, choices, correct answer, explanation Retention assessments. Daily Scripture day/date, title, reference, preview, truth, context, URL, language 365-day scheduled encounters. Translation content ID, language code, translated fields, reviewed/published status Scalable multilingual content. Media ID, type, URL/storage, title, language, captions/transcript Reusable video/audio assets. AI Source Document source ID, title, book/pathway/lesson, language, chunk/index status Grounded AI retrieval. Notification audience, language, schedule, title/body, deep link Member engagement. Church Partner church ID, church name, country, city/region, coordinates or map location, languages, worship times, contact, website, pastor/contact person, statement-of-faith review, verification status, visibility Supports a trusted fellowship directory for new converts and traveling members. Church Resource resource ID, title, category, file/PDF URL, language, version, audience, print/download permission, publish status Allows approved churches to download and print discipleship materials, sermon/teaching resources, decision resources, and training tools. Tournament / Ministry Event event ID, title, sport/type, country, community, venue, dates, age groups/divisions, capacity, registration window, language, status Creates reusable community-by-community registration for Kingdom Heirs sports outreaches and ministry events. Tournament Registration registration ID, event ID, participant/team, age/division, contact, guardian if minor, church/community, consent/waiver status, check-in status, notes Captures registrations and produces usable rosters while protecting participant data. Church User Role user ID, church ID, role, permissions, approval status Allows approved church leaders to access partner resources without receiving global ministry-admin permissions. 12. Navigation — Phase 1 Keep the main navigation simple. Recommended bottom navigation for the pilot: • Home — continue pathway, daily Scripture, key next actions. • Pathways — browse/current programs. • Ask — AI search and content discovery. • Community or Prayer — choose one for Phase 1 based on development scope; the other can follow. • Profile / More — language, settings, progress, downloads, support. Do not overload the first release with every future menu item. Media, Events, Giving, Store, Directory, advanced community features, leadership tools, and other modules can be added after the core discipleship loop is proven. 13. Developer Deliverables for the First Milestone • Clickable FlutterFlow prototype or test build covering Screens 1–10 before deep data integration. • Database/schema diagram and list of external services/accounts. • Come & See pathway fully populated with sample/real content for all 14 days. • Working login, survey, pathway recommendation, lesson progress, Bible access, two quizzes, and completion. • Working admin workflow demonstrating an edit to a lesson that appears in the app without a mobile store update. • Working test of at least two languages in the interface/content architecture. • Working first-pass AI retrieval for a small approved content set. • Android test build and iOS TestFlight build (or equivalent test access). • Screen-recorded walkthrough plus live review call. • Source-code repository access and owner/admin access to all project services for Kingdom Heirs. 14. Definition of “Phase 1 Approved” Phase 1 is not approved because screens look attractive. It is approved when the entire member journey works reliably from installation to completion and Kingdom Heirs can manage content without the developer. • PASS: New user can install the app on iPhone and Android. • PASS: User selects a language, creates an account, and completes onboarding. • PASS: Survey returns the expected pathway recommendation. • PASS: User can start Come & See and complete all 14 lessons. • PASS: Every Scripture action opens the correct passage/resource. • PASS: Progress is saved after logout/login and, if supported, across devices. • PASS: Both quizzes score correctly and store results. • PASS: Daily Scripture Encounter displays in the intended fixed sequence. • PASS: AI search returns grounded answers from approved content with source links. • PASS: Administrator can edit/publish content without developer intervention. • PASS: Kingdom Heirs has owner/admin access to code, backend, app stores, hosting, and services. • PASS: No major navigation dead ends, placeholder screens, or non-working buttons remain. 15. Expansion After Pilot Approval Once the Come & See architecture is proven, the developer should duplicate the same reusable pathway framework rather than rebuild each program from scratch. The pathway engine must support books that become curricula, including Counterfeit Gospels / The Truth Stick, and must allow future Kingdom Heirs discipleship and ministry-training curricula to be added from the admin system. Order Pathway / Module Length Special Notes 1 Come & See 14 days Pilot; 2 quizzes. 2 Rooted in Christ 30 days 4 weekly quizzes. 3 Journey into Discipleship & Evangelism 90 days 12 weekly quizzes. 4 The New Man 90 days Freedom/addiction resource; privacy-sensitive. 5 Kingdom Heirs Foundations 120 lessons Deep biblical framework; periodic quizzes after lesson build. 6 Counterfeit Gospels / The Truth Stick Variable pathway Apologetics and discernment pathway; build from the book/curriculum using the same reusable pathway engine. 7 Children / Learn English / regional programs Variable Education and children’s discipleship architecture; language/localization is essential. 8 Leadership / Fivefold Equipping Advanced For mature disciples after foundational pathways; equipping for ministry and multiplication. 9 Future Kingdom Heirs Curricula Variable Admin-created pathways must be addable without code changes or app-store resubmission. 16. Questions the Developer Must Answer Before Coding Begins 9. Which backend will store users, pathways, lessons, progress, translations, quizzes, and AI source content? 10. Which features are being built directly in FlutterFlow and which require custom Flutter/Dart code? 11. How will the Bible experience be implemented, and what provider/licensing/deep-link approach is proposed? 12. How will localization and right-to-left layouts be handled? 13. What AI/retrieval architecture will keep answers grounded in Kingdom Heirs-approved materials? 14. What admin interface will Kingdom Heirs staff use every day? 15. What accounts, repositories, keys, and services will be owned by Kingdom Heirs from Day 1? 16. How will backups, version control, and disaster recovery be handled? 17. What is the exact deliverable and price for Phase 1 only? 18. What objective acceptance tests must pass before Phase 2 begins? Developer Instruction Do not build ahead of approval. Complete the Phase 1 flow, demonstrate it on both platforms, give Kingdom Heirs administrative access, and obtain written approval before beginning the next pathway or major module. The goal is to build a stable discipleship platform that can scale globally without repeatedly rebuilding the core app.   17. Future-Ready Ministry Ecosystem — Required Now in the Architecture Phase 1 still builds and tests one complete pathway first. However, the database, navigation model, roles, and administrator system must be designed now so the following modules can be added without rebuilding the app core. These are not optional ideas; they are planned Kingdom Heirs capabilities. • Expandable Pathway Library — books and new curricula can become guided pathways using the same reusable pathway/lesson/quiz/progress engine. • Church Partner Network — churches can apply to become verified fellowship locations so new converts can find trustworthy community worship near them. • Church Resource Library — approved churches can access and print Kingdom Heirs discipleship materials, sermon/teaching resources, decision resources, training guides, and future ministry tools. • Sports & Outreach Registration — each city/community event can collect participant or team registrations, permissions, and check-in information. • Global Localization — all of these modules must inherit the user’s language and support new countries/languages over time. 18. Growing Pathway Library The app must treat a pathway as a reusable content container, not as a hard-coded list of the first five programs. Kingdom Heirs will continue producing books, discipleship curricula, evangelism tools, and ministry-training resources. An administrator must be able to create a new pathway, assign its audience and languages, add lessons, quizzes, media, completion rules, and publish it without a new mobile-app release. Future pathway flow: Admin creates pathway → adds lessons/media/Scripture → adds translations → assigns quizzes/completion rules → previews → publishes → survey/recommendation rules can point qualified members to it. Pathway Capability Developer Requirement Admin Action Member Experience Acceptance Test Come & See source book Use the book/curriculum as the content source for the 14-day pilot. Edit lesson content and translations. Complete a 14-day guided encounter with Jesus. All 14 days function end-to-end. Counterfeit Gospels / The Truth Stick Create with the same pathway engine; no custom-coded pathway screens. Create lessons, Scripture links, quizzes, media, and languages. Follow a structured discernment/apologetics pathway. Admin can publish it without app rebuild. Future curricula No fixed maximum number of pathways. Create, archive, reorder, feature, and localize pathways. New programs appear when published and may be recommended by survey rules. A test pathway can be created entirely from admin. Recommendation rules Rules must be data-driven, not hard-coded in FlutterFlow widgets. Map survey answers/needs to pathway IDs and priorities. User receives an explainable recommendation but may browse alternatives. Admin can change recommendation mapping without store update. 19. Church Partner Network — Fellowship & Community Worship Kingdom Heirs needs a church-partner network that helps a new convert move from an outreach or digital encounter into healthy Christian fellowship in the person’s own community. This is a directory and ministry-partner function, not a local-church management system. Member flow: Home/Connect → Find a Church → use current location or choose country/city → filtered church results → church profile → directions/contact/service information. Church sign-up flow: Church Partner → Apply → church/pastor/contact details → location/languages/service information → ministry/faith information → submit → Kingdom Heirs review → approved/changes requested/declined → verified listing published. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test C1. Find a Church Help members locate fellowship. Search by location; map/list; language; distance; worship times; verified badge. Search; filter; open profile. Relevant verified churches appear for selected location. C2. Church Profile Give practical information before a visit. Church name; location/map; service times; languages; contact; website; pastor/contact; ministries; verification status. Directions; call/contact; website; save. Member can contact or navigate without exposing private admin data. C3. Become a Partner Church Explain benefits and responsibilities. Why partner; listing; discipleship resources; expectations; verification process. Start application. Church understands approval is required before public listing. C4. Church Application Collect required partner information. Church identity; country/city; location; pastor/contact; languages; services; website/social; faith/ministry questions; consent. Save draft; submit. Application reaches admin queue and applicant receives confirmation. C5. Church Partner Portal Give approved churches resources and listing controls. Listing status; editable public details; resource library; downloads; announcements relevant to partner churches. Edit permitted fields; browse/download resources. Partner cannot edit verification/admin-only fields. 20. Church Resource Library — Printable Discipleship & Teaching Tools Approved church partners should have a resource area they can use immediately in local ministry. The resource library must support downloadable/printable files and translated versions without requiring the church to contact the app developer. • Resource categories should support discipleship materials, sermon/teaching outlines, evangelism resources, decision/covenant materials, small-group guides, leader resources, certificates, children’s materials, and future categories. • Each resource needs title, description, category, audience, language, version/date, file type, download/print permissions, and published status. • Resources may be public, member-only, or verified-church-only according to permissions. • Admin should be able to replace a PDF or upload a translated edition while keeping one resource record and its version history. Church resource flow: Partner Portal → Resources → choose category/language → preview resource → download/print → optional related pathway/sermon links. 21. Sports Tournament & Community Outreach Registration Kingdom Heirs conducts sports tournaments and community outreaches in different communities. The app should provide reusable event registration so each new location does not require a separate form or custom development. Participant flow: Events → choose tournament/community → event details → Register → individual/team information → age/division → contact/guardian information when required → consent/waiver → review → submit → confirmation/check-in code or QR if implemented. # / Screen Purpose Key UI / Content Primary Actions Acceptance Test E1. Events / Tournaments Show available ministry events. Country/community filters; upcoming events; registration open/closed; sport; dates. Filter; open event. Correct localized events appear. E2. Event Detail Explain the tournament/outreach. Venue; map; dates/times; sport/divisions; age rules; registration deadline; ministry information; contact. Register; share; directions. All event-specific rules are backend-driven. E3. Registration Type Route participant correctly. Individual / team / coach-manager; relevant divisions. Choose type; continue. Only applicable fields appear. E4. Participant / Team Form Capture usable roster information. Name/team; age/division; contact; country/community; church/community affiliation optional; guardian for minors; required consent fields. Save; next; add team members. Validation prevents incomplete required records. E5. Consent / Waiver Capture required acknowledgement. Event-specific terms; parent/guardian consent when applicable; privacy notice. Accept/sign/confirm according to implementation. Consent status stored with registration and timestamp. E6. Confirmation / Check-In Give registrant proof and next step. Registration number; event summary; QR/check-in code optional; contact/update instructions. Save/share; add to calendar if supported. Admin roster and member confirmation match. 22. Admin Screens for Churches, Resources & Events Admin Screen Purpose Key Functions Permissions Acceptance Test A9. Church Applications Review partner churches. Queue; application detail; request changes; approve/decline; verification notes; publish/unpublish. Kingdom Heirs admin only. Approval controls public directory visibility. A10. Church Directory Manager Maintain approved listings. Search; edit admin fields; verification status; featured status; inactive/archive. Kingdom Heirs admin; limited partner self-edit. Partner changes do not bypass protected verification fields. A11. Resource Library Manager Publish printable ministry resources. Upload file; language/version; category; permissions; preview; publish/archive. Content admin. New PDF/resource appears without mobile rebuild. A12. Event/Tournament Manager Create community events. Location; dates; sport/divisions; capacity; registration window; form fields; consent text; publish. Event admin. Admin can clone an event for a new community. A13. Registration & Check-In Manage participants/teams. Search; filters; roster; consent status; check-in; export CSV/PDF; counts. Event admin; data access limited by role. Roster accurately reflects live registrations. 23. Privacy, Roles & Global Data Requirements • Collect only information needed for discipleship, church connection, or event operations. Do not make private member data visible in the public church directory. • Minor participants require age-appropriate handling and guardian/consent logic where required for the event and jurisdiction. • Use role-based access: Kingdom Heirs global admin, content admin, event admin, verified church partner, and ordinary member should not share the same permissions. • Country, language, timezone, and localized content must be first-class data fields rather than assumptions embedded in the interface. • Church and event modules should support country/community filters so the same app can operate across Africa, South Asia, the United States, and future regions. • Backups, source control, service credentials, and owner access must remain under Kingdom Heirs control even when contractors build individual modules. 24. Revised Development Order — Do Not Build Everything at Once Milestone Scope Milestone 1 Core shell + onboarding + language + account + survey + recommendation. Milestone 2 Come & See 14-day pathway completely working, including Scripture/Bible, progress, two quizzes, and completion. Milestone 3 Admin content workflow + 365 Daily Scripture import/scheduling + initial grounded AI search. Milestone 4 iOS and Android testing; fix all navigation/dead-end issues; Kingdom Heirs acceptance of pilot. Milestone 5 Reusable pathway expansion: Rooted in Christ, 90-Day Journey, Foundations, The New Man, Counterfeit Gospels / The Truth Stick, then future curricula. Milestone 6 Church Partner Network + verified directory + church resource library. Milestone 7 Sports tournament/community-event registration and admin roster/check-in. Milestone 8 Advanced community, media, prayer, giving, leadership/fivefold equipping, and other approved modules. Developer rule: Build each milestone to a working, testable state and obtain written Kingdom Heirs approval before beginning the next paid milestone. The architecture must anticipate later modules, but payment and acceptance should be tied to demonstrated functionality rather than percentage-complete claims.