NativePageTransi VS capacitor

I've been wondering why webviews with native page transitions aren't a more commonly used thing. It improves the UX a lot by dealing with the abrupt navigation changes of regular web apps. There was a plugin for Cordova that did this (https://github.com/Telerik-Verified-Plugins/NativePageTransi...) but it's abandoned.

It should also be mentioned that the official VSCode Ionic Plugin is also capable of migrating your existing application. Capacitor v6 now also supports bun as a package manager.

> PWA optionally bundled with some native components for filing the gaps, as in Tauri.

Isn't that essentially Capacitor?

https://capacitorjs.com

Have you experienced slow scrolling issues?

https://github.com/ionic-team/capacitor/issues/4187

Project: Build This Webpage (just this one page, make sure it is responsive (useful on all screen sizes)) => https://capacitorjs.com/

Capacitor

For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.

The traditional alternative to Electon on mobile platforms is Capacitor (which uses the system webview):

https://capacitorjs.com/

(fka Apache Cordova, fka PhoneGap)

Ionic Framework UI Components are used to build a website and then a mobile application is built using Ionic Capacitor. Ionic UI components are not required but are used for UX. The vue js code presented here will work fine in a separate application.

Welcome to Part Two of this four-part series on building a mobile game using open source technologies. We'll be using Phaser, along with Ionic, Capacitor, and Vue.