<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Elad Ash on Medium]]></title>
        <description><![CDATA[Stories by Elad Ash on Medium]]></description>
        <link>https://medium.com/@ashelad?source=rss-b2d982b485b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*myS36LUnd43nvDQ8</url>
            <title>Stories by Elad Ash on Medium</title>
            <link>https://medium.com/@ashelad?source=rss-b2d982b485b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:49:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashelad/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[VP R&D tech decision — when to use flutter /  PWA / native?]]></title>
            <link>https://medium.com/@ashelad/vp-r-d-tech-decision-when-to-use-flutter-pwa-native-3a5d4afe69cd?source=rss-b2d982b485b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a5d4afe69cd</guid>
            <category><![CDATA[here-mobility]]></category>
            <category><![CDATA[mobility-as-a-service]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[crossplatform-mobile-app]]></category>
            <dc:creator><![CDATA[Elad Ash]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 15:32:54 GMT</pubDate>
            <atom:updated>2020-05-10T15:02:48.149Z</atom:updated>
            <content:encoded><![CDATA[<h3>VP R&amp;D tech decision — when to use flutter / PWA / native?</h3><p>As VP R&amp;D, we are required to make technical decisions under low certainty. Our ability to dig deep into the technical portions is limited, which makes decisions such as “right technology to support different platforms” very challenging. We must take many aspects into account such as time-to-market, long-term cost (scale, maintenance, reuse…), available developers, dev experience etc...</p><p>In this post, I would like provide points to ease at least some of the aspects in selecting the right mobile technology when considering cross platform needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHDvtkfLBk0Y9p8qAir7vg.jpeg" /><figcaption>what mobile technology to use for cross platform apps?</figcaption></figure><h3><strong>Our challenge at Here Mobility: TLDR</strong></h3><p>At <a href="https://mobility.here.com/">Here Mobility</a> we are building mobility as a Service (MaaS) solutions that serve all levels of partners and support all types of transportation. <br>In many cases this also requires building applications that support mobile and web as well as desktop experience. Our solutions also have extensive use of locations and maps technology and a high performance backend infrastructure that supports optimisation, machine learning and matching logic.</p><p>Our global partners rely on us to provide sustainable high performance solutions that can scale to millions of rides per day. We operate in a highly competitive environment where time-to-market is crucial and requires us to provide production grade solutions with high quality at lightning speed.</p><p>Luckily I have a great engineering org, that has already build several native, flutter apps and experimented with PWA solutions.</p><h3>With great power comes great responsibility</h3><p>Even with great engineers, there is always a risk of wasting time on double or even triple effort (like in the case of Native apps and Web) or rewriting a solution as we chose the wrong technology. So with that in mind I’ve embraced the challenge of getting to know some of the different options.</p><h4>COVID-19 and Passover to the rescue.</h4><p>One of the benefits of the COVID-19 combined with Passover holiday was that for the first in a long time, I had some spare time to dig deeper, hands-on, into two of the new cross platform technologies: Flutter and Progressive Web Apps (PWA). <br>By building some stuff myself I’m able to make technical decision with more confidence and answer the question:</p><blockquote><strong>“What technology provide most value for cost?”</strong></blockquote><p><strong><em>Note</em></strong><em> — Cost in this context of the question refers also to the long term cost such as maintenance, reusability, scale and stability, and not only to the immediate cost of building a basic POC.</em></p><p>I had a great time returning to the core of my technical passion and simply code till I get the “Eureka” moment when everything starts working. (I am originally a Backend, Firmware and Alg developer, so be patient with my Front-end solutions as they are far from being complex and innovative). See the sample apps I used at the end of this post.</p><p>I assume that you already have some basic understanding with mobile technologies, cross-platforms development history and have already led building or even better built your own mobile application. if you are less familiar with this, here are some fun reading stuff I found on the web:</p><ul><li><a href="https://www.merixstudio.com/blog/cross-platform-mobile-development/">Cross-platform mobile development 2020: trends and frameworks</a></li><li><a href="https://blog.bitsrc.io/what-is-a-pwa-and-why-should-you-care-388afb6c0bad">What is a PWA and why should you care?</a></li><li><a href="https://www.freecodecamp.org/news/what-is-flutter-and-why-you-should-learn-it-in-2020/">What is Flutter and Why You Should Learn it in 2020</a></li><li><a href="https://dinarys.com/blog/flutter-vs-pwa-what-is-the-future-of-cross-platform-mobile-app-development">Flutter vs PWA: What to Choose for Cross-platform Mobile development in 2020?</a></li><li><a href="https://blog.codemagic.io/why-android-developers-should-pay-attention-to-flutter-in-2020/">Why Android Developers should pay attention to Flutter in 2020 - Codemagic blog custom</a></li><li><a href="https://icapps.com/blog/progressive-web-apps">Progressive web apps: how - and why - to build a website on steroids.</a></li></ul><h3>So what did I learn</h3><p>Well, other than the fun I had with creating these starting apps, I also wanted to gain a bit more understanding on the technology behind it, such that will support better tech decision of what technology to use, when and for what?</p><p>Both technologies are mature enough and have large community, sample code and apps. This simplifies the build of almost any basic applications you’ll need. Also, both support the SDLC flows, CI/CD and testing best practices.</p><p>Though my tech background is not with Front-end solutions, it was easy to build something, that could look reasonable.</p><blockquote><strong><em>Important note</em></strong><em> — Building two basic solutions is by no mean a way to evaluate technology, and needless to say that reaching the following conclusions took much more reading and consulting with people that have much more hands-on experience than myself.</em></blockquote><p><strong>flutter:</strong> provides a more mobile like experience for users, it has introduced web support as well (in Beta mode, see link below) and with its massively growing community it is my bet for cross-platform solution. One of the only drawback I found to flutter is that as it uses <a href="https://dart.dev/">dart</a> language which may have a longer ramp-up time than JavaScript and finding experienced devs for that language is more rare (though I strongly believe it will change quickly).</p><p><a href="https://flutter.dev/web">Web support for Flutter</a></p><p><strong>PWA: </strong>a PWA is basically “web app on steroids”. The steroids part is mainly (but not only) its ability to work offline and provide app like interaction. The fact it is a web technology enables re-use of any of your existing web components, and if you have created a responsive web app, it should literally take you few minutes to create a PWA cross-platform application. One additional important benefit of PWA concepts is that it is being indexed for SEO and marketing campaigns which may also reduce marketing costs. PWA lacks the basic app-like experience and has bigger gap vs. native solutions (especially with iOS).</p><h4>Any decisions on what to use needs to be dependent on many factors, some are:</h4><ol><li>How many developers you have in the org for Mobile / Web, and how experienced are they with each technology?</li><li>What is the level of production you’re trying to achieve: POC, limited MVP, or Full production grade?</li><li>What platforms should this product support — mobile only or also web-apps and desktop?</li><li>What are the key features your application require, and are they supported on flutter and PWA.</li></ol><h3>My recommendation:</h3><h4>Use Flutter</h4><p>As much as possible, Flutter is my bet for the future cross platform technology, be it a basic MVP or full blown production solution.</p><p>Even in cases when flutter lacks some of the technologies which are required for your application, I’d still recommend to start with it and take out the complex functionality from the MVP.</p><h4>Use PWA</h4><p>When most of your developers are Web developers and you are building an initial POC that needs to support web as well.</p><p>I’d also suggest that if you don’t have previous experience with mobile apps, and especially in the early stages of a product, you should start with PWA, one of the reasons is that embedding PWA in flutter / native solution is easy, while the other way around is not. This will mean that if I’m wrong with this advise, you will still be able to quickly move to flutter / native — so I just reduced the risk for you :-)</p><h4>Use Pure Native</h4><p>With the leap the cross platforms have gained over the last couple of years, you owe it to yourself to check cross-platform option first. Our experience with flutter and PWA proved that this could save substantial duplicated effort. Most basic functionality is supported and the ones that are not, will soon be available.</p><p>Even if your application functionality or UX require you to use Pure-native, try building a hybrid solution with a native backbone under a cross platform. This will enable you to enjoy all the worlds and as the cross platform closes the tech gaps, the migration will be much simpler. See the following link for example of integrating flutter to existing native app</p><p>Regardless of your companies selected technology, I highly recommend any mobile developer to enrich his skill set with at least one cross-platform technology.</p><p><a href="https://flutter.dev/docs/development/add-to-app">Add Flutter to existing app</a></p><h4>As for existing solutions and migration from native apps:</h4><p>This is a more complex question, that should be answered ad-hoc per each option, yet, as a rule of thumb, I’d perform the migration to Flutter as much as possible. This will enable better reusability and maintenance, and unless the app is in maintenance mode, you should definitely invest the time in it.</p><h3>Some final words:</h3><p>As I stated earlier Flutter and PWA are just a portion of the cross-platforms solutions out there, in case you’d prefer other cross-platform solutions such as react-native, go ahead.</p><h3>Do or do not, there is no try — Let’s code!</h3><p>As promised, some guidelines and references to building sample apps and trying the technology.</p><p>My weapons of choice were:</p><ul><li>MacBook,</li><li>VSCode as IDE,</li><li>Node (npm) for running http-server,</li><li>xCode Version 11.3.1 (11C505) for configuration of flutter for iOS with iPhone 6 simulator</li></ul><p>I’m aware that PWA and Flutter are only a portion of the cross-platform technologies, yet I’ve decided to check those two as we had some experience with them and have already built a few applications using it.</p><p>I started by strolling around the internets to find simple quick starts for both technologies. Ones I can handle and that will provide good understanding of the concepts. The amount of information about these two was overwhelming, and after a few hours of reading and some trial and error, I managed to find two nice sample apps described below.</p><h4>Flutter login page tutorial</h4><p>nice and simple video series by Coding with Andrea that guides you from scratch to build a login based flutter app that uses Firebase for authentication.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fu_Lyx8KJWpg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Du_Lyx8KJWpg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fu_Lyx8KJWpg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/73bdf504eac3a1e5043589b82161e968/href">https://medium.com/media/73bdf504eac3a1e5043589b82161e968/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*kpK6aRj_m_ujfjcx3h2Nbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*q2ex2CdOkxzIAL8nAv6vtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*meqit-5H-qmCSb3Nuhzgmg.png" /><figcaption>Installed login on simulator with login and create account flow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*edcKu4E-C-bc0hwmI5LTSg.png" /><figcaption>showing connection and authentication via Firebase</figcaption></figure><p>And a bonus that comes with Flutter Beta web support, it can also run as PWA</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JBfdRKCn3FmjO8nOJuvk8g.png" /><figcaption>Flutter log in run as web app on Chrome</figcaption></figure><h4>PWA in 20 minutes :</h4><p><a href="https://javaninja.io/build-your-first-pwa-in-20-minutes/">Build Your First PWA in 20 minutes! - Progressive Web App - JavaNinja</a></p><p>good sample code by JavaNinja (<a href="https://ajeet.io/">AJEET SINGH</a>) to build a simple PWA app. To be honest, it took me a bit longer then 20 min, but it is probably my own fault as I was also searching to optimise the static launch screen and the app icon (see <a href="https://www.netguru.com/codestories/few-tips-that-will-make-your-pwa-on-ios-feel-like-native">this link</a> to learn how to do it)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fbje85AdBOgs%3Fstart%3D153%26feature%3Doembed%26start%3D153&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dbje85AdBOgs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fbje85AdBOgs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/515a58d9573e85ca5fce3dbbf81d5942/href">https://medium.com/media/515a58d9573e85ca5fce3dbbf81d5942/href</a></iframe><h3>Thanks:</h3><p>To my dear engineering org, for pushing and delivering no-matter-what. keeping open mind and learning (as well as teaching) new things.</p><p>Also, special thanks to Anat Koren, Roman Baron, Nir Oren, Itzhak Gueta, Lior Ben-Arie and Koby Berkovich for their review and valuable feedbacks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a5d4afe69cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>