Appearance
lt-app
needs verificationPurpose
lt-app lets researchers and coordinators record chaptered research videos on a phone and manage their work. It owns the mobile interface; lt-core owns the business rules.
What it does
Researchers have Workspace and Profile tabs. Coordinators have Workspace and My Researchers. The center button starts a new LT Work. Administrators select a user to impersonate before entering that person's workspace.
A Publication starts with source papers, then chapter recording. A Profile Video skips the papers. Coordinators first select the subject researcher. Publication Plus has no supported creation flow in this app.
The recording screens provide a camera, teleprompter, face alignment, preview and cover photography. Kept recordings upload through lt-core's multipart upload control plane. Submission and approval belong to the publication story.
For a step-by-step explanation, read the sign-in flow and the video-creation flow.
Sign in
The app offers email with a password, email with a one-time code, and Open Researcher and Contributor ID (ORCID) sign-in. ORCID is the researcher's persistent identifier. Email identity checking determines the existing account's available methods. Registration supports researcher or coordinator accounts; administrators also complete two-factor authentication before user selection.
Get the app on your phone
Ask the team lead for the current installation link and the right tester invitation.
iOS staging: install TestFlight from the App Store, open the invitation on your phone, and install LT STG. The documented tester groups are Welink Internal for internal testers and Latest Thinking for external testers, which needs Beta App Review for its first build. Builds expire after 90 days. The mobile team prepares the builds and can help if an invitation or installation fails.
Android staging: ask for the EAS build download link for the staging profile, download the Android application package (APK), permit installation from that source on the device, and install it. Developers can use the Android Debug Bridge (adb): adb install -r builds/<file>.apk. EAS is Expo Application Services, the build and distribution service. The configuration provides internal APK distribution; a Play Store internal track is not documented.
| Variant | Display name | iOS bundle and Android package | Backend |
|---|---|---|---|
| Development | LT DEV | software.welink.lt.app.dev | Developer configured |
| Staging | LT STG | software.welink.lt.app.staging | core.stg.lt.org |
| Production | Latest Thinking | org.lt.app | core.lt.org |
The separate identifiers allow the variants to coexist. The production identifier is reserved for the client's publisher decision and must never be built or uploaded from Welink accounts. The configuration does not prove a production store release exists.
No over-the-air update channel is documented. Treat a new distributed version as a new native build until the mobile team confirms otherwise. The startup API Healthcheck log names the environment and backend URL.
See LT Work statuses for every app label, who acts next, and how revision, cancellation and restoration work.
For maintainers: technology
Expo software development kit (SDK) 53, React Native 0.79, Expo Router, React Query, Zustand, NativeWind and Vision Camera. The in-app player is a native implementation using expo-video, with its own controls, chapters and subtitles. It does not embed the web LT Player package.
How it connects
The app sends account and video-work requests to lt-core. Recordings are uploaded to storage for processing. Only administrators can change the acting context when working on someone else's behalf.
Who can do what
“Yes” means the relevant app interface exists; “partial” means impersonation or an incomplete surface. An Editor is a Strapi role, not a mobile role.
| Action | Anonymous | Researcher | Coordinator | Administrator | Editor |
|---|---|---|---|---|---|
| Open sign-in and registration | Yes | Yes | Yes | Yes | No |
| Maintain own mobile account | No | Yes | Yes | Partial | No |
| Create and record own Publication or Profile Video | No | Yes | No | Partial | No |
| Create work for a researcher | No | No | Yes | Partial | No |
| Use My Researchers | No | No | Yes | Partial | No |
| Manage researcher connections | No | Partial | Yes | Partial | No |
| Select and impersonate a user | No | No | No | Yes | No |
Researcher-side My Connections is currently hidden and described as placeholder content in the settings code. Do not assume every backend connection action has a finished mobile screen.
Environments and links
Local backendhttp://core.lt.localhostPhone connectivity requires the local development setup
Staging backendhttps://core.stg.lt.orgLT STG
Production backendhttps://core.lt.orgConfigured target; app release requires publisher decision
Backend targets come from EAS profiles. Local networking is explained in the environment guide.
Where to read more
Getting the app, the publication journey and Publication and Publication Plus.
Known gaps
Researcher connection management is incomplete. Push notifications remain a brief-recorded gap. Store distribution and the absence of an over-the-air update channel need mobile-team confirmation. Some older installation guidance needs updating. Track these in open questions.
For maintainers: source references
These references require repository access. Everything needed to understand this page is explained above.
- Responsibility boundary
- Tabs
- user selection
- Flow registry
- Recording screen
- cover screen
- upload client
- Authentication service
- ORCID flow
- registration
- TestFlight runbook
- Build profiles
- device installation
- Variant configuration
- publisher constraint
- Environment guide
- Dependencies
- native player
- Context retrieval
- context headers
- uploads
- Settings implementation
- EAS profiles
- environment guide
- Repository and setup
- Project guidance
- Recording flow skill