<story><title>All you should know about Flutter development</title><url>https://github.com/nepaul/awesome-flutter</url></story><parent_chain><item><author>udbhavs</author><text>I&amp;#x27;ve been wondering why webviews with native page transitions aren&amp;#x27;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 (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Telerik-Verified-Plugins&amp;#x2F;NativePageTransitions&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Telerik-Verified-Plugins&amp;#x2F;NativePageTransi...&lt;/a&gt;) but it&amp;#x27;s abandoned.</text></item><item><author>samwillis</author><text>I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app&amp;#x2F;market but also the skills and experience within your team. No 1 priority is move quickly.&lt;p&gt;Flutter is brilliant, and probably the way to go, for some apps. A great example  of a successful Flutter app is the Sonos app, relatively simple and responsive ui talking to an api. No “rich” or user supplied content. Although they haven’t replaced their desktop app with the flutter app, my guess is that it is the plan.&lt;p&gt;I think Flutter is brilliant for that type of IOT app, banking&amp;#x2F;crypto&amp;#x2F;utilities also the sort that would work well. I don’t think it’s best placed if you want to start using WebViews for some content, when I was last looking at it a year ago there were serious problems.&lt;p&gt;If you are building a social media app, either Native or React Native (or a combination) is probably the best way to go. You are aiming high so need the best performance and ux.&lt;p&gt;If you are building a b2b SAAS app I would probably reach for something like Ionic&amp;#x2F;Capacitor. You can share almost all you codebase with your web&amp;#x2F;PWA&amp;#x2F;desktop (electron) apps and can achieve it all with a tiny team. If you need a little more native functionality then adding in NativeScript to a Capacitor works very well.&lt;p&gt;For an e-commerce app I would probably go Iconic&amp;#x2F;Capacitor too, the Amazon app for example is mostly webviews.&lt;p&gt;Productivity apps are much more difficult to recommend for as you probably need large native components.</text></item></parent_chain><comment><author>joemasilotti</author><text>I use Turbo Native on iOS to do exactly this.&lt;p&gt;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 &amp;quot;boring&amp;quot; SAAS apps with little interaction outside of forms. And when you need higher fidelity dropping down to SwiftUI or UIKit is straightforward.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;hotwired&amp;#x2F;turbo-ios&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;hotwired&amp;#x2F;turbo-ios&lt;/a&gt;&lt;p&gt;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.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jumpstartrails.com&amp;#x2F;ios&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jumpstartrails.com&amp;#x2F;ios&lt;/a&gt;</text></comment>
<story><title>All you should know about Flutter development</title><url>https://github.com/nepaul/awesome-flutter</url></story><parent_chain><item><author>udbhavs</author><text>I&amp;#x27;ve been wondering why webviews with native page transitions aren&amp;#x27;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 (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Telerik-Verified-Plugins&amp;#x2F;NativePageTransitions&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Telerik-Verified-Plugins&amp;#x2F;NativePageTransi...&lt;/a&gt;) but it&amp;#x27;s abandoned.</text></item><item><author>samwillis</author><text>I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app&amp;#x2F;market but also the skills and experience within your team. No 1 priority is move quickly.&lt;p&gt;Flutter is brilliant, and probably the way to go, for some apps. A great example  of a successful Flutter app is the Sonos app, relatively simple and responsive ui talking to an api. No “rich” or user supplied content. Although they haven’t replaced their desktop app with the flutter app, my guess is that it is the plan.&lt;p&gt;I think Flutter is brilliant for that type of IOT app, banking&amp;#x2F;crypto&amp;#x2F;utilities also the sort that would work well. I don’t think it’s best placed if you want to start using WebViews for some content, when I was last looking at it a year ago there were serious problems.&lt;p&gt;If you are building a social media app, either Native or React Native (or a combination) is probably the best way to go. You are aiming high so need the best performance and ux.&lt;p&gt;If you are building a b2b SAAS app I would probably reach for something like Ionic&amp;#x2F;Capacitor. You can share almost all you codebase with your web&amp;#x2F;PWA&amp;#x2F;desktop (electron) apps and can achieve it all with a tiny team. If you need a little more native functionality then adding in NativeScript to a Capacitor works very well.&lt;p&gt;For an e-commerce app I would probably go Iconic&amp;#x2F;Capacitor too, the Amazon app for example is mostly webviews.&lt;p&gt;Productivity apps are much more difficult to recommend for as you probably need large native components.</text></item></parent_chain><comment><author>danielvaughn</author><text>Wow that’s a really good idea. I love it.</text></comment>