# MVP

The MVP should prove that language-first discovery is useful before attempting the full ecosystem platform.

## MVP Goal

Help a worker quickly find appropriate Christian resources for a target language.

The MVP should answer:

- What resources exist for this language?
- Which resources are recommended?
- What are they useful for?
- Where can I access or share them?

## Access Principle

Prioritize openly accessible online resources that field workers can easily view, play, link to, or share.

The MVP should not focus on resources behind logins, paywalls, closed platforms, or unclear access rules. If a worker cannot quickly share or use the resource in the field, it is lower priority.

## Initial Scope

Build a simple web platform with:

- language landing pages
- resource search
- basic filtering
- resource detail pages
- featured or recommended resources
- basic multilingual UI support
- API-first source ingestion
- fuzzy language search backed by normalized language records
- AI-assisted metadata ingestion later for messy sources and URLs

## MVP User

The first user is a field worker who needs to quickly find and share a useful resource for someone from a specific language community.

The product should not require this user to know ISO codes, exact dialect labels, source organizations, or expert terminology.

## MVP Region

Start with South and Southeast Asian languages in and around:

- India
- Pakistan
- Bangladesh
- Thailand
- Laos
- Cambodia
- Vietnam
- Indonesia

## First Language Pages

Start with a small set of pilot languages rather than broad coverage.

Possible pilot language criteria:

- known field need
- available starter resources
- reachable workers for feedback
- manageable metadata volume
- regional clustering

Example pilot pages:

- `/shan`
- `/khmer`
- `/nepali`

Pilot pages should be chosen based on available source data and real field-worker usefulness, not only broad language size.

## MVP Resource Fields

Minimum fields:

- title
- language
- optional language variant
- country or region
- media type
- source URL
- public access status
- organization or platform
- short description
- topics
- audience
- recommended usage
- duration
- tags
- quality or curation status
- original source language label
- normalized language code

## Discovery Features

Initial filters and groupings:

- media type
- topic
- audience
- literacy level
- use case
- source organization
- recommended
- recently added

Initial recommendation groups:

- start here
- short videos
- audio resources
- Bible and Scripture
- discipleship
- seeker friendly
- low bandwidth

## Initial Sources

Start with structured sources before messy ingestion.

Initial source targets:

- Joshua Project for people group, country, and language context
- Jesus Film Project for video resources by language
- Global Recordings Network as a likely next source after the first integration path is proven

The goal is to build the discovery experience and language normalization layer before investing heavily in scraping or AI cleanup of messy catalogs.

Video and audio should be prioritized over text in the initial source work. Text resources are allowed, especially when highly useful, but they are less central to the first field-worker experience.

## AI-Assisted Ingestion

AI-assisted ingestion is important, but it should come after API-first ingestion proves the core user experience.

A later ingestion flow can be semi-manual:

1. User submits a URL.
2. System extracts title, description, transcript, and metadata where available.
3. AI detects language and possible language variant.
4. AI proposes topics, audience, summary, and recommended usage.
5. Human curator reviews and approves.
6. Resource becomes searchable and appears on language pages.

## Not In MVP

Avoid building these too early:

- mobile apps
- full offline sync
- organization dashboards
- complex analytics
- public API
- automated ranking from engagement signals
- large-scale partner integrations
- advanced chatbot assistant
- indexing closed or locked resources

These may become important later, but the first milestone is proving usefulness with a small, trusted, curated resource set.

## MVP Success Signals

Useful indicators:

- workers can find a resource faster than before
- language pages are shared in real ministry conversations
- users save or share resources
- field workers submit corrections or recommendations
- partner organizations see value in being included
- curated recommendations are trusted