<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/3HYJCKr3V" -->

---
title: NativePHP v4: Build Native iOS and Android UI in Blade
description: NativePHP v4 introduces SuperNative, a rendering mode that compiles Blade components directly into real SwiftUI views on iOS and Jetpack Compose views on...
canonical: https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: NativePHP v4: Build Native iOS and Android UI in Blade | daily.dev
og:description: NativePHP v4 introduces SuperNative, a rendering mode that compiles Blade components directly into real SwiftUI views on iOS and Jetpack Compose views on...
og:url: https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v
og:image: https://api.daily.dev/og/posts/3HYJCKr3V.png
og:image:alt: NativePHP v4: Build Native iOS and Android UI in Blade
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# NativePHP v4: Build Native iOS and Android UI in Blade

**[Laravel News](https://daily.dev/sources/ln)** · 8 min read · 22 upvotes · 4 comments

## Summary

NativePHP v4 introduces SuperNative, a rendering mode that compiles Blade components directly into real SwiftUI views on iOS and Jetpack Compose views on Android, with no web view or HTML involved. Screens are now PHP classes extending NativeComponent paired with Blade templates using native elements styled by Tailwind classes. PHP and native code share memory directly, eliminating bridge round-trips, and accessibility features like VoiceOver and TalkBack work natively. Web views remain supported as an embeddable component for screens not yet converted. A new Pest testing suite lets developers test native screens without a device using a FakeBridge. The only breaking change in v4 is that four plugins (Device, Dialog, File, System) are now folded into core, requiring their standalone packages to be uninstalled before upgrading. Version 4.1, released August 7, added the #[Locked] attribute, TreeObservers for debugging, and Tailwind class validation warnings.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://laravel-news.com/nativephp-v4-supernative>

## Questions this post answers

### What is the breaking change when upgrading from NativePHP v3 to v4?

The four plugins Device, Dialog, File, and System are folded into core as part of the nativephp/mobile package, and it declares Composer conflicts with the old standalone plugin packages. Composer will not resolve dependencies until those four packages are removed using 'php artisan native:plugin:uninstall --core-v4', after which you bump the version constraint to ~4.0.0 and run 'native:install --force'.

_Anyone planning a NativePHP v3 to v4 migration can track breaking changes like this one on daily.dev._

### Does NativePHP v4's SuperNative rendering use a web view or HTML at all?

No, SuperNative renders Blade components as real SwiftUI views on iOS and Jetpack Compose views on Android with no web view or HTML involved. A custom Blade engine converts components into a fixed-length binary representation instead of HTML, and a native-side interpreter reads that representation to build the actual platform views, sharing memory directly with PHP without a network hop.

_Developers weighing native UI frameworks against web-view-based mobile tooling can follow deep dives like this on daily.dev._

### Can I keep using web views in an existing NativePHP v3 app after upgrading to v4?

Yes, web views still work in v4 and are not required to be replaced; a web view becomes a component, such as <webview php url="/" fullscreen />, placed inside a native screen rather than being the whole app. This lets a team convert screens one at a time, mixing native navigation with unconverted web-view screens, while each embedded web view gets its own dedicated PHP runtime.

_Teams incrementally adopting native mobile UI can weigh migration trade-offs like this using daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@rgodiyal** · 2 upvotes

> ![GIF](https://static.klipy.com/ii/4e7bea9f7a3371424e6c16ebc93252fe/2b/c5/92NRju5IsMQLy5aaCN9.gif)

**@legacy8** · 2 upvotes

> PHP on steriods here BTW!

## Similar posts on daily.dev

- [NativePHP For Desktop](https://daily.dev/posts/nativephp-for-desktop-byi2zo65r) · Larablog · 19 upvotes · 0 comments

---

Tags: [#mobile](https://daily.dev/tags/mobile), [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel)

[View this post on daily.dev](https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"NativePHP v4: Build Native iOS and Android UI in Blade","url":"https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v"},"datePublished":"2026-08-17T13:57:40.206Z","dateModified":"2026-09-13T21:59:04.192Z","description":"NativePHP v4 introduces SuperNative, a rendering mode that compiles Blade components directly into real SwiftUI views on iOS and Jetpack Compose views on...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/43c17ee625a6550d9264fc30795923e2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/43c17ee625a6550d9264fc30795923e2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Laravel News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Laravel News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ln","url":"https://daily.dev/sources/ln"},"commentCount":4,"discussionUrl":"https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":22},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":4}],"keywords":"mobile,php,laravel","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Laravel News","item":"https://daily.dev/sources/ln"},{"@type":"ListItem","position":3,"name":"NativePHP v4: Build Native iOS and Android UI in Blade"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v","comment":[{"@type":"Comment","text":"","datePublished":"2026-08-18T04:59:12.761Z","url":"https://daily.dev/posts/3HYJCKr3V#c-hfdRLP4fr","author":{"@type":"Person","name":"Rahul Godiyal","url":"https://daily.dev/rgodiyal","image":"https://lh3.googleusercontent.com/a/ACg8ocJUbWuKor0twjzGVmI3sXXFcW_cr9pu-M4_NN4eu3TOF-7Cf9o=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"PHP on steriods here BTW!","datePublished":"2026-08-18T23:34:11.728Z","url":"https://daily.dev/posts/3HYJCKr3V#c-l2LO94Thr","author":{"@type":"Person","name":"Legacy","url":"https://daily.dev/legacy8","image":"https://avatars.githubusercontent.com/u/52163001?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/nativephp-v4-build-native-ios-and-android-ui-in-blade-3hyjckr3v#faq","mainEntity":[{"@type":"Question","name":"What is the breaking change when upgrading from NativePHP v3 to v4?","acceptedAnswer":{"@type":"Answer","text":"The four plugins Device, Dialog, File, and System are folded into core as part of the nativephp/mobile package, and it declares Composer conflicts with the old standalone plugin packages. Composer will not resolve dependencies until those four packages are removed using 'php artisan native:plugin:uninstall --core-v4', after which you bump the version constraint to ~4.0.0 and run 'native:install --force'. Anyone planning a NativePHP v3 to v4 migration can track breaking changes like this one on daily.dev."}},{"@type":"Question","name":"Does NativePHP v4's SuperNative rendering use a web view or HTML at all?","acceptedAnswer":{"@type":"Answer","text":"No, SuperNative renders Blade components as real SwiftUI views on iOS and Jetpack Compose views on Android with no web view or HTML involved. A custom Blade engine converts components into a fixed-length binary representation instead of HTML, and a native-side interpreter reads that representation to build the actual platform views, sharing memory directly with PHP without a network hop. Developers weighing native UI frameworks against web-view-based mobile tooling can follow deep dives like this on daily.dev."}},{"@type":"Question","name":"Can I keep using web views in an existing NativePHP v3 app after upgrading to v4?","acceptedAnswer":{"@type":"Answer","text":"Yes, web views still work in v4 and are not required to be replaced; a web view becomes a component, such as \u003cwebview php url=\"/\" fullscreen /\u003e, placed inside a native screen rather than being the whole app. This lets a team convert screens one at a time, mixing native navigation with unconverted web-view screens, while each embedded web view gets its own dedicated PHP runtime. Teams incrementally adopting native mobile UI can weigh migration trade-offs like this using daily.dev."}}]}
```

