<?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 Rohit Rajendran on Medium]]></title>
        <description><![CDATA[Stories by Rohit Rajendran on Medium]]></description>
        <link>https://medium.com/@rohitr?source=rss-6fecf4b4eba8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*k41F_vkVtrOANq6u-JTf4Q.jpeg</url>
            <title>Stories by Rohit Rajendran on Medium</title>
            <link>https://medium.com/@rohitr?source=rss-6fecf4b4eba8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:41:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rohitr/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[We do talk about Bruno: The API Client]]></title>
            <link>https://rohitr.medium.com/we-do-talk-about-bruno-the-api-client-6c5192e7cd98?source=rss-6fecf4b4eba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c5192e7cd98</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Rohit Rajendran]]></dc:creator>
            <pubDate>Mon, 11 Mar 2024 01:46:54 GMT</pubDate>
            <atom:updated>2024-03-11T01:46:54.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yk7ZRKiIXkoxQ-IFSr6JeA.jpeg" /></figure><p>Despite the catchy song from “Encanto” advising us otherwise, today we’re going to talk about Bruno, an API client, which has quickly become my go-to API client.</p><p>Our team, like many others, used Postman as our preferred REST API client. It helped streamline and simplify the process of interacting, debugging, and testing our endpoints and those of 3rd parties that we worked with.</p><p>Unfortunately, when Postman pivoted to a cloud-centric model, it greatly limited what you could do without a cloud account (something that we were not allowed to use because of company restrictions due to security risks).</p><p>This started a search for a new alternative. Little did we know, we’d end up finding something that would end up working out better for our needs and workflow.</p><h3>The Search Criteria</h3><p>Our journey began when Postman’s pivot to a cloud-centric model prompted us to seek an alternative that aligned more closely with our requirements:</p><ol><li><strong>Multiple Collections Support</strong>: Essential for organizing our API requests efficiently.</li><li><strong>Environment Variables:</strong> A must-have feature for seamless switching between development and production environments.</li><li><strong>Scripting Capabilities:</strong> Highly desirable for leveraging responses across endpoints and adding logic to our processes.</li><li><strong>Local Support:</strong> A non-negotiable attribute, ensuring no reliance on cloud storage or external servers.</li><li><strong>Cost-Effective:</strong> Free access was a critical factor, given the logistical challenges of obtaining approval for team-wide purchases.</li><li><strong>Team Synchronization:</strong> Ideally, a solution that facilitates easy sharing and updating of collections among team members. This was a big nice to have. We were using the free tier of Postman so we had been passing around exported files to share collections between teammates. This led to out-of-sync collections and was a big hassle to maintain. This wasn’t the only team I had encountered this with, so I really wanted a solution to make this easier going forward.</li></ol><h3>The Contenders</h3><p>Our evaluation included several promising tools, each with its unique strengths and limitations:</p><ul><li><strong>Insomnia:</strong> A strong Postman competitor that used to be my preference, but after an update, it also required a cloud account access similar to Postman and severly limited local only use of the application. (I haven’t gone back to try it out since, but it looks like they reversed this <a href="https://github.com/Kong/insomnia/discussions/6626">decision</a>.)</li><li><strong>Thunder Client:</strong> Being built into VS Code, meant that you don’t have to leave your IDE, but it only supported VS Code which not everyone in our team uses. The free tier only allows for 50 requests per collection which would also have meant that we would need to break down our collections.</li></ul><h4>Why Bruno Stood Out</h4><p>Bruno emerged as the clear winner in our search. Here’s why:</p><ul><li><strong>Comprehensive Feature Set</strong>: Bruno offers an array of functionalities, from multiple collections and environment variables to scripting capabilities, without compromising on user experience.</li><li><strong>Multi-Platform Support: </strong>There are multiple ways to use Bruno including a desktop app, CLI, and VS Code extension; making everyone on our team happy regardless of their preferences.</li><li><strong>Versatile Import Support: </strong>We could easily import our Postman collections and enviornments into Bruno. It also supports importing Insomnia collections and OpenAPI v3 specs.</li></ul><p>But the things that really stood out were:</p><ul><li><strong>Team Collaboration</strong>: Unlike our previous approach with Postman, Bruno’s git-friendly nature streamlines collection sharing and updates, fostering better team collaboration. No paid tier needed and no more passing export files back and forth!</li><li><strong>Local, Open Source, and Free</strong>: Bruno’s commitment to local support and open source aligns perfectly with our team’s principles and logistical constraints.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wsyprX6KXiHWI_yxaiOdWw.png" /><figcaption>What collections and API requests look like within Bruno.</figcaption></figure><h3>Questions about Bruno</h3><h4>How does Bruno manage the collections?</h4><p>After you point Bruno to a folder, Bruno automatically organizes your collections as subfolders within it and your API requests as plain text files. You can set this folder up as a Git repository so that you and your team can manage this with version control. Anyone else on your team that wants to use your collection, can just clone the repository and open the collection in Bruno.</p><p>You can check out Bruno’s <a href="https://github.com/usebruno/github-rest-api-collection/tree/main">sample repository</a> as an example.</p><h4>If it’s getting managed in Git, how do you prevent secrets from getting committed?</h4><p>When using environment variables in Bruno, you may encounter sensitive data, like secrets, that shouldn’t be exposed in your repository. To protect these, ensure you mark them as “Secret” within Bruno. This action signals Bruno to handle these secrets discreetly, ensuring they are not recorded in the text files, thus maintaining the security of your sensitive information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXZ9lf2UPkwlWhxzhm0Ykg.png" /><figcaption>Make sure to check the “Secret” box for any environment variables that should not get committed.</figcaption></figure><h3>Conclusion</h3><p>Bruno stands out as an API client that offers a good blend of functionality, collaboration, and user-friendliness. For any team looking to enhance their API development and testing processes, Bruno is a compelling choice that is worth considering.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c5192e7cd98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get Started with Firebase Realtime Database and watchOS]]></title>
            <link>https://medium.com/firebase-developers/get-started-with-firebase-realtime-db-and-watchos-84f3b70d36e?source=rss-6fecf4b4eba8------2</link>
            <guid isPermaLink="false">https://medium.com/p/84f3b70d36e</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[watchos]]></category>
            <dc:creator><![CDATA[Rohit Rajendran]]></dc:creator>
            <pubDate>Wed, 28 Apr 2021 04:24:40 GMT</pubDate>
            <atom:updated>2023-12-08T13:21:06.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcPyO8hC-9QYNhsv7fsBfA.png" /></figure><p>Firebase Realtime Database is a NoSQL database that lets you store and sync data between your users in realtime. I loved how easy and simple it made it to integrate to my apps and websites without the need of APIs or servers but was disappointed when I was trying to build out a watchOS app and realized it wasn’t supported.</p><p>But there’s good news! As of version 7.9.0 of the Firebase iOS SDK, watchOS is now supported for Realtime Database. It’s been working great for me and it’s been amazing to have the realtime sync capabilities easily enabled in my Apple Watch app. In this guide, I’ll go through an example of getting your Firebase Realtime Database connection started with your Watch app. If you already have an Xcode and Firebase project to try this out with, you can skip straight to the good stuff at the “Working with Firebase” section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODhVhKx1MaLdNUzDxBDcEQ.png" /></figure><h3>Create a watchOS Project</h3><p>Let’s start off by creating a new watchOS project that we will get talking to the Firebase Realtime Database.</p><ol><li>Open up Xcode and create a new project. For this example, we’ll use the <em>Watch App</em> template with a <em>Swift UI</em> interface and <em>Swift UI App</em> lifecycle. We’ll also uncheck <em>Include Notification Scene</em> and <em>Include Tests</em> to keep things simple.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugfvtUgbEpgARIWk4jwvVw.png" /><figcaption>Select “Watch App” as the template.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dfb4w0X6sNSe3Hq2oV32Dw.png" /><figcaption>Enter an organization identifier and set the following set: Interface as “SwiftUI”, Life Cycle as “SwiftUI App”, Language as “Swift”, Uncheck “Include Notification Scene”, Uncheck “Include Tests.”</figcaption></figure><p>2. Navigate to the Project File &gt; WatchKit App Target &gt; Signing and Capabilities. Note the bundle identifier for the Watchkit app, you’re going to need this in the next step where you’re setting up the Firebase Project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cDAnNwcmEU7I1660TVa3Bg.png" /></figure><h3>Setup Firebase Project</h3><p>Now that we have a watchOS app and a bundle identifier, let’s head over to Firebase and add the app to our Firebase project. If you don’t already have a Firebase project, you can just visit <a href="https://firebase.google.com/">https://firebase.google.com/</a>, log in and follow the steps to create a project.</p><ol><li>Navigate to the <em>Realtime Database</em> section and create a database. For this exercise, we’ll start it in <em>test mode</em> to make things easier.</li><li>Next, from your project dashboard, click on the button to add an iOS app to your project. In the first step, you’ll want to enter the bundle identifier you used when you created the watchOS project. You can enter an app nickname if you’d like. We don’t have an App Store ID yet so we’ll leave that blank. Click on <em>Register App</em> when you’re done.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TpFjD5yDF4Uw986Tcz_5Cg.png" /></figure><p>2. Just like Firebase helpfully explains, we’ll want to download the GoogleService-Info.plist, move it to the root of the Xcode project, and add it to all targets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzcp_5ZZe9NttIQMqFSVhA.png" /></figure><h3>Working with Firebase</h3><h4>Initializing Firebase</h4><p>1. Next, we’re going to add the Firebase SDK. Now there’s a couple ways you can do this: CocoaPods, Swift Package Manager, Install from Github, and Carthage. You can choose whichever you would prefer. There are instruction details for each of these methods in the <a href="https://github.com/firebase/firebase-ios-sdk#installation">Firebase iOS SDK repo</a>. Make sure you include the Firebase/Database package. I’ve been using the Swift Package Manager so I’ll walk through the steps with that as part of this guide.</p><p>2. To add Firebase as a Swift Package, navigate to <em>File &gt; Swift Packages &gt; Add Package Dependency</em>. Paste the URL of the Firebase Github (<a href="https://github.com/firebase/firebase-ios-sdk.git">https://github.com/firebase/firebase-ios-sdk.git</a>) and select U<em>p to Next Major </em>version. WatchOS support for Firebase Realtime Database was only added as of Version 7.9.0 so make sure you’re using a version higher than that. You’ll then want to choose the Firebase products that you want installed. For this example, we’ll want to check <em>FirebaseDatabase </em>and add it to the <em>WatchKit</em> Extension target.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPPG7g6SovMKH1yxL_ecZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSlb4hrh2yHD9Z4eKceD0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WB3ZbAnt-a0Wr9I_V8mR7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KALSv6o4IR_EWPtC3f_HLA.png" /></figure><p>3. In the WatchKit Extension folder of your project, you’ll want to open up the [APP_NAME].swift file. This is where you’re going to initialize Firebase. In this file, we’re going to import Firebase and add call FirebaseApp.configure() in the initializer of the struct. When you call Firebase.configure(), it’ll automatically pull the credentials from the GoogleService-info.plist file you added and get everything set up. You’re now ready to start talking to Firebase Realtime Database (or any other Firebase product)!</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3231c3b60bd9aea4825d5a95987d345/href">https://medium.com/media/e3231c3b60bd9aea4825d5a95987d345/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z8OdsimzT_8lfpfvaOhiDQ.png" /></figure><h4>Working with Firebase Realtime Database</h4><p>You’re now ready to start cooking with fire(base). Sorry I had to 🥸. Working with Firebase Realtime Database in a watchOS app is exactly like working with it in iOS app. Let’s take a look by updating a screen to show a message live from the the database.</p><ol><li>We’ll start with creating a new Swift file in the WatchKit Extension called MessageManager that will consist of a class that will get our message from Firebase Realtime Database.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/21d83e620115310815b524b19e3e7b9f/href">https://medium.com/media/21d83e620115310815b524b19e3e7b9f/href</a></iframe><p>Let’s break down what’s happening here. We published the message var so that changes to that variable can be watched. messageRef stores a reference to where our message is located in the database. messageHandle is used to store the handle of the observer we’re creating on the reference so that it can be removed later.</p><p>We’ve also created a start and stop <em>message listener</em> since we’ll want to make sure we appropriately start and stop watching the reference when we enter and leave the view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rR9AwbVwBSkK0DKFTQZyfw.png" /></figure><p>2. In ContentView.swift, initialize the message manager and display that message variable instead. We’ll also hook up to the onAppear and onDisappear methods to make sure we’re appropriately starting and disposing of the watcher.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7013fac9a1c1537b85ae36d1112696f9/href">https://medium.com/media/7013fac9a1c1537b85ae36d1112696f9/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*agJsikuiKkCYyUdY4PLyNA.png" /></figure><p>3. Now let’s run this in the simulator and test this out by editing the Realtime Database in the console. Navigate to the Firebase console for the Realtime Database and add a key value pair of message and OMG, IT WORKS. You should instantly see changes getting reflected in your Watch app!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODhVhKx1MaLdNUzDxBDcEQ.png" /></figure><p>There you have it! A watchOS app working seamlessly with Firebase Realtime Database.</p><p>Have something you want me to dive into more detail into? Run into any problems getting it set up? Just post a comment and I would be happy to help out!</p><h3>Resources</h3><ul><li><a href="https://firebase.google.com/docs/database/ios/start">Installation &amp; Setup on Apple platforms | Firebase Realtime Database</a></li><li><a href="https://github.com/firebase/firebase-ios-sdk">GitHub - firebase/firebase-ios-sdk: Firebase SDK for Apple App Development</a></li><li><a href="https://github.com/firebase/firebase-ios-sdk/issues/4556">FR: RealtimeDatabase support for WatchOS · Issue #4556 · firebase/firebase-ios-sdk</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84f3b70d36e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/firebase-developers/get-started-with-firebase-realtime-db-and-watchos-84f3b70d36e">Get Started with Firebase Realtime Database and watchOS</a> was originally published in <a href="https://medium.com/firebase-developers">Firebase Developers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>