Weave Code
Ux Native Laravel Package
symfony/ux-native
Symfony UX Native lets you build native iOS and Android apps using Symfony, Twig, and Turbo, wrapping your server-rendered web UI in native shells. Reuse existing Symfony skills and components to deliver mobile experiences without a separate frontend stack.
Hotwire Native integration for Symfony
Frequently asked questions about Ux Native
- Is symfony/ux-native a Laravel package?
- No. symfony/ux-native is a Symfony UX package that integrates Hotwire Native with Symfony and is built around FrameworkBundle conventions such as a bundle class, a DI extension, Twig extensions, and config/packages YAML files. Laravel has none of that scaffolding, so it should not be treated as an install-and-go Laravel dependency. Laravel does consume individual Symfony components, but Symfony UX packages assume the full-stack Symfony kernel.
- Can I install symfony/ux-native in a Laravel application with Composer?
- Realistically no, or at least not cleanly. A composer require into a Laravel app will likely fail on constraint resolution or land code you cannot wire up without Symfony's bundle and container conventions. The TPM assessment rates it low as a dependency for a Laravel estate, and the recommended path is to port the pattern rather than the package.
- What does Symfony UX Native actually do?
- It wraps an existing server-rendered Symfony app in native iOS and Android shells using Hotwire Native and Turbo, so you can ship a native presence without a separate mobile codebase. Its likely surface area includes user-agent detection for the native webview, a path-configuration endpoint describing which URLs stay in-app versus open in the system browser, and helpers for Turbo bridge components. The point is to avoid hand-rolling that glue yourself.
- Does Symfony UX Native support both iOS and Android path configuration?
- The evaluation flags this as an open question rather than a confirmed capability, so verify it in src before relying on it. The package description covers native iOS and Android broadly, but per-platform coverage of path configuration is not stated in the overview. Treat Android parity as something to confirm in the code and in the Hotwire Native SDK docs.
- Is there a Laravel alternative to symfony/ux-native for Hotwire Native?
- Yes, evaluate Turbo Laravel and its Hotwire Native support before considering a port. The TPM assessment explicitly calls it out as the maintained Laravel-ecosystem equivalent to check first. Given the framework mismatch here, that is the lower-risk path for a Laravel estate.
- Is symfony/ux-native maintained and production-ready?
- Treat it as reference source rather than a dependency. The evaluation cites 12 stars, a score around 19.8, and effectively single-maintainer status, with no community to absorb questions or upstream fixes. The stated last release date of 2026-10-13 is a future date and must be verified on Packagist and in the repo tags before anyone plans around it.
- What is the real cost of adopting Hotwire Native in a Laravel app?
- The glue code is small; the prerequisite work is not. The real cost is making the web app Turbo-correct: no full-page reload expectations, correct data-turbo attributes, fragment and history handling, and auth and session behavior inside a webview. That work is framework-agnostic and dwarfs the package code, which is why the evaluation rates prerequisite risk high and under-weighted.
- Does symfony/ux-native handle iOS and Android builds, signing, and app store submission?
- No. Nothing in the package provides iOS or Android builds, code signing, TestFlight or Play Console workflows, or store review. Those are separate disciplines the PHP team would need to own. The evaluation rates mobile delivery risk high for exactly this reason.
- What PHP, Symfony, and Turbo version constraints does symfony/ux-native require, and does it need AssetMapper?
- The overview does not state version constraints or AssetMapper requirements, so confirm them on Packagist and in composer.json before planning anything. Symfony UX packages commonly ship Stimulus controllers through AssetMapper and importmap, but that is an assumption to verify rather than a documented fact here. The TPM assessment lists version constraints and AssetMapper as key open questions.
- How would a Laravel team replicate symfony/ux-native's functionality?
- Build a thin internal Laravel package rather than installing the Symfony one. The four pieces to reproduce are middleware that detects the Hotwire Native user agent and sets a request attribute, a path-configuration controller returning the JSON rules, a Blade directive or helper emitting native bridge attributes, and a small Turbo-correctness layer. A spike reading src/ to confirm that scope is estimated at one to two days and should gate everything else.
Weaver
How can I help you explore Laravel packages today?