<?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 Animesh Jain on Medium]]></title>
        <description><![CDATA[Stories by Animesh Jain on Medium]]></description>
        <link>https://medium.com/@animeshjain?source=rss-c79f92aa50a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JCOgSAChMoXwqqQ4dcELNw.png</url>
            <title>Stories by Animesh Jain on Medium</title>
            <link>https://medium.com/@animeshjain?source=rss-c79f92aa50a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:40:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@animeshjain/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[Opportunity in the AI job apocalypse]]></title>
            <link>https://medium.com/@animeshjain/opportunity-in-the-ai-job-apocalypse-f8c2b6699390?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c2b6699390</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 03:57:40 GMT</pubDate>
            <atom:updated>2026-02-12T03:57:40.222Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are young, coming out of college, and feeling scared by the impending AI apocalypse on jobs, I want to say something to you</p><p>Finding a job working for large corporations, may be a rarity in the near future. This was an obvious popular choice after college. Being financially independent is your top priority and corporations were a great way to exchange your servitude for some money. Everyone gets it, no shame in it.</p><p>But now industry pundits are calling software engineering (and soon other knowledge work) dead. they’re saying in politically correct terms that fresh grads are f*cked. so let’s just take a look at the situation here…</p><ul><li>is there a systemic shift coming in how companies work? for sure. (invoke macron voice)</li><li>will they hire fewer people? for sure.</li><li>are fresh grads the worst hit by this? yes sir.</li><li>is shit getting scary? you bet!</li></ul><p>But here’s the dealio. Some unsaid industry knowledge. Some people get butthurt about it when it is said out loud, so many of you might not be aware of it: most jobs (80%) are bullshit. Not only that, given enough time, they drain the life out of you. so the life in a corp is not all that fun. and in any case, if these jobs are not around any more, where do you go from here.</p><p>It is bleak. But if you squint, I think there is a silver lining in what is about to happen.</p><p>If you have noticed, software in general is not really getting any better. It is getting sicker (not the good ‘sick’ you genz mofos). and it’s not hard to see why. Corporations are merchants of complexity (thanks for the articulation <a href="https://x.com/@dhh">@dhh</a>). The above mentioned 80% of people in large corps who are assigned some BS jobs, are not necessarily willingly doing these jobs. But they are part of the corporate organism which has a BIIIG ego. It must be serviced. They can’t help but create more complexity. And with AI in everyone’s hand, it is going to be a perfect catalyst for a supernova of complexity that the collective individuals in the org cannot comprehend any more.</p><p>Simplicity and efficiency are going to die at the hands of this brain soup of human and AI minds.</p><p>Here arises opportunity for the underdogs (yes you). Bespoke software can now actually be built at low cost. You don’t have to be a Jony Ive or Steve Jobs to do that. There is millions of narrow niches which can be serviced. A big company will be doing that by letting customers in these niches talk to an AI fuckin bot. You can do that by being actually there and building what they need. Smaller teams able to understand problems directly will win.</p><p>So my take is, become an entreprenuer. No matter small. But as an entrepreneur with little resources, there has never been a better time. Your college is not going to be a waste. It may be cliched, but what you found in college was your band of brothers and sisters. Band up. Practice hard. It’s rock and roll time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c2b6699390" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build flavors in Flutter (Android and iOS) with different Firebase projects per flavor]]></title>
            <link>https://medium.com/@animeshjain/build-flavors-in-flutter-android-and-ios-with-different-firebase-projects-per-flavor-27c5c5dac10b?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/27c5c5dac10b</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 11:28:39 GMT</pubDate>
            <atom:updated>2020-06-23T12:36:18.210Z</atom:updated>
            <content:encoded><![CDATA[<pre><strong>[update March 7, 2020]</strong><br>- added instructions for different app icons for different flavors in iOS and Android<br><strong>[/update]</strong></pre><p>After plenty of trial and error to get flavors to work, especially in iOS, I decided to write this article with my learnings. So jumping right into it — build flavors in flutter — in all their comprehensive glory.</p><h4><strong>Why do you need flavors</strong></h4><p>Flavors are typically used to build your app for different environments such as <strong>dev</strong> and <strong>prod</strong>. <br>For eg. <br>- your development version of the app might want to point to an API host at dev.api.myapp.com <br>- and your production version of the app might want to point to api.myapp.com.</p><p>Instead of hardcoding these values into variables and building an app for every environment manually, the right approach is to use <strong>flavors</strong>, and supply these values as build time configurations.</p><p>Funnily, this article does <em>not</em> tackle the use-case of how to handle different API hosts. I feel another article does this well, and I did not want to repeat that information. Please check <a href="https://medium.com/flutter-community/flutter-ready-to-go-e59873f9d7de">Flutter Ready to Go</a> for the same. (What I cover in this article is explained in the next section)</p><p>I feel almost everyone launching an app <em>should</em> be using flavors, but I see that most people avoid using them until much longer. Usually the initial setup inertia is enough to leave it for later, and in the end developers end up wasting a lot of time unintentionally. Unfortunately, in the case of Flutter, they are still not *that* straightforward to setup, hope this article helps with that.</p><h4>A note on documentation on Flutter flavors</h4><p>Flutter flavors support is not very well documented in the <a href="https://flutter.dev/docs/deployment/flavors">official docs</a> (yet) — they point to the following three articles as of writing</p><ul><li><a href="https://cogitas.net/creating-flavors-of-a-flutter-app/">Creating flavors of a Flutter app</a> (Android only)</li><li><a href="https://medium.com/flutter-community/flutter-ready-to-go-e59873f9d7de">Flutter ready to go</a> (Android only)</li><li><a href="https://medium.com/@salvatoregiordanoo/flavoring-flutter-392aaa875f36">Flavoring Flutter</a> (Android and iOS)</li></ul><p>The Android setup is fairly straightforward. The iOS one is a little low on detail and I had a harder time following it. So I had two main reasons to write this article</p><ul><li>Build upon the above articles and also explain how to setup different Firebase projects for different flavors</li><li>Do a deeper dive into the iOS flavor setup, with steps explained more clearly so that you don’t have to spend about as much time I did trying to get it to work.</li></ul><h4>The approach for this tutorial</h4><p>I am going to build a sample app with two flavors: <strong>dev</strong>, <strong>prod</strong>.<strong><br></strong>The sample app has commits after every step, so that you can look at code diffs to understand what all changed. And of-course I’ll try and put in detailed instructions as well. It should be easy to use these instructions for an already existing app quite easily.</p><p>The sample app is here</p><p><a href="https://github.com/animeshjain/flavor_test">animeshjain/flavor_test</a></p><p>Cool? So lets hit the road with the steps…</p><h4>Step 1: Initialize a default flutter app</h4><p>Run flutter create flavor_test to create a default flutter project. Nothing fancy.. this is the first commit of the sample app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9XCChfYRDbNPp9GPsPfN3g.png" /><figcaption>default flutter project</figcaption></figure><h4>Step 2: Configure the app to connect to Firebase</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J-Dyca2ckAPXUnJnuJPK3g.png" /><figcaption>create a new Firebase project called Flavor Test Dev</figcaption></figure><p>Create the app for iOS and Android in Firebase console and download the GoogleService-Info.plist and google-services.json respectively. You can follow detailed instructions to add Firebase to your Flutter project here — <a href="https://firebase.google.com/docs/flutter/setup">https://firebase.google.com/docs/flutter/setup</a></p><blockquote><strong>An XCode peculiarity for Android guys</strong>:</blockquote><blockquote>You’ll have to add the ios file through XCode, as the project file does not detect it if you simply copy it to the ios/Runner directory via the command line. Drag and drop it in the Runner folder in XCode, and select all targets. I learned this only while I was writing this tutorial, so thought it might be helpful to someone setting this up from scratch.</blockquote><p>In this step I have also updated the main.dart file to store the counter in the Firebase Realtime DB instead of just locally. Make sure you setup the Firebase Realtime DB via the console and add security rules to allow write access.</p><p>This is what the app looks like after this commit -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*agv95IAEjFwm-MA7FQWDLQ.png" /><figcaption>the counter is now connected to Firebase Realtime Database</figcaption></figure><p>You can look at the commit diff here to see what all changed —</p><pre><strong>Code Diff : Step 1 to Step 2</strong></pre><pre><a href="https://github.com/animeshjain/flavor_test/compare/step_1_init...step_2_firebase">https://github.com/animeshjain/flavor_test/compare/step_1_init...step_2_firebase</a></pre><h4>Step 3: Adding build flavors to Android</h4><p>We are ready with a basic counter app. However, when we ship this app, it will connect to the same firebase database, as it does when we are building and testing it locally. This is a problem, and this is what flavors are supposed to solve.</p><p>The current Firebase project we created was for our <strong>dev</strong> environment (it was named as such as well), and now we want to create a flavor which will be for our <strong>prod</strong> environment.</p><p>So we can create a new Firebase project for the prod environment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnQm0P1PC6jLPss6AwCyjg.png" /><figcaption>Dev and Prod are separate projects, so that they can have separate realtime DB instances</figcaption></figure><p>Also create an Android app in the project and download the google-services.json file and keep it handy. We will shortly add it to our app.</p><p>For kicks, let’s just see what flutter says when we try to run our app using the --flavor flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Im8iINMGFR-D3weNLFB9TQ.png" /><figcaption>So this gives us a hint that we need to add product flavors to our build.gradle</figcaption></figure><p>We add flavors to app/build.gradle and it looks something like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tNnJs2WAlbn0nO1j0sEI7A.png" /><figcaption>adding product flavors dev and prod to the app/build.gradle</figcaption></figure><p>The <strong>dev</strong> flavor will use the default applicationId as com.kanily.flavortest and the <strong>prod</strong> flavor will use the flavor specific applicationId as defined in the <strong>prod</strong> flavor definition com.kanily.flavortest.prod. We have also defined a string resource called app_name which we are using in the AndroidManifest.xml instead of hard coding the app name. Finally, regarding the google-services.json, it can be put under the source folder within subfolders with names matching the flavors. From <a href="https://firebase.google.com/docs/projects/multiprojects">Firebase Docs</a> -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDScpOh_o65nP6cHWe9Drw.png" /><figcaption><a href="https://firebase.google.com/docs/projects/multiprojects">https://firebase.google.com/docs/projects/multiprojects</a></figcaption></figure><p>So these settings take care of</p><ul><li>Different app id’s for different flavors, so that all flavors can be installed simultaneously on the device</li><li>Different application names for different flavors, so that users/testers/developers can easily differentiate</li><li>Each flavor pointing to its own Firebase project (<em>this is automatically taken care of by the convention of placing the files in folders names the same as flavors</em>)</li></ul><p>Now you can run the app using the commands</p><p>flutter run --flavor dev or flutter run --flavor prod</p><p>Both apps can be installed on the device now and they can run in parallel.</p><blockquote><strong>Notes</strong>: For simplicity, I have removed the profile and release directories which were there in the default flutter scaffold project. They were only adding the Internet Access permission via AndroidManifest.xml, which I have added to the main file.</blockquote><p>Here is the code diff to see what all changed —</p><pre><strong>Code Diff : Step 2 to Step 3</strong></pre><pre><a href="https://github.com/animeshjain/flavor_test/compare/step_2_firebase...step_3_android_flavors">https://github.com/animeshjain/flavor_test/compare/step_2_firebase...step_3_android_flavors</a></pre><h4>Step 4: Adding build flavors to iOS</h4><p>iOS flavors are going to be more nuanced to setup. Also, iOS configuration is mostly done using the XCode UI and not by editing config files in a text editor😱, it is quite messy to explain by typing words. But I have you covered, to help with understanding I’ve recorded all actions and embedded the screencast gifs. So have a glass of water and buckle up…</p><p>Let’s just start with running the flutter run command targeting an iOS device/simulator and see what happens</p><p>flutter run --flavor dev</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTsXzR4wC6kYjnGMwVQk3w.png" /><figcaption>Xcode has the concept of schemes and build configurations as a parallel to product flavors in Android</figcaption></figure><p>So we need to setup something called custom schemes it seems. We’ll need to fire up Xcode and openios/Runner.xcworkspace</p><p>And then, here’s how to setup a custom scheme called dev…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*tctD2CuUZuCV4FcFIXXddw.gif" /><figcaption>Create a new scheme called “dev”</figcaption></figure><p>Now running flutter run --flavor dev again…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xk5I8T1v-M61zizsn81hcw.png" /></figure><p>So the error message tell us that Flutter expects a <em>build configuration</em> by the name of <strong>Debug-dev</strong> or similar. Let’s create these build configurations…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*XsDo_Kv4UPiS-Qeix9YEEA.gif" /><figcaption>Duplicate build configuration to create “Debug-dev” and similar</figcaption></figure><p>Trying flutter run --flavor dev again…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GEzmIt6j8hFHVXcpwJccvA.png" /></figure><p>So this worked. But right now we have not customized anything in the build scheme / build configuration, so the app is running with the same configuration as it was earlier. Let’s rename the default build scheme and build configurations to <strong>prod</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*3TPzQMrFbtwBoe3-seCDhg.gif" /><figcaption>Rename default scheme and build configurations to “prod”</figcaption></figure><p>Since we duplicated the build configurations, the dev ones are still connected to the original scheme (which we have now renamed to prod). Lets fix that as well…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*qXSwfOJfHFWmBgnb2Rqzrw.gif" /><figcaption>Connect “dev” build configurations to “dev” scheme</figcaption></figure><p>Now we have two schemes connected to their own build configurations. We can now customize things per scheme. Let’s first change the app bundle identifier to be different for both schemes. Our <strong>prod</strong> applicationId in Android was com.kanily.flavortest.prod, bundle identifier in iOS is parallel to the applicationId in Android. So let’s change our prod bundle identifier to com.kanily.flavortest.prod…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*huXgYB4sDD092hq75PAnyg.gif" /><figcaption>Update Bundle Identifier for prod build configurations</figcaption></figure><p>We would also like to use different Display Names for the app. However, the Display Name parameter is not there in the Build Settings for the target, so we simply make a user defined parameter, and use it instead…</p><p><strong>[UPDATE May 5, 2020. Thanks to Stanford Lin for the comment]</strong></p><p>There has been a change in how Flutter ios build works now, and this video is a bit outdated. You will probably get an error that says</p><pre>Could not find the built application bundle at build/ios/iphoneos/Runner.app</pre><p>To avoid this error, instead of adding the `$(APP_DISPLAY_NAME)` to the Display Name property in General Settings tab, you should update your Info.plist file to include a new property</p><pre>&lt;dict&gt;<br>...<br>&lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br>&lt;string&gt;$(APP_DISPLAY_NAME)&lt;/string&gt;<br>...<br>&lt;/dict&gt;</pre><p>You do not need to change the Display Name property in General Settings tab any more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*VJhfqIi3-Y365nfM3D99BQ.gif" /><figcaption>Set a custom App Display Name per build configuration</figcaption></figure><p>Finally we have to figure out a way to use a different GoogleServices-Info.plist based on the build configuration. There are some solutions which suggest doing this at runtime on app startup, basically initializing Firebase by explicitly specifying which config file to use (the Firebase docs suggest the same — <a href="https://firebase.google.com/docs/projects/multiprojects">https://firebase.google.com/docs/projects/multiprojects</a>). But I like the other option of copying the right file at the default location at build time, so that when the app bundle gets generated, it used the right file automatically.</p><p>To achieve that, first we will keep the GoogleServices-Info.plist files for each flavor in a separate folder like follows…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*2QT0g0XVi72daZz3tYJdmw.gif" /><figcaption>Copy GoogleServices-Info.plist files to a separate config directory, and link to that directory in XCode</figcaption></figure><p>Make sure you drag and drop the config folder explicitly into XCode after copying it to the correct location from the command line or finder. XCode only adds it to it’s project reference after you add it explicitly. It does not pick up files/folders kept in the project directory by default. XCode folder structure after following the above steps looks like…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yKZ2O9axPUXeupwAYZfeqA.png" /></figure><p>Now we need to figure out how to add a step in the build process so that the respective GoogleServices-Info.plist file is copied into the correct location, i.e. inside the Runner directory. This can be accomplished by adding a new <strong>Run script Build Phase</strong> to the target…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*5tcidmX4DPIvskHpgtec0Q.gif" /><figcaption>Create a Run Script build phase to copy GoogleServices-Info.plist to the default location in app package</figcaption></figure><p>The script I used is below…</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b99b9f4b7fe057358817154c9b0ac428/href">https://medium.com/media/b99b9f4b7fe057358817154c9b0ac428/href</a></iframe><p><strong>[UPDATE June 23, 2020. Thanks to </strong><a href="https://medium.com/u/45a61e86343f"><strong>Dharma Teja Nuli</strong></a><strong> for the comment]</strong></p><p>Paraphrasing the comment here for ease :</p><blockquote>For people who are using <strong>zsh</strong> instead of <strong>bash</strong>, you need to make a small adjustment to make the script run.</blockquote><blockquote>I had to wrap the script provided by the author with two lines. So the script becomes:</blockquote><blockquote><em>setopt KSH_ARRAYS BASH_REMATCH<br>&lt;insert the author’s script&gt;<br>unsetopt KSH_ARRAYS</em></blockquote><blockquote>I got it from <a href="https://stackoverflow.com/a/31695639">here</a>. Thanks.</blockquote><p>And with this, we should be done! Now we can run</p><p>flutter run --flavor dev or flutter run --flavor prod</p><p>And the iOS device / simulator will install separate apps which connect to separate Firebase DBs!</p><pre><strong>Code Diff : Step 3 to Step 4</strong></pre><pre><a href="https://github.com/animeshjain/flavor_test/compare/step_3_android_flavors...step_4_ios_flavors">https://github.com/animeshjain/flavor_test/compare/step_3_android_flavors...step_4_ios_flavors</a></pre><h4>Step 5: Adding different app icons for different flavors</h4><p>Sometimes just different names are not enough. You might want different app icons as well for a more clear visual distinction when multiple flavors are installed in a device.</p><p>So far I was using the default launcher icon that Flutter comes with, but to illustrate the steps I have create two icons for <strong>prod</strong> and <strong>dev</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*sy73NQPreDC2kQK5EGBhrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*O7vX9Gd0Ucv-cbZYTUG8Fw.png" /><figcaption>Slurp! (Courtesy <a href="https://appicon.co/">https://appicon.co/</a> and <a href="https://www.iconfinder.com/">https://www.iconfinder.com/</a>)</figcaption></figure><ul><li><strong>Steps for Android</strong></li></ul><p>Depending on which flavor you consider “default”, one of these icons can simply go to the android/app/src/main/res folder and replace the existing ic_launcher.png files for all the sizes. I’m going to put my <strong>dev</strong> icon into the default folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*S0quEEvU9PT2JkEc4M1W0g.png" /></figure><p>For the <strong>prod</strong> flavor, as some of you might have guesses, we will simply create a res folder in the prod folder, and add all size specific folders there. So your directory structure will look something like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*sy953R1CLa3EsGtPsy73wA.png" /></figure><p><strong><em>Note:</em></strong> You could have put your dev app icon files into the dev folder specifically as well. Android just looks into the flavor specific directory first, and if nothing is found there, then it falls back to the default directory called <strong>main</strong> and uses the resources found in that instead.</p><p>This is how the icons look on Android -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6Lc0gc8VD7r6cOKpyNzdw.png" /><figcaption>Both Flavors installed on the same device</figcaption></figure><ul><li><strong>Steps for iOS</strong></li></ul><p>We’ll jump back to Xcode for this one. We create app icon assets and then tell XCode to use different icons for different flavors. Check the gif…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xypye_bHeBkBjN5bENbX-w.gif" /><figcaption>Different AppIcons for different build configs in Xcode</figcaption></figure><p>Now when you build the app on iOS, you’ll get something like this -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*u-0PSm5qxF02W1ZHYZfevg.png" /><figcaption>Vola!</figcaption></figure><p>That’s all folks, hope this tutorial helps clear up any confusion in setting up flavors, especially on iOS. Below are some helpful articles / resources I came across while trying to get this to work.</p><h4>Supplementary resources</h4><ul><li>The github pull request which explains how Flutter Flavors (and build modes — debug, release, profile) map to the respective OS specific build constructs — <a href="https://github.com/flutter/flutter/pull/11734">https://github.com/flutter/flutter/pull/11734</a></li><li>For those of you interested in a deeper dive on how XCode builds your app — <a href="https://www.youtube.com/watch?v=yazY8hCO46s">https://www.youtube.com/watch?v=yazY8hCO46s</a></li><li>Source code for the flutter command line tool that runs the XCode build — <a href="https://github.com/flutter/flutter/blob/27b058a41473d5ef136f3874ed6f0a2ccaf969d0/packages/flutter_tools/lib/src/ios/xcodeproj.dart">https://github.com/flutter/flutter/blob/27b058a41473d5ef136f3874ed6f0a2ccaf969d0/packages/flutter_tools/lib/src/ios/xcodeproj.dart</a></li><li>For a detailed explanation on how to implement flavors in Dart Code — <a href="https://medium.com/flutter-community/flutter-ready-to-go-e59873f9d7de">https://medium.com/flutter-community/flutter-ready-to-go-e59873f9d7de</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27c5c5dac10b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why native app developers should take a serious look at Flutter]]></title>
            <link>https://medium.com/hackernoon/why-native-app-developers-should-take-a-serious-look-at-flutter-e97361a1c073?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e97361a1c073</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Wed, 08 Nov 2017 12:43:02 GMT</pubDate>
            <atom:updated>2017-11-09T09:03:58.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Before I start, in case you haven’t heard about it, <a href="https://flutter.io/">Flutter</a> is an app SDK (backed by Google) to build ‘<em>modern mobile apps</em>’. It is still in alpha, but comes with great documentation and tooling, with some production apps already out.</p><p>I am a hobbyist developer, and I recently launched an app using Flutter myself. It was such a pleasurable experience, that I <em>had</em> to share why I liked it so much.</p><h4>A little backstory…</h4><p>The app I made (called <a href="http://chipsoffury.com/">Chips of Fury</a>) is a virtual poker chips app (now live on the <a href="https://play.google.com/store/apps/details?id=com.kanily.chipsoffury">Play store</a> and <a href="https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=1292493748&amp;mt=8">App store</a>). It is for those times when you want to play poker (or any other card game) with friends, but don’t have a poker chip set available. So it is a non-trivial multi-player app, which requires real time sync between all devices as players play turns, with plenty of custom UI elements.</p><p>It took me about 1.5 months to code ‘Chips of Fury’ end-to-end, including my time spent learning Flutter. In my previous attempts to launch this app, I tried writing native apps in Android/Java and iOS/Swift, but left them both at varying degrees of completion. I just couldn’t get them to a ‘good enough to launch’ stage. The reason was mostly boredom, of doing the grunt work one needs to do to finish a project. So Flutter not only helped me build fast, more importantly, it helped me actually finish. It was that much fun! Needless to say, I’m a Flutter fan now.</p><h4>So is it like React Native?</h4><p>I bumped across Flutter 5–6 months back, and at that time I had bookmarked it for a future weekend of hacking. I did not delve into much detail then, and mentally bucketed it into the same category as <a href="https://facebook.github.io/react-native/">React Native</a>.</p><p>On a cursory look, the React Native comparison is pretty obvious. But on an ideological level, the similarities with RN start and end with the reactive programming model. IMHO, Flutter takes a <a href="https://www.youtube.com/watch?v=VUiVkDpikDI">generational leap forward</a> in terms of the ideas it has implemented upon. Just to be clear, I’ve tried using React only a couple of times, for learning purposes mostly. So I am not going to compare Flutter and React. In fact, I have a feeling that most developers are _not_ looking at Flutter seriously enough because of this mental bucketing with RN.</p><p>My goal is to try and convince native app developers (iOS/Swift/ObjC or Android/Java/Kotlin) to give Flutter a serious look. The fact that the same code can run on Android and iOS is arguably <em>not</em> the biggest reason why Flutter will impress you the most. Without further ado, here are the reasons why I feel Flutter is what the future of app development will look like. Listen up yo!</p><h3>1. It is all Dart</h3><p><a href="https://www.dartlang.org/">Dart</a> what? 😕. This is a common reaction, when I talk about Flutter to other fellow developers. And to be honest, <a href="https://www.dartlang.org/">Dart</a> does not offer much of a syntactical advantage compared to Swift or Kotlin.</p><p>However, I just wanted to stress on this point, because I think Google under-estimates how many developers don’t try out a new tool when they think they’ll have to learn a new language. So much so, that it wouldn’t matter even if it is technically superior.</p><p>So <strong>in Dart’s defence</strong>, it is a simple language to learn, and is unlikely to be a deterrent for trying Flutter out. Have a look at this sample class in Dart.</p><pre><strong>class </strong>Vehicle {<br>  <strong>final </strong>int numberOfWheels;<br>  <strong>final </strong>double mileage;<br>  <strong>final </strong>double horsePower;<br><br>  int speed = 0;<br><br>  Vehicle(<strong>this</strong>.numberOfWheels, <strong>this</strong>.mileage, <strong>this</strong>.horsePower);<br><br>  <strong>void </strong>accelerate() {<br>    speed = speed + 1;<br>  }<br><br>  <strong>void </strong>decelerate() {<br>    speed = speed - 1;<br>  }<br><br>  <strong>void </strong>brake() {<br>    speed = 0;<br>  }<br>}</pre><p>As you can see, it is pretty straightforward to read with syntax similar to most popular object oriented languages. Of course, there is some language specific syntactical sugar, and you can start writing code that is more concise once you learn the language, but my point is that the learning curve is rather small.</p><p>In fact, if you have not tried Swift/Kotlin, then Dart might be a good alternative to play around with.</p><p><strong>In Flutter’s defence</strong>: Google/Flutter had <a href="https://flutter.io/faq/#why-did-flutter-choose-to-use-dart">good reason to choose Dart</a>. The way Flutter works, it needs to create and destroy a large number of short lived objects very fast. Dart’s ‘garbage collection’ is very well suited for such a use case. And it shows in the performance of the apps that can be built using Flutter.</p><p>So assuming that you’ll not be writing off Flutter just because of Dart, let me proceed further.</p><h3>2. It is all Dart — Part II</h3><p>If you develop apps for Android or iOS, following IDE workflows are common-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWwGVIW98CLUd_mUz1eYjA.png" /><figcaption>Android Studio / XCode development flow when building screen layouts</figcaption></figure><p>And you’re also probably familiar with markup such as the following-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hfp1eKdNl5lmallgeTiztg.png" /><figcaption>Layout XML’s / JSX (React native)</figcaption></figure><p>In Flutter, layouts are defined using Dart code only. There is no XML / templating language. There’s no visual designer/storyboarding tool either.</p><p>My hunch is, upon hearing this, a number of you might even cringe a little. Prima facie, that was my reaction too. Isn’t it easier to do layouts using a visual tool. Wouldn’t writing all kinds of constraint logic in code make things overly complicated?</p><p>The answer for me turned out to be <strong>no</strong>. And boy! what an eye opener it has been. Let me try and make that case.</p><p>First of all.. meet Mr. <strong>Hot Reload</strong>.</p><p>Here is a sample with app code and the emulator side by side. This is a totally custom layout with a top and bottom bar and a middle container for the content. The code you see is the _whole_ code needed to run the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3Lry5LY0xTllLE7-p3fF-g.gif" /></figure><p>There is no separate layout xml, no xib file etc. The changes you make in code can be <strong>hot reloaded</strong> instantly. Hot reloads even preserve your application state, so you don’t even have to click and reach the screen you were on to proceed. I can’t stress enough how this is light years ahead of Android’s Instant Run, or any similar solution. It just works, even on large non-trivial apps. And it is crazy fast. That’s the power of Dart for you.</p><p>In practice, that makes a visual editor interface redundant. I did not miss XCode’s rather nice auto layout <em>at all</em>.</p><p>And as a result, I have been way more productive writing layouts in Flutter (Dart) than either Android/XCode. Once you get the hang of it (for me that meant a couple of weeks), there is a substantial overhead reduction because of very little context switching that is happening. One does not have to switch to a design mode, and pick a mouse and start clicking around. And then wondering if something has to be done programmatically, how to achieve that etc. Everything is programmatic. And the APIs are very well designed. It becomes intuitive soon and is much more powerful than the constructs offered by auto layout / layout XMLs.</p><h3>3. Flutter is reactive</h3><p>If you’ve never used a Reactive framework, then this might be a learning curve. The API prevents coding in an imperative style. To me this took a little bit of getting used to, but it has been a blessing (in disguise?).</p><p>For those of you who are aware of the reactive paradigm, you can skip the rest of this point. For the rest, I wanted to illustrate the reactive style using a small example. Have a look at this simple app. It shows ‘Hello &lt;name&gt;’ with the name that the user inputs, and lets the user select a color for the message as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/269/1*ZV5tGO0o7iUW-Y2HDZx9yw.gif" /></figure><p>Lets imagine how you would go about architecting such an app in native Android (or iOS). Since this is a simple one page app, lets just say we’ll code it all in a single Activity (or ViewController). In an imperative style, the structure would look something like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*gkgMvXelRxjTJf03qLWVVw.jpeg" /><figcaption>Imperative style of code</figcaption></figure><p><strong>How it works:</strong> There will be a listener to track changes in the TextField and the Dropdown values. On change we would be obtaining an instance of the Text label and calling the relevant methods to update its values. (It is likely that we will be keeping these values in some private instance variables to maintain state as well)</p><p>This means, that in a typical public API for a View in Android or iOS, you would find a number of getters and setters for various properties. For example, look at the public API for the TextView class in Android. I can’t reproduce it in full here as it is too long. The number of methods it has is in the hundreds — 259 to be exact, plus 4 constructors.</p><pre>Some methods in the Android TextView.java class</pre><pre>getText<br>setText<br>setTextSize<br>length<br>getLineHeight<br>getLayout<br>setCompoundDrawables<br>setCompoundDrawablesWithIntrinsicBounds<br>setPadding<br>getTextSize<br>setTextSize<br>getLetterSpacing<br>setLetterSpacing<br>setFontFeatureSettings<br>setTextColor<br>getTextColors<br>getCurrentTextColor<br>.<br>.<br>.<br>.<br>200+ more</pre><p>So each View has some specific properties which are exposed via these methods. It is not uncommon to find tens or hundreds of methods exposed by any given widget type, which let you customize its look &amp; feel and behavioural aspects to your heart’s content. Cool right? 😱</p><p>Now lets look at how the structure might look like in a reactive style of code…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*__pI7kJQYUO2MpDl9p9W7g.jpeg" /><figcaption>Reactive style of code</figcaption></figure><p><strong>How it works:</strong> There will be a listener to track changes in the TextField and the Dropdown values. On change we would be updating these values in the ‘global state’ and tell Flutter to repaint.</p><p>Flutter will automatically take care of figuring out what the Text label should look like.</p><p>This style of coding comes with a lot of advantages. For example, suppose the next version of this app has another greeting text widget added to it, that says “Bye”.</p><blockquote>Hello &lt;name&gt;. <br>Bye &lt;name&gt;.</blockquote><p>Now in the imperative style, the listeners will need to be updated to call the relevant setter methods on the new “Bye” text widget (or View) as well.</p><p>Whereas, in the reactive app, the listeners stay the same. They will continue to update the global state (as earlier). The new widget will simply repaint itself as per that state.</p><p>In complex apps, this style of coding really starts to shine. It is much simpler to maintain and reason about.</p><p>Another advantage is that the public API is hugely simplified. Although this is also due to the Widget architecture of Flutter (which is explained in the next point). To illustrate, have a look at the code for the Text widget in Flutter.</p><pre>class Text extends StatelessWidget {</pre><pre>const Text(this.data, {<br>    Key key,<br>    this.style,<br>    this.textAlign,<br>    this.textDirection,<br>    this.softWrap,<br>    this.overflow,<br>    this.textScaleFactor,<br>    this.maxLines,<br>  }) : assert(data != null),<br>       super(key: key);</pre><pre>/// The text to display.<br>  final String data;</pre><pre>  final TextStyle style;<br>  final TextAlign textAlign;<br>  final TextDirection textDirection;<br>  final bool softWrap;<br>  final TextOverflow overflow;<br>  final double textScaleFactor;<br>  final int maxLines;</pre><pre><a href="http://twitter.com/override">@override</a><br>  Widget build(BuildContext context) {...}</pre><pre><a href="http://twitter.com/override">@override</a><br>  void debugFillProperties(DiagnosticPropertiesBuilder description {...}<br>}</pre><p>It has a single constructor. And that’s about it. The other two methods are to be called by the framework. This is the <em>whole code</em> with the comments removed and a few lines removed from the overridden methods. Isn’t it elegant? It is possible in part because there are no setters and getters. The Widgets prefer to rebuild themselves using their constructor arguments, rather than mutating themselves using setters.</p><p><strong>Reactive vs imperative, the mindset change:</strong></p><p>I feel if you’ve always been coding in an imperative style, the appreciation for a reactive style comes once you actually try it out and it <em>clicks</em>💡. In the beginning, I spent a lot of time trying to figure out how I’ll call a method on a child widget to update its internal state (like the greeting label in our example). I was stuck in an imperative mindset of doing things.</p><p>I remember what lit a bulb in my head after struggling for a few days. It was a conversation I was having with a friendly member on the <a href="https://gitter.im/flutter/flutter">Flutter gitter channel</a>. Here was his advice (emphasis is mine).</p><pre>@rrousselGit<br><strong>A widget shouldn&#39;t visit it&#39;s children</strong>. It becomes messy. But you can access the state of your parents.</pre><pre>@animeshjain<br>hmm ok. perhaps i&#39;m still stuck with an imperative style of programming.</pre><pre>@rrousselGit<br><strong>Think in immutable</strong>. Don&#39;t update the child. Update the parent, and create a new batch of child. Once you get used to it, you realize it has a lot of advantages.</pre><p>The architecture in Reactive tends to be more around figuring out how to manage State. This deserves proper discussion in a separate series of articles, as there are multiple ways to doing it. But needless to say, once I got the hang of this style of coding, it was pretty awesome. Just speaking from the experience of having built a fully functional app now, I realise I have spent almost zero time on bugs caused by side effects!</p><h3>4. Everything is a widget</h3><p>I briefly touched upon how elegant and concise the Flutter widget APIs are in the previous point. This point will explain it further.</p><p><strong>What is a widget?</strong></p><p>For most developers, a widget typically invokes a mental picture of an element that renders on a screen and encapsulates some behaviour. The Android and iOS counterparts would be the various View classes.</p><p>Flutter has taken a different/broader view of this concept, and in the process has extended it beyond just structural elements. The widget architecture heavily favours composition over inheritance, thus making widgets much more powerful and composable (duh!). Quoting from <a href="https://flutter.io/technical-overview/">Flutter’s documentation</a> -</p><blockquote>A widget can define<br>- a structural element (like a button or menu)<br>- a stylistic element (like a font or color scheme)<br>- an aspect of layout (like padding)<br>and so on…</blockquote><p>Even a behaviour is a widget (like <a href="https://docs.flutter.io/flutter/widgets/GestureDetector-class.html">GestureDetector</a>). There is a type of widget that helps with state management (<a href="https://docs.flutter.io/flutter/widgets/InheritedWidget-class.html">InheritedWidget</a>), and one that helps build animations (<a href="https://docs.flutter.io/flutter/widgets/AnimatedWidget-class.html">AnimatedWidget</a>). Quoting again from the documentation-</p><blockquote>You can also control the <em>layout</em> of a widget by composing it with other widgets. For example, to center a widget, you wrap it in a Center widget. There are widgets for padding, alignment, row, columns, and grids. These layout widgets do not have a visual representation of their own. Instead, their sole purpose is to control some aspect of another widget’s layout. To understand why a widget renders in a certain way, it’s often helpful to inspect the neighboring widgets.</blockquote><p>By following “Composition &gt; Inheritance”, the widgets start from primitive ones, to some really complex ones. For eg. the <a href="https://docs.flutter.io/flutter/widgets/Container-class.html">Container widget</a> provided by Flutter is composed of a number of primitives</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*YPnhpNun4kA_qxsNowY4Lg.png" /><figcaption>Container is made of upto 7 nested widgets!</figcaption></figure><p>The ingenuity of this design strikes once you start building. The framework make it extremely easy to customise the look and feel of any stock widgets, and build your own if needed. And this has the effect of making the API footprint very small. For eg. every Text widget does not need a property called Padding. You simply wrap the Text widget with a Padding widget.</p><p>To repeat, they key thing to remember is… Composition over Inheritance. It is powerfully applied throughout Flutter’s API and makes it really elegant and simple.</p><h3>5. Say goodbye to Activity lifecycle management</h3><p>I’m not sure I’ve met anyone who has liked managing the lifecycle of an Activity (or Fragment or ViewController). As someone who does not develop apps on a day to day basis, I found them annoying to say the least, and a huge time suck in general.</p><p>Getting a Fragment to work inside an Activity, with asynchronous data loading and local state management might as well be some kind of black magic to me. So I did what an average engineer would do.. I copy pasted code, toiled through documentation, watched cat videos, tried to make it all work and life stuttered by.</p><p>Flutter takes away the fun in all that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*qzQSQNsLHg37uw_iUaYxgw.gif" /></figure><h3>6. Consistent 60 FPS (frames per second) performance</h3><p>Flutter apps compile to Native code, so the performance is as good as it gets. In fact, I found it to be much more suitable for building a game like app than using Java/Swift. Because of its reactive nature, writing UI code is much cleaner. And that combined with the performance characteristics, probably makes it a good contender for building games as well.</p><p>This article by <a href="http://twitter.com/wmleler1">@wmleler1</a> (developer advocate @ Google) does a great job of explaining why Flutter’s rendering is crazy fast - <a href="https://hackernoon.com/whats-revolutionary-about-flutter-946915b09514">https://hackernoon.com/whats-revolutionary-about-flutter-946915b09514</a>. I’ll just borrow from this article and post a few diagrams and quotes that present a TLDR version of it, comparing the three architectures - Native vs React Native vs Flutter.</p><p><strong>Native apps (Java/Swift)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*c4-dPk9FGweW7XawcLxYPQ.png" /><figcaption>How native Android/iOS code interacts with the platform</figcaption></figure><blockquote>Your app talks to the platform to create widgets, or access services like the camera. The widgets are rendered to a screen canvas, and events are passed back to the widgets. This is a simple architecture, but you pretty much have to create separate apps for each platform because the widgets are different, not to mention the native languages.</blockquote><p><strong>React Native apps (Javascript)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*kIH_djrXMlSsoYra92_S0g.png" /><figcaption>How React Native interacts with the platform</figcaption></figure><blockquote>React Native is very popular (and deserves to be), but because the JavaScript realm accesses the OEM widgets in the native realm, it has to <a href="https://medium.com/@talkol/performance-limitations-of-react-native-and-how-to-overcome-them-947630d7f440">go through the bridge</a> for those as well. Widgets are typically accessed quite frequently (up to 60 times a second during animations, transitions, or when the user “swipes” something on the screen with their finger) so this can cause performance problems. As <a href="https://medium.com/@talkol/performance-limitations-of-react-native-and-how-to-overcome-them-947630d7f440">one article about React Native</a> puts it:</blockquote><blockquote>Here lies one of the main keys to understanding React Native performance. Each realm by itself is blazingly fast. The performance bottleneck often occurs when we move from one realm to the other. In order to architect performant React Native apps, we must keep passes over the bridge to a minimum.</blockquote><p><strong>Flutter apps (Dart)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*1DiOFy8WN0dgoV16iK02BQ.png" /><figcaption>How Flutter interacts with the platform</figcaption></figure><blockquote>Flutter takes a different approach to avoiding performance problems caused by the need for a JavaScript bridge by using a compiled programming language, namely <a href="https://www.dartlang.org/">Dart</a>. Dart is compiled “ahead of time” (AOT) into native code for multiple platforms. This allows Flutter to communicate with the platform without going through a JavaScript bridge that does a context switch.</blockquote><blockquote>Flutter has a new architecture that includes widgets that look and feel good, are fast, and are customizable and extensible. That’s right, <strong>Flutter does not use the OEM widgets</strong> (or DOM WebViews), <strong>it provides its own widgets</strong>.</blockquote><blockquote>Flutter moves the widgets and the renderer from the platform into the app, which allows them to be customizable and extensible. All that Flutter requires of the platform is a canvas in which to render the widgets so they can appear on the device screen, and access to events (touches, timers, etc.) and services (location, camera, etc.).</blockquote><p>Do give that article a full read in case you want to understand Flutter’s performance better.</p><p>If you’re on Android, you can try the Flutter gallery app, it has some very cool animations showcased - <a href="https://play.google.com/store/apps/details?id=io.flutter.gallery">https://play.google.com/store/apps/details?id=io.flutter.gallery</a>. Here’s a gif from that app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*350ujaVYToF28-RAusHnbQ.gif" /></figure><p>(iOS app store does not list demo apps, so on iOS you’ll have to build it for yourself - <a href="https://github.com/flutter/flutter/tree/master/examples/flutter_gallery">https://github.com/flutter/flutter/tree/master/examples/flutter_gallery</a>)</p><p>This brings us to our penultimate, but one of the biggest wins of Flutter…</p><h3>7. Release on both android and iOS like a boss.</h3><p>Enough said!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*CK0PaBUo-uFpmpufwPOemQ.gif" /></figure><p>And last but not the least is…</p><h3>8. The Flutter Community</h3><p>This is a very important point because Flutter is new (and alpha). And from that perspective, the community support is <em>very</em> good. The <a href="https://gitter.im/flutter/flutter">Flutter gitter channel</a> has constant chatter and a good mix of newbies and experienced devs hanging out. Most of my questions got answered within a few hours there. For longer form questions, <a href="https://stackoverflow.com/questions/tagged/flutter">stackoverflow</a> is also answered pretty fast.</p><p>The Flutter dev team that hangs out on chat is very helpful. They’re very welcoming of new people and answering the simple questions that we tend to get stuck at. And in general I found the tone of the conversation to be humble and authentic. I think it bodes well for the future of the framework.</p><p>That’s all folks. I hope I’ve been able to convince you to play around with Flutter. The article is mostly talking about the positive aspects of Flutter, because in my development experience that is what my overwhelming experience was. That doesn’t mean there are no shortcomings.</p><p>The caveat is that Flutter is new, so there <em>are</em> known issues/limitations, and of course unknown ones that may come along. It is not within the scope of this article to address the limitations. Also, many limitations are a moving target and the Flutter dev team is closing stuff rapidly.</p><p>Listing some of the limitations here, that seem to be commonly brought up in the community -</p><ul><li>Inline maps are not supported yet - <a href="https://github.com/flutter/flutter/issues/73">https://github.com/flutter/flutter/issues/73</a></li><li>Lack of support for inline video. But a patch is in it seems and that should hit the master branch soon 🎉 🍻 - <a href="https://github.com/flutter/flutter/pull/12525">https://github.com/flutter/flutter/pull/12525</a></li><li>Instance state (Android) is not saved. So if the app gets killed in the background, you will lose state. There’s no simple way to handle this yet — <a href="https://github.com/flutter/flutter/issues/6827">https://github.com/flutter/flutter/issues/6827</a></li></ul><p>Acknowledgements: Thanks for proof reading and the suggestions - Brian Egan, Ajeet Kushwaha, Sajat Jain, Gaurav Karwa, Arpit</p><p><em>If you enjoyed this article, please share within your network. And if you play poker, try giving </em><a href="http://chipsoffury.com/"><em>Chips of Fury</em></a><em> (the app I made using Flutter) a spin.</em></p><p><em>Thanks!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e97361a1c073" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/why-native-app-developers-should-take-a-serious-look-at-flutter-e97361a1c073">Why native app developers should take a serious look at Flutter</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fliptrazon coupon search engine has been shut down]]></title>
            <link>https://medium.com/@animeshjain/the-fliptrazon-coupon-search-engine-has-been-shut-down-e1f11b592f05?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1f11b592f05</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 19:18:30 GMT</pubDate>
            <atom:updated>2016-08-04T19:18:30.068Z</atom:updated>
            <content:encoded><![CDATA[<p>It did not see much (any?) traction, so it became pointless to maintain it.</p><p>I’ll keep the b2b product up and running. So you can still use Fliptrazon to host your own offers page.</p><p>For eg. HealthKart hosts their offer page using Fliptrazon, here is the link:</p><p><a href="http://coupons.healthkart.com/">HealthKart Coupons, Offers &amp; Deals | HealthKart Promo Codes</a></p><p>It is pretty simple to use. It takes care of the hassle of removing expired coupons from your offers page etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1f11b592f05" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we are making Fliptrazon]]></title>
            <link>https://medium.com/@animeshjain/why-are-we-making-fliptrazon-21e4858d0ac8?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/21e4858d0ac8</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Tue, 02 Feb 2016 07:50:18 GMT</pubDate>
            <atom:updated>2016-02-02T07:51:35.861Z</atom:updated>
            <content:encoded><![CDATA[<p>We hate coupon sites. More specifically, coupon sites in their current avatar. They offer a poor user experience. And I used to hate them even more when I used to run marketing at <a href="https://www.healthkart.com/">HealthKart</a>. Let me quickly explain why, to set the context.</p><p>Almost all coupon sites make most of their money by earning affiliate commission. Affiliate commission is the commission on an order placed, that a retailer (such as Amazon or Flipkart), pays to the publisher that is driving traffic to them (for eg. Coupon sites). This is usually a very performance driven way to advertise for retailers, because they only pay when a sale happens, and not per click, or per impression.</p><p>However, from a retailer’s stand point, not all affiliate traffic is equal. The users that come from coupon sites are not usually new users. They are mostly users who already know about the retailer, and are just looking for a coupon to complete their checkout process. On the other hand, some other kinds of affiliate businesses work at the top of the funnel, for eg. <a href="http://www.indiabookstore.net/">IndiaBookStore</a>, a popular book search engine that I made a long time back, still works well for those who want to buy books in India.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1m005yX1Ro2YxPsoIEPEw.png" /><figcaption>typical flow of user traffic. coupon sites do not usually send traffic at the top of the funnel.</figcaption></figure><p>As a retailer, paying for the traffic coming from coupon sites does not make a lot of sense, as most customers are in the process of completing their checkout anyway. And naturally, the more clicks a coupon site sends to a retailers website, the more affiliate commission it stands to earn. So as a result, this is what coupon sites start to look like (the world over)-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RYPFCVCfel0fJsvtGY8kKQ.png" /><figcaption>screenshot from couponraja.in</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPQE2zGby8yhSndyHBK6-g.png" /><figcaption>screenshot from retailmenot.com</figcaption></figure><p>As you can see, some can be ad-filled disasters, while others can be more pleasing to look at but still irritating to use, with the commonality of those forced “click to see coupon codes” boxes.</p><p>We thought we could do a simpler, easier to use version of coupon sites. So this is how we started Fliptrazon. Our current avatar is the minimum viable product that we want to test waters with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*uf-KFFqHDzmshTqDppHB9Q.png" /><figcaption>Fliptrazon.com is much simpler and cleaner</figcaption></figure><p>You can easily copy and paste coupon codes and try them out without having to click hidden links, or without being bothered by windows opening in the background etc. We are also trying to be more genuine about the quality of traffic that retailers get from us. Since there are no click-baits, it means we “drive” lesser traffic.</p><p>We will be working on interesting ways to drive traffic to retailers in the future. All the while, we want to give user experience the highest pedestal.</p><p>The common irritants still remain to be tackled more effectively. Such as, those of us who use coupons a lot, know that most of the listed coupons do not work. We’re trying to do some creative solutions to those problems as well.</p><p>Give <a href="http://fliptrazon.com/">Fliptrazon.com</a> a try the next time you look for coupons and let us know what you think! As of now, it only lists coupons from Indian sites.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21e4858d0ac8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Fliptrazon blog]]></title>
            <link>https://medium.com/@animeshjain/welcome-to-fliptrazon-blog-b79f7ee132e1?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b79f7ee132e1</guid>
            <category><![CDATA[startingline]]></category>
            <category><![CDATA[launch]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 06:08:09 GMT</pubDate>
            <atom:updated>2016-01-26T06:21:13.383Z</atom:updated>
            <content:encoded><![CDATA[<p>Where the making of the bot, and the stories around it, shall live on for eternity &lt;Grand music playing&gt;</p><p>OK lets get back to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*3DwJhPdy8hI9dPn1oOUaNg.png" /><figcaption><a href="https://xkcd.com/1596/">https://xkcd.com/1596/</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b79f7ee132e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pessimism]]></title>
            <link>https://medium.com/@animeshjain/pessimism-5505063ec8df?source=rss-c79f92aa50a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5505063ec8df</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[optimism]]></category>
            <dc:creator><![CDATA[Animesh Jain]]></dc:creator>
            <pubDate>Fri, 22 Jan 2016 10:59:44 GMT</pubDate>
            <atom:updated>2017-11-19T05:21:59.283Z</atom:updated>
            <content:encoded><![CDATA[<p>Going into something unknown, one of my instincts is to think about what all can go wrong. I may take it to extremes in some cases too (like what if.. death!). This is often taken as me being a pessimist. A friend of mine hinted at the same conclusion just yesterday and I mumbled something about me being an unlikely pessimist, after all I like to pursue lofty goals, try things that may be unlikely to succeed etc.</p><p>I thought I’ll put down a better articulation of why I (and others who do the same) think like that. It is easy to brand it as “negative thinking”, but hear me out..</p><p>In a way, this may be a trait acquired from an engineering background. As an engineer we like to think of failure cases. In fact, we design for failure (and a little bit beyond)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fgg_bIMJ7I0M%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dgg_bIMJ7I0M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fgg_bIMJ7I0M%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5552f4f151bffa72034b016e5ad57d94/href">https://medium.com/media/5552f4f151bffa72034b016e5ad57d94/href</a></iframe><p>In my opinion, the so called “negative thinking” is quite the opposite to being a pessimistic approach. It is something that sets the foundations for optimism. If optimism were to be based on failure scenarios not occurring at all, I would compare that to making a building assuming that the earthquake will never strike. On the other hand, since we do not know the future, and have no way to predict it either, it is safe to assume that failure will happen (in life, as in business), and to build with that knowledge. It helps in being better prepared, when that earthquake does strike.</p><p>So to me optimism is in knowing</p><ul><li>that bad things <em>will</em> happen</li><li>we <em>will</em> take a few tumbles</li><li>and maybe even a few battles <em>will</em> be lost</li></ul><p>Eventually, we <em>will</em> prevail.</p><p>PS. My post is titled pessimism, kill me!</p><p>This is a repost from <a href="http://www.animeshjain.com/pessimism/">http://www.animeshjain.com/pessimism/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5505063ec8df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>