<?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 Damodar Lohani on Medium]]></title>
        <description><![CDATA[Stories by Damodar Lohani on Medium]]></description>
        <link>https://medium.com/@lohanidamodar?source=rss-21afa4abace7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*NGUiCAw_X3uA_2NehhLb4w.jpeg</url>
            <title>Stories by Damodar Lohani on Medium</title>
            <link>https://medium.com/@lohanidamodar?source=rss-21afa4abace7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:34:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lohanidamodar/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[Embark on a Project-Based Learning Adventure with Our #30DaysMasterFlutter Challenge and Become a…]]></title>
            <link>https://lohanidamodar.medium.com/embark-on-a-project-based-learning-adventure-with-our-30daysmasterflutter-challenge-and-become-a-fd22f76d2602?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd22f76d2602</guid>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Wed, 10 May 2023 00:17:36 GMT</pubDate>
            <atom:updated>2023-05-10T00:17:36.158Z</atom:updated>
            <content:encoded><![CDATA[<h3>Embark on a Project-Based Learning Adventure with Our #30DaysMasterFlutter Challenge and Become a Confident App Developer!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*LQxwRqkozJIBItt1Cf4CWA.png" /></figure><p>Hello, aspiring app developers! 📱</p><p>We are thrilled to announce that our <a href="https://appwriters.dev/30days/flutter">#30DaysMasterFlutter</a> challenge is now live, and you can join in on this exciting journey to mastering Flutter &amp; Dart. This project-based course 📚 is entirely free and provides you with the knowledge and tools to learn one of the most exciting technologies in the world of app development.</p><p>Over the next 30 days, we will focus on one key concept per day and equip you with the resources to understand and implement these concepts. You’ll learn and apply these concepts in building real-world projects. 💻🌍 This course is suitable for all levels of expertise, from complete beginners to experienced programmers.</p><p>If you ever feel stuck, don’t worry! <a href="https://discord.gg/gFYRMGjqYa">Our vibrant community of learners</a> 👥 is always there to support you, answer your questions, and collaborate with you.</p><p>This learning journey is about growing and building together, so let’s take on this challenge and come out as confident app developers. 🎉</p><p>Don’t forget to share your daily progress on social media using the hashtag #30DaysMasterFlutter. We can’t wait to see your achievements! 🏅</p><p>Are you ready to dive in and start coding? <a href="https://appwriters.dev/30days/flutter">Let’s do this! </a>🤓</p><p>Happy Learning! 🎓</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd22f76d2602" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phone Authentication with Twilio and Appwrite for your Flutter Applications]]></title>
            <link>https://lohanidamodar.medium.com/phone-authentication-with-twilio-and-appwrite-for-your-flutter-applications-434468bb7d85?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/434468bb7d85</guid>
            <category><![CDATA[appwrite]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[dart]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Wed, 29 Jun 2022 00:18:45 GMT</pubDate>
            <atom:updated>2022-07-19T02:33:25.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*qhT3ki5bXOlY-GV4.png" /></figure><p>Phone authentication is one of the most reliable authentication methods for mobile applications. And Appwrite has now introduced phone authentication in our recent release. In this article, we will learn how to implement Appwrite’s phone authentication in our Flutter applications.</p><blockquote><strong><em>New to Appwrite?</em></strong></blockquote><blockquote><a href="http://appwrite.io/"><em>Appwrite</em></a><em> is an open-source back-end-as-a-service that abstracts all the complexity of building a modern application by providing a set of REST and Realtime APIs for your core back-end needs. Appwrite minimizes the heavy lifting for developers and handles user authentication and authorization, databases, file storage, cloud functions, webhooks, and much more!</em></blockquote><h3>Prerequisites</h3><ul><li>Access to an Appwrite project or permission to create one. If you don’t already have an Appwrite server running, follow the official<a href="https://appwrite.io/docs/installation"> installation tutorial</a> for setup instructions.</li><li>A <a href="https://flutter.dev/">Flutter</a>-configured development machine.</li></ul><h3>Twilio Account Setup</h3><p>We first need to set up a phone service provider for authentication. Twilio is a popular choice — a Twilio account can provide API access keys, allowing Appwrite to send codes to mobile phones. If you don’t have an existing Twilio account, you can visit <a href="https://www.twilio.com/try-twilio">https://www.twilio.com/try-twilio</a> and create a free account using your email and password. Via email, you will then receive a verification link, clicking on which will verify your Twilio account. It will also ask you to verify your phone number.</p><p>Enter your phone number and click on the <strong>Verify</strong> button. You will then receive a code via SMS. Enter the received code in Twilio and click <strong>Submit</strong> to confirm your number.</p><p>On the next screen, enter your choices. It doesn’t matter which coding language you choose, as we will integrate Twilio with Appwrite, so we don’t have to interface with Twilio directly. Next, click on <strong>Get started with Twilio</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*Y_ETGhkiiFsIs5m9.png" /></figure><p>You should then be redirected to the Twilio console. Click the <strong>Getting your Twilio number</strong> button. The initial trial account can only send texts and calls to your verified numbers, and for testing, that’s perfect. However, for production use, you must upgrade your Twilio account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*qroQYo4nwetEFX-4.png" /></figure><p>You can see the Account SID, Auth Token, and Phone number in the console. You will need these in the next session to set up Twillio as an SMS provider Appwrite can use. Your Twilio account should now be ready to integrate with Appwrite.</p><h3>Appwrite Setup</h3><p>Follow the <a href="https://appwrite.io/docs/installation">official guide</a> to set up and run Appwrite. For Appwrite to know about Appwrite, we need to open the .env file from the appwrite directory where you installed Appwrite, and update the following environment variables.</p><pre>_APP_PHONE_PROVIDER=phone://&lt;ACCOUNT SID&gt;:&lt;AUTH TOKEN&gt;@twilio _APP_PHONE_FROM=&lt;TWILIO_PHONE_NUMBER&gt;</pre><p>Once the environment variables are updated, run the following command from the command line in the installation directory that contains the .env and docker-compose.yml files.</p><p>This will restart the containers, providing new values for the environment variables, so Appwrite can connect to Twilio. We are now ready to implement phone authentication in our application.</p><p><strong>Install and Configure Appwrite’s Flutter SDK</strong></p><p>Cloning the project we created for this tutorial lets us skip the setup and UI part, and focus on the main topic. Clone <a href="https://github.com/lohanidamodar/appwrite_phone_auth.git">https://github.com/lohanidamodar/appwrite_phone_auth.git</a>. Once cloned, open it in your favorite IDE.</p><p>We will start by adding Appwrite’s SDK as a dependency. Open pubspec.yaml file and add Appwrite&#39;s SDK under dependencies.</p><pre>dependencies:<br>    appwrite: ^6.0.0</pre><p>If the IDE doesn’t get dependencies automatically, run the following command from the terminal.</p><pre>flutter pub get</pre><p>Next, open lib/providers/app_state.dart file. This is where we will configure our Appwrite SDK. First, import the appwrite package.</p><pre>import &#39;package:appwrite/appwrite.dart&#39;;<br>import &#39;package:appwrite/models.dart&#39;; // Response type definitions</pre><p>In the AuthState class, add new properties.</p><pre>class AuthState extends ChangeNotifier {<br>  final _client = Client();<br>  late final Account  _account;<br>}</pre><p>Then in the constructor, let’s configure the client and instantiate the account.</p><pre>AuthState() {<br>    _client.setEndpoint(&#39;YOUR_ENDPOINT&#39;)<br>       .setProject(‘YOUR_PROJECT_ID’);<br>    _account = Account(client);<br>  }</pre><p>Once the SDK is installed and configured, the final step is adding the platform to our Appwrite project. Open the Appwrite console and choose the project you created for this application. You can find the <strong>Add Platform</strong> button on the project home page. Click on the <strong>Add Platform </strong>button and select <strong>New Flutter App</strong>. In the dialog box that appears, choose the appropriate Flutter platform, assign it a recognizable name, and add the application ID or package name based on the platform. You must complete this step for each Flutter platform you build in your application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*dlKjYjvZEiiIHa1Z.png" /></figure><p>Flutter developers can find more detail instructions on using Appwrite in our official<a href="https://appwrite.io/docs/getting-started-for-flutter"> Getting Started for Flutter</a> guide.</p><p>Now that our SDK is installed and configured, we are ready to implement phone authentication in our application.</p><h3>Creating a Session with a Phone</h3><p>Two steps are needed to create a valid session for users with phone numbers. First, to initiate the session creation process, we will use the setup provider for sending a verification code to the provided phone number. Next, the verification code will confirm and create a valid session for the user. So let’s implement those two methods in our AuthState class.</p><p>To initiate the session, we call createPhoneSession from the account service and pass the userId and phone numbers. Passing &#39;unique()&#39; as userId allows Appwrite to generate a unique Id.</p><pre>Future&lt;bool&gt; createSession(String phone) async {<br>    try {<br>      final token =<br>          await _account.createPhoneSession(userId: &#39;unique()&#39;, number: phone);<br>      userId = token.userId;<br>      return true;<br>    } on AppwriteException catch (e) {<br>      _error = e.message ?? e.toString();<br>      isLoggedIn = false;<br>      notifyListeners();<br>      return false;<br>    }<br>  }</pre><p>Calling createPhoneSession returns a token object with userId. We save the userId because we need it to confirm authentication and create a valid session. To do that, we need to call updatePhoneSession from the account service. Let’s follow the confirmSession method.</p><pre>Future&lt;bool&gt; confirmSession(String secret) async {<br>    if (userId.isEmpty) {<br>      _error = &#39;userId not known, call `createSession` first to get userId&#39;;<br>      notifyListeners();<br>      return false;<br>    }<br>    try {<br>      await _account.updatePhoneSession(userId: userId, secret: secret);<br>      await getAccount();<br>      return true;<br>    } on AppwriteException catch (e) {<br>      _error = e.message ?? e.toString();<br>      isLoggedIn = false;<br>      return false;<br>    }<br>  }</pre><p>Now let’s call these methods in the appropriate UI. Open lib/login.dart and find the Login button. In the onPressed action of the button, add the following code after the check.</p><pre>final success = await ref<br>  .read(AuthState.provider.notifier)<br>  .createSession(_phoneController.text);<br>if (!mounted) return;<br>if (success) {<br>  Navigator.pushNamed(context, &#39;/verify&#39;);<br>}</pre><p>Open lib/verify_phone.dart and find the Verify button. In the onPressed action of the button, add the following code after the check.</p><pre>final loggedIn = await ref<br>    .read(AuthState.provider.notifier)<br>    .confirmSession(currentText);<br>if (!mounted) return;<br>if (loggedIn) {<br>  Navigator.pushReplacementNamed(context, &#39;/&#39;);<br>} else {<br>  ScaffoldMessenger.of(context).showSnackBar(SnackBar(<br>    content: Text(ref.read(AuthState.provider).error),<br>  ));<br>}</pre><p>Here we are calling Appwrite with the code received in the SMS. There’s one last thing we need to do -- we need to make a call to get an account. Open lib/providers/app_state.dart and add the following function.</p><pre>Future&lt;bool&gt; getAccount() async {<br>    try {<br>      user = await _account.get();<br>      isLoggedIn = true;<br>      notifyListeners();<br>      return true;<br>    } on AppwriteException catch (e) {<br>      _error = e.message ?? e.toString();<br>      isLoggedIn = false;<br>      user = null;<br>      notifyListeners();<br>      return false;<br>    }<br>  }</pre><p>Call this function in the constructor of the AuthState, so when the application starts, it checks if we already have a valid session. You can now run the application and see the phone authentication in action.</p><h3>Conclusion</h3><p>That’s how easy it is to set up phone authentication with Appwrite. You can choose between different providers --<a href="https://twilio.com/">Twilio</a>, <a href="https://www.telesign.com/">Telesign</a>, and <a href="https://www.textmagic.com/">TextMagic</a> at the moment. You are also welcome to contribute by adding more providers. To learn more about Appwrite and to integrate it with Flutter, here are a few more resources that might help:</p><ul><li><a href="https://appwrite.io/docs/getting-started-for-flutter">Getting Started for Flutter</a></li><li><a href="https://appwrite.io/docs">Appwrite Docs</a></li><li><a href="https://appwrite.io/discord">Appwrite Discord</a></li><li><a href="https://github.com/appwrite/appwrite">Appwrite Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=434468bb7d85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Social Authentication on Flutter with Appwrite]]></title>
            <link>https://medium.com/appwrite-io/social-authentication-on-flutter-with-appwrite-7639529eb0cc?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7639529eb0cc</guid>
            <category><![CDATA[appwrite]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Fri, 17 Jun 2022 04:18:17 GMT</pubDate>
            <atom:updated>2022-07-18T18:39:31.599Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*t3nslJ0paAYGCHUA.png" /></figure><p>Today, we will learn to set up social authentication in our Flutter applications using Appwrite. By the end of this tutorial, you will know that setting up social authentication in the Flutter app using Appwrite is so easy that it can be done in a few minutes.</p><h3>Prerequisites</h3><p>To take full advantage of this tutorial, you need the following:</p><ul><li>Access to the Appwrite project or permission to create one. If you don’t already have an Appwrite server running, follow the official<a href="https://appwrite.io/docs/installation"> installation tutorial</a> to set up one.</li><li>Flutter configured development machine.</li></ul><h3>Source Code</h3><p>To begin, clone the <a href="https://github.com/lohanidamodar/flappwrite_oauth">repository</a> I’ve prepared for this tutorial where I have already set up a basic UI so that we can focus on implementing social login with Appwrite. We will start by adding and configuring the Appwrite SDK.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jRtBF7RyiXqn0oZ9" /></figure><h3>Configure Appwrite’s SDK</h3><p>First, open pubspec.yaml and add appwrite: 4.0.2 as a dependency, and run flutter pub get.</p><pre>dependencies:<br>  appwrite: 4.0.2</pre><p>Next open main_screen.dart and import the package.</p><pre>import &#39;package:appwrite/appwrite.dart&#39;;</pre><p>In the _MainScreenState , let&#39;s configure the client.</p><p>First, create a client property.</p><pre>class _MainScreenState extends State&lt;MainScreen&gt; {</pre><pre>  final Client client;</pre><pre>  ...</pre><pre>}</pre><p>Then in initState function, we configure the client.</p><pre>client = Client();</pre><pre>client</pre><pre>  .setEndpoint(&#39;[YOUR_APPWRITE_ENDPOINT]&#39;) // your endpoint</pre><pre>  .setProject(&#39;[YOUR_PROJECT_ID]&#39;); // Yout project id</pre><h3>Configure Discord OAuth</h3><p>Either use an existing Appwrite project or create a new one. Go to <strong>Users →Settings.</strong> This is where we will set up the OAuth providers. Let’s first set up Discord. Click to turn on the Discord’s switch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cSKprtgBR9o5Id2g72HvQ.png" /></figure><p>We need to fill in the app ID and secret in the dialog that appears. We can get that from the Discord developer portal following the <a href="https://discord.com/developers/docs/topics/oauth2">official guide</a>. Copy the callback URL provided in the dialog and paste it into Discords setup for the redirect URL. Click Update once the app ID and secrets are filled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d6_-xuFmHIoM6M_x" /></figure><h3>Configure Google Sign In</h3><p>In the Appwrite console, visit the Users→Settings page. There, find Google from the list and turn the switch on. To complete this, you will need an App ID and App Secret, which you can easily set up from Google API Console. Check out <a href="https://support.google.com/googleapi/answer/6158849">their official documentation</a> for more details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2PCvoGMZkmE4EY4KyauTA.png" /></figure><p>Once you get and fill in the Google <strong>App ID</strong> and the <strong>App Secret</strong>, you need to provide the callback URL shown in the dialog to the Google OAuth2’s Authorized redirect URIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6ltedpqY6SOgG4aC" /></figure><p>Authorized JavaScript origins are required only for a web app. If you are also using Flutter web, you should add the URL as the Authorized JavaScript origins</p><p>Now that we have configured Google and Discord OAuth in the Appwrite console, we will implement this social auth in our Flutter application in the next section.</p><h3>Implement OAuth login on Appwrite</h3><p>Before we can make any request to the Appwrite server from our applications, we need to add the platform we are building for <a href="http://appwrite.in/">Appwrite.</a> On the project dashboard, click <strong>Add Platform</strong> → <strong>New Flutter App</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwnemsbjQ6mTpUs5Wkag3w.png" /></figure><p>In the dialog that appears, add the relevant platforms. I’ll be adding Android. If you want to add more than one platform, follow the same process for each platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJttFeDZt-MVAU1DUwlxDA.png" /></figure><p>Next, in Android, to handle redirection successfully after the authentication is completed, we need to add the following to the AndroidManifest.xml.</p><pre>&lt;manifest ...&gt;<br>  ...<br>  &lt;application ...&gt;<br>    ...<br>    &lt;!-- Add this inside the `&lt;application&gt;` tag, along side the existing `&lt;activity&gt;` tags --&gt;<br>    &lt;activity android:name=&quot;com.linusu.flutter_web_auth.CallbackActivity&quot; android:exported=&quot;true&quot;&gt;<br>      &lt;intent-filter android:label=&quot;flutter_web_auth&quot;&gt;<br>        &lt;action android:name=&quot;android.intent.action.VIEW&quot; /&gt;<br>        &lt;category android:name=&quot;android.intent.category.DEFAULT&quot; /&gt;<br>        &lt;category android:name=&quot;android.intent.category.BROWSABLE&quot; /&gt;<br>        &lt;data android:scheme=&quot;appwrite-callback-[PROJECT_ID]&quot; /&gt;<br>      &lt;/intent-filter&gt;<br>    &lt;/activity&gt;<br>  &lt;/application&gt;<br>&lt;/manifest&gt;</pre><p>For iOS, version 12+ and macOS version 10.15+ are required for OAuth to work. And open Info.plist file and add the following configuration.</p><pre>&lt;key&gt;CFBundleURLTypes&lt;/key&gt;<br>&lt;array&gt;<br>  &lt;dict&gt;<br>    &lt;key&gt;CFBundleTypeRole&lt;/key&gt;<br>    &lt;string&gt;Editor&lt;/string&gt;<br>    &lt;key&gt;CFBundleURLName&lt;/key&gt;<br>    &lt;string&gt;io.appwrite&lt;/string&gt;<br>    &lt;key&gt;CFBundleURLSchemes&lt;/key&gt;<br>    &lt;array&gt;<br>	&lt;string&gt;appwrite-callback-[PROJECT_ID]&lt;/string&gt;<br>    &lt;/array&gt;<br>  &lt;/dict&gt;<br>&lt;/array&gt;</pre><p>Finally, we can now log in with Google and Discord in our Application. It is straightforward. We instantiate Account with an instance of Client and call createOAuth2Session.</p><pre>final account = Account(client);<br>account.createOAuth2Session(provider: &#39;google&#39;);</pre><p>Open main_screen.dart find _MainScreenState, and there find the handleLogin function. This is called when we press Google login or Discord login buttons. We pass the respective provider, google, or discord as the param. Update the handleLogin function as the following.</p><pre>handleLogin(String provider) async {<br>    await Account(client).createOAuth2Session(<br>      provider: provider,<br>    );<br>    checkedLoggedIn();<br>  }</pre><p>The first thing to note, we only need to pass the provider and not the success and failure URL. Success and failure URLs are required only if we implement our own web application that handles completing the login process from the authorization code obtained from OAuth providers. However, this is handled by the Appwrite server internally, so we don’t need to provide the success and failure URLs.</p><p>Another thing to note, the log-in and sign-up process for OAuth-based authentication are the same, and the createOAuth2Session automatically creates a User if it doesn’t already exist in Appwrite. Also, if a user account already exists with the same email address, the OAuth session is linked to the same user account.</p><h3>Conclusion</h3><p>Well, that’s all that is required to set up OAuth-based authentication with Appwrite. The final code can be found in the <a href="https://github.com/lohanidamodar/flappwrite_oauth/tree/final">final branch of the repository</a>. The challenging parts are setting up the specific provider and getting the client ID and secret from them. The rest is straightforward using Appwrite. Following resources can be handy if you want to explore Appwrite further.</p><ul><li><a href="https://appwrite.io/docs/getting-started-for-flutter">Getting Started for Flutter</a></li><li><a href="https://appwrite.io/docs">Appwrite Docs</a></li><li><a href="https://appwrite.io/discord">Appwrite Discord</a></li><li><a href="https://github.com/appwrite/appwrite">Appwrite Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7639529eb0cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appwrite-io/social-authentication-on-flutter-with-appwrite-7639529eb0cc">Social Authentication on Flutter with Appwrite</a> was originally published in <a href="https://medium.com/appwrite-io">Appwrite</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s New in Appwrite’s Storage]]></title>
            <link>https://lohanidamodar.medium.com/whats-new-in-appwrite-s-storage-2fb0273c545b?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fb0273c545b</guid>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[appwrit]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Wed, 09 Mar 2022 19:45:41 GMT</pubDate>
            <atom:updated>2022-03-23T07:59:17.938Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Z8wUvI9ogaW6VdHc.png" /></figure><p><a href="https://appwrite.io/">Appwrite</a> comes with a robust storage service to help you manage files required for your application. Appwrite’s storage service provides API for uploading and managing files, manipulating images, getting image previews, and more. It has built-in security, access control using users, teams, and roles, built-in encryption, and antivirus scanning. Also, the image preview manipulation endpoint comes with caching to keep it efficient. With the release of Appwrite 0.13, we are adding more power to Appwrite’s already powerful storage service. We have introduced buckets to group files with additional configurations. We have improved efficient handling of large files and have introduced support for external storage services to use as Appwrites storage location. Let’s look at each of these new features independently</p><p>Appwrite is an open source backend-as-a-service that abstracts all the complexity involved in building a modern application by providing you with a set of REST APIs for your core backend needs. Appwrite handles user authentication and authorization, databases, file storage, cloud functions, webhooks, and much more! If anything is missing, you can extend Appwrite using your favorite backend language.</p><h3>Buckets</h3><p>With version 0.13 of Appwrite, we have introduced buckets. Buckets are simply a collection of files. If you have previously worked with Appwrite’s database service, buckets are similar to collections in database service. Buckets allow you to have additional control over your files. You can group files based on domain, type, or any other logic that suits your application using buckets. Buckets make file organization better. Not only that, buckets allow you additional control by specifying what type and size of files can go into it, whether or not to encrypt the files in the bucket and whether or not to scan files going into the bucket with antivirus. To learn more about buckets, visit our storage docs.</p><h3>External Storage Support</h3><p>Files are important and even important is to have them in a reliable storage. Appwrite 0.13.0 introduces support for AWS S3 and DigitalOcean spaces as a storage solution for Appwrite. So, if you want to, you can set any files uploaded to Appwrite storage to directly be uploaded to AWS S3 bucket or DigitalOcean spaces. In the upcoming days we will introduce support for more storage solutions so that you will not be limited to these two services. To learn more about setting up Appwrite to use S3 or DigitalOcean spaces, check out the storage environment variables docs.</p><h3>Large File</h3><p>There are many applications where we would want to use and store huge files. Appwrite 0.12, and the previous versions did not handle large files efficiently. From version 0.13, Appwrite handles the uploading and downloading of large files efficiently. You can now upload gigabytes of files easily using the chunked upload process. Appwrite uploads large files by breaking them into smaller chunks so that the server can handle them efficiently and the API is more robust and stable. Check out our blog post to learn more about implementing large file support.</p><h3>Conclusion</h3><p>Storage is an essential service for applications, and Appwrite, a back-end service, provides a practical storage service that you can use to manage your application files. And with the 0.13 version of Appwrite, the storage service adds more powerful features that will help you organize your files, play with large files for complex applications, and more. We hope these new features of Appwrite will open up a whole new domain of possibilities for developers out there. We can’t wait to see what you will build with it.</p><p><em>Originally published at </em><a href="https://dev.to/appwrite/whats-new-in-appwrites-storage-30pf"><em>https://dev.to</em></a><em> on March 9, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fb0273c545b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Efficiently Handling Large Files Upload and Download]]></title>
            <link>https://lohanidamodar.medium.com/efficiently-handling-large-files-upload-and-download-bd5cdfbd09c0?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd5cdfbd09c0</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[appwrite]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Tue, 08 Mar 2022 16:41:54 GMT</pubDate>
            <atom:updated>2022-03-23T07:58:18.390Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*an_ns84JAwa9UNZy.png" /></figure><h3>Introduction</h3><p>Uploading files to remote servers is an essential operation for many applications. While developing a tool like Appwrite, it is crucial to efficiently handle the uploading of files to use it in their application without being concerned about the efficiency and reliability. Managing files upload comes with a challenge when dealing primarily with huge files. We need to think about efficient resource usage in both the client and server and a reliable upload process. This article will discuss our learning from adding support for huge file upload in Appwrite’s 0.13 release. So let’s get started.</p><blockquote><a href="https://appwrite.io/"><em>Appwrite</em></a><em> is an open source backend-as-a-service that abstracts all the complexity involved in building a modern application by providing you with a set of REST APIs for your core backend needs. Appwrite handles user authentication and authorization, databases, file storage, cloud functions, webhooks, and much more! If anything is missing, you can extend Appwrite using your favorite backend language.</em></blockquote><h3>Overview</h3><p>First, when discussing file uploads using the HTTP protocol, let us understand the basic upload process from client and server perspectives. To upload a file to the client, first, we load the file into memory and make a request over HTTP to the server. The server then receives the file and saves it in a temporary location. Then we can decide to move the file to the appropriate location. The problem with this process is that the server freezes until the file is completely uploaded. And If we want to handle huge files, say gigabytes of files, we would need as many resources, memory, and CPU to handle those files. Also, the server would take much time to respond to requests. If the upload fails in between, the client will have to re-initiate the upload process from the beginning, which wastes time and resources. Also, imagine a server where hundreds of users are trying to upload gigabytes of files simultaneously. The server would need considerable resources to handle those requests. Many requests will have to wait long before the server can respond to them if the server resources are limited, which is not recommended. So this method is suitable for reasonably small file size uploads. Now that we know the challenges of uploading files, we will discuss what options are available to upload files in the next section.</p><h3>Handling File Uploads</h3><p>Researching the ways to handle file uploads to web servers, we mainly found two ways. On is the basic upload process we discussed in the previous section. If we use this approach, it is recommended to set a maximum upload size limit to around 20–30 MB to keep things simple and effective. But for us, that was not an option, as a developer tool limiting our users and would be unsuitable for various applications.</p><p>The next method that we found was the chunked upload process. Which was efficient, less resource-intensive, and in case of failure, would support resumable upload. Which meant we could use this for smaller as well as huge files. And that is what we decided to implement in Appwrite 0.13 to power our developers. In the next section, we will look into how this method works and its efficiency.</p><h3>Chunking and Content Range</h3><p>Until a specific file size, it is okay to use the simple file upload approach. However, when the file size grows, it is recommended to use chunked upload. So how do we upload files using chunks? In this method, we don’t send the whole file in a single request; we instead send a chunk (a part of the file) and make multiple requests with each part. The benefit is that the server doesn’t have to receive the whole file at once but rather receives small chunks. This makes both the upload process and server responsive. Also, we can only upload those chunks that failed; we don’t have to upload the whole file again. This makes uploading large files efficiently, even over unstable connections. Also, this opens up another possibility to upload multiple chunks in parallel, making the upload process much faster if the network bandwidth allows. While sending each chunk, we set the associated content-range header. The server uses the content-range header to determine the total chunks uploaded and part of the file the chunk belongs to. The content-range header is defined in the HTTP specification. The syntax is defined as the following</p><pre>Content-Range: &lt;unit&gt; &lt;range-start&gt;-&lt;range-end&gt;/&lt;size&gt; Content-Range: &lt;unit&gt; &lt;range-start&gt;-&lt;range-end&gt;/* Content-Range: &lt;unit&gt; */&lt;size&gt;</pre><p>We need to set the unit, generally in bytes, and then the range-start is the start offset of this chunk and range-end is the end offset of this chunk, and finally, the size is the total size of the file. The value of range-start, range-end, and size must be in the unit provided. These headers in each chunk will tell the server exactly how to combine the chunks to get the original file. Now that we know how the chunked upload process works let’s see how we can make the upload process resumable in the next section.</p><h3>Resumable Upload</h3><p>With the implementation of chunked upload, it is relatively easy to implement resumable uploads. To make it happen, we can track each successful chunk uploaded and each that has failed during upload. Whenever the upload process stops in between, we will record all the successfully uploaded chunks. Next time, we can start the upload process only for the remaining chunks. This makes it very easy to upload large files over an unstable connection as we can upload small chunks and only upload failed and remaining chunks with as many retries as possible.</p><h3>Conclusion</h3><p>Handling file uploads reliably and efficiently can be challenging. We saw in this article that we have two ways of uploading files: one, we upload the whole file in a single request, and another where we upload a file in smaller chunks. We should use the first approach for smaller file sizes, maybe up to 20–30MB, and for any file larger than that, it’s best to implement a chunked upload to make the upload process reliable and efficient. We hope this article will be helpful to anyone trying to build an upload service. However, if you are using Appwrite, you will not have to think about all these things. Appwrite handles everything internally to provide reliable and efficient storage service to upload and manage files.</p><p><em>Originally published at </em><a href="https://dev.to/appwrite/efficiently-handling-large-files-upload-and-download-5eg1"><em>https://dev.to</em></a><em> on March 8, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd5cdfbd09c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s Build a Job Portal with iOS]]></title>
            <link>https://lohanidamodar.medium.com/lets-build-a-job-portal-with-ios-385818b61386?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/385818b61386</guid>
            <category><![CDATA[appwrite]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Thu, 21 Oct 2021 18:25:51 GMT</pubDate>
            <atom:updated>2021-10-28T07:25:18.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8-F0QMF0efyYL64dQ7S9g.png" /></figure><p>Hey 👋 iOS devs, if you hadn’t heard, Appwrite 0.11 has just released with platform wide Apple support. So, what is Appwrite? Appwrite is an open-source self-hosted end-to-end backend as a service for web and mobile applications. Learn more at <a href="https://appwrite.io/">Appwrite.io</a>. In this tutorial, we are going to build a job portal application for iOS with SwiftUI using Appwrite as the back-end service. So let’s get started.</p><h3>📝 Technical Requirement</h3><p>In order to continue with this tutorial, you will need to have the following:</p><ol><li>Access to an Appwrite project or permission to create one. If you don’t already have an Appwrite instance, you can always install it using our <a href="https://appwrite.io/docs/installation">official installation guide</a>.</li><li>Access to XCode 12 or newer. Find more about Xcode <a href="https://developer.apple.com/xcode">here</a></li></ol><h3>🛠️ Create iOS project</h3><p>We will start by creating a new project. Open Xcode and select start new project. On the next screen select iOS -&gt; App, then click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AoNDcY9lHZKxaseWzdkhlw.png" /></figure><p>On the next screen, give your project a name, organization id and in interface select SwiftUI and language Swift, then click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-H2NGI7g_kDx30C8jvWooA.png" /></figure><p>On the next screen, select the folder where you want to save your new project and click create. This will create a new project and open it in Xcode. You should now see the following screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L60G5CdCOAluBCjMAMFD_Q.png" /></figure><h3>🔐 Authentication</h3><p>We will start by implementing authentication. For that we will create a LoginView, AuthViewModel and AppwriteService. In order to create a view just hit cmd+N on your keyboard. You will be presented with the new file dialog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kaCSwx6h4gniy6GQDuhatQ.png" /></figure><p>There select <strong>SwiftUI View</strong> option and click next. In the next dialog box rename your view to <strong>LoginView</strong> and click create button to create the view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7dZ5L9U68dO8v_zg7iIWQ.png" /></figure><p>Update the code of the <strong>LoginView</strong> to the following.</p><pre>import SwiftUI<br><br>struct LoginView: View {<br>    @State private var email = &quot;&quot;<br>    @State private var password = &quot;&quot;<br>    @State private var isActiveSignup = false<br><br>    @EnvironmentObject var authVM: AuthViewModel<br><br>    var body: some View {<br>        NavigationView {<br>            VStack {<br>                NavigationLink(destination: SignupView(), isActive: $isActiveSignup) {<br>                    EmptyView()<br>                }<br>                HStack {<br>                    Text(&quot;Welcome back to\nAppwrite Jobs&quot;)<br>                        .font(.largeTitle)<br>                        .padding(.top, 60)<br>                        .multilineTextAlignment(.leading)<br>                    Spacer()<br>                }<br>                Spacer().frame(height: 10)<br>                HStack {<br>                    Text(&quot;Let&#39;s sign in.&quot;)<br>                        .font(.title)<br>                    Spacer()<br>                }<br>                .padding(.bottom, 30)<br><br>                TextField(&quot;E-mail&quot;, text: self.$email)<br>                    .padding()<br>                    .background(Color.gray.opacity(0.2))<br>                    .cornerRadius(16.0)<br><br>                SecureField(&quot;Password&quot;, text: self.$password)<br>                    .padding()<br>                    .background(Color.gray.opacity(0.2))<br>                    .cornerRadius(16.0)<br><br>                Spacer().frame(height: 16)<br><br>                Button(&quot;Login&quot;) {<br>                    authVM.login(email: email, password: password)<br>                }<br>                .foregroundColor(.white)<br>                .padding()<br>                .frame(width: 300, height: 50)<br>                .background(Color.pink)<br>                .cornerRadius(16.0)<br><br>                HStack {<br>                    Text(&quot;Anonymous Login&quot;)<br>                        .onTapGesture {<br>                            authVM.loginAnonymous()<br>                        }<br>                    Text(&quot;.&quot;)<br>                    Text(&quot;Signup&quot;)<br>                        .onTapGesture {<br>                            isActiveSignup = true<br>                        }<br>                }<br>                .padding(.top, 30)<br>                Spacer()<br><br>            }<br>            .foregroundColor(.white)<br>            .padding([.leading, .trailing], 40)<br>            .navigationBarTitleDisplayMode(.inline)<br>            .navigationBarHidden(true)<br>        }<br>    }<br>}<br><br>struct LoginView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        LoginView()<br>            .preferredColorScheme(.dark)<br>    }<br>}</pre><p>This will create a simple login view as the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqQo9u3vOBp3xrrHK6WWwA.png" /></figure><p>Similarly let’s create <strong>SignupView</strong> and update with the following code.</p><pre>import SwiftUI<br><br>struct SignupView: View {<br>    @State private var email = &quot;&quot;<br>    @State private var password = &quot;&quot;<br>    @State private var name = &quot;&quot;<br><br>    @EnvironmentObject var authVM: AuthViewModel<br>    @Environment(\.presentationMode) var presentationMode<br><br>    var body: some View {<br>        VStack {<br>            HStack {<br>                Image(&quot;back-icon&quot;)<br>                    .resizable()<br>                    .frame(width: 24, height: 21)<br>                    .onTapGesture {<br>                        presentationMode.wrappedValue.dismiss()<br>                    }<br>                Spacer()<br>            }<br>            .padding([.top, .bottom], 30)<br><br>            HStack {<br>                Text(&quot;Join\nAppwrite jobs&quot;)<br>                    .font(.largeTitle)<br>                Spacer()<br>            }<br><br>            Spacer().frame(height: 10)<br><br>            HStack {<br>                Text(&quot;Create an account&quot;)<br>                    .font(.title)<br>                    .padding(.bottom)<br>                Spacer()<br>            }<br>            .padding(.bottom, 30)<br><br>            TextField(&quot;Name&quot;, text: self.$name)<br>                .padding()<br>                .background(Color.gray.opacity(0.2))<br>                .cornerRadius(16.0)<br><br>            TextField(&quot;E-mail&quot;, text: self.$email)<br>                .padding()<br>                .background(Color.gray.opacity(0.2))<br>                .cornerRadius(16.0)<br><br>            SecureField(&quot;Password&quot;, text: self.$password)<br>                .padding()<br>                .background(Color.gray.opacity(0.2))<br>                .cornerRadius(16.0)<br>            Spacer().frame(height: 16)<br>            Button(&quot;Create account&quot;) {<br>                authVM.create(name: name, email: email, password: password)<br>            }<br>            .foregroundColor(.white)<br>            .padding()<br>            .frame( maxWidth: .infinity, maxHeight: 60)<br>            .background(Color.pink)<br>            .cornerRadius(16.0)<br><br>            Spacer()<br>        }<br>        .padding([.leading, .trailing], 27.5)<br>        .navigationBarHidden(true)<br>    }<br>}<br><br>struct SignupView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        SignupView()<br>            .preferredColorScheme(.dark)<br>    }<br>}</pre><p>This will create a simple signup view as the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72UxefkdjuRcDWRwiG7mTA.png" /></figure><p>Also create <strong>HomeView</strong> where later we will display the list of jobs.</p><pre>import SwiftUI<br><br>struct HomeView: View {<br>    @EnvironmentObject var authVM: AuthViewModel<br><br>    var body: some View {<br>        VStack {<br>            HStack {<br>                Text(&quot;Appwrite Jobs&quot;)<br>                    .font(.title)<br>                    .fontWeight(.bold)<br>                Spacer()<br>                Text(&quot;Logout&quot;)<br>                    .onTapGesture {<br>                        authVM.logout()<br>                    }<br>            }<br>            .padding(.top, 40)<br>            .padding(.horizontal, 36)<br><br>            ScrollView {<br>                HStack {<br>                    Text(&quot;Find your dream\njobs&quot;)<br>                        .font(.largeTitle)<br>                    Spacer()<br>                }<br>                .padding(.vertical, 30)<br>                .padding(.horizontal, 36)<br><br>                Text(&quot;Hello World&quot;)<br>            }<br>        }<br>    }<br>}<br><br>struct HomeView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        HomeView()<br>            .preferredColorScheme(.dark)<br>    }<br>}</pre><p>Also create <strong>MainView</strong> and update with the following code</p><pre>import SwiftUI<br><br>struct MainView: View {<br>    @EnvironmentObject var authVM: AuthViewModel<br><br>    var body: some View {<br>        Group {<br>            if authVM.isLoggedIn {<br>                HomeView()<br>            } else {<br>                LoginView()<br>            }<br>        }<br>        .animation(.easeInOut)<br>        .transition(.move(edge: .bottom))<br>    }<br>}<br><br>struct ContentView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        MainView()<br>    }<br>}</pre><p>This is a simple view that displays either <strong>LoginView</strong> or <strong>HomeView</strong> based on authentication state.</p><p>Next, let’s create our <strong>AuthViewModel</strong>. Hit cmd+N again. This time select <strong>Swift File</strong> and click next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*etQf5HFtFYLd6apyVGdVtw.png" /></figure><p>Now name your file <strong>AuthViewModel</strong> and click create.</p><p>Following the above steps, create another swift file and name it <strong>AppwriteService</strong>.</p><p>This is a simple class responsible for initializing the Appwrite SDK and exposing the account service for use in the authentication view model.</p><p>Let us also organize our code files into groups. In the left sidebar right click on <strong>Appwrite Jobs</strong> and select New Group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ilIdXxugf_oMaxyUckVW8g.png" /></figure><p>Rename the newly created group into <strong>Views</strong>. Follow the same process to create another group called <strong>ViewModels</strong>. Now drag and drop the view files and view model files to the respective groups. Your project explorer should look like the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjV1HwqJdtt3rqS8lhPM2w.png" /></figure><p>Before we can continue, we first need to add the Appwrite Swift SDK as a dependency. To do that, go to File -&gt; Add Packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mr-Mx7tKUuFcbZTcSDILvA.png" /></figure><p>In the new dialog that appears, tap the top right search icon and type the GitHub URL for the SDK <a href="https://github.com/appwrite/sdk-for-apple"><strong>https://github.com/appwrite/sdk-for-apple</strong></a> and hit Enter. You should see the <strong>sdk-for-apple</strong> package listed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7aaqy1Zo27avZU8SqbSpQ.png" /></figure><p>Now select the <strong>sdk-for-apple</strong> package and on the right side, select dependency rule as * <em>Branch</em>, then choose from main for stable code or dev for the latest code. Now click on the Add Package button. Xcode will download the Appwrite Swift SDK along with its dependencies and will be added to your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQTRcCyF4X-NfOOpWBpy6Q.png" /></figure><p>Make sure the proper target is selected in the Add to target view, then click Add Package button. The package should successfully be added to your project.</p><p>Once we have the package, now we can initialize our Appwrite SDK. To do that, update <strong>AppwriteService</strong> class with the following code.</p><pre>import Foundation<br><br>import Appwrite<br><br>class AppwriteService {<br>    private(set) var client: Client<br>    private(set) var account: Account<br><br>    static let shared = AppwriteService()<br><br>    init() {<br>        client = Client()<br>            .setEndpoint(&quot;YOUR_ENDPOINT&quot;)<br>            .setProject(&quot;YOUR_PROJECT_ID&quot;)<br><br>        account = Account(client: client)<br>    }<br>}</pre><p>Here, we are creating an Appwrite service class that has client and account variables. We also have a public static shared instance of AppwriteService class to make it easily accessible.</p><p>In the init method we are initializing our SDK and then the account service. To initialize the SDK, you need to instantiate the Client object and set at least the endpoint and project ID, both of which can be obtained from the Appwrite console, which we will look into in the next section.</p><p>Now that we have our SDK initialized and ready and account service instantiated, let us update the <strong>AuthViewModel</strong> with the following code.</p><pre>import Foundation<br>import Appwrite<br><br>class AuthViewModel: ObservableObject {<br>    @Published var isLoggedIn = false<br>    @Published var error: String?<br>    @Published var user: User?<br><br>    static let shared = AuthViewModel()<br><br>    init() {<br>        getAccount()<br>    }<br><br>    private func getAccount() {<br>        AppwriteService.shared.account.get() { result in<br>            DispatchQueue.main.async {<br>                switch result {<br>                case .failure(let err):<br>                    self.error = err.message<br>                    self.isLoggedIn = false<br>                case .success(let user):<br>                    self.user = user<br>                    self.isLoggedIn = true<br>                }<br><br>            }<br>        }<br>    }<br><br>    func create(name: String, email: String, password: String) {<br>        AppwriteService.shared.account.create(email: email, password: password, name: name) { result in<br>            switch result {<br>            case .failure(let err):<br>                DispatchQueue.main.async {<br>                    print(err.message)<br>                    self.error = err.message<br>                }<br>            case .success:<br>                self.login(email: email, password: password)<br>            }<br>        }<br>    }<br><br>    func logout() {<br>        AppwriteService.shared.account.deleteSession(sessionId: &quot;current&quot;) { result in<br>            DispatchQueue.main.async {<br>                switch result {<br>                case .failure(let err):<br>                    self.error = err.message<br>                case .success(_):<br>                    self.isLoggedIn = false<br>                    self.error = nil<br>                }<br>            }<br>        }<br>    }<br><br>    func loginAnonymous() {<br>        AppwriteService.shared.account.createAnonymousSession() { result in<br>            switch result {<br>            case .failure(let err):<br>                DispatchQueue.main.async {<br>                    self.error = err.message<br>                }<br>            case .success:<br>                self.getAccount()<br>            }<br>        }<br>    }<br><br>    public func login(email: String, password: String) {<br>        AppwriteService.shared.account.createSession(email: email, password: password) { result in<br>            switch result {<br>            case .failure(let err):<br>                DispatchQueue.main.async {<br>                    self.error = err.message<br>                }<br>            case .success:<br>                self.getAccount()<br>            }<br>        }<br>    }<br>}</pre><p>Here we are extending ObservableObject so that we can publish changes to our UI. We have two published var to keep track of errors and logged in state so that UI can subscribe to those and update accordingly. Next up we have methods for login, get account and logout. Here we are using the Appwrite’s account service to perform those action. Logging in is as simple as calling a <strong>createSession</strong> method on account service object with email and password. Once the session is created calling the <strong>get</strong> method on account service will return the active user’s details. Finally logging user out is simple by calling <strong>deleteSession</strong> method with session id parameter as current to delete the currently active session.</p><p>We need to update the <strong>Appwrite_JobsApp</strong> as the following.</p><pre>import SwiftUI<br><br>@main<br>struct Appwrite_JobsApp: App {<br>    var body: some Scene {<br>        WindowGroup {<br>            MainView()<br>                .environmentObject(AuthViewModel.shared)<br>                .preferredColorScheme(.dark)<br>        }<br><br>    }<br>}</pre><p>Here we are passing the instance of <strong>AuthViewModel</strong> as the environment object so that we can access it from all of our views.</p><h3>👷‍♂️ Setting up Appwrite Project</h3><p>Great work. Now the only thing left to do to get our authentication working is set up our Appwrite project. If you already have a project set up on your Appwrite console, you can skip to the next section. If not, and you have a freshly installed Appwrite following our installation guide, then you can signup to create a root account. You should now be logged in and see an empty list of projects. Click on the <strong>Create Project</strong> button and give your project a name. Finally, click <strong>Create</strong> to create your project. You should then be redirected to the project’s dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lyoxRViIo1hqk6vEaCIEug.png" /></figure><p>Click Settings option to access the project settings. There on the right sidebar, you should find your endpoint and your project id. Update YOUR_ENDPOINT and YOUR_PROJECT_ID in the <strong>AppwriteService</strong> class with the values you obtain from project settings page. Finally you need to add a platform. Back to project home, scroll down and click on the <strong>Add Platform</strong> button and select New iOS App option. In the dialog box that appears, enter the easy to recognizable name for your platform and then the bundle id. You can find the bundle id for your project in XCode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SpiW6z1nCIMXS9MqW5Nc-g.png" /></figure><h3>💾 Setting up Database</h3><p>Now that we have set up our project, time to set up the database, a jobs collection for saving the list of jobs. In the Appwrite console on left sidebar, click on <strong>Database</strong>. In the database page, you can click <strong>Add Collection</strong> to create a new collection. In the dialog box that appears, enter the name of your collection and click <strong>Create</strong>. This will redirect you to the newly created collection’s page. We now need to add attributes to our collection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53dxiCllRH18EmowRtPEXQ.png" /></figure><p>On the collection settings page, tap on add and enter Label <strong>Title</strong>, key <strong>title</strong> and rule type <strong>Text</strong> and click on <strong>create</strong> button.</p><p>Once created, you can expand the rule under rules section and make it required. Similarly add the following rules</p><ul><li>Location<br>label : Location<br>key: location<br>rule type: Text<br>required: true</li><li>Link<br>label : Link<br>key: link<br>rule type: url<br>required: true</li><li>Company<br>label : Company<br>key: company<br>rule type: text<br>required: true</li></ul><p>Set the read and write permission as the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVn81UaLldCaDUc-fHA72A.png" /></figure><h3>🔬 Let’s Test Authentication</h3><p>Now that we have set up Appwrite project as well as our iOS project. It’s time to build and test that authentication is working. Open your iOS project in XCode and hit the play icon in the top left to start building the project. Once built it will run inside the Simulator that is selected and if successful it should look like the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqQo9u3vOBp3xrrHK6WWwA.png" /></figure><p>Tap <strong>Anonymous Login</strong>, you should be able to login and see the Home Page.</p><h3>👮‍♀️ Listing Jobs</h3><p>Time for listing jobs. We will start by creating <strong>Job</strong> model and update with the following code.</p><pre>import Foundation<br><br>class Job: Identifiable {<br>    public let id: String<br>    public let title: String<br>    public let link: String<br>    public let logo: String<br>    public let company: String<br>    public let description: String<br>    public let location: String<br><br>    init(<br>        id: String,<br>        title: String,<br>        link: String,<br>        logo: String,<br>        company: String,<br>        description: String,<br>        location: String<br>    ) {<br>        self.id = id<br>        self.title = title<br>        self.link = link<br>        self.logo = logo<br>        self.company = company<br>        self.description = description<br>        self.location = location<br>    }<br><br>    public static func from(map: [String: Any]) -&gt; Job {<br>        return Job(<br>            id: map[&quot;$id&quot;] as! String,<br>            title: map[&quot;title&quot;] as! String,<br>            link: map[&quot;link&quot;] as! String,<br>            logo: map[&quot;logo&quot;] as! String,<br>            company: map[&quot;company&quot;] as! String,<br>            description: map[&quot;description&quot;] as! String,<br>            location: map[&quot;location&quot;] as! String<br>        )<br>    }<br><br>    public func toMap() -&gt; [String: Any] {<br>        return [<br>            &quot;title&quot;: title as Any,<br>            &quot;link&quot;: link as Any,<br>            &quot;logo&quot;: logo as Any,<br>            &quot;company&quot;: company as Any,<br>            &quot;description&quot;: description as Any,<br>            &quot;location&quot;: location as Any<br>        ]<br>    }<br>}</pre><p>Secondly, create the <strong>JobItemView</strong> and update with the following code.</p><pre>import SwiftUI<br>import Kingfisher<br><br>struct JobItemView: View {<br>    let job: Job<br><br>    init(_ job: Job) {<br>        self.job = job<br>    }<br><br>    var body: some View {<br>        ZStack {<br>            RoundedRectangle(cornerRadius: 16, style: .continuous)<br>                .fill(.blue.opacity(0.2))<br><br>            VStack (alignment: .leading) {<br>                ZStack(alignment: .center) {<br>                    RoundedRectangle(cornerRadius: 14, style: .continuous)<br>                        .fill(.gray.opacity(0.5))<br><br>                    KFImage.url(https://medium.com/URL(string:%20job.logo))<br>                        .resizable()<br>                        .scaledToFit()<br>                        .frame(height: 50)<br>                }<br>                .frame(width: 86, height: 82)<br><br>                Text(job.title)<br>                    .font(.largeTitle)<br>                    .padding(.top, 24)<br><br>                HStack (spacing: 20) {<br>                    Text(job.company)<br>                        .fontWeight(.semibold)<br>                    Text(job.location)<br>                        .fontWeight(.semibold)<br>                }<br>                .padding(.bottom, 24)<br><br>                Text(job.description)<br>            }<br>            .padding(.all, 26)<br>        }<br>    }<br>}<br><br>struct JobItemView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        JobItemView(<br>            Job(<br>                id: &quot;1&quot;,<br>                title: &quot;Swift Developer&quot;,<br>                link: &quot;https://appwrite.io&quot;,<br>                logo: &quot;https://demo.appwrite.io/v1/storage/files/61667e8e6cb16/preview?project=615d75f94461f&quot;,<br>                company: &quot;Google&quot;,<br>                description: &quot;Swift Developer&quot;,<br>                location: &quot;Tel Aviv&quot;<br>            )<br>        )<br>        .preferredColorScheme(.dark)<br>    }<br>}</pre><p>This will create a simple job item card view.</p><p>Let us also create the <strong>JobsViewModel</strong> file and update with the following code.</p><pre>import Foundation<br><br>class JobsViewModel: ObservableObject {<br>    @Published var jobs: [Job] = []<br><br>    init() {<br>        getJobs()<br>    }<br><br>    func getJobs() {<br>        AppwriteService.shared.database.listDocuments(collectionId: &quot;615ec687829fa&quot;) {<br>            result in<br>            DispatchQueue.main.async {<br>                switch result {<br>                case .failure(let err):<br>                    print(err.message)<br>                case .success(let docList):<br>                    let convert: ([String: Any]) -&gt; Job = { dict in<br>                        return Job.from(map: dict)<br>                    }<br>                    self.jobs = docList.convertTo(fromJson: convert)<br>                }<br>            }<br>        }<br>    }<br>}</pre><p>Here again we are creating an observable object so that we can get and display the list of jobs in our UI. To get the list of jobs we are calling listDocuments and passing the collection id of the collection we created. If successful we update the list of job by converting the json into our job model.</p><p>Finally let’s update the <strong>HomeView</strong> with the following code.</p><pre>import SwiftUI<br><br>struct HomeView: View {<br>    @EnvironmentObject var authVM: AuthViewModel<br>    @ObservedObject var jobsVM: JobsViewModel = JobsViewModel()<br><br>    var body: some View {<br>        VStack {<br>            HStack {<br>                Text(&quot;Appwrite Jobs&quot;)<br>                    .font(.title)<br>                    .fontWeight(.bold)<br>                Spacer()<br>                Text(&quot;Logout&quot;)<br>                    .onTapGesture {<br>                        authVM.logout()<br>                    }<br>            }<br>            .padding(.top, 40)<br>            .padding(.horizontal, 36)<br><br>            ScrollView {<br>                HStack {<br>                    Text(&quot;Find your dream\njobs&quot;)<br>                        .font(.largeTitle)<br>                    Spacer()<br>                }<br>                .padding(.vertical, 30)<br>                .padding(.horizontal, 36)<br><br>                ForEach(jobsVM.jobs) { job in<br>                    JobItemView(job)<br>                        .padding(.vertical, 12)<br>                        .padding(.horizontal, 36)<br>                }<br>            }<br>        }<br>    }<br>}<br><br>struct HomeView_Previews: PreviewProvider {<br>    static var previews: some View {<br>        HomeView()<br>            .preferredColorScheme(.dark)<br>    }<br>}</pre><p>Now if you run and login you should see the list of jobs you have added in your collection. Mine looks as the following.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohBMg5BJ9HPIFceN5WoCCg.png" /></figure><p>We’ve built a complete app that interacts with Appwrite’s account and database APIs with our <a href="https://github.com/appwrite/sdk-for-apple">SDK for Apple</a> and SwiftUI, which you can find over at our <a href="https://github.com/appwrite/demo-job-portal-with-apple">GitHub Repo</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWoZgKj-rUe3IuPvTKMJQg.gif" /></figure><h3>✨️ Credits</h3><p>Hope you enjoyed this article! We can’t wait to see what you will build. If you get stuck anywhere, feel free to reach out to us on our <a href="https://appwrite.io/discord">friendly support channel</a> run by humans 👩‍💻.</p><p>Here are some handy links for more information:</p><ul><li><a href="https://appwrite.io/docs/getting-started-for-apple">Getting Started with Apple</a></li><li><a href="https://github.com/appwrite/playground-for-apple-swiftui">Swift Playground</a></li><li><a href="https://github.com/appwrite">Appwrite Github</a></li><li><a href="https://appwrite.io/docs">Appwrite Documentation</a></li></ul><p><em>Originally published at </em><a href="https://dev.to/appwrite/lets-build-a-job-portal-with-ios-50in"><em>https://dev.to</em></a><em> on October 21, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=385818b61386" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter Appwrite Tutorial Series — (ongoing)]]></title>
            <link>https://lohanidamodar.medium.com/flutter-appwrite-tutorial-series-ongoing-72ef3d5bb8ba?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/72ef3d5bb8ba</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[appwrite]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Fri, 04 Sep 2020 03:13:56 GMT</pubDate>
            <atom:updated>2021-02-25T01:59:04.239Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flutter Appwrite Tutorial Series — (ongoing)</h3><p>Appwrite is an open source back-end server, that you can easily setup using docker. And it can be used to support your web and mobile applications. And, it is great for Flutter developers to have Appwrite in their toolbox, as this will give them alternative to Firebase, or building own service in back-end. This is unique opportunity for Flutter developers, as they can focus on their application rather than on setting up a remote database, API and stuff. So, in this ongoing tutorial series, we will learn to setup Appwrite and use it as a back-end for our flutter application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_8DUuSZrmAKx23OHhWbgVw.png" /></figure><h3>Introduction</h3><p>In this episode I will introduce you to Appwrite and why is it important and what it provides.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeYXb_xbUjio%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeYXb_xbUjio&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeYXb_xbUjio%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/b828fc14161eaf64b90274da637ce1fc/href">https://medium.com/media/b828fc14161eaf64b90274da637ce1fc/href</a></iframe><h3>Episode 1 — Setup</h3><p>In this episode we will learn to setup Appwrite locally using docker, and define a database structure in Appwrite for the application we will be building in this series</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FteUUt4ZqIvI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DteUUt4ZqIvI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FteUUt4ZqIvI%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/82c5f7da7b43df8bed0a3d236a2f063f/href">https://medium.com/media/82c5f7da7b43df8bed0a3d236a2f063f/href</a></iframe><h3>Episode 2 — Wireframing</h3><p>In this episode we will create wireframe design for our flutter application using open source vector design tool — <a href="https://inkspace.org/">Inkspace</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRjE0tmyBdow%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRjE0tmyBdow&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRjE0tmyBdow%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/5b2ecafe04b3f89330f10f628436eedf/href">https://medium.com/media/5b2ecafe04b3f89330f10f628436eedf/href</a></iframe><h3>Episode 3 — New flutter project and UI design</h3><p>In this episode we will create a new flutter project and create UI for login and signup.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHvcemJhSeE8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHvcemJhSeE8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHvcemJhSeE8%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/5f2d4b7e721a42f8bf932c2a3a040b62/href">https://medium.com/media/5f2d4b7e721a42f8bf932c2a3a040b62/href</a></iframe><h3>Episode 4 — Authenticating users</h3><p>In this eipsode we will connect our Flutter app with Appwrite and allow users to login and signup.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FWcGQDmuwGMM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DWcGQDmuwGMM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FWcGQDmuwGMM%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/dc26e1305bdcd66b1ae04c0f0825272c/href">https://medium.com/media/dc26e1305bdcd66b1ae04c0f0825272c/href</a></iframe><p>Also remember to watch the 4.1 quick fix for permission error.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEBevk7dfTjY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEBevk7dfTjY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEBevk7dfTjY%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/10710aa8ecf262060faae77bdad6209a/href">https://medium.com/media/10710aa8ecf262060faae77bdad6209a/href</a></iframe><h3>Episode 5 — State management, Routing and Navigation setup</h3><p>In this episode, we will setup state management using Provider, setup Routing and Navigation</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FkYpwnYY9Gf8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DkYpwnYY9Gf8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkYpwnYY9Gf8%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/ded9c21a60229941f34c4cc7a997f03d/href">https://medium.com/media/ded9c21a60229941f34c4cc7a997f03d/href</a></iframe><h3>Episode 6 — Routing, profile page and logging out user</h3><p>In this episode we will continue on, setup routing, and design and display user’s profile page and allow users to logout.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4ZSX0VSg4bM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4ZSX0VSg4bM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4ZSX0VSg4bM%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/6a9b84cb257e555deb0b8a1e5616bccd/href">https://medium.com/media/6a9b84cb257e555deb0b8a1e5616bccd/href</a></iframe><h3>Episode 7 — Querying and Listing Transactions</h3><p>In this episode we will learn to query the appwrite database that we designed during appwrite setup and list the returned documents in Flutter application</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX9vw4PGDbGc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX9vw4PGDbGc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX9vw4PGDbGc%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/e0b867da7faaecf635610163f9dfe9ec/href">https://medium.com/media/e0b867da7faaecf635610163f9dfe9ec/href</a></iframe><h3>Episode 8 — Create, Read, Update and Delete operations</h3><p>In this episode we will allow users to create, read, update and delete the documents in the database.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1HodtTldSdA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1HodtTldSdA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1HodtTldSdA%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/0d89b49af5f2e52439ca1bf6b3ea3185/href">https://medium.com/media/0d89b49af5f2e52439ca1bf6b3ea3185/href</a></iframe><h3>Episode 9 — Searching, ordering and filtering</h3><p>In this episode we will learn to use appwrite to query, order and filter the documents returned by database.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbcG7G-1QBOk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbcG7G-1QBOk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbcG7G-1QBOk%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/e6e643dd60a24e9026cc666df28e0a73/href">https://medium.com/media/e6e643dd60a24e9026cc666df28e0a73/href</a></iframe><h3>Episode 10 — Deploying appwrite in VPS + Tips for running Appwrite in Production</h3><p>In this episode we will learn to deploy Appwrite server in production using digitalocean servers.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FWzHdvLItrEc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DWzHdvLItrEc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FWzHdvLItrEc%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/f44ae70f93d012748fabd93e806c12c8/href">https://medium.com/media/f44ae70f93d012748fabd93e806c12c8/href</a></iframe><h3>Episode 11 — User Preferences and Locale API</h3><p>In this episode we will learn about User’s preferences api that we can use to store settings for particular users and also some uses of Locale API provided by appwrite.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqKkgXy3H7Mw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqKkgXy3H7Mw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqKkgXy3H7Mw%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/11ccb1b6698ee2498b9c39fea9a4b43f/href">https://medium.com/media/11ccb1b6698ee2498b9c39fea9a4b43f/href</a></iframe><h3>Episode 12 — Storage Service, uploading files, preview</h3><p>In this episode we will learn to leverage the Appwrite’s storage service, to upload file and display previews. Here we are using it for uploading and displaying user’s profile picture.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCNjvNNYWgGU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCNjvNNYWgGU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCNjvNNYWgGU%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/89e12e7bc148a5926f419849927ea679/href">https://medium.com/media/89e12e7bc148a5926f419849927ea679/href</a></iframe><h3>Bonus — What’s coming to Appwrite 0.7 and beyond</h3><p>Appwrite has more greate features in plan for next version and beyond. We will look into those and also show you some of those features in action.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQEzvo9sUkik%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQEzvo9sUkik&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQEzvo9sUkik%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/7902315adf18aba9bf8d64976a14189c/href">https://medium.com/media/7902315adf18aba9bf8d64976a14189c/href</a></iframe><h3>Appwrite 0.7 is here</h3><p>Appwrite 0.7 has been released with awesome new features like Cloud Functions, Flutter Web support, Appwrite CLI and 100+ more features.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuuZq3K4Wjrc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuuZq3K4Wjrc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuuZq3K4Wjrc%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/5143b3053ebd7101b49108609653804e/href">https://medium.com/media/5143b3053ebd7101b49108609653804e/href</a></iframe><h3>Watch the whole series here</h3><p>This is the playlist for the whole Flutter + Appwrite tutorial series.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLUiueC0kTFqI9WIeUSkKvM-a_3fyaIiuk&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fplaylist%3Flist%3DPLUiueC0kTFqI9WIeUSkKvM-a_3fyaIiuk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeYXb_xbUjio%2Fhqdefault.jpg%3Fsqp%3D-oaymwEWCKgBEF5IWvKriqkDCQgBFQAAiEIYAQ%3D%3D%26rs%3DAOn4CLAp6Uzas4JABtDo0wsTTBeICjImOw&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="853" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/33c9055a1e032cfaa85e3d0135124643/href">https://medium.com/media/33c9055a1e032cfaa85e3d0135124643/href</a></iframe><h3>Source code for the series</h3><p>The source code for the series can be found in the Github repository linked below. The code after the completion of each episode can be found in the specific branches linked above</p><p><a href="https://github.com/lohanidamodar/flutter_appwrite">lohanidamodar/flutter_appwrite</a></p><h3>Want to Connect with me</h3><p>Facebook: <a href="https://fb.me/lohanidamodar"><strong>https://fb.me/lohanidamodar</strong></a><br>GitHub: <a href="https://github.com/lohanidamodar"><strong>https://github.com/lohanidamodar</strong></a><br>YouTube: <a href="https://youtube.com/c/reactbits"><strong>https://youtube.com/c/reactbits</strong></a><br>Twitter: <a href="https://twitter.com/LohaniDamodar"><strong>https://twitter.com/LohaniDamodar</strong></a><br>Linked In: <a href="https://www.linkedin.com/in/lohanidamodar"><strong>https://www.linkedin.com/in/lohanidamodar</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72ef3d5bb8ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter URL Preview]]></title>
            <link>https://lohanidamodar.medium.com/flutter-url-preview-a386920bdfe6?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a386920bdfe6</guid>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[flutterdev]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Tue, 25 Aug 2020 10:11:14 GMT</pubDate>
            <atom:updated>2020-08-25T10:11:14.680Z</atom:updated>
            <content:encoded><![CDATA[<p>So, what is URL preview if you remember whenever you share some url in facebook or twitter or any other social network the app automatically generates the preview for that url with the title image description this seems like a simple feature but this can add a lot of value to few types of applications like chat applications social network applications and any other applications where users are allowed to share data with one another so if they share any link having the preview of the url adds a lot of value.</p><p>If you would rather watch a video</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8c-EIwbNchw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8c-EIwbNchw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8c-EIwbNchw%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/558c849773e860bd0bda18aeea1d35f1/href">https://medium.com/media/558c849773e860bd0bda18aeea1d35f1/href</a></iframe><p>In flutter I found few different plugins to help display URL preview. However the one I liked “<a href="https://pub.dev/packages/flutter_link_preview">flutter_link_preview</a>” provided the most customization possible. One thing to note that, I was unable to get preview of youtube URLs from any of the available plugins. However most of them worked fine with other URLs. So in this tutorial we will learn to use “flutter_link_preview” plugin to display the preview of URL in our Flutter application.</p><p>The final source code for this tutorial can be found at my Github repository.</p><p><a href="https://github.com/lohanidamodar/flutter_plugin_tuts/tree/link-preview">lohanidamodar/flutter_plugin_tuts</a></p><h3>Let’s Begin</h3><p>To start, add flutter_link_preview: to the pubspec.yaml file under dependencies.</p><pre>dependencies:<br>  flutter_link_preview: ^1.4.2</pre><p>Then in your widget where you want to use the preview widget, import the “flutter_link_preview”</p><pre>import &#39;package:flutter_link_preview/flutter_link_preview.dart&#39;;</pre><p>Next, to get the preview of any url, use the following code, it gives the default preview with title, fav icon etc.</p><pre>FlutterLinkPreview(url: &quot;your url&quot;)</pre><p>Easy as that. Now, if we want to style the title and body text, we can pass in titleStyle and bodyStyle parameters.</p><pre>FlutterLinkPreview(<br>    url: &quot;your url&quot;,<br>    bodyStyle: TextStyle(<br>        fontSize: 18.0,<br>    ),<br>    titleStyle: TextStyle(<br>        fontSize: 20.0,<br>        fontWeight: FontWeight.bold,<br>    ),<br>)</pre><p>Default preview for URL “<a href="https://medium.com/@LohaniDamodar/flutter-recipes-2-firebase-firestore-recipes-2f09e58a7298">https://medium.com/@LohaniDamodar/flutter-recipes-2-firebase-firestore-recipes-2f09e58a7298</a>&quot; looked like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qeAF9aAX7ACfksBiI3BEPw.png" /><figcaption>Flutter URL Preview, default</figcaption></figure><p>Finally, if we want to completely customize how our preview looks, we can use the builder parameter, that gives us the information returned after parsing the url we provided and we build our own preview widget using the information provided.</p><pre>FlutterLinkPreview(<br>    url: article,<br>    bodyStyle: TextStyle(<br>        fontSize: 18.0,<br>    ),<br>    titleStyle: TextStyle(<br>        fontSize: 20.0,<br>        fontWeight: FontWeight.bold,<br>    ),<br>    builder: (info) {<br>        if (info is WebInfo) {<br>        return SizedBox(<br>            height: 350,<br>            child: Card(<br>            shape: RoundedRectangleBorder(<br>                borderRadius: BorderRadius.circular(20.0)),<br>            clipBehavior: Clip.antiAlias,<br>            child: Column(<br>                crossAxisAlignment: CrossAxisAlignment.start,<br>                children: [<br>                if (info.image != null)<br>                    Expanded(<br>                        child: Image.network(<br>                    info.image,<br>                    width: double.maxFinite,<br>                    fit: BoxFit.cover,<br>                    )),<br>                Padding(<br>                    padding: EdgeInsets.fromLTRB(16.0,16.0,16.0, 0),<br>                    child: Text(<br>                    info.title,<br>                    style: TextStyle(<br>                        fontSize: 20.0,<br>                        fontWeight: FontWeight.bold,<br>                    ),<br>                    ),<br>                ),<br>                if (info.description != null)<br>                    Padding(<br>                    padding: const EdgeInsets.all(16.0),<br>                    child: Text(info.description),<br>                    ),<br>                ],<br>            ),<br>            ),<br>        );<br>        }<br>        if (info is WebImageInfo) {<br>        return SizedBox(<br>            height: 350,<br>            child: Card(<br>            shape: RoundedRectangleBorder(<br>                borderRadius: BorderRadius.circular(20.0)),<br>            clipBehavior: Clip.antiAlias,<br>            child: Image.network(<br>                info.image,<br>                fit: BoxFit.cover,<br>                width: double.maxFinite,<br>            ),<br>            ),<br>        );<br>        } else if (info is WebVideoInfo) {<br>        return SizedBox(<br>            height: 350,<br>            child: Card(<br>            shape: RoundedRectangleBorder(<br>                borderRadius: BorderRadius.circular(20.0)),<br>            clipBehavior: Clip.antiAlias,<br>            child: Image.network(<br>                info.image,<br>                fit: BoxFit.cover,<br>                width: double.maxFinite,<br>            ),<br>            ),<br>        );<br>        }<br>    },<br>)</pre><p>Custom preview for URL “<a href="https://medium.com/@LohaniDamodar/flutter-recipes-2-firebase-firestore-recipes-2f09e58a7298">https://medium.com/@LohaniDamodar/flutter-recipes-2-firebase-firestore-recipes-2f09e58a7298</a>&quot; looked like</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c9FonCgZ6GFsgkiTR7-6BQ.png" /><figcaption>Flutter URL preview, with custom builder</figcaption></figure><p>As we can see from the code above, the information returned after parsing the URL can be of three different types WebInfo for normal web URLs, WebImageInfo for URLs of images and WebVideoInfo for the URLs of videos. We can us the type of information returned to display different preview and actions in our application.</p><h3>Want to connect with me</h3><p>Facebook: <a href="https://fb.me/lohanidamodar">https://fb.me/lohanidamodar</a><br>GitHub: <a href="https://github.com/lohanidamodar">https://github.com/lohanidamodar</a><br>YouTube: <a href="https://youtube.com/c/reactbits">https://youtube.com/c/reactbits</a><br>Twitter: <a href="https://twitter.com/LohaniDamodar">https://twitter.com/LohaniDamodar</a><br>Linked In: <a href="https://www.linkedin.com/in/lohanidamodar/">https://www.linkedin.com/in/lohanidamodar/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a386920bdfe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter Recipes 2 — Firebase Firestore Recipes]]></title>
            <link>https://lohanidamodar.medium.com/flutter-recipes-2-firebase-firestore-recipes-2f09e58a7298?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f09e58a7298</guid>
            <category><![CDATA[firestore]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 05:34:31 GMT</pubDate>
            <atom:updated>2020-02-20T05:34:31.191Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flutter Recipes 2 — Firebase Firestore Recipes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQtQBuQ2aB3Ci1-mgNEv7A.jpeg" /></figure><p>I have built quite a few apps with Flutter and Firebase. And, for most of those projects I used Firestore as the database. So, I had to perform all sorts of query, pagination, mapping Firestore returned Maps to data models. So over that period of time, I have created a simplified, generalized helper class with various methods that help me work with Firestore database. That is what I am publishing here. Hope it will be useful for those using Firestore in their database.</p><h3>General Class</h3><p>This class has the most commonly used methods on firestore. It can get list of items from collection, single item, remove item, add item. It provides list and single item both as a future and stream. It also provides methods for easier query and simple paginations. It uses generic type so that, we can use it to convert firestore map to the required data model we want</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/de4d63488c4ef1376b03f4a3ff7f6a62/href">https://medium.com/media/de4d63488c4ef1376b03f4a3ff7f6a62/href</a></iframe><h3>Using it in Action</h3><p>Below I will show how to use this class to get a list of Note items from notes collection.</p><h3>Step 1</h3><p>We create a notes item model for our data</p><pre>class Note{<br>final String title;<br>final String id;<br>final String description;<br>final DateTime createdAt;<br>final String userId;</pre><pre>Note({this.title, this.id, this.description, this.createdAt, this.userId});</pre><pre>Note.fromDS(String id, Map&lt;String,dynamic&gt; data):<br>    id=id,<br>    title=data[&#39;title&#39;],<br>    description=data[&#39;description&#39;],<br>    userId=data[&#39;user_id&#39;],<br>    createdAt=data[&#39;created_at&#39;]?.toDate();</pre><pre>Map&lt;String,dynamic&gt; toMap() =&gt; {<br>    &quot;title&quot;:title,<br>    &quot;description&quot;:description,<br>    &quot;created_at&quot;: createdAt,<br>    &quot;user_id&quot;: userId,<br>};<br>}</pre><h3>Step 2</h3><p>We instantiate the generic class using the Note model as our type. Pass the collection path as notes and provide functions to convert from DocumentSnapshot to note and note to Map</p><pre>DatabaseService&lt;Note&gt; notesDb = DatabaseService&lt;Note&gt;(&quot;notes&quot;,fromDS: (id,data) =&gt;  Note.fromDS(id,data), toMap:(note) =&gt; note.toMap() );</pre><h3>Step 3</h3><p>Finally we can use notesDb instance to work with notes collection in our Firestore. For example to create item</p><pre>Note note = Note(<br>    title: &quot;Hello Note&quot;,<br>    description: &quot;This is notes description&quot;,<br>);<br>notesDb.createItem(note); <em>//this function will add our note item to the firestore database</em></pre><p><strong>You can see this in action in the following repository</strong></p><p><a href="https://github.com/lohanidamodar/flutter_notes_app">lohanidamodar/flutter_notes_app</a></p><p><strong>Want to connect with me</strong><br>Facebook: <a href="https://fb.me/lohanidamodar">https://fb.me/lohanidamodar</a><br>GitHub: <a href="https://github.com/lohanidamodar">https://github.com/lohanidamodar</a><br>YouTube: <a href="https://youtube.com/c/reactbits">https://youtube.com/c/reactbits</a><br>Twitter: <a href="https://twitter.com/LohaniDamodar">https://twitter.com/LohaniDamodar</a><br>Linked In: <a href="https://www.linkedin.com/in/lohanidamodar/">https://www.linkedin.com/in/lohanidamodar/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f09e58a7298" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most common misconception among beginner Mobile App Developers]]></title>
            <link>https://lohanidamodar.medium.com/most-common-misconception-among-beginner-mobile-app-developers-6309b08f36a7?source=rss-21afa4abace7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6309b08f36a7</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Damodar Lohani]]></dc:creator>
            <pubDate>Tue, 18 Feb 2020 11:40:12 GMT</pubDate>
            <atom:updated>2020-02-18T11:40:12.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apdEc2lc5CmYF1Nz8M7Y3w.jpeg" /></figure><p>In this article I would like to clear up the common misconceptions between beginner mobile app developers. In many mobile app groups that I follow I find questions from beginner developers like how do I connect my mobile app to a MySQL server or a SQL database? How do I dynamically load data into my mobile application from my database? This is the same kind of questions that used to pop into my head, back when I was beginning with Android development.</p><p>The very first thing you need to understand is that a mobile app remains in mobile of your users, however your data or your database remains in a server. And that is what makes it accessible to all the instances of your application installed on millions of users mobile phone.</p><p>Next thing you need to understand is, we do not directly connect to the database from our mobile application, at least it is not secure and not the right way to do. So how do we connect our mobile application to our database or load dynamic data from server to our mobile application. This is where the API comes into play.</p><p>API (Application Programming Interface) is a standard that allows interconnection between various different services and that is how we connect our mobile app or front-end to a our back-end service for our database server.</p><p>Now getting into the point. How do we connect our mobile applications developed in flutter or in Android or iOS to our database? To store data on server we use databases like MySQL or SLQ Server or MongoDB or any database and to connect to the database we write a code in languages like Python or PHP or java or any other language that support connecting to database and writing a backend services. Using those services we create a API, most common is the REST API.</p><p>A REST API is just a collection of URLs that we can call from our mobile applications using the libraries and services provided for our application development framework. Let’s say for an example we have a database of users and we want to add a new user from a mobile application to our database when user signs up. How it happens is first we create our in our API we expose a URL suppose, let’s say <a href="http://example.com/add-user">example.com/add-user</a> and we write a code so that whenever someone sends a data in that URL our back-end application will connect to the database and store the data in the users table. And, in our mobile application, let’s say Flutter, we use libraries like http, to call that URL and send the data received from our user to that URL.</p><p>Now let’s say we want to retrieve that users data in our mobile application. For that we create and expose yet another URL in our API, for example let’s say <a href="http://example.com/users">example.com/users</a> and when our application connects to this URL or request data from this URL or back-end application will connect to the database, retrieve the list of users from users table and send it back to this URL. This is in general how our mobile application can connect to the database server.</p><p>So, do we always need to create our own API for our mobile applications? The answer to this question is both yes and no. If you want our own database server and own logic to handle our data then we have to write our own API for our mobile applications. However nowadays there are many services like Firebase, back4app and other headless CMS that provides us API, for our mobile applications for any front end applications. This way we do not have to write own API however our mobile app needs to connect to their API and follow their API standards and structures to write and read data to the database server they provide. Each of these services have their own API and set of standards that we need to follow.</p><p>So to get started with mobile app development where you want to provide dynamic data for your users to manipulate, you either need to create your own database server and write your own API or use one of the managed database services like Firebase, Contentful, Back4App etc.</p><p>For those of you who would like to develop a complete mobile app from scratch using Flutter but don’t want to write your own API, I have created this awesome tutorial, on creating a complete App from scratch using Flutter and Firebase. Do check it out.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLUiueC0kTFqJS4m0Ehg6OVlYyGVXywmyU&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fplaylist%3Flist%3DPLUiueC0kTFqJS4m0Ehg6OVlYyGVXywmyU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-ydsl4_FF6o%2Fhqdefault.jpg%3Fsqp%3D-oaymwEWCKgBEF5IWvKriqkDCQgBFQAAiEIYAQ%3D%3D%26rs%3DAOn4CLBMWuoivii36gQ5uftV1RFuG41ZTA&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="853" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c38cf54342bea901ce2e2fdb04127eb9/href">https://medium.com/media/c38cf54342bea901ce2e2fdb04127eb9/href</a></iframe><p><strong>Want to connect with me</strong><br>Facebook: <a href="https://fb.me/lohanidamodar">https://fb.me/lohanidamodar</a><br>GitHub: <a href="https://github.com/lohanidamodar">https://github.com/lohanidamodar</a><br>YouTube: <a href="https://youtube.com/c/reactbits">https://youtube.com/c/reactbits</a><br>Twitter: <a href="https://twitter.com/LohaniDamodar">https://twitter.com/LohaniDamodar</a><br>Linked In: <a href="https://www.linkedin.com/in/lohanidamodar/">https://www.linkedin.com/in/lohanidamodar/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6309b08f36a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>