4 ms·

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

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/NativePageTransitions https://github.com/Telerik-Verified-Plugins/NativePageTransi...) but it's abandoned.

samwillis 5y ago
Same here, it’s something I wish Capacitor supported. Last year I experimented with using NativeScript in a Capacior app to open native modals with a second webview. Since then Ionic have released “Capacitor Portals” which brings all the native apis available within the Capacitor webview to native apps, effectively allowing you to embed capacitor views in another app. I wander if there is the potential to combine the two to get the native view transitions. Edit: Just to elaborate a little further on my experiment. Effectively what you ended up with was the two webviews being able to communicate with each other as though you had used the window.open or frames JavaScript api in the browser.
danielvaughn 5y ago
Wow that’s a really good idea. I love it.
ohgodplsno 5y ago
Because the UX of having a non-native app is, and will always be dogshit.
joemasilotti 5y ago
I use Turbo Native on iOS to do exactly this. You render your mobile web view like normal, wire up a JavaScript handler (formerly known as Turbolinks), and push native screens on iOS. It works really well for CRUD and "boring" SAAS apps with little interaction outside of forms. And when you need higher fidelity dropping down to SwiftUI or UIKit is straightforward. https://github.com/hotwired/turbo-ios https://github.com/hotwired/turbo-ios To make things even simpler, I built Jumpstart iOS, which takes care of all of the Swift boilerplate. Navigation, authentication, and push notifications all work out of the box after adding a few endpoints to your server. https://jumpstartrails.com/ios https://jumpstartrails.com/ios
mamcx 5y ago
Because, specialy on android, is far slower…

samwillis 5y ago

Same here, it’s something I wish Capacitor supported. Last year I experimented with using NativeScript in a Capacior app to open native modals with a second webview. Since then Ionic have released “Capacitor Portals” which brings all the native apis available within the Capacitor webview to native apps, effectively allowing you to embed capacitor views in another app. I wander if there is the potential to combine the two to get the native view transitions. Edit: Just to elaborate a little further on my experiment. Effectively what you ended up with was the two webviews being able to communicate with each other as though you had used the window.open or frames JavaScript api in the browser.

danielvaughn 5y ago

Wow that’s a really good idea. I love it.

ohgodplsno 5y ago

Because the UX of having a non-native app is, and will always be dogshit.

joemasilotti 5y ago

I use Turbo Native on iOS to do exactly this. You render your mobile web view like normal, wire up a JavaScript handler (formerly known as Turbolinks), and push native screens on iOS. It works really well for CRUD and "boring" SAAS apps with little interaction outside of forms. And when you need higher fidelity dropping down to SwiftUI or UIKit is straightforward. https://github.com/hotwired/turbo-ios https://github.com/hotwired/turbo-ios To make things even simpler, I built Jumpstart iOS, which takes care of all of the Swift boilerplate. Navigation, authentication, and push notifications all work out of the box after adding a few endpoints to your server. https://jumpstartrails.com/ios https://jumpstartrails.com/ios

mamcx 5y ago

Because, specialy on android, is far slower…