<?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 Fabio de Matos on Medium]]></title>
        <description><![CDATA[Stories by Fabio de Matos on Medium]]></description>
        <link>https://medium.com/@fmatosqg?source=rss-49d3cdc09a40------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3XKVYS07bijmfAQ8.jpg</url>
            <title>Stories by Fabio de Matos on Medium</title>
            <link>https://medium.com/@fmatosqg?source=rss-49d3cdc09a40------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:45:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fmatosqg/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[Webview hidden costs]]></title>
            <link>https://medium.com/flutter-community/webview-hidden-costs-989bbbb6a303?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/989bbbb6a303</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Sun, 03 Mar 2019 23:27:25 GMT</pubDate>
            <atom:updated>2019-03-04T01:08:34.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s77AF8l4XX2Bo9L6jWqIwQ.jpeg" /></figure><p>Webviews seem to be an easy way out for when resources are short and you already have a responsive web page. Seems like a no brainer for those non-critical pages like terms and conditions, or for whole flows that we know we’ll never get enough budget to handle in native coding. But there are a lot of little problems that can make the user experience quite awkward. Below I’ll be discussing the most common ones, according to my experience.</p><p><strong>Menu</strong></p><p>Responsive web pages usually contain a menu near the top where you can navigate to different parts of the web page. This is a two fold problem, first because from this menu it’s possible to reach any place in the web page — including screens implemented fully in native. And second because each webview in the app should be limited to a single flow/funnel.</p><p>Also, it ends up pushing your CTA down the fold.</p><p><strong>Headers and footers and big logos.</strong></p><p>Native apps have their own headers, which are called navigation bars. So imagine having both a navigation bar and a web page responsive header. Not very useful, and will take quite some space, in some cases consuming all the “above the fold”. Web desktop designs love big logos, and they’re usually carried over to their responsive designs. The CTA is then pushed a bit further down the fold.</p><p>And footers, well, native apps don’t have them. It’s a convention, but I have never seen one in a full native app. They could be added, but nobody does it. Don’t try to outsmart the crowd unless you really know what you’re doing.</p><p>In some extreme cases it’s even worse because some of these elements are sticky, effectively reducing your big expensive 7&#39;’ screen to a 5&#39;’. Well, that’s if you started with a big phone anyway.</p><blockquote>Don’t try to outsmart the crowd unless you really know what you’re doing.</blockquote><p><strong>GDPR banner</strong></p><p>Who knew that native mobile apps used cookies to track users? Hmmm. Well, less pixels for the real stuff.</p><blockquote>So many elements pop up on the top of the screen that we can’t even find that CTA anymore.</blockquote><p><strong>Navigation bar</strong></p><p>The native navigation bar is supposed to tell the user at all times where he is, and while navigating back and forth this is an inexpensive helper, specially because neither the web address nor tab title are going to be visible anymore. It is totally possible to implement communication between the Webview and the native code to update the navigation title, but that’s often overlooked or downplayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywdo49zszxohRTNRQQZIAQ.jpeg" /><figcaption>Disorienting the user is not a good idea. Sticking to good UX practices is.</figcaption></figure><p><strong>Back button</strong></p><p>This was supposed to be an easy one, but somehow I have met more cases of bad rewritten history breaking the back/up button behaviour than I expected.</p><p><strong>Confirmation pages and end of flows</strong></p><p>In a lot of cases when you reach the last screen in a flow there is some state that is changed in the backend. When native developers implement that last page it’s not uncommon to trigger some kind of mobile database update, so there’s no outdated information while the user navigates throughout the app. However, if the last screen in the flow is not native you’ll either have to integrate the javascript with the native code to trigger such events, or risk showing stale information.</p><p><strong>Session management</strong></p><p>This is an easy problem to explain, and not that easy to solve. Basically, it means that if the user logs on the native view, he shouldn’t have to type her password again when going into the webview. It means that we have obtain session keys from one domain and convert them to the other while doing some sort of invisible, seamless new login. Sounds easy, but it’s guaranteed to give you a handful of annoying issues. In some cases the user is allowed to login first in the webview, so it’s necessary to transfer the session in the other direction as well.</p><p>Kind reminder: don’t store passwords on devices if you can avoid. They will make for a lot less effort for solving this problem, at the cost of being less secure. Even storing them on the keychain can be argued to be an obfuscation approach. See how gmail deals with it on <a href="https://android.stackexchange.com/a/29195/135337">https://android.stackexchange.com/a/29195/135337</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rU6KNs9KfdROiENL-UQTNA.jpeg" /><figcaption>More requirements mean more moving pieces, more people.</figcaption></figure><p><strong>Location permission</strong></p><p>This one is more common than it should. If your project needs location services both in the native code and in the webview the user will need to authorize it twice.</p><p><strong>Bugs</strong></p><p>If any bugs surface on the iOS’s webview you’ll probably need the frontend developer to debug it. The downside is that he can only do that from a computer running OS X.</p><blockquote>Is there a better way to trigger the OCD in your user than having different screens with different button/typography styles?</blockquote><p><strong>People won’t wait for the page to load before interacting with it</strong></p><p>Web pages are slow compared to native apps, no news here. However a good practice is to block the screen with a loader so the user can’t interact with a partially loaded screen. I swear, I do that every time I have the chance. Then you need to add a timer in case it never finishes loading, either because of network timeout or other issues.</p><p>A note on screen loading times: in the ideal case where the data is locally available from the phone’s database or internal files the user would be able to see the full screen loaded much in less than 100ms after an action, even if a db query is involved. As a reference UI transitions on mobile apps tend to last about 300ms, but that’s an intentional delay to make the experience better. And they can’t be replaced by a loading animation.</p><p><strong>UI consistency</strong></p><p>There are rare projects where the design style is uniform across different platforms. If you’re in that situation consider yourself a lucky person. Otherwise, is there a better way to trigger the OCD in your user than having different screens with different button/typography styles?</p><p>These are not the only cases though. Can you tell me what’s the point of having 2 crosses on the following screen?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPFQBuiRK-zwHH-Z1OLQdw.jpeg" /><figcaption>Uuuh, how did I end up here???</figcaption></figure><blockquote>The problem with hyperlinks is actually not what they do, is how they look. Unless they’re fine print and you don’t want people to go there, transforming them into a button is the most decent thing to do.</blockquote><p><strong>Hyperlinks — can you hit them?</strong></p><p>Mobile guidelines say that anything that is tappable must be this or that big. Android states it should be at least 7mm x 7mm, or the “thing” will possibly be too small to hit safely. Apple has similar requirements for iOS apps. And browsers provide augmentation so it’s actually easier to hit those targets, while mobile apps don’t. And google also has similar guidelines for web pages with touch screens: <a href="https://developers.google.com/web/fundamentals/accessibility/accessible-styles">https://developers.google.com/web/fundamentals/accessibility/accessible-styles</a>.</p><p>Bottom line, they worked very well for many years when people were chained to their mouses. Unfortunately they don’t play well with touch devices. The problem with hyperlinks is actually not what they do, is how they look. Unless they’re fine print and you don’t want people to go there, transforming them into a button is the most decent thing to do.</p><p><strong>Hyperlinks — please don’t leave my app!</strong></p><p>Actually I lied. Hyperlinks can be a problem depending on where they lead to. It’s not uncommon to see a few of those that lead us to a different domain! Your native developer can control whether those links should be blocked, allowed inside the webview or launched outside the app in a full blown browser. There are cases where each one of those is the most appropriate, but getting all the rules right can be a headache.</p><blockquote>Actually I lied. Hyperlinks can be a problem depending on where they lead to.</blockquote><p><strong>Banners to install the mobile app</strong></p><p>It happened to me in one occasion where the responsive page had a banner to install the mobile app. As a consequence, when we displayed a Webview inside the app we could see an invitation to install the app we were running!</p><p>Fortunately we had a strong team that caught and fixed it before going to production.</p><p>Credits for stock photos:</p><ul><li>Girl with Phone Photo by <a href="https://unsplash.com/photos/1eJUN_S_1dY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sarah Diniz Outeiro</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.com</li><li>Money Bills Photo by <a href="https://unsplash.com/photos/9oHlADjtBTQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Niels Steeman</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.com</li><li>Puzzle Photo by <a href="https://unsplash.com/photos/UFCVxUC-PqM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/collections/1224719/business?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.com</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=989bbbb6a303" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-community/webview-hidden-costs-989bbbb6a303">Webview hidden costs</a> was originally published in <a href="https://medium.com/flutter-community">Flutter Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contributing to Flutter — part 3]]></title>
            <link>https://medium.com/flutter-community/contributing-to-flutter-part-3-4b96d924d8ba?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b96d924d8ba</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[pull-request]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Thu, 24 May 2018 07:22:29 GMT</pubDate>
            <atom:updated>2018-05-24T07:22:29.606Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The tale of </em><a href="https://github.com/flutter/flutter/pull/16413"><em>PR #16413</em></a><em> aka scan folders for all its assets.</em></p><ul><li><em>Part 1: </em><a href="https://medium.com/@fmatosqg/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc">https://medium.com/@fmatosqg/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc</a><em>, covers the less technical parts</em></li><li><em>Part 2 : </em><a href="https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e">https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e</a>, <em>covers how to configure and deal with IDE and environments</em></li><li><em>Part 3: You’re Here!</em></li></ul><p>Here’s the tale of <a href="https://github.com/flutter/flutter/pull/16413">Flutter PR #16413</a>, who enables developers to add lots of assets by simply adding their folder name on pubspec.yaml. It lived for 1 month 13 days<strong> 😨</strong>. Nothing compared to its parent <a href="https://github.com/flutter/flutter/issues/4890">Issue #4890</a>, which was getting near it’s second birthday 😵 when it got closed!</p><p>Here’s a glimpse of what it can and cannot do. And why.</p><p>Imagine you have dozens or hundreds of images or json files that you want to bundle with your flutter app. Before this feature you had to do something like the flutter_svg package (<a href="https://github.com/dnfield/flutter_svg.git">https://github.com/dnfield/flutter_svg.git</a>) :</p><pre>. . .</pre><pre><strong>  assets:</strong></pre><pre>    - assets/flutter_logo.svg</pre><pre>    - assets/dart.svg</pre><pre>    - assets/w3samples/alphachannel.svg</pre><pre>    - assets/w3samples/aa.svg</pre><pre>    - assets/deborah_ufw/new-action-expander.svg</pre><pre>    - assets/deborah_ufw/new-camera.svg</pre><pre>    - assets/deborah_ufw/new-gif-button.svg</pre><pre>    - assets/deborah_ufw/new-gif.svg</pre><pre>    - assets/deborah_ufw/new-image.svg</pre><pre>    - assets/deborah_ufw/new-mention.svg</pre><pre>    - assets/deborah_ufw/new-pause-button.svg</pre><pre>    - assets/deborah_ufw/new-play-button.svg</pre><pre>    - assets/deborah_ufw/new-send-circle.svg</pre><pre>    - assets/deborah_ufw/numeric_25.svg</pre><pre>    - assets/simple/clip_path_3.svg</pre><pre>    - assets/simple/clip_path_2.svg</pre><pre>    - assets/simple/clip_path.svg</pre><pre>    - assets/simple/ellipse.svg</pre><pre>    - assets/simple/group_opacity.svg</pre><pre>    - assets/simple/nested_group.svg</pre><pre>    - assets/simple/rect_rrect.svg</pre><pre>    - assets/simple/linear_gradient.svg</pre><pre>    - assets/simple/linear_gradient_2.svg</pre><pre>    - assets/simple/radial_gradient.svg</pre><pre>    - assets/simple/dash_path.svg</pre><pre>    - assets/simple/text.svg</pre><pre>    - assets/simple/style_attr.svg</pre><pre>    - assets/wikimedia/Ghostscript_Tiger.svg</pre><pre>    - assets/wikimedia/chess_knight.svg</pre><pre>    - assets/android_vd/battery_charging.xml</pre><pre>. . .</pre><p>There are exactly 29 lines dedicated assets, one per file present on disk. How nice would it be if we could make that shorter? With this feature it’s enough to specify the folder followed by a /</p><pre>. . .</pre><pre><strong>  assets:</strong></pre><pre>    - assets/</pre><pre>    - assets/w3samples/</pre><pre>    - assets/deborah_ufw/</pre><pre>    - assets/simple/</pre><pre>    - assets/wikimedia/</pre><pre>    - assets/android_vd/</pre><pre>. . .</pre><p>That’s the gist of it, and although not perfect I hope it helps a lot.</p><h3><strong>Why can’t it do X?</strong></h3><p>Now, a common question is why not specify simply -assets/ and support recursive scanning, globbing and wildcards as originally suggested? In the ideal case the above project could simply reference the parent folder and Flutter would take care of finding all the assets:</p><pre>. . .</pre><pre><strong>  assets:</strong></pre><pre>    - assets/</pre><pre>. . .</pre><p>Easy right? Well…</p><p>The reason is how variants are handled in Flutter, which makes it tricky. Variant is a name used in Android to cover differences in phone resolutions among other things. A quick Flutter example: if you include both files assets/foobar.png and assets/3.0x/foobar.png they should be automatically linked, and one should be used for low-res phones while the second would be chosen on flagship ones (better examples at the official docs). And by doing a naive implementation of subdirectory scanning we could end up having 2 unlinked assets and fail to use the high-res assets/3.0x/foobar.png at the appropriate places, having the user seeing the less beautiful version. That’s the short story.</p><p>A slightly smarter implementation could use some regex to identify that those 2 files are linked. As easy as it sounds it can bring a couple unexpected surprises if both the scanning (build time) and painting (run time) code don’t agree. Adding to it that currently in Flutter variants are used exclusively for image resolution, but if later it’s expanded in a similar way as in Android to cover things such as localization, screen size or orientation, and we could end up in a situation where upgrading the flutter version could break your build. Consider the hypotetical files:</p><pre>assets/hero.png</pre><pre>assets/3.0x/hero.png</pre><pre>assets/landscape/hero.png</pre><pre>assets/landscape/3.0x/hero.png</pre><p>Today it means that we’re talking about 2 assets — assets/hero.png and assets/landscape/hero.png, as well as a their 3.0 variants. But it’s not possible to guarantee that a future flutter feature (😮 pun intended) will decide to handle landscape variants, which could potentially misinterpret the developers’ intentions and treat those 4 files as one asset + 3 variants. The result would probably be detected when the app tries to reference those files, which makes it quite tricky to detect, specially if the developer is not aware of the change in behaviour.</p><p>There is at least one solution to this problem, but it’s much better to enjoy the non-controversial part of the feature before getting it perfect, right?</p><h3><strong>How do I benefit from it?</strong></h3><p>Any time you have multiple asset files in the same folder you can stop adding them one by one and simply add their folder name, followed by /. If you forget to add that character at the end there will be a nice error message: “No file or variants found for asset: assets/images”. That’s the same message when you mention a file that doesn’t exist, because Flutter doesn’t know you would like it to be treated as a folder.</p><p>Also now that the role of image variants is clear, remember to always pack hi-res images for those nice devices with high dpi. For reference, the ideal situation is adding files for 1.0x ( asset/filename.png) as well as 2.0x and 3.0x (asset/2.0x/filename.pngand asset/3.0x/filename.png). But if you want to add a single file for each asset you should skip the 1.0x resolution and just include the 3.0x version. When adding the folder to pubspec.yaml you will still reference the 1.0x variant AS IF it were present on disk (-asset/), and Flutter will understand that only the 3.0x variant should be used in all devices no matter what.</p><p>A nice alternative is using svg format through the flutter_svg package, which is better both because these files are smaller and also because it has less problems with rescaling for the exact resolution of the phone. It may use a bit more of CPU and battery in the typical case, but that’s a small price to pay for the benefits.</p><h3><strong>How do I use it with font files?</strong></h3><p>This is actually a completely separated feature, because of the way the schema for fonts work. Fonts a) need the developer to specify the font family name as a string, and b) have optional parameters for font weight, things get a bit more complex. It’s definitely possible to come up with something better, but that’s a subject for another PR.</p><h3><strong>What’s in the future?</strong></h3><p>As I write this is feature about to travel from master channel to the dev channel, until it eventually reaches beta. Big thanks to github user @tvolkert who had a LOT of patience to get me out of all the rabbit wholes every time I got lost.</p><p>What do I see coming next?</p><p>- Documentation will be updated as soon as the feature reaches beta</p><p>- Analyzer currently tells us things like “<em>warning: The asset assets/w3samples/ does not exist. (asset_does_not_exist at [flutter_svg] pubspec.yaml:38)</em>”</p><p>- Adoption by developers ;)</p><p>- Stop using strings to reference images and assets (the idea is for developers to stop using new Image.asset(&quot;asset/folder/filename.png&quot;) and start using something likenew Image.asset(AppPackage.filename);</p><p>- Scan for font files and use some heuristics to figure out family name and font weight automatically; encourage developers to stop referencing them by strings in dart code similar to the proposed new feature for images</p><p>- And subdirectory scanning, globbing and wildcards</p><p>I’m open to ideas, and the Flutter team accepts PRs, so if anyone feels there’s something important or urgent missing there’s the opportunity to step in and do it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b96d924d8ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-community/contributing-to-flutter-part-3-4b96d924d8ba">Contributing to Flutter — part 3</a> was originally published in <a href="https://medium.com/flutter-community">Flutter Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contributing to your preferred open source project, starring Flutter — part 2]]></title>
            <link>https://medium.com/flutter-community/contributing-to-flutter-part-2-46092dc4417e?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/46092dc4417e</guid>
            <category><![CDATA[android-studio]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 04:33:57 GMT</pubDate>
            <atom:updated>2019-03-08T00:28:35.273Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How to configure your tools to edit native code, or flutter SDK.</em></p><ul><li><em>Part 1: </em><a href="https://medium.com/@fmatosqg/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc">https://medium.com/@fmatosqg/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc</a><em>, covers the less technical parts</em></li><li><em>Part 2 : this one</em>, <em>covers how to configure and deal with IDE and environments</em></li><li><em>Part 3: </em><a href="https://medium.com/@fmatosqg/contributing-to-flutter-part-3-4b96d924d8ba">https://medium.com/@fmatosqg/contributing-to-flutter-part-3-4b96d924d8ba</a>, covers the tale of a flutter issue</li></ul><p>In this post I’ll cover</p><ul><li>how to modify a package’s source code in either Dart, or Native, and use it in your project</li><li>how to modify Flutter SDK source code and use it in your project</li></ul><p>There will be a resonable amount of content to cover, but hopefully we’ll see more things than you need.</p><p>I’m assuming that if you need to use a particular flutter/android/iOS feature you both know the language and the framework you’re writing on. What I’ll show instead is how to use the tools you already know, to write that code and do all sorts of TDD and library/app development. I also assume you’re familiar with git and github. But even if you don’t you can still get some understanding of how the cogs move each other.</p><h3><strong>Editing Android or iPhone native source code</strong></h3><p><strong>Disclaimer</strong></p><ul><li>VS Code is not really an alternative for this section. To the best of my knowledge it doesn’t have support for Android or iOS native projects. But if it’s your thing use it at your own risk. BTW Jetbrains has an IDE for iOS development called AppCode. Trying to use Android Studio or Intellij to edit iOS native projects as likely to result in little more than frustration.</li><li>The only operating system that can compile files for iOS is Apple’s. You can still edit source code, but the compiler and linker necessary to build the files accepted by the app store only run on OS X.</li></ul><p><strong>Editing your own apps’ native code</strong></p><p>The following steps apply if you want to modify the native source code from either an app or a package.</p><ul><li>Open flutter project on Android Studio (AS)</li><li>Go to menu tools, select flutter</li><li>Choose ‘Open Android module on Android Studio’ (this does the same as opening an existing project in AS, pointing to &lt;your flutter project root folder&gt;/android)</li><li>Or you can choose ‘open ios module on XCode’ (this is the equivalent of opening XCode and then opening project &lt;your flutter project root folder&gt;/ios/Runner.xcworkspace)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlmb2rI7Slw25nFv9FHcng.png" /><figcaption>Check out, we even have an option for writing feedback right here. It will immediately create a new issue in the AS plugin repository (not the SDK one) <a href="https://github.com/flutter/flutter-intellij/issues/new">https://github.com/flutter/flutter-intellij/issues/new</a></figcaption></figure><p>Android Studio and XCode users should be familiar with what to expect next: you can benefit from proper syntax highlight, code completion and debug breakpoints on native code.</p><p>You can also run the flutter project from here. Gradle has a reference for a flutter plugin, who will compile dart files followed by the usual build process. XCode still uses CocoaPods to reference external code and hook into Dart compiler. There’s no support for hot reload, although the usual native environment works exactly as expected.</p><p><strong>Is it worth using the native IDE?</strong></p><p>You can also access everything else those tools offer, such as: android/app/build.gradle, where you have native build setup, dependencies configuration and app signing. Or android/app/src/main/AndroidManifest.xml, that hold permissions, screen orientation and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*98fXLxA1sN-o-u78fppCDA.png" /><figcaption>Android studio from flutter app, showing included package video_player as a submodule</figcaption></figure><p>There’s other reasons to use such tools. If you want to configure Android’s status bar you can edit android/app/src/main/res/styles.xml. For example to make it go away you’d add &lt;item name=”android:windowFullscreen”&gt;true&lt;/item&gt; to LaunchTheme. Also XCode is notorious for having nice interfaces for editing files with proprietary formats (varying from mildly hard to impossible to either read or solve merge conflicts). Or the plist file for iOS, which stores a great deal of information of all sorts. Most of those files will have linters and compilers running before you think about running your app, suggesting changes and providing autocomplete so the effort to type the correct thing is greatly reduced. And preventing you from running the app until you fix syntax and compiler errors, which is actually a big time saver. I still wish</p><p>Eventually you’ll want to configure a package that needs editing some of those files. For example when you add firebase or facebook to your project, either through pubspec or directly on native configuration. What’s quite interesting , when you want to add a file to an iOS project you absolutely need to do it by opening XCode. Then you drag and drop the file on it, and it gets added to project.pbxproj that registers all files in your project. Adding the firebase json file is one such example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*qYna0vtBvyyLNO5WgZiRAQ.png" /><figcaption>XCode showing sibling native project, displaying included flutter package video_player</figcaption></figure><p><strong>Understanding the build system for packages</strong></p><p>Once you open the native IDE you also have access to all the source code and related files from all the <strong>included</strong> flutter packages. They are not subfolders, but from the way the build system references them they will pop-up as if they were, as submodules/pods in your project. I got quite a surprise when I discovered this: packages don’t include code in binary form, and it’s your project that compiles and processes all of that — dart, and java, and swift, as well as any assets. I guess that if you have a big project with lots of dependencies the full compile time will get quite big quite fast.</p><p>To better understand how flutter builds apps I’d encourage you to quickly explore into the code for one of those packages. If you make changes there and relaunch your app you’ll be able to immediately see changes. It’s an interesting learning tool, but I strongly discourage you from changing package code this way. On one side you may not know how to undo the changes, because git won’t be tracking those folders — they live on ~/.pub-cache/hosted/pub.dartlang.org/. On the other hand you’ll see those changes applied to all projects that import those versions of such packages. Do it at your own risk, but if you want to do it for legitimate purposes know there’s a right way to fiddle with packages’ code and this is not it.</p><p>That’s how:</p><ul><li>clone such repository somewhere in your disk</li><li>change your pubspec.yaml to something like this:</li></ul><p>from something like this:</p><pre>dependencies:<br>  flutter_staggered_grid_view: 0.1.2</pre><p>to</p><pre>dependencies:<br>  flutter_staggered_grid_view: “0.1.2”<br>. . .<br>dependency_overrides:<br>  flutter_staggered_grid_view:<br>    path: /path/to/flutter_staggered_grid_view</pre><p>Or even commit and upload your changes, that’s an effective way of testing with your co-workers or making a company-wide fork:</p><pre>dependencies:<br>  flutter_staggered_grid_view: “0.1.2”<br>. . .<br>dependency_overrides:<br>  flutter_staggered_grid_view:<br>    git:<br>      url: <a href="https://github.com/letsar/flutter_staggered_grid_view/">https://github.com/letsar/flutter_staggered_grid_view</a>.git<br>      ref: 938575 &lt;replace with branches, tags, etc&gt;<br>      path: &lt;path to folder containing pubspec_file, usually ommited&gt;</pre><p>For more details on syntax for dependencies see <a href="https://www.dartlang.org/tools/pub/dependencies#path-packages">https://www.dartlang.org/tools/pub/dependencies#path-packages</a></p><p>If you did modify those files and want to revert everything back to normal, a pub cache -repair will re-download all packages you have on your disk. Or you can also delete . ~/.pub/cache followed by flutter packages get, so you dump all packages and only download the ones you’ll be using immediately.</p><p>(thx @zoechi and @Mahi-K for pointing in the right directions)</p><p>Once you want to run your recently typed changes forget about hot reload. This code is not interpreted, so you will have to stop the app and launch it again. Though Android allows you to do hot swap in traditional Android development I haven’t tried it yet — search for Instant Run for more info. And the full restart is actually not that full, so you really will need to see the app go away and come back. I find that confusing, so I added some notes here <a href="https://github.com/flutter/flutter/issues/16493">https://github.com/flutter/flutter/issues/16493</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KsFrENMdSud1olOYfS24Lw.png" /><figcaption>Opening the Android project of a package, starting from your flutter app project</figcaption></figure><p><strong>Why is this all important?</strong></p><p>There’s a whole world of APIS and documentation built over a decade, it’s just impossible to access all of it from flutter. And if Fuchsia ( the new experimental mobile OS ) comes out virtually none of the existing packages will work. As the platform is relatively new there’s a lot of low hanging fruits, and I hope my contribution will help cover that gap. Some that I noticed are</p><ul><li>the connectivity plugin doesn’t have an api for showing the wifi or mobile IP address. This requires a little bit of Dart and a handfull of java/kotlin and swift code.</li><li>there’s no way to dynamically hide the status bar. I couldn’t find a package closely related to that, so that would involve creating one from scratch. SystemChrome.<a href="https://docs.flutter.io/flutter/services/SystemChrome/setEnabledSystemUIOverlays.html"><strong>setEnabledSystemUIOverlays</strong></a> allows you to move it around (for fuchsia support?), so it may be a good place to add it.</li><li>the animations’ interpolators still don’t include a Curve that implements springs. This can be done writing Dart code alone, although peeking into the existing java implementation can save some time. And you can brag with your React Native colleagues that they had to do it in java because of bridge speed issues.</li><li>a plugin to read phone number (without relying on firebase)</li><li>add github authentication for the firebase_auth package — @osorito will be happy :). Get in touch with him if you plan doing it.</li><li>a plugin to read/write images to the gallery, which could also provide path to other common folders in android (the concept is new on iOS, not sure how it works)</li></ul><p>The last one could be a bit more complicated: a) add permission to read external memory on manifest b) get permission to read on external memory c) find the folder where gallery gets stored (with path_provider) d) download file and write there e) call the appropriate Android method to scan for images (if you skip last step you’d have to reboot phone).</p><p>Some useful resources</p><ul><li>How to use flutter channels, so you can have Dart code interoperability with native <a href="https://flutter.io/platform-channels/">https://flutter.io/platform-channels/</a></li><li>How to create packages from scratch <a href="https://flutter.io/developing-packages/">https://flutter.io/developing-packages/</a></li><li>React Native implementation of spring animation <a href="https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/animated/SpringAnimation.java">https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/animated/SpringAnimation.java</a></li><li>The official gitter channel, where there’s a lot of devs who helped me get where I am: <a href="https://gitter.im/flutter/flutter">https://gitter.im/flutter/flutter</a> (yes I’m calling gitter a resource, not the people)</li></ul><p>And non-tech resources</p><ul><li>Flutter guide to contributing to SDK source code, from where I got a lot of information for this blog: <a href="https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md">https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md</a></li><li>Google advice on code reviews: <a href="https://testing.googleblog.com/2017/06/code-health-too-many-comments-on-your.html">https://testing.googleblog.com/2017/06/code-health-too-many-comments-on-your.html</a></li></ul><h3><strong>Flutter SDK development</strong></h3><p>This covers changes to the part of flutter written in Dart that all developers use when building their apps and libraries.</p><p>There are 3 important branches you must know about. beta is the stablest version we have, and it gets update quite… not often. Then there’s the dev branch which has less stable code, and finally master where every new piece of code goes first. These 3 branches are also called channels, and so far they’re the only official channels we have.</p><p>Unfortunately they also coined the term channel to designate how to communicate between dart and native code. That’s a completely unrelated topic, but I’d rather mention it to avoid confusing both.</p><p>Now in beta 2 there are 2 ways to install flutter. You can download a big fat zip or you can clone from <a href="https://github.com/flutter/flutter">https://github.com/flutter/flutter</a>. Either way is fine, but I recommend you make a second copy of whatever you have. So my suggestion is that before making any planned changes you keep your main copy on beta to keep writing stable apps, and your working copy on master so you can put it on steroids. The reason is that when you find odd behaviour you can quickly recompile your app with the beta and rule out any quirks.</p><p><strong>Using alternative installation for flutter</strong></p><p>Simply copy the folder in your preferred way, there’s nothing mystical about a flutter installation. Let’s say your main copy will stay on ~/bin/flutter and your dev copy will be on ~/code/projects/flutter.</p><p>Now let’s update our tools to point to the new folder. One way is to put this in your .bashrc</p><p>alias flutter_experimental=’export PATH=~/code/projects/flutter:$PATH’</p><p>and every time you want to use it in a fresh terminal do</p><p>flutter_experimental</p><p>And on either Android Studio or Intellij go to preferences / Languages and Frameworks / Flutter. On the field for “Flutter SDK” path put ~/code/projects/flutter. Just remember to do that for every flutter app or plugin you want to compile, it won’t be carried over to all projects at once.</p><p>Yes, it does mean you don’t have to wait for google to approve your changes so your team benefits from your changes! Life is good, and is about to get better!</p><p>Now change to the master channel, followed by getting all the latest changes. You can do that with:</p><pre>flutter channel master<br>flutter update</pre><p>Instead you can also use the usual git commands and get the same results.</p><pre>cd &lt;wherever your flutter is installed&gt;<br>git checkout master<br>git pull origin master</pre><p>And you can use these steps to have at hand a working copy for each channel, to quickly switch whenever you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/1*PU0-64eCumEVb0N9O4aQLg.png" /></figure><p>At this point you probably want to fork on github. Login and hit the fork button on top right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*1odLs1eNMq0x8oaix91inw.png" /></figure><p>I always use command line, but GUI tools also have a way of adding a second remote repository to a folder. Mine was added like this:</p><pre>git remote add upstream git@github.com:fmatosqg/flutter.git</pre><p>where fmatosqg is my user.</p><p>This way you can still get changes by doing git pull origin master while pushing your changes to git push upstream my_feature.</p><p><strong>Changing sample code</strong></p><p>Just as an exercise, let’s add a log to the file that handles the manifest.</p><p>Open Android Studio or VS Code. Then open project, on folder ~/code/projects/flutter/packages/flutter_tools. Check that Dart is configured and after that open file lib/src/flutter_manifest.dart.</p><p>An alternative way on AS is to quickly tap shift (it only works with the shift to the left of the keyboard). Type FlutterManifest and pick flutter_manifest.dart from the list.</p><p>Find method createFromPath and on its first line add print(‘Hello World’);. That’s it for editing.</p><p>Tips: to quickly see and access the classes and methods in a file open the flutter outline panel — don’t forget to turn off the filter by views option, which is the funnel on the top right. You can also use the structure panel, accessible with Cmd+7</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yc576yCloxnaPiAbzI9YPg.png" /></figure><p>Now open a second Android Studio instance (or VS) and open a project with a flutter app.</p><p>As explained in previous section, change your configuration — either command line or AS or VS — to point to your modified copy of flutter.</p><p>Launch the app and see your hello world message show up.</p><p>Now let’s change it again, to print(“Hello Manifest”);</p><p>Stop the app, relaunch and… nothing changed. That’s because flutter optimizes and caches the result of its last build. To trigger it again:</p><ul><li>Delete bin/cache/flutter_tools.snapshot, it’s on ~/code/projects/flutter/</li><li>flutter clean to delete app’s build folder</li></ul><p>Stop the app one more time and start it again. You’ll notice it takes a little longer, it crunches that change you just made, and finally prints it on screen.</p><p><strong>Running tests</strong></p><p>You can also run a particular unit test in AS by opening the test file, say, packages/flutter_tools/test/flutter_manifest_test.dart. On the top of that file there’s a main method. Right click it on the editor window and choose either Run or Debug. You can also run individual groups of tests, doing the same with either the group method or the individual unit tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UYTb9YZPH1MeL88CQ0fwAw.png" /></figure><p>Now you’re ready to do your magic. When you’re finished and before sending a pull request to github remember to check the dart analyser from inside AS. And that all unit tests are successful.</p><pre>flutter packages pub run test  | tee test.log</pre><p>I like to do it from AS’s own terminal:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRlEF6XL0-0ZQF6weRW3cA.png" /></figure><p><strong>Epilogue</strong></p><p>Flutter and React Native are based on the principle of Learn Once Write Everywhere. It doesn’t mean that you can do it without access to OS X.</p><p>It also means you can write apps that do exactly the same thing on all platforms it supports, but not that you should do it. Users expectations are very deep into their behaviours, and breaking those patterns must be a conscious choice. There are big differences, such as the Material vs Flat design and the ways to deal with background operations. There are also subtle things, such as the friction coefficient of scrolling views and how you should ask the user that the app needs access to GPS. Not to mention all the rules Apple want you to follow before it approves your app in the store.</p><p>Also some gotchas, as expected flutter draws every pixel on your app. That’s true, but technically the status bar doesn’t belong to the app, instead we kindly ask the operating system to perform a couple of operations on it on our behalf. In the same sense, all sockets opened by the Dart code will obey to rules set up in the app, who will ask the operating system for it. If you don’t include internet permissions in the manifest (or a flutter package does it for you), or if the SSL certificate from the server is not accepted by the OS, there’s no possible way to get a single bit from the cloud. The same goes for asking for permissions before sending push notifications. Unless dealt according to what each ecosystem needs it won’t just work.</p><p>You can get away with a lot by only learning flutter and dart. When you cross from Dart to native you have to deal with platform specific documentations. And when you don’t you’ll still be occasionally tapp into that. You still need XCode to build for iPhone, and understand its ecosystem properly when setting push notifications, configuring provisioning profiles and deploying to the store. Android builds still rely by and large on gradle, Android’s SDK, java and also on NDK, and it may be useful to understand them when something breaks — at least so you know whether it’s a package import problem or it’s coming from something you wrote in your app.</p><p>These examples are just to illustrate that flutter is “simply” a layer on top of the existing Android/iPhone tools and source code and operating system. It’s quite an impressive project, and it implements the UI code from a very low level, arguably even more native than Android native, but almost everything else is built on top of the same tools and procedures that native apps use normally.</p><p>Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46092dc4417e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-community/contributing-to-flutter-part-2-46092dc4417e">Contributing to your preferred open source project, starring Flutter — part 2</a> was originally published in <a href="https://medium.com/flutter-community">Flutter Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contributing to your preferred open source project, starring Flutter — part 1]]></title>
            <link>https://medium.com/flutter-community/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/9783db763ecc</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Wed, 11 Apr 2018 05:30:56 GMT</pubDate>
            <atom:updated>2018-05-24T07:23:56.900Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this installment: How to help the community without writing code.</em></p><ul><li><em>Part 1: this one, covers the less technical parts</em></li><li><em>Part 2 : </em><a href="https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e">https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e</a>, <em>covers how to configure and deal with IDE and environments</em></li><li><em>Part 3: </em><a href="https://medium.com/@fmatosqg/contributing-to-flutter-part-3-4b96d924d8ba">https://medium.com/@fmatosqg/contributing-to-flutter-part-3-4b96d924d8ba</a><em>, covers the tale of a flutter issue</em></li></ul><p>I’ll show you how you can add a completely new feature to Flutter framework in 3 short steps:</p><ul><li>Have an idea!</li><li>Learn Dart and also how Flutter works</li><li>Modify its internal source code, test it, follow all the review comments and Done!</li></ul><p>See how easy?</p><p>And if you fine tune the second step you can apply it to so many things, that’s the power of oversimplification that often goes underrated. Look at my other very interesting bullet list, for how to be a millionaire:</p><ul><li>Have a very good idea</li><li>?</li><li>Get a million dollars</li></ul><p>Unfortunately talk is cheap, so let’s stop with the click bait and get to the next part. I’ll guide you through those 3 steps above, from how I went from identifying a feature that I wish was present, to actually making it available and trying to bundle it into the Flutter framework that is used to build all apps.</p><h3><strong>Have an idea</strong></h3><p>This is the story of how I started learning Flutter and missed something. <strong>I want X when I do Y.</strong></p><p>The way Flutter manages assets, either for images or json, is by adding entries to the pubspec.yaml file. They look like this:</p><pre>flutter:</pre><pre>assets:</pre><pre>- assets/images/easter_bunny.png</pre><pre>- assets/images/christmas_reindeer.png</pre><p>The second step is to actually add them to your disk.</p><p>And finally, that’s how you use them in your source code:</p><pre>new ImageAsset(&#39;assets/images/easter_bunny.png&#39;);</pre><p>That made me cringe. Coming from an Android background and a long time user of different static languages. And the worst part is when you make a typo you’ll only find out when the app is running. It means when you have an image displayed in that rarely used screen that shows after a 10-step checkout flow and you do a refactor, you’d actually never notice unless you have unit tests. Unit tests are important, but they shouldn’t be the only way to detect these kinds of errors. There must be a better and safer way.</p><p>Let me show you how Android does it.</p><p>Step 1: add file to disk in the appropriate folder. Usually what you want will go in app/main/res/drawable/.</p><p>Step 2: Use it in source code in a statically typed and safe way</p><p>From xml it looks like this</p><pre>&lt;ImageButton</pre><pre>. . .</pre><pre>android:id=“@id/image_easter_bunny”&gt;</pre><pre>android:src=“@drawable/easter_bunny”&gt;</pre><pre>/&gt;</pre><p>That’s still a string, but don’t get me wrong, you can’t build your app if that name doesn’t match an existing file in the disk. It’s not a linter feature, it’s really part of the build tools.</p><p>Or if accessed with java or kotlin you can write it this way.</p><pre>imageEasterBunny.setImage(R.drawable.easter_bunny);</pre><p>And there’s nothing between step 1 and 2. Well, actually Android Studio will crunch a few files around, but as a developer it’s completely seamless.</p><p>If you’re developing for iOS step 1 consists of a) drag and dropping the file on XCode (the official IDE) and b) ticking one or two checkboxes.</p><p>Step 2 with the GUI consists of selecting from a dropdown list, and only if you rather do it dynamically in Swift you’ll get something unsafe.</p><pre>UIImage(named: “easter_bunny.png”)</pre><h3>Exploring</h3><p>I started to wonder, how could it work similarly in Flutter. Fortunately they are an open source project, which means I could peek into http://github.com/flutter/flutter and check if somebody already had that idea and was working on it. As it happens there was issue #4890 about people who wanted to avoid specifying assets one by one, and instead they think there should be a better way to include lots of assets. A real case had LOTS of assets, like, 3000 of them. Well if that’s not going to help me push my case, what would? That’s when I fleshed out some specs:</p><ul><li>Easy way to add an entire folder</li><li>Tap into some internal structure and generate a dart source code file with accessors that would lead me to the right string</li></ul><p>I actually wanted to have only the second part, but I noticed that they are pretty related. And I decided that I’d give it a try at writing the code myself.</p><p>The surprising part is that even before I started coding and was looking at related github issues I found lots of interesting information. And most projects can benefit from people opening issues or writing comments into existing ones, so I’d encourage people to do that part. It doesn’t require you to read code or deep dive into the moving parts, you learn about how things (are supposed to) work and it makes the world a slightly better place. Win-win.</p><p>Coding is still in progress, so hold on and check out what will happen in part 2.</p><p>Read the next part here: <a href="https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e">https://medium.com/@fmatosqg/contributing-to-flutter-part-2-46092dc4417e</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9783db763ecc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-community/ill-show-you-how-you-can-add-a-completely-new-feature-to-flutter-framework-in-3-short-steps-9783db763ecc">Contributing to your preferred open source project, starring Flutter — part 1</a> was originally published in <a href="https://medium.com/flutter-community">Flutter Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native or Hybrid?]]></title>
            <link>https://medium.com/@fmatosqg/native-or-hybrid-aceeca62ed4b?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/aceeca62ed4b</guid>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Sun, 28 Jan 2018 12:53:34 GMT</pubDate>
            <atom:updated>2018-01-28T12:53:34.822Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*KlNvLsvcTyZrTkpqVH2PiQ.jpeg" /></figure><p>This weekend I took to myself to compare 2 versions of twitter: the android app, that I know for a long time now, and the lite version implemented with PWA. Overall they’re both nice, and I won’t get into any details (but obviously I like the native more). End of comparison.</p><p>(Disclaimer: now starts a shamelessly biased opinion from a passionate android native developer).</p><p>This brought me a couple of things to think about, not specific to twitter apps or even about the never ending debate about native apps vs the thing that’s going to completely substitute it in the next x years/months/whatever. And I remembered how much talk there was about globalization shaking the way things are done and some jobs moved to other places, and how radio would die because now TV was the thing. Or how movie theaters would cease to open because of VHS, who lost its place to DVDs who got substituted by streaming. You get the idea. Well, the glory may shift — along with bulk sums of money — but some things just stay for much longer than the predictions.</p><p>So what all of this means for the latest native apps debate about being killed by React Native or PWAs? There are projects suited for all of those. Or even for the old Cordova/Phonegap/Ionic, or Xamarin. New tech will emerge and play catch up, and other ones will sunset, based not only on their technical qualities and money saving abilities, but as well as other subjective things such as perceived reliability, and apparent correlation with high quality apps.</p><p>Often the conversation about which is better revolves about costs and features and trends, and a few times about technical feasibility. Usually goes unnoticed the status quo of higher quality hold by native apps, and I think this can’t be fully explained by rational arguments.</p><p>Here’s a little secret: no matter how bad or good your technology stack is, if you know how to do it right you’ll be able to overcome lots of problems. It’s not inherently easier to do a good app in technology X and a bad one in Y. It may not be the cheapest or quickest way, but if there a will, and there’s skilled people to plan and execute it, there’s a way. On the other way, you can do the best tech decisions ever, but on the wrong hands there’s no chance of success.</p><p>So where do each technology stand? Every one of them have passionate people defending and making it advance as fast as they can, though the mainstream one is still native. And those people come with a baggage of experience on their belts that new trends have to wait until getting on the same level. Their communities are the biggest, so ideas get interchanged more often. They understand better the respective platforms, how to push things farther, what are the wiser options, and what users in their respective ecosystems expect (hint: it’s not the same for Android as it is for iOS). Simply because they’ve been there for longer: there’s more people sharing that knowledge for a longer time.</p><p>Other subtle factors also play in. Fandom among Apple enthusiasts is unrivalled, you can count on people knowing in detail whatever they unveil for iOS for years to come. And Google’s effort in educating on Android is hard to find, engaging developers with official blogs, courses, podcasts and even more.</p><p>Time changes the way the same things are done over and over, and the pace is ever faster in IT, where usually there’s no reason to embrace establishment or old practices that don’t work better than newer ones. Some of the people and companies doing native mobile development now may migrate to other forms of mobile, or even find their place farther away in either IT or outside. I think it’s a good thing that everybody has more options on how to do the same stuff, and the obvious effect is the burden of choosing it. But in the end, every field in the world has passionates and specialists, and they’ll stay longer than the average when adversities come. On a personal level, while this group stands for the quality of the work it’s still going to be worth being there.</p><p>After all, who knows what will be going on 10 years from now? Mobile can be completely obsolete!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aceeca62ed4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s the point of suits anyway?]]></title>
            <link>https://medium.com/@fmatosqg/whats-the-point-of-suits-anyway-b1cbf9c8e02a?source=rss-49d3cdc09a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1cbf9c8e02a</guid>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[suits]]></category>
            <category><![CDATA[it]]></category>
            <dc:creator><![CDATA[Fabio de Matos]]></dc:creator>
            <pubDate>Thu, 27 Jul 2017 03:03:45 GMT</pubDate>
            <atom:updated>2017-07-27T03:03:45.521Z</atom:updated>
            <content:encoded><![CDATA[<p>What’s the point of suits anyway?</p><p>I wonder who decided that interviews mandate wearing suits. It’s a pity, for me they should be reserved for wedding ceremonies. And when people went on to wedding parties they should be offered to dress up. Or dress normal. Whatever doesn’t involve a suit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*Snp6fHmg_j3WDAmMEQgHZQ.jpeg" /><figcaption>Clothes are like IT’s snake oil</figcaption></figure><p>The thing is, now I’m a free commodity in the job market. That means I’m proudly unemployed. I guess I need to get myself a new suit. And probably a new shirt and maybe even shoes? Because you know, that’s how my coding skills get assessed? And still, nothing makes me feel sillier than being the best dressed person in the room, right? There was this time I even was interviewed by a guy bare foot, and the worst part is that I couldn’t do the same. The look on people’s faces would’ve been amazing though.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/183/1*-L0BqHYgVhfChohblOMhXA.jpeg" /><figcaption>Highly skilled developer in his natural habitat</figcaption></figure><p>My usual trousers will never care if I won or lost a kilo, they only care whether they’re clean. But my suit’s trousers are a different game.</p><p>- Hey</p><p>- Heya. Long time no see.</p><p>- Yep. How’s things going?</p><p>- Same old. A little bit of dust, no big deal. Oh, it’s a little dark here in the closet, you should have a brighter lamp here.</p><p>- I know, I know.</p><p>- So what’s new? I guess you’ve been happy in your job for a while now, right? Last time I saw you was like 2 years ago.</p><p>- Well… it’s been tough for a couple of months. But happy to take you for a walk these days.</p><p>- What do you mean? Have you been to interviews without me???</p><p>- Sort of.</p><p>- Wha-what? Why?</p><p>- So… the thing is… I got… fat. It’s not you, it’s me.</p><p>- Wait! I can be altered. We can work this through!</p><p>- Sorry mate. I got tooo fat.</p><p>Long live phone interviews. Longer live home working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*DAvBm5T2Z6LjA_NA2UdSdg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1cbf9c8e02a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>