lynxjs.org valid

Read This Before Building with Lynx

This guide targets developers who are already familiar with the web front-end stack. It explains Lynx's core principles, how it differs from the web, and how to build cross-platform applications with Lynx.

For agents: Lynx developer guide for building cross-platform apps with web front-end skills; covers core principles, web differences and full Lynx API reference.

lynx frameworkcross-platform appsreactweb front-endapi reference

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:47:54.813Z. Cached copy · Source on lynxjs.org

# Read This Before Building with Lynx

> This guide targets developers who are already familiar with the web front-end stack. It explains Lynx's core principles, how it differs from the web, and how to build cross-platform applications with Lynx.

---

> \[!IMPORTANT] > **Critical information:**
>
> Reference links are provided after certain statements, pointing to the corresponding sections of the official Lynx documentation. Please read them **proactively** for a complete understanding.

---

## 1. Positioning and Capability Boundaries

* **What**: Lynx is a cross-platform rendering engine that treats the web as its semantic baseline. It targets iOS, Android, HarmonyOS, and the web with a single codebase. A unified element abstraction maps to native views or custom web elements on different hosts, avoiding the performance bottlenecks of traditional WebViews. (See [Composing Elements](https://lynxjs.org/guide/ui/elements-components.md))
* **Why**: Mobile users are extremely sensitive to first-screen time and interaction latency. Lynx combines a dual-thread JavaScript runtime, Instant First-Frame Rendering (IFR), and a native rendering pipeline to deliver the React developer experience alongside near-native performance. (See [Instant First-Frame Rendering](https://lynxjs.org/guide/interaction/ifr.md))
* **How**: On the tooling side, use Rspeedy (an Rspack-powered build tool) to generate a Lynx bundle. On the front end, ReactLynx (a React implementation with a Preact core) describes the UI and communicates with the host through Native Modules or Custom Elements. (See [ReactLynx](https://lynxjs.org/react/introduction.md), [Native Modules](https://lynxjs.org/guide/use-native-modules.md))

## 2. Mental Model: Align Lynx with the Web

| Web Mental Model             | Lynx Counterpart                                                                | Key Differences                                                                                                                                                                                                               |
| ---------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `index.html` + assets        | Lynx bundle (binary that contains JS bytecode + styles) or a `template.js` file | Bundles must be compatible with the Lynx engine version; configure `engineVersion` (previously `targetSdkVersion`). (See [Compatibility](https://lynxjs.org/guide/compatibility.md))                                                            |
| DOM + CSSOM                  | Element tree + styling system                                                   | Every element behaves like a block-level node. Custom tags such as `view`/`text` map to na
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=lynxjs.org · GET /v1/domain/lynxjs.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for lynxjs.org:
1. POST https://agentwebmap.com/v1/sites/lynxjs.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://lynxjs.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/lynxjs.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/lynxjs.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.