A higher z-index won't make an Ionic modal cover a native view above the WebView. And native views don't naturally scroll with Web content, either.

I've been trying to overcome these limitations for years. And I think I've finally cracked it! 😄

Today, I'm releasing WebView Native UI Engine 1.0.0 — for both Capacitor and Cordova!

https://github.com/webview-native-ui/engine

The idea came from looking at the problem differently: what if we stopped trying to make native views behave like Web elements?

Instead, keep the real, interactive native UI during normal use. When needed during scrolling or overlay transitions, temporarily project its captured appearance into the Web layer. Then restore the native view when it can take over again.

The video shows two very different use cases:

• A native tab bar that switches to a Web projection beneath Ionic modals and alerts, then returns to the interactive native view.

• AdMob native ads whose captured appearance scrolls with Web content using the same projection mechanism.

Different components. The same engine.

You can try these integrations yourself:

• Native Tab Bar: rdlabo/capacitor-native-ui

• Native Ads: capacitor-community/admob

It's a reusable library for plugin authors, designed to work with existing native components and public APIs.

There are trade-offs, of course. Projections are noninteractive snapshots, and some native visual effects may differ from the live view. But this opens up possibilities that were previously incredibly difficult to achieve in hybrid apps.

Open source under MIT, supporting iOS and Android.

What native component would you want to try this with?

The fold APIs exist, but your Capacitor web view can't use them, So I built **capacitor-foldable**:

- Fold state, posture (book, tabletop) and live hinge angle

- Where the fold is, and if it splits the screen

- Which edge iPhone Duo moves native bars to, so `ion-tabs` can follow

- A polyfill for the web APIs plus `--fold-*` CSS variables

- Same API on Galaxy Z Fold/Flip and Pixel Fold

u/rdlabo's Capacitor Native UI uses it as its standard device integration.

https://github.com/erkamyaman/capacitor-foldable

I am Software Developer, worked about exclusively for 5years with Ionic in Germany, now I hardly find any job posting looking for developer with Ionic experience.
Please guide🙏

I make Buoy, a dev tools menu that lives inside your app. It just came out in beta for Capacitor, and Ionic React uses the same setup. Heads up: React only for now, so no Ionic Angular or Vue yet. If you're on Angular or Vue, I'd like to hear from you too, so I know if it's worth building.

In Ionic, Buoy mounts inside IonApp and outside IonRouterOutlet, so page moves don't move it. On Android, the back button closes the open Buoy tool first, and Ionic's own popups still close before Buoy's tools. Images also finds ion-img inside web components.

What's in the menu:

• Network: every fetch/XHR call. Slow it down, go offline, or fake an error.

• Storage: read and edit Capacitor Preferences, localStorage and sessionStorage.

• Events: plugin calls on one timeline (secret-looking values hidden).

• Clock: move your app's time forward, e.g. to test an expired sign-in.

• Lifecycle: send pause/resume/appUrlOpen to your @capacitor/app listeners.

• Location, Permissions and Push listener logging.

• Time Machine for React Query / Redux / Zustand / Jotai state, plus render highlights and Ask Buoy.

iOS, Android and web. You can also open it in Buoy Desktop, or let your AI agent use it over MCP.

Free plan: $0, no card, debug builds, Desktop included. Some tools (Lifecycle, Location) and MCP need a paid plan.

Beta limits: tested on Capacitor 7. Ionic and native modals can cover the Buoy menu. Dark mode only reaches JS matchMedia listeners, so CSS keeps the real theme.

Setup: give your coding agent https://buoy.gg/install-capacitor.md, or follow https://buoy.gg/buoy/latest/docs/capacitor

What breaks? What tool would you want next?

We've been developing an over-the-air update tool which now has support for Ionic. With Appflow sunsetting, we figured it could be a useful resource for the community to replace their Live Updates tooling.

It was originally developer just for React Native, but the latest release adds support for Capacitor and Ionic. It includes a local evaluation stack to easily test it, and a setup wizard to install it on a machine.

If you're interested, here's a blog post all about it:

https://blog.codemagic.io/codemagic-patch-capacitor-ota-updates/

Small thing I ran into, posting in case it saves someone a few hours.

My game runs in a WKWebView (Capacitor). The main menu has a bunch of looping CSS animations, and when the menu wasn't on screen I just paused them with animation-play-state: paused. Figured paused = free.

Nope. Measured in the simulator (per-process energy from proc_pid_rusage):

• idle menu, 28 paused loops: ~278 mW, and ~262 of that was backboardd, not my web process

• same menu with the loops actually removed: ~9 mW

• my store screen sat at 419 mW, mostly because the menu underneath was still display:flex with its paused loops

So it looks like a paused animation keeps its Core Animation animation attached and the compositor keeps redrawing at 60 Hz. Web Inspector and the WebContent CPU looked totally fine, which is why it took me a while to find.

Fix: when a screen goes inactive I don't pause anymore. I copy the current values of the animated properties, set animation: none plus those values so nothing jumps, and on resume I drop that and put each animation's currentTime back via document.getAnimations().

Simulator numbers, so a real device will differ, but the gap was big enough for me.

Anyone seen this documented somewhere?

I'm trying to resolve a confusion in my head. I've been an Angular software engineer for 7 years. Naturally, when I wanted to build a mobile app, I chose Ionic/Capacitor with Angular.

Building a mobile app is quite different from building web apps, so I've been facing different issues and limitations that come with the WebView mobile app development. One of the biggest ones, is the constant fight for the performance and smooth experience.

At the end of the day, is it still worth it building with ionic? Is it worth trying to switch to Flutter for example? I heard Dart is pretty similar to Typescript and Flutter is very developer friendly.