KTP Life App¶
Product overview¶
The KTP Life App is Kappa Theta Pi's member-facing mobile application. It brings chapter onboarding, member profiles, a searchable KTP network, chapter events, RSVP handling, attendance check-in, and push-notification registration into one application.
Current status: TestFlight beta
TestFlight testing is active as of September 2, 2026. Access is limited to approved testers while the product team validates functionality, privacy, accessibility, support, and release readiness. A public production launch date has not been documented.
The official product name still needs confirmation: the supplied engineering documentation calls it the Kappa Theta Pi Mobile App, while this portal previously used National Life App. This section uses KTP Life App as the working name until National Technology publishes a naming decision.
Current beta capabilities¶
| Area | Documented behavior |
|---|---|
| Account and chapter selection | Select a chapter, register, sign in, and restore an authenticated session |
| Home | See a personalized welcome, chapter announcements, upcoming events, RSVP state, and member suggestions |
| Calendar and events | Browse chapter events, refresh synchronized event data, and respond going, maybe, or not going |
| Attendance | Authorized EBoard users display a rotating event QR code and members scan it to check in |
| Network | Search and filter the selected chapter's member directory |
| Profiles | View and maintain approved academic, professional, social, profile-image, résumé, pledge-class, and internship information |
| Notifications and connectivity | Register a physical device for push notifications, show offline state, and refresh data after connectivity returns |
These capabilities are taken from client documentation supplied to this project on September 2, 2026. A capability should be described as released only after it is verified against the current beta build and its required backend services.
Documentation map¶
- Architecture: client layers, services, data flow, and repository boundaries
- Developer Setup: public-safe prerequisites, local setup, checks, and first-run verification
- Chapter Onboarding: how a chapter joins the current beta and transitions its app contacts
- Teams and Ownership: chapter-led engineering teams, decision rights, staffing, and handoffs
- Data and Access: member information, authorization boundaries, exports, and incidents
- Support and Releases: beta feedback, severity, release gates, and public release notes
Product boundaries¶
The documented client is an Expo/React Native application with a web-compatible target. Its source repository does not contain every system required to operate the product. The following are separate sources of truth:
- the KTP management dashboard;
- database schema and migrations;
- server authorization policies;
- backend functions;
- server-side calendar synchronization; and
- production operations, credentials, signing, and recovery procedures.
Public documentation may explain the architecture and contribution workflow. Exact production identifiers, credentials, private service links, member data, security findings, and operational recovery details belong in approved restricted systems.
Product principles¶
- The member experience should be useful without requiring unnecessary personal information.
- UI role checks improve usability but never replace server-side authorization.
- Every feature has a product owner, technical owner, data classification, and support route.
- Beta builds use development or approved test data whenever practical.
- A chapter-led team always has a cross-chapter backup and a National sponsor; both mobile development areas are staffed as teams rather than single-developer assignments.
- Documentation, tests, accessibility, privacy, and release notes are part of feature completion.
Facts still needed¶
The highest-priority confirmations are the official product name, canonical organization-owned repositories, current TestFlight build/version, participating beta chapters, Android plan, approved tester and feedback routes, product owner, release authority, privacy notice, and production launch criteria. Track these and other gaps in the Factual Information Audit.
Getting help¶
Use the Technology route in the National Organization Map. Do not place credentials, invitation links, member records, private logs, or screenshots containing personal information in public issues.