External Resource Links
Feature Detail
Description
External Resource Links surfaces an organization-configured list of external URLs within the mobile app. Link lists are managed by org admins in the Admin Web Portal and fetched at module bootstrap, letting each tenant expose relevant resources without a client release. The screen renders links with descriptive labels, opens them in the device browser, and caches the list in Drift for offline access. Organizations can categorize entries and apply terminology overrides to labels.
Sources & reasoning
The priority matrix in §4 places External Resource Links at NICE priority, Fase 2, present for all four organizations. Fase 2 maps to v1.0 by ordinal position (second phase). The HLF portal coordination requirement in §3.3 reinforces the need to surface external links as a bridge rather than a replacement. Blueprint assigns v1.0, consistent with the source evidence.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Each organization has existing digital infrastructure - member portals, training platforms, external sites - that users need regularly. Surfacing links inside the app reduces context switching and support burden. For HLF this is especially relevant: the parallel Dynamics portal project must remain accessible from Meander without conflicting with it. Admin-managed lists mean organizations update resources without a client release, giving operational autonomy and reducing dependency on Norse for content changes. This directly addresses the HLF portal coordination requirement in the source document.
The external_resource_links table stores entries per organization with title, URL, category, and sort order. The mobile app fetches the list at module bootstrap and caches it in Drift; links are read-only and low-churn, making indefinite caching safe until the next sync. URL opening must use url_launcher with canLaunchUrl validation and a graceful fallback when the URL cannot be opened. The Admin Web Portal provides a CRUD UI under Organization Settings with HTTPS enforcement and title length limits. The screen registers deep-link entry points via the module registry.
Components (45)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.