<?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 Nitya Narasimhan, PhD on Medium]]></title>
        <description><![CDATA[Stories by Nitya Narasimhan, PhD on Medium]]></description>
        <link>https://medium.com/@nitya?source=rss-6cb0ee65d029------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rtALJz38bhvudeEgKxMFhA.jpeg</url>
            <title>Stories by Nitya Narasimhan, PhD on Medium</title>
            <link>https://medium.com/@nitya?source=rss-6cb0ee65d029------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nitya/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[#4 — The Rendering Pipeline]]></title>
            <link>https://medium.com/flutter-camp/4-the-rendering-pipeline-45c5baf5e763?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c5baf5e763</guid>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 20:46:56 GMT</pubDate>
            <atom:updated>2018-06-18T20:46:58.508Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Coming up soon..</em></p><p>An article diving into how Flutter renders the UI based on this video and other learnings from trawling the Flutter docs. <strong>Stay tuned for the updated post.</strong></p><p>Till then, go watch the video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUUfXWzp0-DU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUUfXWzp0-DU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUUfXWzp0-DU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/201561428e530908e82ff352d9006cdd/href">https://medium.com/media/201561428e530908e82ff352d9006cdd/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c5baf5e763" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-camp/4-the-rendering-pipeline-45c5baf5e763">#4 — The Rendering Pipeline</a> was originally published in <a href="https://medium.com/flutter-camp">Flutter Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#3 — Build a More Complex App]]></title>
            <link>https://medium.com/flutter-camp/3-build-a-more-complex-app-2165290f746?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/2165290f746</guid>
            <category><![CDATA[fluttercamp]]></category>
            <category><![CDATA[flutterfyi]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 20:33:22 GMT</pubDate>
            <atom:updated>2018-06-18T20:35:19.926Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is from a series of articles I’m putting together for FlutterCamp 2018. Read more about it in the </em><a href="https://medium.com/flutter-camp/flutter-camp-2018-7f916f145324"><em>first article of the series here</em></a><em>.</em></p><p>Woot! At this point you have your <a href="https://medium.com/flutter-camp/this-is-from-a-series-of-articles-im-putting-together-for-fluttercamp-2018-c1893b085d38">development environment setup</a> — you verified it by creating and running your first app on a real or virtual device. Let’s keep going.</p><p>Next, we explore the <a href="https://flutter.io/get-started/codelab/">simple Startup Namer app tutorial</a> to build a custom app from the scaffold. We’ll learn a bit about how Flutter apps are structured, about the importance (and power) of widgets.</p><p><em>Don’t worry about the </em><a href="https://dartlang.org/"><em>Dart</em></a><em> syntax for now. We’ll do a deep dive on that soon. For now, know that if you have experience with Java, JavaScript or Swift, you can immediately grok the code and get a sense for the development patterns. That is all we want to achieve at this stage.</em></p><h3>STEP-1: Goal = Startup Namer app</h3><p>This is an app that generates potential names for a new startup. We can use this to learn the following key concepts:</p><ul><li><strong><em>Views &amp; Layout</em></strong><em> — we’ll build the one in </em><a href="https://flutter.io/get-started/codelab/images/startup-namer-app.gif">this image</a></li><li><strong><em>Interaction Events &amp; Handling</em></strong><em> — users can select/unselect names</em></li><li><strong><em>Infinitely scrolling, lazily-loaded list</em></strong><em> — add 10 at a time on scroll ups</em></li><li><strong><em>Theming</em></strong> (how to change look and feel of UI)</li><li><strong><em>Packages</em></strong> (and using them to to extend core Flutter functionality)</li></ul><p><em>NN&gt; Plus, a little bit about how Flutter apps are structured, the role of widgets, state management and stateful hot reload.</em></p><h3>STEP-2: Starting Point = Scaffolded App</h3><p>Walk through the basic steps of creating a new Flutter app as before, but call it <em>startup_namer. </em>Open lib/main.dart, delete existing code and replace it with this code as explained <a href="https://flutter.io/get-started/codelab/#step-1-create-the-starting-flutter-app">in Step 1</a>.</p><pre>import &#39;package:flutter/material.dart&#39;;</pre><pre>void <strong>main()</strong> =&gt; runApp(new MyApp());</pre><pre>class MyApp extends <strong>StatelessWidget</strong> {<br>  @override<br>  <strong>Widget build</strong>(BuildContext context) {<br>    return new <strong>MaterialApp</strong>(<br>      title: &#39;Welcome to Flutter&#39;,<br>      home: new Scaffold(<br>        appBar: new AppBar(<br>          title: new Text(&#39;Welcome to Flutter&#39;),<br>        ),<br>        body: new Center(<br>          child: new Text(&#39;Hello World&#39;),<br>        ),<br>      ),<br>    );<br>  }<br>}</pre><p><em>NN&gt; This requires nothing more than delete-save-reload. No issues for me. However some observations …</em></p><h4>OBSERVATIONS:</h4><ol><li><strong>Functions vs. Classes: </strong>Note that the same file contains both top-level functions and top-level classes.<em>.</em></li><li><strong>Line 1</strong>: `import &#39;package:flutter/material.dart&#39; brings the relevant Dart packages into your codebase. In this case, we are importing the <a href="https://flutter.io/widgets/material/">Material package</a> which provides all the classes (visual, behavioral and motion-rich widgets) implementing <a href="https://material.io/design/introduction/">Google’s Material Design</a> for Flutter.</li><li><strong>Line 2:</strong> `void main() =&gt; runApp(new MyApp()); is the mandatory entry point for a Flutter app. It calls the <a href="https://docs.flutter.io/flutter/widgets/runApp.html">runApp function</a> which inflates the provided widget (here an instance of MyApp) and attaches it to the screen with constraints that force it to <em>fill the full screen.</em> To have a custom widget not fill the screen, wrap it in Center or Align widgets (which then fill it up)</li><li><strong>Line: </strong>MyApp extends StatelessWidget shows that your custom widget is a Stateless one; we’ll learn about Stateless &amp; Stateful widgets later.</li><li><strong>Everything in Flutter is a widget; everything.</strong> The style (alignment, padding etc.), the layout, the behaviors (gesture, touch etc.) are all widgets. And UI development is all about widget composition. The key is the <strong>build </strong>function that describes how to assemble that widget’s subtree (from lower-level widgets). <em>To learn how Flutter transforms a widget tree into pixels on a screen, </em><a href="https://www.youtube.com/watch?v=UUfXWzp0-DU"><em>watch this talk</em></a><em>.</em></li><li><strong>MaterialApp, Scaffold &amp; AppBar.</strong> <a href="https://docs.flutter.io/flutter/material/MaterialApp-class.html&#39;">MaterialApp</a> is a stateful convenience widget that wraps a number of widgets commonly required for Material Design. It also works with the top-level Navigator to map routes correctly.</li></ol><h3>STEP-3: Dependencies = Add external package</h3><p>Many third-party Dart packages for Flutter exist on <a href="https://pub.dartlang.org/flutter/">pub.dartlang.org</a>. Work through <a href="https://flutter.io/get-started/codelab/#step-2-use-an-external-package">the Step 2 directions</a> to add the <em>english_words</em> package and use that to randomly select a new english word to show in the onscreen message.</p><p><strong>Steps:<br></strong>1. Add english_words dependency in <strong>pubspec.yaml<br>2. </strong>When in that file, click <em>get package icon</em> (top right) to fetch the package<br>3. Add import &#39;package:english_words/english_words.dart&#39;; in main.dart<br>4. Then use it e.g., final wordPair = new WordPair.random();</p><p><em>NN&gt; This was a fairly painless process for me. No issues. Things to explore: what happens when an imported package has its own dependencies?</em></p><h3>STEP-3: Stateful Widget = Add new</h3><p>Work through <a href="https://flutter.io/get-started/codelab/#step-3-add-a-stateful-widget">the Step 3 directions</a> to build out the first Stateful Widget.</p><p><em>NN&gt; This was also a straightforward step. But let’s spend a few minutes here talking about some interesting aspects.</em></p><h4>OBSERVATIONS:</h4><ol><li>You can define multiple classes and functions in the same source file.</li><li>The StatefulWidget does little more beyond creating its associated State instance; it’s the latter that does the heavy lifting on widget creation here.</li><li>Both the StatelessWidget and StatefulWidget <em>classes</em> are immutable; their properties cannot be changed once created. The latter however has an associated mutable State object that persists for the lifetime of the widget.</li><li>You can see how your UI can be iteratively designed and built by composing it out of lower-level stateful and stateless widgets. We’ll talk about state management later.</li></ol><h3>STEP-4: List View = Infinite Scroll</h3><p>Work through<a href="https://flutter.io/get-started/codelab/#step-4-create-an-infinite-scrolling-listview"> step 4 of the tutorial</a> to create a list of names that the user can scroll through, infinitely.</p><p><em>NN&gt; This was also a straightforward step. But the interaction between the ListView, the ListView.builder and the helper “_build” functions can be a bit complicated to untangle.</em></p><h4>OBSERVATIONS:</h4><ol><li><strong>Private Variables. </strong>In Dart, prefixing a variable with an underscore (_) automatically makes that a private variable. So here, a number of defined class variables and functions are visible only within the class/instance.</li><li><strong>Everything’s a Widget.</strong> And widgets can be composed of other widgets to create custom complex views. And so on until you get to the lowest-level (nodes) where you’ll likely be using <a href="https://flutter.io/widgets/">a standard Flutter widget</a> as core. So one way to develop UI is to start by returning a core widget from the build method — then refactoring just that method to wrap the core widget in another widget that provides additional capability; this could for example be a container widget which now lets you return a complex or managed layout instead of a single widget.</li><li><a href="https://docs.flutter.io/flutter/widgets/ListView-class.html"><strong>ListView</strong></a> is a widget that represents a scrollable set of widgets arranged linearly —when using builder (itemBuilder) it takes a context and an index that increases monotonically. You simply return the ListTile widget for that index if you can create one — so you can create an infinitely scrolling list if you make sure you always return something for each index.</li></ol><p><em>The main thing to look at and understand here is that the code looks more complex than it is because it has all been inlined. Later, we can see how we can make the code clearer to read by simply abstracting out some of this into private functions that are invoked instead.</em></p><h3>STEP-5: Interactivity = Event handling</h3><p>Work through <a href="https://flutter.io/get-started/codelab/#step-5-add-interactivity">step 5 of the tutorial.</a></p><p><em>NN&gt; This was also a straightforward step. The key to understand here is the usage of setState() to trigger state changes, which in turn cause render tree to be re-evaluated and re-rendered with the updated state. In this case, it means we go from showing a clear heart to a colored heart (or vice versa) after each click.</em></p><h3>STEP-6: Navigation = Route handling</h3><p>Work through<a href="https://flutter.io/get-started/codelab/#step-6-navigate-to-a-new-screen"> step 6 of the tutorial</a></p><p><em>NN&gt; This is an interesting step to stop and think about since it’s the first place where navigation enters the equation. Let’s talk about Navigator, MaterialApp and the MaterialPageRoute first, then look at code.</em></p><p><strong>The</strong><a href="https://docs.flutter.io/flutter/widgets/Navigator-class.html"><strong> Navigator</strong></a><strong>: </strong>is a Flutter core widget that manages a set of child widgets as a “stack” using <a href="https://docs.flutter.io/flutter/widgets/Overlay-class.html">an Overlay</a> pattern. Overlay allows a widget to be floated above another, to showcase relative importance or provide visual transition effects. If widgets are full-screen, then Navigator effectively creates the illusion of moving from screen to screen (pages) by floating widgets up and down in the Overlay.</p><p><em>This is how routing gets handled (with widgets mapped to routes).This behavior will be very familiar to web developers particularly given the named routes use the path/a/b/c structure for </em><strong><em>named routes.</em></strong></p><p><a href="https://docs.flutter.io/flutter/material/MaterialApp-class.html"><strong>MaterialApp: </strong></a>You can create a Navigator for your app, or use one from MaterialApp or WidgetsApp (if they are managing the root of your widget tree). Use Navigator.push(context, new MaterialPageRoute&lt;void&gt;( ... )) to push a new route onto the stack on demand; the MaterialPageRoute takes a builder function which can create the page (widget) to show, and also handle the Navigator.pop(context) behavior to return “back” to the previous screen.</p><p><em>If you use MaterialApp with Scaffold, it automatically adds a”back” button in AppBar that pops the Navigator stack for you in any context.</em></p><p><a href="https://docs.flutter.io/flutter/widgets/Navigator-class.html"><strong>Routes can return a value.</strong></a> This is cool. It is analogous to <em>startActivityFor Result</em> in Android where, when you trigger the new screen (Navigator.push) you do so with the intent of taking the user to a new screen from which you expect a result to be returned when he is don (Navigator.pop).</p><p><em>There is also support for popup routes (modal part-screen overlays) and custom routes (to control the animations on transition for that route).</em></p><h3>STEP-7: Theming = Changing look &amp; feel</h3><p>Work through <a href="https://flutter.io/get-started/codelab/#step-7-change-the-ui-using-themes">step 7 of the tutorial</a></p><p><em>NN&gt; Theme controls look &amp; feel of the app. Changing an app’s theme is as simple as configuring the ThemeData class at the top-level widget (e.g., MaterialApp).</em></p><p><strong>Exercise</strong>: Check out <a href="https://docs.flutter.io/flutter/material/ThemeData-class.html">ThemeData</a> capabilities and make other changes to see how you can customize the theme more rigorously. Here is the list of attributes that can be changed:</p><pre><a href="https://docs.flutter.io/flutter/material/ThemeData/ThemeData.html">ThemeData</a>({</pre><pre><a href="https://docs.flutter.io/flutter/services/Brightness-class.html">Brightness</a> brightness, <br><a href="https://docs.flutter.io/flutter/material/MaterialColor-class.html">MaterialColor</a> primarySwatch, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> primaryColor,<br><a href="https://docs.flutter.io/flutter/services/Brightness-class.html">Brightness</a> primaryColorBrightness, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> primaryColorLight, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> primaryColorDark, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> accentColor, <br><a href="https://docs.flutter.io/flutter/services/Brightness-class.html">Brightness</a> accentColorBrightness, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> canvasColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> scaffoldBackgroundColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> bottomAppBarColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> cardColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> dividerColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> highlightColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> splashColor, <br><a href="https://docs.flutter.io/flutter/material/InteractiveInkFeatureFactory-class.html">InteractiveInkFeatureFactory</a> splashFactory, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> selectedRowColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> unselectedWidgetColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> disabledColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> buttonColor, <br><a href="https://docs.flutter.io/flutter/material/ButtonThemeData-class.html">ButtonThemeData</a> buttonTheme, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> secondaryHeaderColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> textSelectionColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> textSelectionHandleColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> backgroundColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> dialogBackgroundColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> indicatorColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> hintColor, <br><a href="https://docs.flutter.io/flutter/dart-ui/Color-class.html">Color</a> errorColor, <br><a href="https://docs.flutter.io/flutter/dart-core/String-class.html">String</a> fontFamily, <br><a href="https://docs.flutter.io/flutter/material/TextTheme-class.html">TextTheme</a> textTheme, <br><a href="https://docs.flutter.io/flutter/material/TextTheme-class.html">TextTheme</a> primaryTextTheme, <br><a href="https://docs.flutter.io/flutter/material/TextTheme-class.html">TextTheme</a> accentTextTheme, <br><a href="https://docs.flutter.io/flutter/material/InputDecorationTheme-class.html">InputDecorationTheme</a> inputDecorationTheme, <br><a href="https://docs.flutter.io/flutter/widgets/IconThemeData-class.html">IconThemeData</a> iconTheme, <br><a href="https://docs.flutter.io/flutter/widgets/IconThemeData-class.html">IconThemeData</a> primaryIconTheme, <br><a href="https://docs.flutter.io/flutter/widgets/IconThemeData-class.html">IconThemeData</a> accentIconTheme, <br><a href="https://docs.flutter.io/flutter/material/SliderThemeData-class.html">SliderThemeData</a> sliderTheme, <br><a href="https://docs.flutter.io/flutter/material/ChipThemeData-class.html">ChipThemeData</a> chipTheme, <br><a href="https://docs.flutter.io/flutter/foundation/TargetPlatform-class.html">TargetPlatform</a> platform </pre><pre>})</pre><h3>ERROR: How do you know something’s wrong?</h3><p>The awesome thing about Flutter development is that the simulator/emulator immediately provides feedback through the <em>red screen of death.</em> The descriptions are verbose giving you insights into where the problem lies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*xwP6l8FtAOUAIPT9-d84lQ.png" /><figcaption>The red screen of death</figcaption></figure><p>You can quickly explore ideas by undoing recent changes, commenting-out and modifying the sections identified (e,g, if the offending widget is RandomWords, start there..). Hot reload makes it possible to track and fix at least UI related errors, relatively quickly.</p><h3>EXPLORATION IDEAS</h3><p><em>Try out some of these things to get a better sense for the development environment:</em></p><ol><li><strong>Change ThemeData</strong> properties and see how that affects</li><li>Change <strong>the ListView builder</strong> to use a different kind of item widget. See how that impacts the scrolling and appearance.</li><li><strong>Explore routing options</strong>. Try to create a new route and associated widget and see if you get the default Back behavior.</li></ol><h3>OPEN ISSUES</h3><p><em>I’ll use this section to capture any issues experienced by attendees at the workshop. In particular, I am interested in seeing if the process/experience for attendees on Windows or Linux development environments is as painless.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2165290f746" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-camp/3-build-a-more-complex-app-2165290f746">#3 — Build a More Complex App</a> was originally published in <a href="https://medium.com/flutter-camp">Flutter Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#2 — Getting Started]]></title>
            <link>https://medium.com/flutter-camp/this-is-from-a-series-of-articles-im-putting-together-for-fluttercamp-2018-c1893b085d38?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1893b085d38</guid>
            <category><![CDATA[flutterfyi]]></category>
            <category><![CDATA[dartlang]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[fluttercamp]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 04:26:32 GMT</pubDate>
            <atom:updated>2018-06-18T17:55:11.677Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is from a series of articles I’m putting together for FlutterCamp 2018. Read more about it in the </em><a href="https://medium.com/flutter-camp/flutter-camp-2018-7f916f145324"><em>first article of the series here</em></a><em>.</em></p><p>At this point, I am assuming you have just arrived at a FlutterCamp event (in person) or learnt about Flutter (online). So where do you go next?</p><h3>2a. Get Flutter SDK set up.</h3><p>If you haven’t already done so, <a href="https://flutter.io/setup-macos/">follow these instructions</a> to get the <a href="https://flutter.io/setup-macos/#get-sdk">Flutter SDK </a>installed in your development platform. I use MacOSX and I found the process fairly painless.</p><h3>2b. Verify Flutter SDK set up.</h3><p>Once installed, run<em> </em>flutter doctor<em> </em>to verify your development environment is ready. You should see recommendations to fix any missing dependencies if not. If, like me, you had installed an earlier version of flutter (e.g., alpha), run flutter upgrade and you should be set.</p><p><strong>For reference, this is my current flutter setup:</strong></p><pre>$ flutter doctor<br>Doctor summary (to see all details, run flutter doctor -v):<br>[✓] Flutter (Channel beta, v0.4.4, on Mac OS X 10.13.4 17E199, locale en-US)<br>[✓] Android toolchain - develop for Android devices (Android SDK 28.0.0-rc1)<br>[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)<br>[✓] Android Studio (version 3.1)<br>[✓] IntelliJ IDEA Ultimate Edition (version 2018.1.4)<br>[!] VS Code (version 1.24.1)<br>[✓] Connected devices (1 available)</pre><p><em>I currently have an issue with flutter doctor incorrectly reporting VSCode missing a Dart extension (hence the “!” on that line) but otherwise you should see something similar, customized to your development platform.</em></p><p><strong><em>Update: </em></strong><em>The author </em><a href="https://twitter.com/DanTup/status/1008577107654512640"><em>has a PR out to fix the issue</em></a><em> but it is not a show-stopper (your code will still compile, run etc.) so for now, we’ll just ignore this.</em></p><h3>2c. Get Target Platform support set up.</h3><p>Flutter can be used to develop apps for both Android and iOS devices. Have at least one of these environments available — see <a href="https://flutter.io/setup-macos/#ios-setup">these instructions for iOS setup</a> and <a href="https://flutter.io/setup-macos/#android-setup">these instructions for Android setup</a>.</p><p>This includes ensuring that the required development SDKs are installed, but also setting up virtual targets for these environments — e.g., the iOS simulator and the Android emulator.</p><p><em>In my case, since I am on MacOS I elected to get both setup. For quick prototyping and testing, I elect to use the iOS simulator using</em>open -a Simulator <em>to run it from the command line.</em></p><p><em>To test against both devices, I have been switching over to the Android Studio IDE and using that to launch Android emulators — however, I am currently exploring VS Code. I will update this section with insights when done.</em></p><h3><strong>2d. Configure Editor.</strong></h3><p>The <a href="https://flutter.io/get-started/editor/#vscode">Flutter docs page</a> will identify Android Studio and VS Code as the two top-level tabs for editors. If you open the Android Studio tab, you can also find instructions for using the IntelliJ IDEA editor. I’ve used all three; IntelliJ IDEA and Android Studio are similar; no surprise — they’re both from JetBrains.The Android Studio and IntelliJ IDEA installs were routine. The VS Code install also was effortless.</p><p><em>Note: you don’t need all these editors installed. Just pick one.</em></p><p><em>Technically, you can get away with using just the Flutter CLI (comes with their SDK) and any text editor (no IDE needed). However the IDE provides visual tools (e.g., Flutter widget inspector) that simple text editors don’t. Tradeoffs are in speed vs. capability. Pick your lane. It’s fairly painless to switch between lanes at any point so you don’t risk much with your decision.</em></p><h3>2e. Your First Test App</h3><p>The Flutter docs provide instructions for <a href="https://flutter.io/get-started/test-drive/#androidstudio">Android Studio</a>, <a href="https://flutter.io/get-started/test-drive/#vscode">VS Code </a>— and also simple <a href="https://flutter.io/get-started/test-drive/#terminal">text editor + CLI</a>. I have used both the first and last options multiple times with no issues — so just jump in if you want to go that route.</p><p><em>I am currently getting my feet wet with VS Code so all my notes/observations here will reflect usage of that editor.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*cNDZgHJxcpGdAG9jbpgKgw.png" /><figcaption>Boilerplate “Hello World” app on Flutter</figcaption></figure><p><strong>Create the App (VS Code)<br></strong>View-Command Palette. <br>Type <em>flutter. <br></em>Pick <strong><em>Flutter:New Project Action</em></strong></p><p><strong>Enter project name</strong>. <em>Lower-case, separate by underscores if needed.<br></em>Select destination folder; wait for build to finish. You’ll get a “Your Flutter project is ready” notification at bottom right.</p><p><strong>Run the App. </strong>Check there to see if device is selected. <em>I had iOS Simulator already running.</em></p><p><strong>Press F5 to launch app</strong> in that device. <em>You should see a screen like the one shown here.</em></p><p><strong>Try Hot Reload.<br></strong>Make a change to some aspect of the code e.g., the color value in “primarySwatch:Colors.blue”. Then just save the change to trigger hot reload. <em>You can also click the green refresh button at top of editor)</em> — demonstrates hot stateful reload of Dart/Flutter.</p><p>At this point, take a deep breath and go drink some coffee. You are now ready to start exploring other tutorials, codelabs and ideas. Your environment is ready!</p><h3>EXPLORATION IDEAS</h3><p>Try out some of these things to get a better sense for the development environment:</p><ol><li><strong>Flutter CLI. </strong>Take a few minutes to play around with the Flutter Command Line Interface using flutter --help to get a sense of available commands. Try creating the app from command line, then running and reloading it from there without using the editor/IDE. <em>NN-TODO: Make a dedicated post about Flutter CLI explaining commands &amp; options …</em></li><li><strong>Hot Reload. </strong>Use the editor or IDE for this so you can trigger hot reload on each save for a more intuitive understanding.</li></ol><h3>OPEN ISSUES</h3><p><em>I’ll use this section to capture any issues experienced by attendees at the workshop. In particular, I am interested in seeing if the process/experience for attendees on Windows or Linux development environments is as painless.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1893b085d38" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-camp/this-is-from-a-series-of-articles-im-putting-together-for-fluttercamp-2018-c1893b085d38">#2 — Getting Started</a> was originally published in <a href="https://medium.com/flutter-camp">Flutter Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#1 — Flutter Camp 2018]]></title>
            <link>https://medium.com/flutter-camp/flutter-camp-2018-7f916f145324?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f916f145324</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[fluttercamp]]></category>
            <category><![CDATA[google-developer-group]]></category>
            <category><![CDATA[dartlang]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Sun, 17 Jun 2018 22:01:40 GMT</pubDate>
            <atom:updated>2018-06-18T04:30:24.571Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello and welcome to <a href="https://medium.com/flutter-camp">Flutter-Camp on Medium</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/1*cqiYrx3XtjeRb1ebQMsphw.jpeg" /><figcaption>Flutter is now in beta 3. Image Credit: Captured by @nitya at Google IO2018</figcaption></figure><h3><strong>About this Publication</strong></h3><p>I recently began my journey exploring the <a href="https://www.flutter.io/">Flutter SDK</a>, first out of curiosity and then out of enthusiasm. Two reasons why — first, I loved the engineering story behind it and their emphasis on performance first; and second, I’ve always wanted to build mobile apps that I could ship to multiple platforms, and this seemed a way to get that list item checked off.</p><p><em>So why this publication?</em></p><p>Well I actually started writing a bit about it in the past few months — some articles on dev.to under their <a href="https://dev.to/t/flutter">#flutter tag</a> and a dedicated <a href="http://www.flutter.fyi/">Blogger site</a> and <a href="https://twitter.com/flutterfyi">Twitter account</a> under a “<strong>Flutter FYI”</strong> brand that I hope to build upon and focus on for the long term.</p><p>But for the short term, I needed a way to quickly put together notes and resources for a real-world full-day workshop event that I will be co-organizing at Google NYC along with my peer GDG co-organizers from: <em>Rainer (GDG New Haven) </em>and <em>Adam (GDG Hampton Roads)</em>.</p><p>We’re also super fortunate that <em>Will Larche (Flutter team, Material Design Lead)</em> is based out of NYC and will be there to keynote the event and help support our full-day learning after.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZZB-vUd2Y5W1sP8IAK-aAQ.png" /><figcaption>Flutter Camp 2018: Learn more at https;//flutter.camp</figcaption></figure><p>The goal for the workshop is to get us quickly and rapidly to the point where we’ve learned the basic concepts of Flutter, setup development environments, completed basic codelabs (to reinforce concepts and validate setup) and are ready to think about free-form exploration of ideas as a group.</p><p><strong>Show-n-Tell Challenge</strong>: In fact we have an interesting idea that we want to try out. Spend the afternoon (1–4pm) extending/modifying a codelab or starting from scratch on a new app — build it out and demo it by 4pm for glory, prizes and community gratitude! That’s the promise of Flutter. That you can actually get up to speed with the tools &amp; concepts in a single morning, and be productive enough by afternoon to show something unique. #LetsDoThis</p><p><strong>Want to participate? </strong><a href="http://bit.ly/2018-fluttercamp-cfp">Register here for an invite</a> but note that the form closes Jun 20. Selected participants will be sent invitations that week and required to confirm their participation within 24 hours or release their seats to wait list. Our hope is to have <strong>100 participants</strong> join us for the day, with at least <strong>50 participants</strong> making it all the way to the end for the Show-n-Tell challenges. Let’s see how we do.</p><p>Alright enough about that. Back to this post. This serves as a roadmap for that FlutterCamp. Hope to post an article a day from now till Jun 30, exploring codelabs, content and tutorials so folks attending have a frame of reference for comparison.</p><h3>Articles</h3><p><em>Check back here for links to articles posted under this publication, gathered into meaningful subtopics..</em></p><p>1. <a href="https://medium.com/p/7f916f145324/edit">About Flutter Camp</a> (this article)<br> 2. <a href="https://medium.com/flutter-camp/this-is-from-a-series-of-articles-im-putting-together-for-fluttercamp-2018-c1893b085d38">Getting Started</a></p><h3>Resources</h3><p><em>Please refer to the </em><a href="https://dev.to/nitya/flutter-learning-resources-for-beginners-5719"><em>Flutter Resources for Beginners</em></a><em> post — I hope to keep that updated and make it the centralized resource for current and future use.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f916f145324" width="1" height="1" alt=""><hr><p><a href="https://medium.com/flutter-camp/flutter-camp-2018-7f916f145324">#1 — Flutter Camp 2018</a> was originally published in <a href="https://medium.com/flutter-camp">Flutter Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#1 Coding Fearlessly: Origin Story]]></title>
            <link>https://medium.com/@nitya/coding-fearlessly-origin-story-d5c7b333efb?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5c7b333efb</guid>
            <category><![CDATA[studycamp]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[nanowrimo]]></category>
            <category><![CDATA[parse]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 18:12:56 GMT</pubDate>
            <atom:updated>2017-11-02T18:17:42.867Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the first of a series of posts where I will explore the Firebase platform in all its splendor, touching upon the good, the bad, and the “OMG what happened!” aspects that make it, in my opinion, a worthwhile tool to add to your dev toolbelt.</em></p><h3>Background</h3><p>Let’s start at the very beginning. Actually let’s not. Let’s just jump in.</p><p>This is the first of a series of planned and unplanned-but-serendipitously-interesting posts that I want to write, to cover the full scope of <strong>Firebase</strong>, the platform that started off as a real-time database but has since evolved into a one-stop-shop catering to all the serverless computing needs of mobile &amp; web developers. And that is both a blessing and a curse.</p><p><strong>The Blessing </strong>is that, as tech advances rapidly, we as developers <em>need</em> these kind of turnkey solutions and delegation-of-management patterns that can help us focus more attention on<em> crafting unique, fulfilling user experiences </em>instead of spinning our cycles writing, rewriting or managing a lot of the complexity that is required on the server side — but which is often unseen or unappreciated by the consumer.</p><p>And because much of this complexity stems from common underlying needs — like authentication, storage, databases, hosting, analytics, payments, performance monitoring, testing, scalability etc. — it actually lends itself well to the <em>backend-as-a-service (BaaS) </em>model. The commonality can be abstracted away into API-based services that can be invoked easily from client-side code — and the process further simplified by standard client-side libraries that are maintained by the BaaS provider, ensuring they are reliable &amp; up-to-date with changing or evolving service features.</p><p><strong>The Curse </strong>is that these platforms provide a non-trivial set of services but it is not always clear when, how, or why, you need them. Are they really necessary or are we falling for the old-fashioned upsell? What if, using a pharmaceutical analogy, we wanted the brand name service for some feature — instead of the bundled-in generic that is provided by the BaaS? Is that viable? Does that add complexity — and if so, what are the tradeoffs? And finally, <em>will I be making an irreversible decision?</em> In other words, does committing to this platform put me on the path of increased dependency on a technology — such that if, or when, it is deprecated (or worse, sunset-ed), I am not effectively left up the creek without a paddle. Let’s be clear. There is no such thing as risk-free technology — rather the discussion here is more about timeframes for obsoleteness, and pathways for migration or mitigation as the ecosystem evolves.</p><h3><strong>Goals</strong></h3><p><strong>First,</strong> was my motivation to write a series of articles that explored this space. The target audience was, in fact, me. I’ve found that writing things down helps me see the gaps in my own understanding — and that teaching others helps me see the gaps in the relevance or applicability of those ideas to diverse contexts. But I could never find time to do this just <em>because life!</em></p><p><strong>Second</strong>, I am passionate about teaching others, and it occurred to me that having this be a series of articles could effectively come in handy if I were to want to create trails or pathways for students in my “FirebaseCamp” events to explore on their own later. In that context, I specifically wanted to highlight the term “<strong>fearless” coding<em>. </em></strong>Too often I have found that adults, perhaps some more than others, underestimate their abilities and overanalyze their failures because of self-image issues that are often a product of popular culture and not reality. I happen to have been one of them.</p><p>I was afraid to admit I didn’t know many things — after 20+ years in tech, it was hard to say “<em>I am not a CS major, I have an ECE background — and most of what I know was self-taught so I have gaps in my knowledge or understanding of foundational things”</em>. It was easier to say “<em>Sure, I know that.” </em>and then pay the price in late nights of studying &amp; innumerable hours of painful debugging to figure it out on my own — rather than just ask for help. Here’s the awesome truth though — once you accept that you don’t know something, you find that an incredible load is off your shoulders and you feel freer to ask questions <em>and actually learn more productively</em> than before. <strong>Yes, just saying “I don’t know so TELL me” is incredibly empowering and liberating at the same time!!</strong></p><p>Hence the focus on <strong>Fearless Coding.</strong> In this series I am going to say, do and share whatever I know. And when I am wrong — and I will be, many times over — I hope people will correct me, educate me, and help me refine those sections so our collective understanding improves. <em>The important thing is that I now have incredible belief in my ability to learn, understand &amp; apply ideas and I want to help everyone else get to that point of positive self-esteem without fear.</em></p><p><strong>Third</strong>, tech moves so fast that sometimes ideas, APIs or tools become obsolete in a matter of months, as new revisions or competitive alternatives emerge. And so this is also meant to be a <em>living document</em> — a place where I can come back and update sections as things change, to reflect current best practices. And also have it serve as a repository of <em>code snippets</em> that describe frequently-used code patterns or quick-lookup method invocation examples, that I can repurpose in my personal and professional projects built with Firebase.</p><h3>Outcomes</h3><p>Alright, great. So where do I go from here? I want to write articles and have goals for doing this — but how do I incentivize myself? And what is the endgame?</p><p>Glad you asked.</p><p>November is National Novel Writing Month (NaNoWriMo). And if there is one thing my recent #30Days foray into habit-forming behaviors showed me, it is that setting goals/routines can get you further towards a desired outcome — even if you might fall short or have to revise estimates along the way.</p><p>And so here goes. I am committing to writing my series of articles with the intent of putting them together into a single “novel” by December 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*kDIdn5Sd803z-JPq56FlTA.png" /></figure><p>The focus in November will be to just start getting content in there as articles. I can come back later and finesse the content, update it to be more visual, rearrange or otherwise group things together to form sub-topics etc. It will be raw content but it will be a a start.</p><p><strong>Wish Me Luck!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5c7b333efb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#ElaConf: Why it matters & What I learnt (Part 1)]]></title>
            <link>https://medium.com/@nitya/elaconf-what-it-matters-what-i-learnt-part-1-b6a7d4ac9edd?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6a7d4ac9edd</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[elaconf]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[self-care]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 14:04:16 GMT</pubDate>
            <atom:updated>2017-11-02T14:06:43.608Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is going to be a long read. And even then, it does not cover the half of what I really wanted to say, but couldn’t find words for. It’s a stream of consciousness post — I’ll probably get back to this later to edit it for readability but I wanted to write it while I still *felt* it. You want to grab a cup of tea and settle in? Go ahead .. I’ll wait.</em></p><h3>Some background</h3><p>I’ve been in tech for 20+ years and done my fair share of public speaking at various industry, academic, developer &amp; internal conferences and events.</p><p>But I’ve always focused on doing <strong>technology</strong> <strong>talks </strong>and scrupulously avoided speaking about the <strong>people powering it</strong> — about the challenges, solutions &amp; opportunities faced by tech workers, and about the very human toll exerted by the inhuman pace of a rapidly-evolving ecosystem.</p><p>Until <a href="http://elaconf.com/">ElaConf.</a></p><p>On October 28, 2017 — I gave my first talk at ElaConf 2017 in Philadelphia. You can see <a href="http://elaconf.com/#agenda">the agenda here</a> and learn about <a href="http://elaconf.com/2017/agenda/sorry-not-sorry/">my talk focus here</a>. And yes, it was something I had dreamed of doing for quite a while. And the reality far exceeded my expectations in every way.</p><h3>Nitya Narasimhan on Twitter</h3><p>This is momentous. No kidding! 1. I&#39;m checking an item on my bucket list (speak at @elaconf) 2. I&#39;m talking #selfcare = huge priority for me https://t.co/FO7U2Euteu</p><p>But I’ll get to all that in a minute. As they say, before I can talk about <em>that, </em>I first need to talk about <em>this</em>.</p><h3><em>Why #ElaConf Matters</em></h3><p><a href="http://elaconf.com/"><em>This</em> is ElaConf</a>. On the site, the organizers set out their goals clearly<strong>:</strong></p><blockquote>A safe, inclusive tech leadership conference and <a href="http://ela.community/">community</a> for adult (18+) women (cis and trans), trans men, and genderqueer people to connect with and empower one another.</blockquote><p>But that does not do it justice. This is actually how I felt about ElaConf when I left just 36 hours after I first arrived in Philadelphia.</p><blockquote>ElaConf is a community that makes you feel valued, welcomed and visible. And that trifecta is the ultimate expression of “belonging” — of feeling like you fit in just minutes after you walk into a room full of strangers.</blockquote><blockquote>It is the microcosm of what our diverse tech community should be. You come in with baggage but leave feeling that load was lightened — not because it went away, but because there were now many invisible hands lifting it with you.</blockquote><p>It was in the little things — stickers for self-expression (emojis FTW), gender pronouns to embrace true identity, code of conduct that emphasized safety, a recurring feeling of “it’s okay to stumble —you got this! &amp; we got you! ” from an entire audience, an MC (the fabulous @theonlyruthie) who crafted segues for each speaker with such care that you didn’t realize it was the intro until you had already connected with the narrative of that talk.</p><p>It was about community at its very best, and about sharing your story and speaking your truths at its core. And hearing those stories shifted something in me that I had not realized was there. It made me feel <em>human</em> again. That we were all connected by tech, yes — but tech was not the thing that defined us. Rather, there is something remarkably powerful about <strong>lived experiences </strong>&amp; hearing from people who are like you, and yet <em>not </em>like you.</p><h3>What I learnt</h3><p><em>This is just the tip of the iceberg —I got to attend a lot of talks, meet a lot of people, and have a lot of meaningful exchanges. I have not named people who were non-speakers, only because I want to make sure they are okay with it and that I had the context right — hopefully I can circle back to them later and if they approve, update it to reflect their identities. Because they are all worth knowing — their honestly is compelling and their warmth genuine.</em></p><ol><li><strong>Share your truths — only then can you heal yourself. Everyone is unique but our shared experiences connect us. You are not alone.</strong></li></ol><h3>protein sheikh 🐫 on Twitter</h3><p>Being vulnerable with myself helped me start healing my own pain... to heal we must face the truth&quot; #ElaConf @zalyndria</p><p>The message from the keynote speaker (@zalyndria) was a powerful one about <em>defining success on your own terms — </em>at its core, it had a simple fact. “Trauma persists in silence” and to truly succeed, we need to face our pain boldly. Own it. Accept that things happened but that you survived. Tell your truths without filters. Only then can you truly move forward with hope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XMjWLJNqKajXAAquSbQ5ZQ.jpeg" /><figcaption>My sketchote of @zalyndria keynote</figcaption></figure><p>It occurred to me that in 2017, this has been the core of our healing as a nation, as women, as minorities. More people are stepping up to speak courageous truths about bias, and inequality, and harassment.</p><p>But as an aside, one historical aspect of @zalyndria talk shook me. I had always championed education as the best tool to conquer hate, low esteem or injustice. I’d told myself that through learning, we were better equipped to cope with things we couldn’t change &amp; positively impact the things we could. But what if education was used as a tool for <em>forced assimilation</em>? To replace or eradicate one culture’s norms and values, with that of another? What does that mean for personal identity? <em>I had never ever thought about it. Now I do.</em></p><p><strong>2. We are ALL privileged in some contexts and are minorities in others. Knowing context is key. Extending your privilege when you can, is vital.</strong></p><h3>Alanna Burke on Twitter</h3><p>Next up is @rachel_mcgrane with gender and specifically trans inclusivity on the web!</p><p>I am a South Indian by birth, an American by naturalized citizenship. I have a PhD, run multiple tech communities, organize &amp; speak at tech conferences, have 10+ patents, worked in tech for over two decades in multiple roles, on diverse platforms, with multi-disciplinary teams, am a polyglot &amp; autodidact.</p><p>And yet, by many measures, I can be viewed as part of the under-represented minority in tech.</p><p>To be fair, I have been quite oblivious to this for years. It’s not that I hadn’t faced related challenges, denials, inequalities or dismissiveness. It’s that I was brought up to think that was par for the course. The world was tough. Life wasn’t fair. If you just worked hard, compromised, persevered and followed through, then you would be rewarded. So be humble &amp; don’t waste time or energy complaining. But that’s another story.</p><p>The point was — <strong>I was at least visible</strong>. I had an established identity in terms of the boxes I could check on the various forms I’ve filled in our bureaucracy-heavy world. <em>Gender was a no-brainer and it was on nearly EVERY form.</em></p><h3>Nitya Narasimhan on Twitter</h3><p>And @rachel_mcgrane talk on &quot;Building gender inclusivity into the web&quot; made me *THINK*. How can the web be &quot;open&quot; if it doesn&#39;t know YOU?</p><p>It was a shock to my system that for so many people (@rachel_mcgrane mentioned 6% of Americans) it is something they have to think and worry about every minute. In a digital world where checkboxes dominate, this is emotional burden at its worst — because there is no escape &amp; limited control. She humorously noted that IE10 had ~0.6% adoption but had more people putting time &amp; money into supporting that (legacy) need while the 10X need of gender-inclusivity was not even a blip on most companies’ radars.</p><p><strong>And I realized that here I was absolutely privileged. I had never had to think about it.</strong> And here’s the thing — the solution is easy (“let’s improve the UI/UX by treating inclusivity like we did accessibility — as a core need) but the adoption is hard (there are billions of legacy+new pages/forms in digital and physical spaces) and most importantly <em>awareness is lacking to enforce change.</em></p><p>I was blown away by this talk not only because it opened my eyes to the issue, but because it was actually one where I felt I could at least enforce change in some small way, by incorporating best practices or sharing this with others. I am not quite sure what form this may take but in 2018, I want to spend more time educating myself &amp; exploring this in some actionable way. And for that I give huge props to @rachel_mcgrane — this was an amazing talk!</p><p><em>Wow — there is so much I want to say that I think I’ve run out of time today. I think I’ll defer other things to a Part 2 .. watch this space for updated links.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6a7d4ac9edd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 1: Exploring #AndroidThings]]></title>
            <link>https://medium.com/@nitya/day-1-exploring-androidthings-598bde257f51?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/598bde257f51</guid>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[android-things]]></category>
            <category><![CDATA[thingscamp]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Mon, 07 Aug 2017 02:28:40 GMT</pubDate>
            <atom:updated>2017-08-07T10:47:42.228Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Reporting on my first day of #FearlessCoding — for more about that see </em><a href="https://medium.com/things-camp/30days-of-fearless-coding-85b7d6872846"><em>this post</em></a><em> — and what I explored today..</em></p><p>So its 10:20 pm and I have a 4:00 am start so consider this a placeholder to be filled in with details on what I worked on today. With 2 hours of commute time tomorrow, I should be able to update this with more details.</p><h4>Focus: Android Things</h4><p>So I decided to focus on AndroidThings for my first fearless coding adventure. Two reasons why.</p><ol><li>I am hosting the <a href="https://www.meetup.com/gdgnyc/events/234963772/">GDG NYC meetup</a> tomorrow focused on this topic and this seems a good time to get my feet wet, given there will be a few experts and ideas around tomorrow, for me to kick things up a notch later this week.</li><li>I have always shied away from hardware. Its stupid but the reason is that software always felt more <em>flexible</em> and <em>safe</em> to work with. I lived in eternal fear of “bricking” my expensive hardware board or peripheral by doing something without understanding all the implications or knowing all the underpinning concepts. But that is exactly what fearless coding is meant to overcome right? <em>Am I curious about this space? </em><strong><em>Check.</em></strong><em> Am I going to persist and keep going till I build something? </em><strong><em>Abso-betcha-lutely!</em></strong><em> And am I going to share my mistakes as I learn? </em><strong><em>I kinda think that will be the norm not the exception here :-)</em></strong></li></ol><p>Where I’m at:</p><ol><li>AndroidThings exploration requires <a href="https://developer.android.com/studio/index.html">AndroidStudi</a>o and some <a href="https://developer.android.com/things/training/first-device/create-studio-project.html">dependencies installed </a>as pre-requisities. I am currently running the updates on the background on this machine. I am already tearing my hear out as AndroidStudio spits out ominous messages about being unable to patch some things … <em>hmmm.</em></li><li>AndroidThings exploration requires a compliant <a href="https://developer.android.com/things/hardware/developer-kits.html">Developer Board</a> and optional <a href="https://developer.android.com/things/hardware/developer-kits.html#featured_peripherals">Peripheral Kits</a>. I had purchased an Intel Edison board and peripherals kit earlier from Sparkfun, and have an AndroidThings-compliant kit using Raspberry Pi 3 from Adafruit. And then I happened to pick up an NXP Pico kit from IO 2017. So I am ready with that bit..</li></ol><p>Hopefully the software installs will complete tonight and I can get to work on image downloads (to dev boards) and setting up for my first project tomorrow..</p><p>Till then .. <em>bonne nuit ..</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=598bde257f51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#30Days of Fearless Coding]]></title>
            <link>https://medium.com/@nitya/30days-of-fearless-coding-85b7d6872846?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/85b7d6872846</guid>
            <category><![CDATA[impostor-syndrome]]></category>
            <category><![CDATA[thingscamp]]></category>
            <category><![CDATA[30-day-challenge]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 15:49:28 GMT</pubDate>
            <atom:updated>2017-08-05T15:57:29.099Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re been in the tech industry as long as I have, you’re probably familiar with the term <em>impostor syndrome</em> — a behavior that, not surprisingly, is often experienced by women and minorities in tech.</p><p>By definition, impostor syndrome is ..</p><blockquote>a concept describing high-achieving individuals who are marked by an inability to <a href="https://en.wikipedia.org/wiki/Internalisation_(sociology)">internalize</a> their accomplishments and a persistent fear of being exposed as a “fraud” …. Proof of success is dismissed as luck, timing, or as a result of deceiving others into thinking they are more <a href="https://en.wikipedia.org/wiki/Intelligent">intelligent</a> and competent than they believe themselves to be</blockquote><p>The issue here is in perception of self. And this nagging fear that one is not good enough, smart enough or competent enough, to belong in the role or position you are in — whether that is as a developer, public speaker, manager or advisor.</p><p>None of us are immune to it. And while recent coverage of this issue has resulted in a spate of self-improvement articles like <a href="https://www.fastcompany.com/40421352/the-five-types-of-impostor-syndrome-and-how-to-beat-them">this one from Fast Company</a> (<em>The five types of impostor syndrome .. and how to beat them</em>)<em> </em>the reality is that at its core, it’s about overcoming your fear of being judged by others — and being confident enough about yourself to be vulnerable and open about what you don’t know.</p><p>And with every passing day, as I read more narratives and stories about the bias and challenges faced in trying to grow diversity &amp; inclusion tech, I am reminded again how important it is to <strong>not succumb to this fear of not being good enough to belong in tech.</strong></p><p>That is unmitigated bull. Nobody has the right to tell you that you don’t belong in tech. We are all minorities somewhere. And if someone brings passion, perseverance and a good work ethic to any industry — <strong>recognize and amplify them</strong> instead of feeling insecure or actively undermining that effort. <em>A rising tide lifts all boats.</em></p><p>And when I feel myself giving in to any kind of doubts, I take a minute to look at this picture and remind myself —<strong> behind every so-called “expert” lies a string of failures that paved the way to get to <em>that </em>point where they can make success looks easy.</strong></p><h3>banksy on Twitter</h3><p>People only see the end result.</p><p>It is the failures <em>and the subsequent persistence to keep going </em>that makes them experts — not that final result. And so, my hope is that in everything I do — whether it is in building products or communities — I willingly embrace the failures as a vital part of getting to expertise. It is not easy, but I plan to try.</p><p>And so, this begins my <strong>#30Days </strong>challenge to be a fearless coder. If you want to learn about the <em>30 days challenge </em>check out the TED talk from Matt Cutts!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fmatt_cutts_try_something_new_for_30_days&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fmatt_cutts_try_something_new_for_30_days&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Ftalkstar-photos.s3.amazonaws.com%2Fuploads%2F424e6719-7627-40bc-ae35-1ed70a66ed2a%2FMattCutts_2011U-embed.jpg%3Fh%3D316%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="316" frameborder="0" scrolling="no"><a href="https://medium.com/media/463d6337590c78f435c242e297f88dc7/href">https://medium.com/media/463d6337590c78f435c242e297f88dc7/href</a></iframe><h3>About Fearless Coding</h3><p>For the next 30 days I am going to dive into learning a few new technologies or concepts that I have always wanted to explore more but didn’t feel I had sufficient expertise to talk about. This ranges from conversational UI/UX and machine learning, to embedded systems and IoT — topics that I have explored as a hobbyist but that I hope to use in building real-world products.</p><p>My goal is to write something every day for 30 days, sharing what I did or learnt — even if it is just something fairly trivial. And I hope that each post will showcase what I feel are the three key behaviors of fearless coding</p><ol><li><strong><em>Curiosity: </em></strong>Expertise in any realm often begins with a simple question of “why” or “how”, which leads to exploration, which unveils challenges, which then hopefully leads to innovation and experience. I genuinely believe that as long as we feed our curiosity, we will often find that our minds don’t have much idle room left in them for hate or negativity.</li><li><strong><em>Persistence:</em></strong> Expertise comes from practice. Lots of it. We all lead fast-paced multi-tasking lives and many times it feels like there isn’t sufficient time to dedicate to the kind of practice that builds perfection. And my goal is to try to do something each day to keep myself focused. Chances are there will be lapses — I have a lot on my plate. So I am arming myself with lots of forgiveness and reminding myself to just have fun with it.</li><li><strong><em>Vulnerability</em></strong><em>. </em>Perhaps the most important one of all. I am going to make a point of sharing <em>my mistakes </em>— in other words, I want to share the piles of broken plates even as I try to get to that point where I make juggling look effortless. In particular, I am going to assume that the only reader of this “journal” is me. And in that context, I want to document it in a way that I recall honestly, and that I can revisit later, to improve on that understanding with advanced insights ..</li></ol><p>And so we begin …</p><blockquote>Dear Future Me …</blockquote><blockquote>what have you committed yourself to? If you come revisit this later, I hope you feel proud that you took this step! Onwards!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85b7d6872846" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AndroidThings & IoT Recap]]></title>
            <link>https://medium.com/gdgnyc/androidthings-iot-recap-8759c2b7641f?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/8759c2b7641f</guid>
            <category><![CDATA[android-things]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Sat, 08 Jul 2017 16:29:22 GMT</pubDate>
            <atom:updated>2017-07-08T16:29:22.291Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Android Things team </em><a href="https://android-developers.googleblog.com/2017/06/android-things-hackster-community.html?hl=be"><em>held a webinar today</em></a><em> to spotlight two key resources for IoT developers: the </em><a href="https://developer.android.com/things/index.html"><em>Android Things platform</em></a><em> &amp; the </em><a href="https://www.hackster.io/google"><em>Hackster.io community</em></a><em>.</em></p><h3>GDGNYC on Twitter</h3><p>Boostrapping IoT with #AndroidThings&quot; webinar at 12pm today! https://t.co/WS5c9nclYJ #AndroidThings Event in Aug! https://t.co/G43k8GJ8Lm</p><p><em>This is a quick recap of what we learnt at from that call. The talk was taped — follow </em><a href="https://medium.com/u/149ee411aa42"><em>GDG New York City</em></a><em> to get notified if the video is publicly shared.</em></p><h3>What is IoT?</h3><p>There is a lot of hype, but also a lot of opportunity, in the domain being referred to as the <strong>Internet of Things (IoT)</strong>.</p><p>At its core, the IoT vision involves connecting physical objects to the Internet, enabling an ecosystem of digital services that can be powered by the data generated from these objects (<em>context sensing</em>) or be used to control them <em>(actuation)</em> remotely via mobile or web apps. Gartner predicts these “intelligent things” will be a key strategic technology in 2017.</p><p><a href="http://www.gartner.com/smarterwithgartner/gartners-top-10-technology-trends-2017/">Gartner&#39;s Top 10 Strategic Technology Trends for 2017 - Smarter With Gartner</a></p><p>While IoT is often used to talk about products in the consumer industry (smart home, wearables, autonomous vehicles), the <em>Industrial IoT (IIoT)</em> segment is gaining momentum in the enterprise with a focus on using machine learning, connectivity and big data to tackle challenges in health, safety and efficiency in industries like agriculture and mining.</p><p><a href="https://www.forbes.com/sites/louiscolumbus/2016/11/27/roundup-of-internet-of-things-forecasts-and-market-estimates-2016/#4ce97093292d">Roundup Of Internet Of Things Forecasts And Market Estimates, 2016</a></p><p>Analysts estimates differ but the general consensus is that the number of IoT-enabled “things” will reach ~30B devices by 2020 with a multi-billion dollar consumer market and a multi-trillion dollar enterprise market in IIoT.</p><p><strong><em>So what are the opportunities and challenges for the IoT app developer?</em></strong></p><p>The opportunities lie in areas like service automation, fitness, collaborative computing, real-time tracking/alerts, remote control and quantified self, to name just a few. New areas for exploration include wearables, smart toys, autonomous vehicles and education.</p><p>The challenges lie in tackling security and data privacy concerns, managing complexity in deploying apps to diverse hardware and software platforms, dealing with regulatory approval, and integrating frictionlessly into existing application ecosystems for growth and monetization.</p><p><strong><em>This is where the AndroidThings vision comes in.</em></strong></p><h3>What is AndroidThings?</h3><p><a href="https://developer.android.com/things/index.html">Android Things | Android Things</a></p><p>AndroidThings is Google’s initiative to support development and innovation for the Internet of Things ecosystem.</p><blockquote>All figures below were screenshots from the webinar and have been used for illustration only. All errors in explanations are mine.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*gNl5u0H2i6dVQbWBrZ4Gcg.png" /><figcaption>Core value proposition</figcaption></figure><p>At its core it offers three value propositions — bringing the reach of the Android ecosystem to IoT, delegating the complexity of hardware management to Google (and allowing developers to focus on building custom hardware extensions and rich software experiences), and leveraging the trusted security solutions provided out-of-the-box by Google.</p><ol><li><strong>The Power of Android. </strong>This takes two forms. First, application developers can embrace familiar languages (Java, Kotlin) and tools (Android Studio) for faster development. Second, they can leverage frictionless integration with other Google services (Play, Firebase, Cloud) to get comprehensive solutions with built-in support for monetization, serverless computing and big data analytics.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*H733xVsfmhnioG1tEIUSWQ.png" /></figure><p><strong>2. Managed By Google. </strong>Google manages the complexity of low-level hardware, Linux kernel and Android core components of the stack. Updates (e.g., for security or feature upgrades) get pushed out to devices automatically — you, as developer, need to manage only updates to your apps and any user-level drivers you have added to the platform.</p><p>Not only does this allow developers to quickly scale their products to new devices, but it also reduces the time/cost otherwise spent in oversight efforts instead of product improvements. The new addition of an <a href="https://partner.android.com/things/console/u/0/">AndroidThings Console</a> allows developers to review deployment versions and potentially get usage insights and administrative support in future.</p><p><em>Note: Google advocates mentioned that they are actively continuing to add drivers and libraries to support new/popular boards, sensors &amp; accessories — have one you want to see supported? </em><a href="https://plus.google.com/communities/107507328426910012281"><em>Post an “ask” to their IoT Community</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*3gaUT0BSjDCJ8HDe2xr87Q.png" /></figure><p>3. <strong>Automatic And Secure. </strong>Standard security practices like signed images and verified boot are provided by default. Not only are software updates and security patches proactively pushed out, but their <strong>A/B Rollback Protection</strong> feature ensures this happens with minimum downtime.</p><p>Patches are downloaded and installed in the background, and the devices rebooted when optimal, to have them take effect. If any issues occur during this update, the process is setup to automatically roll back to the last stable image, ensuring that your deployed hardware or software solution is never left in an unavailable state.</p><h3>Turnkey Hardware Support</h3><p>As someone who isn’t familiar with low-level embedded systems architecture or software, this aspect of AndroidThings was appealing. Effectively anyone can get started by using an <a href="https://developer.android.com/things/hardware/index.html">AndroidThings certified development board</a> that uses a <a href="https://en.wikipedia.org/wiki/System_on_module">System-on-Modules (SOM) architecture</a> to abstract complexity and promote rapid composability at the hardware level. Learn more about<a href="https://developer.android.com/things/hardware/developer-kits.html"> the supported hardware platforms here</a>.</p><p><strong>SoM Architecture: </strong>As I understand it, SoM is analogous to how software frameworks abstract complexity of underlying operating systems; as a developer you simply stack the relevant SoM on the baseboard to get a desired hardware platform for rapid prototyping &amp; test. When you finally want to build/release production hardware, you can optimize the design by reusing those modules in a single PCB — ensuring that the end result is consistent with no changes needed to your higher-level software layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*jkOgIAUHJmt0raK9Pi0CYQ.png" /><figcaption><em>Image Credit: </em>Screenshot from “IoT Bootstrapping with Android Things” Webinar</figcaption></figure><p><strong>Google Managed BSP:</strong> Google maintains the BSP (<a href="https://en.wikipedia.org/wiki/Board_support_package">Board Support Package</a>) ensuring the device is updated with the latest software and security patches with minimal developer effort required. This makes it easier for developers who don’t have embedded systems experience, to deploy new IoT solutions with confidence and focus their attention on software at the apps level.</p><p><strong>Simplified Certification and Testing</strong>. All modules Google support are pre-certified for various regulatory or industry testing standards. Once you have prototyped an IoT solution, taking it to market requires you to overcome the regulatory hurdles associated with hardware deployment. Because Google-supported modules are pre-certified, your time/cost for product-readiness is now significantly reduced.</p><h3>What does the platform look like?</h3><p>It helps to first understand what the <strong>standard</strong> Android Development platform looks like. The default architecture builds on a Linux operating system and associated native libraries (for efficiency and abstraction), over which are stacked the Android Application Framework (high-level, reusable services/components) and core Android Applications (high-level, popular apps) both of which have primarily served a consumer market focused on interactive user experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*eiukYp_RGiIRFDdxeuvI6Q.png" /><figcaption><em>Standard Android Architecture (Image Credit: </em>“IoT Bootstrapping with Android Things” Webinar)</figcaption></figure><p>The AndroidThings architecture<em> “scrubs” [</em><a href="http://www.androidpolice.com/2016/12/13/googles-brillo-internet-things-platform-now-android-things-developer-preview-available-download/"><em>like a “Brillo” pad</em></a><em>] </em>the standard architecture down to make it more suitable for the resource-constrained IoT platforms. It does this in two ways. First, it eliminates the default Android Applications (which targeted interactive users) and parts of the Framework (that are not relevant to “headless” or display-less devices). Second, it also provides IoT-ready versions of other components that remain compatible with the usage/behaviors expected by Android developers but are optimized for more resource-constrained hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*7Wygjt0XWjo_90aay5krqw.png" /></figure><p>It also adds a new <em>Peripheral Driver Library</em> to the platform, targeted primarily at supporting better interfacing of applications with the low-level interfaces afforded by sensors and actuators. The library connects popular peripherals to the Android applications layer through <em>User Driver APIs</em> — with pre-written drivers available for most common peripherals. The Peripheral Driver Library is open-sourced and has various samples to get your started — <a href="https://developer.android.com/things/sdk/driver-library.html">read more about it here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*80bMOsQkcYDdCa76cmphEg.png" /></figure><h3>Resources &amp; Next Steps:</h3><p>Where can you go to learn more? We recommend you do the following first:</p><ul><li><strong><em>Follow</em></strong> Developer Advocates: <a href="https://medium.com/u/c91ac3b63127">Dave Smith</a> &amp;<a href="https://medium.com/u/b0d0b1a4ba7">Wayne Piekarski</a></li><li><strong><em>Join</em> </strong><a href="https://www.meetup.com/gdgnyc/">Google Developer Group NYC </a>— <a href="https://www.meetup.com/gdgnyc/events/234963772/">AndroidThings</a> meetup in Aug</li><li><strong><em>Explore</em></strong> <a href="https://codelabs.developers.google.com/?cat=IoT">Google Developers Codelabs — IoT &amp; AndroidThings</a></li><li><strong><em>Watch</em> </strong><a href="https://www.youtube.com/playlist?list=PLOU2XLYxmsIIUtQeTRlRoDCdncUpWnR4M">Android Things @Google IO 2017 — YouTube Playlist</a></li></ul><p>We’ll update this section with more resources (and a link to the webinar recording when we have it) but here are resources worth bookmarking for repeat visits &amp; assistance (with clickable links for image below)</p><ul><li><a href="https://developer.android.com/things/index.html">Android Things SDK</a></li><li><a href="https://www.hackster.io/google">Hackster.io Community</a></li><li><a href="https://plus.google.com/communities/107507328426910012281">Google IoT Developers G+ Community</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*Hh5gsBnTeliWUjjX2dYJzQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8759c2b7641f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gdgnyc/androidthings-iot-recap-8759c2b7641f">AndroidThings &amp; IoT Recap</a> was originally published in <a href="https://medium.com/gdgnyc">Google Developer Group NYC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Road to #PWACamp / Programming]]></title>
            <link>https://medium.com/pwa-camp/road-to-pwacamp-principles-f0fb15d3ae33?source=rss-6cb0ee65d029------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0fb15d3ae33</guid>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[pwacamp]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Nitya Narasimhan, PhD]]></dc:creator>
            <pubDate>Thu, 06 Jul 2017 15:25:52 GMT</pubDate>
            <atom:updated>2017-07-06T15:26:47.097Z</atom:updated>
            <content:encoded><![CDATA[<p>On Jul 22, 2017, we will be running the first <em>Study Camp</em> event focused on Progressive Web Apps (PWA) through the Google Developer Group NYC, hosted at General Assembly in New York.</p><blockquote><em>You can find out more about the agenda on </em><a href="https://pwacamp2017.splashthat.com/"><em>our event page</em></a><em> and </em><a href="https://generalassemb.ly/education/progressive-web-apps-camp/new-york-city/39343"><em>purchase tickets to attend it here</em></a><em>. </em><strong><em>Use the promo code pwa-30 to get a 30% discount for a limited time.</em></strong></blockquote><p>This is the 2nd installment of a series of articles focused on PWA in the days leading to #PWACamp. You can read the <a href="https://medium.com/pwa-camp/road-to-pwacamp-principles-cf1a23886964">first article here</a> — and also find a listing of the entire series there as it progresses.</p><h3>#PWACamp Session 2: Programming</h3><p>Understanding the concepts is important, and having tools and libraries to facilitate development is critical — but as a developer, <em>how do you get started?</em> This is the focus of the second segment of our camp, and something that we hope to elaborate on a bit here.</p><p>At a high level, we want to support two kinds of learning behaviors:</p><ul><li><em>Breadth First. </em>This is for developers who are interested in exploring these concepts with code, but not necessarily tied to a specific framework or build process. In such cases, what would be the simplest way to start exploring ideas with code without having to worry about build processes, deployment options and development environment setup?</li><li><em>Depth First. </em>This is for developers who are working with a specific front-end technology and interested in understanding how they can integrate PWA capabilities into their apps, or audit existing apps for compliance. In such cases, the real focus is on getting some hands-on experience with the libraries/tools and workflow specific to that front-end.</li></ul><p>The 2-hr <em>Programming</em> segment effectively allows you to pick your own adventure — you will hear about two possible options in the <em>instructor-led</em> segment, and then explore those (or other alternatives) through hands-on codelabs in the <em>self-guided</em> segment, with the help of our on-site mentors. The two talks in this segment are:</p><h3>Building With Glitch</h3><p><a href="https://glitch.com/about/">Glitch</a> is the <em>friendly community where you will build the app of your dreams</em>. Built by the amazing folks at FogCreek, Glitch is effectively a cloud-based “sandbox” where you can edit, build and deploy your web apps in one platform, right from the browser.</p><p>More importantly, you can learn by remixing — simply look for example apps that provide specific features or leverage specific APIs, and then remix it to create a custom version that helps you better understand the underlying concepts. Learn about their vision here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*JwaTdeaUvo1kkrSY." /></figure><blockquote><a href="https://www.twitter.com/pketh">Pirijan (@pketh)</a>, Dev/Designer on Glitch team, will speak at #PWACamp about how Glitch works &amp; how you can “remix” existing PWA examples.</blockquote><p><strong>PWA On Glitch:</strong></p><p>Glitch has some PWA examples already available today that might be good places to start for a “Remix”. Take a look at these examples from our other #PWACamp speakers @kosamari and @jeffposnick</p><h3>Mariko Kosaka on Twitter</h3><p>Make your @glitch page load instantly &amp;amp; offline with ServiceWorker 🌈 https://t.co/b1cDKobicO (This is a simple scaffolding for a webpage✨)</p><h3>Jeff Posnick on Twitter</h3><p>Inspired by @kosamari, an offline-first Progressive Web App in @glitch Project: https://t.co/Zc7TNs4vvW Deployed: https://t.co/6nDTK0ilbB</p><p>Or this simple PWA demo from <a href="https://medium.com/u/a7bf6b8f7cd0">Paul Kinlan</a></p><h3>Paul Kinlan on Twitter</h3><p>Should be preparing for a preso. Decided to put up the simplest PWA on glitch. https://t.co/b4m2wn8VSY Clone: https://t.co/LWUdrZ6hWb</p><h3>Building PWA with Angular</h3><p><a href="https://angular.io/">Angular</a> is amongst the first frameworks to embrace <em>declarative </em>coding of web apps with composability, testability and performance as core tenets. In Angular 2.x, <a href="https://angular.io/features">Progressive Web Apps are core to cross-platform support</a>, making it arguably the most popular PWA-ready web app option today.</p><blockquote><a href="https://medium.com/u/5b925f0e218b">Michael Solati</a>, GDG New Haven Organizer &amp; Full-Stack Dev, will walk us through building a PWA with Angular at #PWACamp.</blockquote><p>Want to learn more about how you can build great PWA experiences with Angular? Check out this talk from Google IO, then bring your laptop and come prepared to follow-along with Michael, or do a self-guided codelab.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLNYkxOF6rcICniLJ2rfj0FexlA-9zmJJE&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DC8KcW1Nj3Mw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FC8KcW1Nj3Mw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a30c9e8b02bceb760c79c5a3badd91ae/href">https://medium.com/media/a30c9e8b02bceb760c79c5a3badd91ae/href</a></iframe><p>And check out the Angular Mobile Toolkit: <a href="https://mobile.angular.io/">https://mobile.angular.io/</a></p><h3>Building PWA with other frameworks</h3><p>But what if you are already working with a different production framework? Maybe that’s React? Or Vue? Or Polymer? Or Backbone? Not a problem.</p><p>Come to #PWACamp where we will have a set of resources available for you to start exploring development with any front-end framework — you will have mentors to help with existing codelabs plus a chance to ask your questions on PWA adoption from both members of the Google Chrome &amp; DevRel teams as well as industry experts.</p><p>Watch this space for more resource links.</p><h3>Resources:</h3><ol><li><a href="https://codelabs.developers.google.com/io2017?cat=Web">Google IO 2017 Codelabs</a> — with numerous codelabs updated for the latest features and tools. We’ve identified a few useful ones below.</li><li>Codelab: <a href="https://codelabs.developers.google.com/codelabs/your-first-pwapp/index.html?index=..%2F..%2Fio2017#0">Your First Progressive Web App</a></li><li>Codelab: <a href="https://codelabs.developers.google.com/codelabs/migrate-to-progressive-web-apps/index.html?index=..%2F..%2Fio2017#0">Migrate your site to a PWA</a></li><li>Codelab: <a href="https://codelabs.developers.google.com/codelabs/polymer-firebase-pwa/index.html?index=..%2F..%2Findex">PWA with Polymer &amp; Firebase</a></li><li><a href="https://medium.com/dev-channel/create-react-pwa-7b69425ffa86">Create-React-App with PWA</a> — @jeffposnick <a href="https://twitter.com/sco/status/864936332866367489">PR was merged</a> in May 2017</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0fb15d3ae33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pwa-camp/road-to-pwacamp-principles-f0fb15d3ae33">Road to #PWACamp / Programming</a> was originally published in <a href="https://medium.com/pwa-camp">PWA Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>