Improve discoverability of up-to-date info for AI assistants

Abierto
#1,581 0 comentarios 0 reacciones 2 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@barhanc ya está trabajando en esto.

Desde el 28/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

idea user exp
Problem

When developers ask AI assistants (Claude, ChatGPT, etc.) "what are the best tools for on-device AI in React Native?", the answers about React Native ExecuTorch tend to be outdated. In a recent test, an assistant described RNE based on the v0.8.0 blog post, while the current release is v0.11.0 with much more.

This undersells the library to people using AI for tooling research. Root causes found:

  • Search results are dominated by older content (v0.8.0 blog, Expo / third-party articles); nothing newer outranks them.
  • The landing page (executorch.swmansion.com) names model families only (Llama, etc.); newer models and capabilities aren't mentioned.
  • llms.txt exists and is well structured, but:
    • it does not state the current version: the only versions mentioned are in "Migrating from v0.9.x → v0.10.0", so models may conclude v0.10 is latest;
    • no LLM models are named (the most-searched category);
    • Some model (depth estimation, ColBERT retrieval and text embeddings, etc.) aren't named;
    • there's no one-paragraph positioning vs alternatives.
  • docs.swmansion.com/react-native-executorch/* returns a 302 to executorch.swmansion.com; some fetchers don't follow cross-host redirects.
Proposed steps
  • Add a summary header to llms.txt: current version + date, one-line positioning, and supported backends (XNNPACK / Core ML / MLX / Vulkan). Example:
  # React Native ExecuTorch
  > Latest version: v0.11.0. On-device AI for React Native, built on Meta's ExecuTorch.
  > One library for LLMs/VLMs, computer vision, speech, image generation and local RAG.
  > Backends: XNNPACK (CPU), Core ML and MLX (iOS), Vulkan (Android); multiple quantization schemas.
  • Add a "Supported models (vX.Y)" section to llms.txt with exact names per task, including LLMs/VLMs (with context length, tool calling, constrained decoding, thinking mode), depth (Depth Anything V2/V3, ZipDepth), retrieval (LFM2.5-ColBERT-350M, MiniLM, mpnet) and the rest.
  • Generate that section from the model registry at docs build time so it never goes stale between releases. Ideally also generate the version line from package.json.
  • Add a crawlable "Supported models" page (HTML table: model, task, backends, added-in version, link to benchmark) and link it from the landing page.
  • Update the landing page to list current capabilities and headline models explicitly (not just families), with a visible "Latest: v0.11 — what's new" block.
  • Publish a blog post for every minor release (not only milestones), with descriptive titles, e.g. "React Native ExecuTorch v0.11: depth estimation, inpainting, local RAG with ColBERT". This is what will outrank the v0.8.0 post.
Lenguaje dominante
TypeScript
Estrellas
1.8k
Forks
101
Merge medio
2 d 4 h
PR fusionados (30 d)
58

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de software-mansion/react-native-executorch

Todos los issues de software-mansion/react-native-executorch

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.