<?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 Olawale Timothy Alabi on Medium]]></title>
        <description><![CDATA[Stories by Olawale Timothy Alabi on Medium]]></description>
        <link>https://medium.com/@olawale_alabi?source=rss-d4a7da98f0b1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*j5bnBZgf5q-QqydG.</url>
            <title>Stories by Olawale Timothy Alabi on Medium</title>
            <link>https://medium.com/@olawale_alabi?source=rss-d4a7da98f0b1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:25:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olawale_alabi/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[Android (Flutter) 64K Methods Dex Limit: How to use Proguard in Development]]></title>
            <link>https://medium.com/@olawale_alabi/android-flutter-64k-methods-dex-limit-how-to-use-proguard-in-development-728af11a4e22?source=rss-d4a7da98f0b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/728af11a4e22</guid>
            <category><![CDATA[flutter-ui]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutterio]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Olawale Timothy Alabi]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 10:19:15 GMT</pubDate>
            <atom:updated>2019-02-14T09:56:48.582Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ugrpdAvdCfVaZ2AE" /><figcaption>Photo by <a href="https://unsplash.com/@westingrandcayman?utm_source=medium&amp;utm_medium=referral">Marc Babin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Disclaimer:</h3><p><strong><em>I wrote about how I started my mobile development few weeks ago, </em></strong><a href="https://medium.com/@olawale_alabi/and-so-the-journey-into-the-world-of-flutter-mobile-development-begins-217f7490f3c5"><strong><em>her</em></strong></a><strong><em>e.</em></strong></p><p><strong><em>So this tells you right off the bat that this is an article written by a rookie.</em></strong></p><p><strong><em>I am by no means an expert on this subject, yet.</em></strong></p><p><strong><em>This was mainly written to serve as a gentle memory bank for my future self.</em></strong></p><p><strong><em>So if there are inconsistencies in my views or errors in my judgement of situations, please be gentle with me and be kind enough to state my mistakes in the comments below.</em></strong></p><p>That out of the way, again, I can not overemphasise how much I am enjoying my journey into the flutter world so far.</p><p>The experience has been awesome, humbling and loaded with so many WOWs along the way.</p><p>The tutorials are top notch and the whole community is awesome.</p><p>Thanks to Google and kudos to the flutter team for making Mobile Development Great Again ™</p><p>However, while following one of such tutorials, and trying things out, I hit a snag.</p><p>Yeah, welcome to software development.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0MYC0LajbaPoEADu%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0MYC0LajbaPoEADu%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl0MYC0LajbaPoEADu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="251" frameborder="0" scrolling="no"><a href="https://medium.com/media/f30903362f2d6286eeb44ddb4f5de1ca/href">https://medium.com/media/f30903362f2d6286eeb44ddb4f5de1ca/href</a></iframe><p>This one though was unexpected.</p><p>It was the dreaded dex limit hit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3e7faH1kaQNDalSmLVUewg.jpeg" /><figcaption>The dreaded dex limit error.</figcaption></figure><p>I never imagined to encounter this error, at least not when I was running a basically empty project with about 5 firebase plugins.</p><p>For a quick background, this error means, my project contains over 64,000 methods. Now you can imagine…</p><p>Anyways, as expected, the community and even the Android team had provided solutions to this.</p><p>With just a line of code, you can add:</p><pre><strong>multiDexEnabled true</strong></pre><p>within the defaultConfig block in the app-level build.gradle file.</p><p>The only gotcha is that this works only on SDK version 21 and above.</p><p>Meaning, if your app is to be viewed on a device running an Android sdk lower than 21, it crashes.</p><p>Needless to say, that is not an option for me.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7btT1T9qpQZWhNlK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o7btT1T9qpQZWhNlK%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3o7btT1T9qpQZWhNlK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="251" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d6db0f0ea120b6225cf77ddcb865a8a/href">https://medium.com/media/2d6db0f0ea120b6225cf77ddcb865a8a/href</a></iframe><p>I want to be able to build apps that solve problems within my community and my environment, and in Nigeria, lets just say majority of smart phone users are on low-end android phones running on really old sdk versions.</p><p>So, what then are my options?</p><p>Well officially, the <a href="https://developer.android.com/studio/build/multidex">docs</a> among other things suggested adding this to gradle file:</p><pre>dependencies {<br>  implementation &#39;com.android.support:multidex:1.0.3&#39;<br>}</pre><p>But for some reasons, none of them worked for me.</p><p>I tried several other suggestions and applied various tips and tricks found on Google groups, stackoverflows, blogs, etc.</p><p>What seemed more strange though is that, this was a brand new installation with nothing but a few newly imported firebase plugins.</p><p>I wondered why the default fix couldn’t fix this issue.</p><p>I was lucky enough to stumble on this issue thread on the framework’s github page, where I met a very wonderful senior dev <a href="https://medium.com/u/91cb19edfc82">Simon Lightfoot</a>.</p><p><a href="https://github.com/flutter/flutter/issues/21009">Flutter Gradle should automatically add MultiDex · Issue #21009 · flutter/flutter</a></p><p>He was kind enough to share screen with me for hours (due to my slow laptop, hahaha), but all the suggestions and implementations simply didnt work for me.</p><p>Admittedly, I made some simple dumb mistakes following all his initial steps, but even after spending hours together, it still didn’t work for me.</p><p>Again, remember, this is a virgin project, loaded with only a handful official plugins from Google.</p><p>I shudder at the thought of what would happen when I started adding some packages from the wild.</p><p>But enough of the rant, <strong>tl;dr</strong>, it worked right?</p><p>That is why you are here, right?</p><p>So for anyone with the same strange scenario, what I did was to use Proguard to dramatically reduce the size of the methods.</p><p>But wait…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1EzbweBp6XRv2%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1EzbweBp6XRv2%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F1EzbweBp6XRv2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="243" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6bb017978b488cfaf03a953291c56f9/href">https://medium.com/media/c6bb017978b488cfaf03a953291c56f9/href</a></iframe><p>Yeah.</p><p>At first when the thought crossed my mind I was not so sure, especially since I am thinking of primarily running the app first in debug/development mode.</p><p>All the mention of Proguard that I knew of, and that was explained <a href="https://flutter.io/docs/deployment/android">here</a> refer to the final release of the App’s APK to the store.</p><p><a href="https://flutter.io/docs/deployment/android">Preparing an Android App for Release</a></p><p>Well, among other things, what Proguard does is to obfuscate and minify your codebase, thereby removing all unused and irrelevant fats.</p><p>That sounds awesome for release products.</p><p>But I need something I can play with, right here and now, in development.</p><p>However, what the doc left out was the fact that you can use almost the same configuration settings while in debug mode.</p><p>And that was the breakthrough I needed.</p><p>So this basically means, instead of just doing this:</p><pre>buildTypes {</pre><pre>        release {</pre><pre>            signingConfig signingConfigs.release<br>            minifyEnabled true<br>            useProguard true</pre><pre>            proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;</pre><pre>        }<br>    }</pre><p>You can also do this:</p><pre>buildTypes {<br>    release {<br>            signingConfig signingConfigs.release<br>            minifyEnabled true<br>            useProguard true<br>    }<br>    debug{<br>        minifyEnabled <em>true<br>        </em>useProguard <em>true<br>        </em>proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;<br>    }<br>}</pre><p>That debug section represents your development environment.</p><p>Now, create proguard-rules.pro as a file inside:</p><pre>/android/app</pre><p>And put in there, these lines of code:</p><pre>#Flutter Wrapper<br>-keep class io.flutter.app.** { *; }<br>-keep class io.flutter.plugin.**  { *; }<br>-keep class io.flutter.util.**  { *; }<br>-keep class io.flutter.view.**  { *; }<br>-keep class io.flutter.**  { *; }<br>-keep class io.flutter.plugins.**  { *; }</pre><p>These will simply tell proguard to ignore these classes. They are the core files that make your app useful.</p><p>Do this and be ready for your mind to be…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYVeu2eB7FzszV3P3N9%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FYVeu2eB7FzszV3P3N9%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FYVeu2eB7FzszV3P3N9%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/b16fd60a7fef301804b71ca904b58dd5/href">https://medium.com/media/b16fd60a7fef301804b71ca904b58dd5/href</a></iframe><p>No more need to <strong>multiDexEnabled true</strong><em> </em>especially when I am running the old sdk emulator and no more head spinning work-arounds.</p><p>It just worked.</p><p>Ok how can I know for sure?</p><p>Well, simply analyze your APK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*9m01QR-7DvDuZYljbJPNvQ.png" /><figcaption>Go to Analyze APK to view method counts of your app</figcaption></figure><p>Using the resultant pop-up menu, simply navigate to your:</p><pre>...yourProjectDiectory\build\app\outputs\apk\app.apk</pre><p>If you click on classes.dex on the list of files shown, you will see a full breakdown of all classes and methods used in your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*hpVqW9lqwyfg3e-eQAYHPA.png" /><figcaption>A breakdown of method counts</figcaption></figure><p>As you can see, now all used methods were pruned to 23,634 compared to when it was 71,227!</p><p>And just like that, all is well with the world again.</p><p>And oh, if you are wondering about the difference between the defined methods and reference methods, the official docs says:</p><blockquote>The <strong>Defined Methods</strong> column counts only the methods that are defined in one of your DEX files, so this number is a subset of <strong>Referenced Methods</strong>.</blockquote><p>So in essence, the bottom-line figure is the Referenced Methods.</p><p>Lastly, in addition to the figures, you can also see a complete list of all classes/packages that were ommited here:</p><pre>...yourProjectDiectory\build\app\outputs\mapping\debug\usage.txt</pre><p>If you think a file is more crucial, you can simply move it to the proguard-rules.pro created earlier.</p><p>That’s it folks.</p><p>Hopefully this was useful.</p><p>If you think of a better way or if you know of any defects to this approach, please do not hesitate to post it in the comment section below.</p><p>I wrote my very first Medium article <a href="https://medium.com/@olawale_alabi/and-so-the-journey-into-the-world-of-flutter-mobile-development-begins-217f7490f3c5">here</a>.</p><p>Thanks for the claps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=728af11a4e22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[And so the journey into the world of Flutter Mobile Development begins…]]></title>
            <link>https://medium.com/@olawale_alabi/and-so-the-journey-into-the-world-of-flutter-mobile-development-begins-217f7490f3c5?source=rss-d4a7da98f0b1------2</link>
            <guid isPermaLink="false">https://medium.com/p/217f7490f3c5</guid>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <dc:creator><![CDATA[Olawale Timothy Alabi]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 10:13:51 GMT</pubDate>
            <atom:updated>2019-02-14T10:04:22.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lFvxxiiq_gTLXjUb" /><figcaption>Photo by <a href="https://unsplash.com/@jakehills?utm_source=medium&amp;utm_medium=referral">Jake Hills</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>A brief background/introduction:</strong></h3><p>I am a web dev who dabbled into android development sometimes last year.</p><p>I have always loved the idea of developing native mobile experience and I felt learning android development will afford me the opportunity to bring all my crazy mobile app ideas to reality.</p><p>However, my adventure ended rather abruptly at the time, when I realised that:</p><ol><li>The community was yet to make up her mind about the preferred language of choice. Sure there were lots of buzz around Kotlin and I was impressed by its intentions and implementations, but several useful (read non-trivial, beyond todos) tutorials and courses were written in Java. And I don’t want to learn Java. Heck, about 80% of samples in the official android docs were written in Java at the time.</li></ol><p>2. Secondly, coming from the web, I know all too well how quickly messy browser wars could be. To think that I would be making a jump from the heated furnace of supporting IE10s to the frying pan of dealing with a fragmented universe of crappy OEMs and ODMs, …was rather too much for me. And no, I dont want to learn SWIFT just to develop for iOS.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F11YdnfyG6qvuWk%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fblinds-disinterested-11YdnfyG6qvuWk&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F11YdnfyG6qvuWk%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="327" frameborder="0" scrolling="no"><a href="https://medium.com/media/145c3ce1c49b0b8a0da48882a5036ec7/href">https://medium.com/media/145c3ce1c49b0b8a0da48882a5036ec7/href</a></iframe><p>3. Lastly, maybe I can somehow deal with all the above, I mean what kind of a programmer are you if you can’t deal with programming difficulties right? So I soldered on…until I couldn’t. For me, the last clincher was <strong>Android Studio</strong>. I quickly realised that unless you have a state of the art gadget, that is, a games-grade machine, the workflow can be pretty annoying and tiresome.</p><p>My utmost respect to those devs who do this everyday! .</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FWO5Q7FsxJN2pjYc424%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FWO5Q7FsxJN2pjYc424%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExaW5sNjhwYzZqNHdlbzR1MzVyaGpkaHQ1bjYwODc5ZmJ4YmVrOGllZCZlcD12MV9naWZzX2dpZklkJmN0PWc%2FWO5Q7FsxJN2pjYc424%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c827de53396fb6de9d4698bbef014a8/href">https://medium.com/media/4c827de53396fb6de9d4698bbef014a8/href</a></iframe><blockquote>I cannot emphasise enough how crucial this is, especially if you are learning a new language/framework. You should be prepared to spend a sizeable chunk of your time debugging and going through your logs for immediate feedback. If this process is not reasonably snappy, you can lose interest pretty fast.</blockquote><p>So, TL;DR; I returned back to my ‘calmer’ waters.</p><p>I trudged on, wading through the more familiar and far more ‘navigable’ world of the web.</p><p>But fast forward several months to the last few weeks and boom, I HEARD about flutter.</p><p>Nope.</p><p>I have always known and heard about this cool project being cooked by Google to serve as an alternative to Android development.</p><p>But I never really looked into it.</p><blockquote>When I eventually did, I couldn’t believe my eyes!</blockquote><blockquote>And I could not stop scratching myself for coming so late to the party!</blockquote><p>Suddenly all my earlier noted concerns and reasons for jumping ship were allayed.</p><p>It felt like someone took my list, went through each item one by one and pressed auto-reset on each.</p><p>It felt amazing.</p><p>Now, there is only one language (DART)to deal with, ever.</p><p>And the language itself is so approachable, I skimmed through the whole language tour within few hours.</p><blockquote>Anyone who has ever coded in Javascript will instantly feel at home.</blockquote><p>I was even more impressed when I heard about other exciting capabilities of the language; that is, the things you get free out of the box, just by learning it. You want to build a server side application? Check. You can even write it as a drop-in for Javascript…on the web!</p><p><strong>Woohoo!</strong></p><p>Think about that for a moment.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FLcn0yF1RcLANG%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FLcn0yF1RcLANG%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FLcn0yF1RcLANG%2Fgiphy-downsized-large.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="327" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f59586d15e262e40977f1d3834c7a31/href">https://medium.com/media/6f59586d15e262e40977f1d3834c7a31/href</a></iframe><p>Imagine a magical world where you have everything you have always known and loved in Javascript…(functions as first class citizens for instance) but also where all the bad (read: not-so-great) parts were smoothen out.</p><p>So, to my list, that was the first item checked out.</p><p>No more conflicting postulations and confusing suggestions. Every resource you will ever see was baked in Dart.</p><blockquote>At least I can now focus my energy.</blockquote><p>Second on my list was the headache of maintaining support for an infinite amount of devices out there. I cant be saddled with the responsibilities of providing support systems for various (legacy) android sdk versions, Samsung enchiladas, and inexhaustible Chinese variants.</p><p>With flutter, these concerns were flushed out. This because, now, the team took a new approach to mobile development. Instead of the code to be at the mercy of the platform, flutter comes packaged with its own widgets and designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WZM-eNnqqwVIU5DK" /><figcaption>Photo by <a href="https://unsplash.com/@jadeaucamp?utm_source=medium&amp;utm_medium=referral">Jade Aucamp</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Which is what makes it possible to develop the same codebase even for iOS.</p><p>The apps look the same and work the same on older versions of Android and iOS, with no additional overhead for supporting older devices.</p><p>Thirdly, and again, the most important concern of all…development cycle.</p><p>In flutter, this is a breeze.</p><p>Coming from the web, if you have ever experienced live reload, you will appreciate this even more.</p><p>Now you can hit reload from Android Studio and see result instantly on your palm.</p><p>Even my old (grumpy) laptop delivers results in 3 seconds.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1L5YuA6wpKkNO%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1L5YuA6wpKkNO%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F1L5YuA6wpKkNO%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="377" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba16e9b59e74b675b99909df15c29565/href">https://medium.com/media/ba16e9b59e74b675b99909df15c29565/href</a></iframe><p>So, in conclusion, YES. I am back to mobile development.</p><p>And I am enjoying the ride so far.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYqaqeODWhsbK0%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FYqaqeODWhsbK0%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FYqaqeODWhsbK0%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="306" frameborder="0" scrolling="no"><a href="https://medium.com/media/954105e425300e668948e951a3efd49c/href">https://medium.com/media/954105e425300e668948e951a3efd49c/href</a></iframe><p>I’ve got some cool and interesting ideas and as the flutter team would say, “I cant wait to see what I could build”</p><p>See you around folks.</p><p>And oh, thanks for the claps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217f7490f3c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>