Open-source mobile platform for trusted health articles, podcasts, AI-assisted wellness chat, and community-driven content review. This repository contains the Expo React Native application and supporting TypeScript packages.

• Multilingual articles — Read and publish health content with translation workflows
• Podcast library — Stream, record, and manage health podcasts with offline support
• AI wellness chat — Character-based health Q&A powered by configurable AI backends
• Guest mode — Browse articles and podcasts without signing in
• Community review — Collaborative editing, trust signals, and moderation tooling
• Wellness dashboard — Activity tracking and wearable sync entry points
• Push notifications — Firebase Cloud Messaging integration
• Optional cache layer — Redis-backed persistence package for development tooling

flowchart TB
  subgraph Mobile["UltimateHealth Mobile App"]
    UI[Screens and Components]
    State[Redux Store]
    Query[TanStack Query]
    Config[Runtime Config]
  end

  subgraph Packages["Monorepo Packages"]
    Persistence[packages/persistence]
  end

  subgraph External["External Services"]
    API[Node.js REST API]
    Socket[WebSocket Server]
    Intel[Content Intelligence API]
    Redis[(Redis - optional)]
  end

  UI --> State
  UI --> Query
  Query --> API
  UI --> Socket
  UI --> Intel
  Persistence --> Redis
  Config --> UI

sequenceDiagram
  participant User
  participant App as Mobile App
  participant Redux as Redux Store
  participant API as REST API

  User->>App: Open article feed
  App->>API: GET /articles
  API-->>App: Article list JSON
  App->>Redux: Cache filter state
  App-->>User: Render feed

  User->>App: Like article
  App->>API: POST /articles/:id/like
  API-->>App: Updated counts
  App-->>User: Optimistic UI update

UltimateHealth/
├── frontend/              # Expo React Native app (TypeScript)
│   ├── src/
│   │   ├── components/    # Shared UI
│   │   ├── screens/       # Route views
│   │   ├── hooks/         # API hooks
│   │   ├── services/      # Monitoring, storage helpers
│   │   ├── config/        # Environment accessors
│   │   └── store/         # Redux slices
│   └── app.config.js      # Expo dynamic config
├── packages/
│   └── persistence/       # Optional Redis layer
├── docs/
│   └── internal/          # Maintainer audit and structure notes
└── .github/workflows/     # CI and EAS build pipelines

See docs/internal/STRUCTURE.md for structural decisions.

git clone https://github.com/SB2318/UltimateHealth.git
cd UltimateHealth

# Install all workspaces (frontend + packages)
npm install

# Copy environment templates
cp frontend/.env.example frontend/.env
cp packages/persistence/.env.example packages/persistence/.env

cd frontend
npm install --legacy-peer-deps
npm run check-env
npm run start

Values are injected through app.config.js into expo-constants at build time.

# From repository root — full validation suite
npm run validate

# Frontend only
cd frontend
npm run type-check
npm run lint
npm run test
npm run start          # Expo dev server
npm run android        # Native Android build
npm run ios            # Native iOS build (macOS)

Use Conventional Commits for commit messages.

# Unit tests (Jest + React Native Testing Library)
cd frontend && npm test

# Persistence package (Vitest)
cd packages/persistence && npm test

# Dead code analysis
cd frontend && npm run knip

Test files live alongside source under __tests__/ directories. See TEST_GUIDELINES.md for project conventions.

npx kill-port 8081
npx expo start --port 8082

cd frontend
npm install --legacy-peer-deps

Set ANDROID_HOME to your SDK path and add platform-tools to PATH.

Update Expo Go on your device or use a development build:

npx expo start --dev-client

rm -rf node_modules
npm install --legacy-peer-deps
npm run type-check

Ensure Redis is running locally (redis-server) or set REDIS_ENABLED=false to skip the persistence layer.

Where is the backend API?
The Node.js REST API and MongoDB backend live in a separate repository (ultimatehealth-backend). Configure PROD_URL to point at production or your local instance.

Is Redis required for the mobile app?
No. The persistence package is optional and targets development tooling, CI fixtures, and future cache integrations — not the React Native runtime.

Can I use npm instead of Yarn?
Yes. The root workspace uses npm. The frontend CI still references Yarn lockfiles; both package managers work locally with --legacy-peer-deps for npm.

How do I run on a physical device?
Use Expo dev client or EAS builds. Push notifications require a physical device with FCM configured.

1. Browse open issues
2. Fork the repository and create a feature branch
3. Run npm run validate before opening a PR
4. Read CONTRIBUTING.md and CODE_OF_CONDUCT.md

Maintainer documentation:

• docs/internal/AUDIT.md — Architecture audit and improvement log
• docs/internal/STRUCTURE.md — Folder layout decisions

See LICENSE for details.