<?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 Odeh Sebastine on Medium]]></title>
        <description><![CDATA[Stories by Odeh Sebastine on Medium]]></description>
        <link>https://medium.com/@sebastinesoacatp?source=rss-70705ded826a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FQ0lQc8-HArhcKFdXpfGdg.jpeg</url>
            <title>Stories by Odeh Sebastine on Medium</title>
            <link>https://medium.com/@sebastinesoacatp?source=rss-70705ded826a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:28:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sebastinesoacatp/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[Practical Guide to Flutter Native Integration with Pigeon]]></title>
            <link>https://blog.stackademic.com/practical-guide-to-flutter-native-integration-with-pigeon-b6c575dd033f?source=rss-70705ded826a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6c575dd033f</guid>
            <category><![CDATA[mobile-engineering]]></category>
            <category><![CDATA[cross-platform]]></category>
            <category><![CDATA[native-interop]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Odeh Sebastine]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 18:06:50 GMT</pubDate>
            <atom:updated>2024-03-20T12:56:48.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DqcDDOfVx4Rx9KMGeuabQ.gif" /><figcaption>Pigeon connecting Flutter apps to native platforms</figcaption></figure><p>This article is the second part of a continuously progressing series on integrating native views, Jetpack Compose for native Android and SwiftUI for native iOS, into Flutter apps. In part one of this series which you can read <a href="https://medium.com/@sebastinesoacatp/integrating-jetpack-compose-and-swiftui-into-flutter-apps-via-method-channels-f2e10d0bd4e5">here</a>, we got a Flutter app to receive data from native views through Flutter method channels. In this article, we’ll do the same with another approach using a build tool called Pigeon.</p><h4>Prerequisites</h4><ul><li>A passion to learn something new 🔥🚀</li><li>Some experience building apps with Flutter 💙</li><li>Basic programming knowledge 👾</li></ul><p>What is Pigeon?</p><blockquote>Pigeon is a code generator tool to make communication between Flutter and the host platform type-safe, easier, and faster. — pub</blockquote><p>Pigeon is a code generation tool used to make communication between Flutter and the host platform type-safe(with greater error handling fidelity) easier and faster by generating type-safe, idiomatic code over common Flutter’s foreign function interface(ffi), they’re also called method-channels, patterns.</p><p>Pigeon removes the need to write any interface, or method channel code, to conduct communication between the host platforms since it generates all the code we need. While we’ll be using pigeon in this article from setup to usage, we won’t be covering all its capabilities, to read more you can go <a href="https://pub.dev/packages/pigeon">here</a>.</p><p>We’ll continue from where we stopped in part one which you can get from this <a href="https://github.com/CoderNamedHendrick/declarative_mobile_frameworks/tree/article-project">repository</a>. Once we have that setup, we’ll add pigeon as one of our dev dependencies.</p><p>The current pigeon version at the time of this article is 17.1.2</p><h3>Pigeon Setup</h3><p>To set up the pigeon build runner we’ll create a folder outside our lib which will house any number of pigeons we require for our project which we’ll call pigeons. In this folder, we’ll create a <em>native_moible_pigeon.dart</em> file which will house the instructions for Pigeon to build with. In our <em>native_mobile_pigeon.dart</em> file we have the following code</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/07e16a58eac77f50aecaeb616fbe28bc/href">https://medium.com/media/07e16a58eac77f50aecaeb616fbe28bc/href</a></iframe><p>We’ll go through the code above. First, we have a ConfigurePigeon annotation which takes a PigeonOptions where we specify the code generation paths we want pigeon to use. We’ll go through each of the options<br>- <strong>dartOut</strong>: path to where the generated output file should be created, this contains the name of the file and its path from the root folder so we specify <em>lib/native_api/native_mobile_ui.g.dart</em> to tell pigeon to create the file in the lib folder so our project gets access to it, the .g before the file extension is flutter/dart convention to differentiate generated files.<br>- <strong>dartOptions</strong>: takes some parameters that PigeonOptions already takes such as the copyright header and the source out path, this is mostly used when writing plugins with pigeon so we can use the constructor without parameters here.<br>- <strong>kotlinOut</strong>: specifies the path to the output kotlin generated file if the project uses kotlin.<br>- <strong>javaOut</strong>: specifies the path we want to output generated java code for the project.<br>- <strong>swiftOut</strong>: specifies the path where the generated swift file is created.<br>- <strong>dartPackagename</strong>: the package name for our pigeon</p><p>We also created a <strong>NativeMobileHostApi</strong> class which has a HostApi annotation and a method <em>getNativeUiResult</em> which returns a string with an async annotation. The HostApi annotation is used to tell Pigeon we require host platform code generated since Pigeon can generate code from both ends, that is from flutter to host and from host to flutter. The async annotation is used to tell Pigeon the method is a long waiting call so it deals with it as a future/async task on both ends of the system, that’s from Flutter to the native platform. Now we ask Pigeon to generate the output code with the following command.</p><pre>dart run pigeon  --input pigeons/native_mobile_pigeon.dart</pre><h3>Flutter</h3><p>The flutter-generated file is created in the lib folder now. We won’t be covering the contents of the file, checking it though we can see it has code throwing errors when they come and it generates code that calls the platform channels. To give us a cleaner front-facing API implementation we’ll create a <em>native_mobile_ui.dart</em> file in the same folder as the generated file. The code in this file is as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc8b1a0e7510506cd21a74497127bb6c/href">https://medium.com/media/fc8b1a0e7510506cd21a74497127bb6c/href</a></iframe><p>Now we call this function from the “Call native code” button in our <em>main.dart</em>. That’s it!!!</p><h3>Android</h3><p>Checking the generated code in our android folder we can see that Pigeon generates an interface for our <strong>NativeMobileHostApi</strong>, a <strong>FlutterError</strong> class to make sending errors more streamlined and a <em>wrapError</em> function to serialise errors sent to the flutter side. The interface has a companion object class that handles setting up the communication channel which we can call with the setUp function which takes a binaryMessenger and a nullable <strong>NativeMobileHostApi</strong>. We update our <strong>MainActiviy.kt</strong> with the following code</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce4e6601a1006fbd4bfbade94a0086ac/href">https://medium.com/media/ce4e6601a1006fbd4bfbade94a0086ac/href</a></iframe><p>Since it’s an interface we can have our MainActivity class implement it which we did. We also created a typealias to give us an easy-to-use name for our result callback type. It differs from our first implementation resulting in less code and an easy-to-use <strong>FlutterError</strong> class which takes a code, message and details that are communicated to the flutter side when passed to the Result.failure instance. Voila!!! That’s all there is to fostering typed communication with the native side.</p><h3>iOS</h3><p>The iOS-generated file while displayable from the finder and editors folder view is unavailable to Xcode which we require to use it from. To fix this we open XCode and drag the <em>NativeMobileUi.g.swift </em>file to the Runner folder, this adds an Xcode reference for our file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*Tl4Ag1lEyZzWUew7OW59EA.gif" /><figcaption>Showing how to create a file reference on XCode for NativeMobileUi.g.swift file</figcaption></figure><p>Going through the generated file code we can see Pigeon generates a protocol(think of it as Swift’s interface here) for our <strong>NativeMobileHostApi</strong>. This NativeMobileHostApiSetup class exposes a static <em>setUp</em> function for initialising the channel as we did on Android. It also has wrappers for dealing with its FlutterError class. We’ll make use of the <strong>NativeMobileHostApi</strong> by updating our <em>AppDelegate.swift</em> and <em>DelegateViewController.swift</em> as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff5bd3f7803439467916c28410ae8ba7/href">https://medium.com/media/ff5bd3f7803439467916c28410ae8ba7/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6244009e68a40f75ed642c0740f21051/href">https://medium.com/media/6244009e68a40f75ed642c0740f21051/href</a></iframe><p>Reviewing our updates, we see our AppDelegate now implements our <strong>NativeMobileHostApi</strong> protocol as we did earlier with NativeMobileHostApi for our MainActivity. Similarly, we override its <em>getNativeUiResult</em> function to make the navigation action where we pass the FlutterResult typealias we defined to the navigationController’s result which we use to return the result in the DelegateViewController class. That’s all you need to get Flutter to communicate with iOS swift UI views.</p><p>Now we run the project and we see it’s running as before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*UEJ947qH_iLI7v8sDXJTBA.gif" /><figcaption>Demo showing a flutter app receiving data from the native ends written with swift UI and jetpack compose</figcaption></figure><h3>Conclusion</h3><p>In conclusion, we learnt how to improve our Flutter app’s interaction with native APIs via a more type-safe and idiomatic approach with Flutter’s team pigeon package. The pigeon docs and example projects are great places to start for more customisations. The source code for this article can also be found here.</p><p>If you have any questions or comments about this article, please do not hesitate to contact me on Twitter at <a href="https://twitter.com/H3ndrick_">H3ndrick_</a>, on LinkedIn at <a href="https://www.linkedin.com/in/sebastine-odeh-1081a318b/">Sebastine Odeh</a> or on Github <a href="https://github.com/CoderNamedHendrick">CoderNamedHendrick</a>.</p><p>Happy coding🚀</p><h4>References</h4><p><a href="https://github.com/CoderNamedHendrick/declarative_mobile_frameworks/tree/article-project-pigeon">Project Repository</a><br><a href="https://pub.dev/packages/pigeon">Pigeon</a><br><a href="https://github.com/flutter/packages/tree/main/packages/pigeon/example">Pigeon Example</a></p><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6c575dd033f" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/practical-guide-to-flutter-native-integration-with-pigeon-b6c575dd033f">Practical Guide to Flutter Native Integration with Pigeon</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating Jetpack Compose and SwiftUI into Flutter Apps via Method Channels]]></title>
            <link>https://blog.stackademic.com/integrating-jetpack-compose-and-swiftui-into-flutter-apps-via-method-channels-f2e10d0bd4e5?source=rss-70705ded826a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e10d0bd4e5</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[cross-platform-mobile]]></category>
            <dc:creator><![CDATA[Odeh Sebastine]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 19:36:26 GMT</pubDate>
            <atom:updated>2025-01-05T09:14:46.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ubC1D4tGz93Qy6PxAoJATA.gif" /><figcaption>Feature image for the article</figcaption></figure><blockquote>Update: 18th March 2024.<br>This article is now part of an ongoing series on integrating native platforms into Flutter apps. You can find the part 2, Practical Guide to Flutter Native Integration with Pigeon, <a href="https://medium.com/@sebastinesoacatp/practical-guide-to-flutter-native-integration-with-pigeon-b6c575dd033f">here</a>.</blockquote><p>With several declarative user interface(UI) toolkits available for mobile, learning to interact with them via Flutter is becoming more and more important. Newer native SDKs are built using the native mobile declarative toolkits(Jetpack compose on Android and SwiftUI on iOS) and to integrate them into our apps we need to enable the newer frameworks.</p><p>In this article, we’ll be learning how to interact with the native UI of iOS and Android via method channels, which you can learn about <a href="https://docs.flutter.dev/platform-integration/platform-channels">here</a>. This article would cover enabling and navigating a user to UI built with the native toolkits while also sending information back to the Flutter end via a method channel call.</p><p>Here are a few prerequisites to follow along with this article</p><ul><li>Some experience with any of the declarative toolkits e.g. Flutter, Jetpack Compose or Swift UI.</li><li>Some proficiency with Flutter</li><li>Looking to learn something new</li></ul><p>Kicking off the article we’ll create a new Flutter project which we will call mobile_declarative_ui. After creating the project, we’ll clean the code that comes with creating a new Flutter project and add some code of our own.<br>Our <em>main.dart </em>would look like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6b507e69884eda2bff80551977000b6/href">https://medium.com/media/c6b507e69884eda2bff80551977000b6/href</a></iframe><p>This is a simple Flutter application where we’ll be displaying string content we get from the native ends. Navigating to the native UI will be done by pressing the material button. To get the button to function we’ll be writing the method channel code we need next. We’ll create a file called native_channel which will contain all the method channel codes we need. We’ll call this function navigateToNative and it would look like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3aea98293b76852a436b7f26035fccd0/href">https://medium.com/media/3aea98293b76852a436b7f26035fccd0/href</a></iframe><p>Here, our function invokes a method on the methodChannel instance. It’s wrapped in a try/catch to help deal with any platform exception that could be thrown. We call our method channel method ‘flutterNavigate’. Now we update the onPressed callback of our material button so it looks like this</p><pre>onPressed: () async {<br>   final data = await navigateToNative();<br>    <br>    setState(() {<br>       textFromNative = data<br>    });<br>},</pre><p>When we run the app now we get a missing plugin exception which is thrown because we haven’t written the code on the native side to deal with the method channel call, we’ll be doing this next.</p><h3><strong>Android Jetpack Compose</strong></h3><p>We’ll start with the native Android side of our project. We can open the Android module in Android Studio since it works well for writing Android native code, to do this</p><ul><li>Click on the Android folder to bring out the folder options</li><li>Then click on the Flutter menu option item</li><li>Click on “Open Android module in Android Studio”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*zqWooYG1Am6s1WOSk2SpTw.png" /><figcaption>Opening Android module in Android studio</figcaption></figure><p>When Android studio opens the module we navigate to our MainActivity.kt where we write some code to communicate with Flutter via the method channel. Our MainActivity.kt which was just extending FlutterActivity before would look like this after writing the method channel code</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d50326e6acf872a0d23a581f78a5e8a3/href">https://medium.com/media/d50326e6acf872a0d23a581f78a5e8a3/href</a></iframe><p>On running the app and tapping the call native code button, our UI updates so</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2M3YI92oKOr0OV5hMUnfDQ.png" /></figure><p>So we’ve gotten our method channel to send data to the Flutter side but how do we get the button to navigate the user to a screen we built with Jetpack compose? This is done using native Android navigation’s standard navigation practices with intents, you can learn about navigating with intents <a href="https://developer.android.com/guide/components/intents-filters">here</a>. Now we have to add jetpack compose to our native Android project. To do this we need to add some dependencies to both our app-level gradle file and module-level gradle files. We update both files as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/89d62f4ba4989a0373d187cb02006a2f/href">https://medium.com/media/89d62f4ba4989a0373d187cb02006a2f/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5050ffd314d7e3a746267d1bf9fc19f4/href">https://medium.com/media/5050ffd314d7e3a746267d1bf9fc19f4/href</a></iframe><p>To learn more about adding jetpack-compose to an existing Android project please check this wonderful article by Zive <a href="https://proandroiddev.com/introducing-jetpack-compose-into-an-existing-project-aa7044834510">here</a>. After syncing our gradle file we can easily add a compose activity using the context menu. To do this</p><ul><li>Click on the root com.example.mobile_declarative_ui folder to show the options.</li><li>Select new</li><li>Then select Compose and click on “empty activity”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/1*MFnMEj__-Dr91d-32DnQDg.png" /><figcaption>creating an empty compose activity for the project</figcaption></figure><p>Clicking on empty activity would launch a window where we name the activity. We’ll be calling this activity ComposeActivity for simplicity&#39;s sake and we’ll ensure it’s not selected as a launcher activity. Hit finish and Android Studio will take care of creating the compose activity with all the default boilerplates. We’ll navigate to ComposeActivity.kt and update the boilerplate code to look as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c1a7bbea02830d16fe1d1280ccb74ac6/href">https://medium.com/media/c1a7bbea02830d16fe1d1280ccb74ac6/href</a></iframe><p>Using compose UI preview we can see the output of our code in the preview tab which should look like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*HTe7LRea7NSuTLDkQ-1iwQ.png" /><figcaption>Compose preview for ComposeBody composable</figcaption></figure><p>Our compose UI is going to take two number inputs which we’ll sum. We’ll also be sending the sum of these inputs to our Flutter application. Our composeBody composable function does this by updating the input states and providing an onClick callback which takes a string which we’ll be navigating and returning to the main activity via intents.</p><p>Updating our MainActivity to navigate to the ComposeActivity while dealing with the result returned from it will lead to updates in both files as shown below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0bd1f6af0ec0e9ef5a767305e4286e8d/href">https://medium.com/media/0bd1f6af0ec0e9ef5a767305e4286e8d/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e94ed2ed9b04c35fadf8a8be4d1fab5c/href">https://medium.com/media/e94ed2ed9b04c35fadf8a8be4d1fab5c/href</a></iframe><p>On running the app, it works as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMRMpPHCh9ZLKBMAokKrfA.gif" /></figure><h3><strong>Swift UI</strong></h3><p>Now we’ll do the same for iOS and SwiftUI although we’ll skip some steps while going ahead with the code. Before writing code though we have to open Xcode, we do this by clicking on the iOS folder to expose the available options before selecting Flutter and then clicking on “Open iOS/macOS module in Xcode”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*nzfIw6ZEOhnaRWsTWxZitA.png" /><figcaption>Context menu for opening iOS module in Xcode</figcaption></figure><p>We’ll create a new folder in our Runner folder in Xcode which we’ll call Views. In the views folder, we’ll create 3 swift files. The first one will be Delegate.swift and it will hold a <a href="https://docs.swift.org/swift-book/documentation/the-swift-programming-language/protocols/">protocol</a> whose method we’ll call popViewController which would take a string</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/241e53c47ed20c86ce6ac66650c50708/href">https://medium.com/media/241e53c47ed20c86ce6ac66650c50708/href</a></iframe><p>Next, we’ll create another file which we’ll call DelegateViewController. This class is going to extend UINavigationController and DelegateProtocol. We need the class to work as any standard UINavigatorController which is usually used for navigating in UIkit apps, you can read about them <a href="https://developer.apple.com/documentation/uikit/uinavigationcontroller">here</a>. Our DelegateViewController class would also have a nullable field which we’ll call result and its type is FlutterResult(this is equivalent to Android’s MethodChannel.Result). Our DelegateViewController would look as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ce07c394818c98c8279dadabb20db54/href">https://medium.com/media/9ce07c394818c98c8279dadabb20db54/href</a></iframe><p>Our third file would be the actual swift UI view. In this file, like we did for Android, we’ll have two inputs which will take numbers and a button to send the sum back to Flutter. We’ll call this swiftUI view file SwiftUIView and it would look as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a8c31bb4a3fc29c71c5f91f6b09486ab/href">https://medium.com/media/a8c31bb4a3fc29c71c5f91f6b09486ab/href</a></iframe><p>While SwiftUI comes shipped and is fully compatible with UIKit without adding any dependencies, we have to increase the minimum iOS deployment version as swiftUI only works on iOS 13.0 and up. To do this select the root runner folder icon which will open the targets console where we can set the minimum deployment version to iOS 13</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGAnnc8-csiI1H3r8v5zAQ.png" /></figure><p>After setting it, our swift UI view builds and a preview is shown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*QT3dmTkeCZBKMWIw188QYw.png" /><figcaption>Swift UI preview for SwiftUIView</figcaption></figure><p>Now we head for the iOS project’s AppDelegate.swift which is the root of the iOS app. We’ll update the code in the AppDelegate to perform the navigation to the swift UI view on our method channel call. The updated AppDelegate file looks as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/681df6c29bd288ea013428b9a88a3450/href">https://medium.com/media/681df6c29bd288ea013428b9a88a3450/href</a></iframe><p>Running the iOS app is shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/1*tiVEvFTz66PT5CnhMjJ1OQ.gif" /><figcaption>iOS Flutter app navigating to swift UI view.</figcaption></figure><h3><strong>Conclusion</strong></h3><p>In conclusion, we learnt how to extend our Flutter app interactions with the native APIs via method channels going as far as receiving data from native UI written with the newer declarative toolkits namely jetpack compose for Android and Swift UI for iOS. For more help, the Android docs and iOS docs are a great place to start. The source code for this article can be found <a href="https://github.com/CoderNamedHendrick/declarative_mobile_frameworks/tree/article-project">here</a>.</p><p>If you have any questions or comments about this article, please do not hesitate to contact me on Twitter at <a href="https://twitter.com/H3ndrick_">H3ndrick_</a>, on LinkedIn at <a href="https://www.linkedin.com/in/sebastine-odeh-1081a318b/">Sebastine Odeh</a> or on Github <a href="https://github.com/CoderNamedHendrick">CoderNamedHendrick</a>.</p><p>Happy coding🚀</p><h4><strong>References</strong></h4><p><a href="https://github.com/CoderNamedHendrick/declarative_mobile_frameworks/tree/article-project">Project Repository</a><br><a href="https://proandroiddev.com/introducing-jetpack-compose-into-an-existing-project-aa7044834510">Introducing Jetpack Compose into an existing project</a><br><a href="https://blog.devgenius.io/combining-swiftui-and-uikit-a-guide-to-interoperability-4b458ee75b61">Combining SwiftUI and UIKit: A guide to interoperability</a><br><a href="https://docs.flutter.dev/platform-integration/platform-channels">Writing custom platform-specific code</a></p><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2e10d0bd4e5" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/integrating-jetpack-compose-and-swiftui-into-flutter-apps-via-method-channels-f2e10d0bd4e5">Integrating Jetpack Compose and SwiftUI into Flutter Apps via Method Channels</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Custom Form Fields in Flutter: Creating Validation Behaviors for Any Widget]]></title>
            <link>https://blog.stackademic.com/flutter-custom-widgets-form-validation-3d3623a8c9df?source=rss-70705ded826a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d3623a8c9df</guid>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[form-validation]]></category>
            <dc:creator><![CDATA[Odeh Sebastine]]></dc:creator>
            <pubDate>Tue, 11 Jul 2023 17:42:54 GMT</pubDate>
            <atom:updated>2024-03-20T12:57:00.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Nt22DAxCw0SvD0lA.jpg" /></figure><p>As the range of input fields in apps increases, dependent on the UI specifications of the project, the need for a uniform validation process for all input becomes even more paramount. Luckily, flutter allows any widget to obey form validation rules exactly like <a href="https://api.flutter.dev/flutter/material/TextFormField-class.html">text form fields</a>. In this article, we will be doing just that by making custom form fields of custom widgets.</p><p>To follow along as we learn to make custom form fields, it’s recommended to fulfil these prerequisites:</p><ul><li>Some flutter knowledge.</li><li>Flutter SDK is installed.</li><li>Burning passion to learn something new.</li></ul><p>To kick the article off, we’ll be building two custom widgets. The first widget would be a custom image picker and the second would be a group of radio buttons both with form validation.</p><p>To start this project we go through the following steps</p><ul><li>We create a new flutter project which we’re going to call form_widget_demo.</li><li>Next, we add the image picker package to our pubspec.yaml, we won’t be covering setting it up as it’s outside the scope of this article but you can go through the readme <a href="https://pub.dev/packages/image_picker">here</a> before continuing.</li></ul><p>Here’s how our pubspec.yaml dependencies list looks after adding the image_picker package</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/733662bc5bddda5f86f71042f4b08d80/href">https://medium.com/media/733662bc5bddda5f86f71042f4b08d80/href</a></iframe><p>And our main.dart looks like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/154aa17571aaf7ad85c7218ee275d4df/href">https://medium.com/media/154aa17571aaf7ad85c7218ee275d4df/href</a></iframe><p>Now we are going to create the base image picker widget which we’ll extend to being a form field shortly. We start by creating an image_picker_field.dart file and filling it with the following code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/73299bc4d09b685068e5fa7e948e0cfb/href">https://medium.com/media/73299bc4d09b685068e5fa7e948e0cfb/href</a></iframe><p>Then we add this widget to the column in our MyHomePage widget in our main.dart. Also, we’ll be wrapping the column with a Form to apply form validation and also a button to validate the custom form fields we’ll be creating. Our MyHomePage widget would look like this</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c1c85082dcfcf544a7479d716c38056/href">https://medium.com/media/3c1c85082dcfcf544a7479d716c38056/href</a></iframe><p>Running the app on your device you should see similar as displayed below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*tgHFWdfWlYfJEsrjMNCATg.png" /></figure><p>Pressing the validate form button doesn’t catch any validation error, in this case not selecting an image, and shows the form “is valid” snack bar, we will be fixing that next.</p><p>Our image picker widget validation would work in a way that takes inspiration from text form fields, we’ll give the sides a red border with the validation error message at the bottom also in red. Also taking inspiration from text form fields, we’ll introduce an image picker input controller. The image_picker_field.dart file is updated as shown below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c4fee7fdcac4449bbf1c3aab0700216/href">https://medium.com/media/3c4fee7fdcac4449bbf1c3aab0700216/href</a></iframe><p>We’ve updated the ImagePickerField widget to take 3 parameters, a controller, an onChanged and a side. The controller is a nullable ImagePickerInputController which is defined at the bottom of the file as a class that extends <a href="https://api.flutter.dev/flutter/foundation/ValueNotifier-class.html">ValueNotifier</a> and it takes a type File. We also provide fileName getter which we use to get the file’s name and a file setter to update the value and notify its listeners. We use an onChanged to emit the values from the controller as they’re updated and then a side which we override in the ImagePickerFormField to show the red-coloured border.</p><p>The ImagePickerFormField extends FormField which allows generic types and allows a parent form widget to control its form behaviour like textformFields. We also provide a controller, onChanged as before with a super.validator, super.autovalidateMode, which allows us to pass validation rules. We override the builder parameter of the extended widget class which is a callback that provides a FormFieldState that exposes getters such as errorText for getting validation error text and hasError, a boolean to check if there’s an error. We also update the ImagePickerField to ImagePickerFormField in our main.dart and then add a validation rule to the validator callback which is shown below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7676c0d02848afe7d80518cd1c658c18/href">https://medium.com/media/7676c0d02848afe7d80518cd1c658c18/href</a></iframe><p>This is all we need to make an image picker field a form field which obeys the parent form’s key validation and auto-validation behaviour.</p><p>Next, we’ll be working on making a popular existing use case operate as a form field, that is a group of radio options.</p><p>We’ll start by creating a file we’ll name radio_button_group.dart and add the following code to it</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ee8a190f62d7d33b336b13edc8976d7/href">https://medium.com/media/7ee8a190f62d7d33b336b13edc8976d7/href</a></iframe><p>Updating our MyHomePage column with a sized box for space and the RadioButtonGroup, our UI and code look as below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_5zho33lTWN3G5H5oQETA.png" /><figcaption>Updated UI with Radio button group</figcaption></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2985505a87386ae98a708eb1c3bf8c2/href">https://medium.com/media/b2985505a87386ae98a708eb1c3bf8c2/href</a></iframe><p>Now for how we want validation errors to be displayed, going with the same idea as before we will show the validator error message at the bottom of the group and this time we’ll make the radios red to show there’s an error by updating the radio’s fill color property. Our updated radio_button_group.dart is shown as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ddc614431d5bb9745f8983995c0f0966/href">https://medium.com/media/ddc614431d5bb9745f8983995c0f0966/href</a></iframe><p>Keeping to the same conventions as before we have a controller, onChanged and this time fillColor as parameters of the RadioButtonGroup widget. We also have a form widget that follows what we did earlier with the ImagePickerWidget. Our updated MyHomePage widget looks as follows</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1403b5689d911f49f72130f2555839d/href">https://medium.com/media/e1403b5689d911f49f72130f2555839d/href</a></iframe><p>Different UI for each validation state looks as follows</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlzadNpMiK_y40kAO5nR1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElSblvZEN95AkPHV-dANIA.png" /></figure><p>In conclusion, we’ve learnt how to turn custom widgets to form fields. While this works, it could be better implemented. The implementation of form validation in Flutter’s text field requires some additional overrides which you can check from the source code found <a href="https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/material/text_form_field.dart">here</a>. The full project and demo are also available on <a href="https://github.com/CoderNamedHendrick/flutter_custom_form_fields_demo">GitHub</a>.</p><p>If you have any questions or comments about this article, please do not hesitate to contact me on Twitter at <a href="https://twitter.com/H3ndrick_">H3ndrick_</a>, on LinkedIn at <a href="https://www.linkedin.com/in/sebastine-odeh-1081a318b/">Sebastine Odeh</a> or on Github <a href="https://github.com/CoderNamedHendrick">CoderNamedHendrick</a>.</p><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a><strong> | </strong><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a><strong> | </strong><a href="https://cofeed.app/"><strong>CoFeed</strong></a><strong> | </strong><a href="https://venturemagazine.net/"><strong>Venture</strong></a><strong> | </strong><a href="https://blog.cubed.run/"><strong>Cubed</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d3623a8c9df" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/flutter-custom-widgets-form-validation-3d3623a8c9df">Building Custom Form Fields in Flutter: Creating Validation Behaviors for Any Widget</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to Exploratory Data Analysis(EDA) with python.]]></title>
            <link>https://medium.com/swlh/intro-to-exploratory-data-analysis-eda-with-python-152a37029a8d?source=rss-70705ded826a------2</link>
            <guid isPermaLink="false">https://medium.com/p/152a37029a8d</guid>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[statistical-analysis]]></category>
            <category><![CDATA[statistics]]></category>
            <dc:creator><![CDATA[Odeh Sebastine]]></dc:creator>
            <pubDate>Tue, 05 May 2020 03:25:55 GMT</pubDate>
            <atom:updated>2020-05-05T13:47:52.026Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Prerequisites</strong></p><ul><li>Basic knowledge on python</li><li>Basic knowledge on the numpy and pandas libraries</li></ul><p><strong>Table of content</strong></p><ul><li>Importing data from module</li><li>Descriptive Statistical Analysis</li><li>Correlation and Causation</li><li>ANOVA</li></ul><h3>Importing data from module</h3><p>In python, the libraries used for importing data which is going to be analysed are the numpy(python numerical library) and pandas(a library build on numpy which makes working with datasets easier and visually more appealing). The libraries are imported as shown below.</p><figure><img alt="importing the necessary libraries for working with data" src="https://cdn-images-1.medium.com/max/255/1*wzVREATv2zD4LpuAP3FAqw.png" /></figure><p>Jupyter notebooks are our favorite tool for data analysis since they allow you to document while performing our analysis. The dataset used in this article can be gotten from</p><p><a href="https://s3-api.us-geo.objectstorage.softlayer.net/cf-courses-data/CognitiveClass/DA0101EN/automobileEDA.csv&#39;">https://s3-api.us-geo.objectstorage.softlayer.net/cf-courses-data/CognitiveClass/DA0101EN/automobileEDA.csv</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*PvahL4FQtCWy9o3JNEjO7g.png" /></figure><p>Firstly, we write a variable for the path before applying the pandas function for reading csv files, that is, the pd.read_csv().</p><p>The dataframe.head() method shows us the first 5 rows of the imported data set, this is used to check if what we imported is correct.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*b5DxHbK6Pad8L5zq7qrMYg.png" /></figure><h3>Descriptive statistical Analysis</h3><p>Firstly, we look at the describe function which computes basic statistics for all continuous variables in the data set.</p><p>The describe function shows you:</p><ul><li>the count of that variable</li><li>the mean</li><li>the standard deviation</li><li>the maximum and minimum values</li><li>the IQR(interquartile range: 25%, 50%, 75%)</li></ul><p>we apply the describe method as follows</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/152/1*XxlzOrQSgI267hWa25Asag.png" /></figure><p>the result you get should look like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*n-O2cUpyBm8sHZCqmyKwrA.png" /></figure><ul><li>count: shows the number of values for the variable, in the table it’s 201. The count is used to show the number of inputs we have in a data set.</li><li>mean: the average value of the variable.</li><li>std: standard deviation, a quantity expressing by how much the members of a group differ from the mean value for the group. Simply put it is a measure of how spread out numbers are.</li><li>min: minimum value of the variable</li><li>IQR: the interquartile range shows you the value of the variable at the respective percentiles, that is, 25%, 50%, and 75%.</li><li>max: maximum value of the variable.</li></ul><p>Without an argument the describe method only gives basic statistics for numerical variables. To get statistics for categorical variable, the include=[‘object’] argument is used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/265/1*dbdUhg_ujTIyM0RtmTOKwA.png" /><figcaption>the line of code to get statistics on categorical variables</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*UqYyFeIIZ_TJnU1BnpF20g.png" /><figcaption>notice the new information on the table?</figcaption></figure><p>We notice we have new info in our statistics table, unique, top, and freq.</p><ul><li><strong>unique</strong> : the refers to the number of unique entities we have in a particular series(field) for example the unique of <strong>make</strong> is 22.</li><li><strong>top</strong>: the highest occurring value in the series</li><li><strong>freq</strong>: the number of times the highest occurring value appeared. It is referred to as mode.</li></ul><p>A useful method to know is the value counts method. Which is a good way of understanding the number of units for each characteristic/variable that we have, that is, it shows us the number of times each characteristic appears. Note, the value-counts method works on pandas series and not pandas dataframe so when using the method we include on one square bracket(for working with pandas series) and not two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*U5-6ay94o7pl9PG4LxpWlg.png" /><figcaption>the value-counts method</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/1*5-AqKOBlfHtti25UiN1lIQ.png" /></figure><p>The above image shows the number of units we have for front-wheel-drive(fwd), rear-wheel-drive(rwd), and 4-wheel-drive(4wd).</p><h3>Correlation and Causation</h3><ul><li><strong>Correlation</strong>: interdependence of quantity variables or a measure of the extent of interdependence between variables.</li><li><strong>Causation</strong>: the relationship between cause and effect between variables.</li></ul><p>It is important to note that correlation doesn’t imply causation. Determining correlation is much more simpler because it doesn’t require independent experimentation.</p><p>In descriptive analysis the pearson correlation can be used to determine correlation between two variables X and Y. When the method is used the result varies from -1 to 1 where,</p><ul><li>1: total positive linear correlation</li><li>0: no correlation</li><li>-1: total negative linear correlation</li></ul><p>The pandas method .corr() can be used to find the correlation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/159/1*JNAvnmtY3fu39MpLmF1q6g.png" /><figcaption>the pandas .corr() method</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*HaHNE62D1o4Bctq6AfK3vQ.png" /></figure><p><strong>P-value</strong>: The p-value is the probability that the correlation between variables is statistically significant. As a standard we use a significance level of 0.05 which shows we are 95% confident that the correlation between the variables is significant. Their significance levels are ranked below.</p><ul><li>p-value &lt; 0.001 : this means the correlation is statistically significant</li><li>p-value &lt; 0.05: moderate significance</li><li>p-value &lt; 0.1 : weak significance</li><li>p-value &gt; 0.1 : there is no evidence that the correlation is significant</li></ul><p>We find the p-value between variables by using the pearson correlation function in the scipy(python library for scientific operations) library. The function shows the pearson coefficient and p-value of the variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/1*visumkfBIdF_ordPuU-Y-A.png" /></figure><p>The pearson correlation function is used after importing stats from the scipy library. First we calculate the pearson correlation between wheel and price from the data set we imported earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*l8vKK_DPlqsYAqRULHVd9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*wtoaRha_eOY_VEV3HpRMfA.png" /><figcaption>the output</figcaption></figure><p><strong>Conclusion</strong>: since the pearson coefficient is 0.5846 it shows a positive linear correlation which isn’t really strong while the p-value is statistically significant since its value is &lt;0.001.</p><h3>ANOVA</h3><p><strong>ANOVA</strong> means AnalysisOfVariance which is a collection of statistical models and their associated estimation procedures (such as the “variation” among and between groups) used to analyze the differences among group means in a data set or in simpler terms a method use to test whether there are significant differences between the means of of two or more groups. ANOVA returns two results:</p><ul><li>F-test score: ratio of two variances, ANOVA assumes the means of all groups are the same, calculates how much the actual means deviate from the assumption, and reports it as the F-test score. A larger score means there is a larger difference between the means.</li><li>p-value: the p-value tells us how statistically significant our score is</li></ul><p>With our data set if our price is strongly correlated with the variable we are analyzing, ANOVA returns a sizeable(large) F-score and a small p-value.</p><p><strong>Drive wheels test</strong></p><p>Since ANOVA analyzes the difference between different groups of the same variable, the groupby function will come in handy. Because the ANOVA algorithm averages the data automatically, we do not need to take the average before hand.</p><p>Let’s see if different types ‘drive-wheels’ impact ‘price’, we group the data.</p><p>Let’s see if different types ‘drive-wheels’ impact ‘price’, we group the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*gFoUTIZOR9cCHU5fNLlrqA.png" /></figure><p>which results in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/184/1*nXugVrmY6VRF4dnnnPbpTg.png" /></figure><p>We can obtain the values of the method group using the method “get_group”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*-9aE0CfAxyhjUCBHgIavQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/211/1*dzk0H4PP5spol3OI76eggg.png" /></figure><p>we use the f_oneway function in the module ‘stats’ in the scipy library to get the F-test score and p-value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*XlSOFHdPqdk0CLDPlNwUjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*-ZqpEmSFBnjFb-G88HF65g.png" /></figure><p>With the <strong>ANOVA</strong> results showing a large F score it is strongly correlated with a p-value of &lt; 0.001 it is statistically significant. Although the results a good, that doesn’t mean that all tested three groups are highly correlated.</p><h3><strong>In conclusion</strong>:</h3><ul><li>We’ve learnt how to interpret the statistics table when using the describe function</li><li>We understand how to interpret correlation and what it means when analyzing data and how it doesn’t imply causation.</li><li>We understand the basics of ANOVA and what the parameters it returns means.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=152a37029a8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/intro-to-exploratory-data-analysis-eda-with-python-152a37029a8d">Intro to Exploratory Data Analysis(EDA) with python.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>