From 7c86ed52c8bfa8834dcf1cd0f6aee2019e411c83 Mon Sep 17 00:00:00 2001 From: Shane Rosenthal Date: Thu, 3 Sep 2026 15:55:58 -0400 Subject: [PATCH] Mobile v4 docs: drop the beta caveat from the SuperNative overview v4 is a stable release, not a beta. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_0112bxu7tWLuSwy1NLdV3xwA --- .../docs/mobile/4/architecture/about-the-new-architecture.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/resources/views/docs/mobile/4/architecture/about-the-new-architecture.md b/resources/views/docs/mobile/4/architecture/about-the-new-architecture.md index b0e9a1dd9..46e2df64a 100644 --- a/resources/views/docs/mobile/4/architecture/about-the-new-architecture.md +++ b/resources/views/docs/mobile/4/architecture/about-the-new-architecture.md @@ -67,8 +67,7 @@ app faster. If your app is happy in the web view, it will keep working exactly a ## Should you use it today? -SuperNative is **the default**. New apps render native screens from the very first route. It's in beta, so expect -rapid iteration. If you'd rather wait, -[opting out](../architecture/super-native#is-the-web-view-still-an-option) is one route and one component. +SuperNative is **the default**. New apps render native screens from the very first route. If you'd rather keep the +web view, [opting out](../architecture/super-native#is-the-web-view-still-an-option) is one route and one component. Ready to go deeper? Start with [The Renderer](renderer).