<?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 Sneha Kumari on Medium]]></title>
        <description><![CDATA[Stories by Sneha Kumari on Medium]]></description>
        <link>https://medium.com/@sneha14kumari?source=rss-28828be62868------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*i9YgQ2Shuqu8gOnfPp4Xbg.jpeg</url>
            <title>Stories by Sneha Kumari on Medium</title>
            <link>https://medium.com/@sneha14kumari?source=rss-28828be62868------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:46:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sneha14kumari/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[Bridging the Gap: A Developer’s Journey with BrowserStack]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@sneha14kumari/bridging-the-gap-a-developers-journey-with-browserstack-f8520156d6cb?source=rss-28828be62868------2"><img src="https://cdn-images-1.medium.com/max/1200/1*w4gczSP7-tOZ0nUDjrl9Vg.jpeg" width="1200"></a></p><p class="medium-feed-snippet">In today&#x2019;s development landscape, providing a seamless platform for testing web and mobile applications across various browsers and&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@sneha14kumari/bridging-the-gap-a-developers-journey-with-browserstack-f8520156d6cb?source=rss-28828be62868------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@sneha14kumari/bridging-the-gap-a-developers-journey-with-browserstack-f8520156d6cb?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8520156d6cb</guid>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Fri, 12 Dec 2025 08:22:24 GMT</pubDate>
            <atom:updated>2025-12-12T08:22:24.196Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Firebase Analytics — A Step-by-Step Guide to Firebase Implementation]]></title>
            <link>https://medium.com/@sneha14kumari/firebase-analytics-a-step-by-step-guide-to-firebase-implementation-aa3e1edc5f24?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa3e1edc5f24</guid>
            <category><![CDATA[report]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[firebaseanalytics]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 11:19:34 GMT</pubDate>
            <atom:updated>2024-01-29T11:19:34.383Z</atom:updated>
            <content:encoded><![CDATA[<h3>Firebase Analytics — A Step-by-Step Guide to Firebase Implementation</h3><p>To implement Firebase Analytics in your project involves below steps:</p><p><strong>Create a Firebase Project:</strong> Go to the <a href="https://console.firebase.google.com/">Firebase Console</a> and click on “Add project” to create the project after following the prompts to set up different information about project like Project Name, Project ID etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*7AiEeS_A-bzLLZEkzgQ4_w.png" /></figure><p><strong>Add Firebase to the App:</strong> Next add Firebase to your app by selecting the platform (Android, iOS, Web). This typically involves adding a configuration file to your project and some initialization code.</p><p><strong>Add Firebase SDK:</strong> Install the Firebase SDK for your platform using the appropriate dependency management system (e.g., CocoaPods for iOS, Gradle for Android, npm for web).</p><p><strong>Initialize Firebase:</strong> This needs to be done in code AppDelegate (for iOS) or MainActivity (for Android) file.</p><pre>// For Android<br>import com.google.firebase.FirebaseApp;<br><br>public class MainActivity extends AppCompatActivity {<br>    @Override<br>    protected void onCreate(Bundle savedInstanceState) {<br>        super.onCreate(savedInstanceState);<br>        setContentView(R.layout.activity_main);<br><br>        // Initialize Firebase<br>        FirebaseApp.initializeApp(this);<br>    }<br>}</pre><pre>// For iOS<br>import Firebase<br><br>func application(_ application: UIApplication, didFinishLaunchingWithOptions <br>launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {<br>    FirebaseApp.configure()<br>    return true<br>}</pre><p><strong>Log Events:</strong> By using Firebase Analytics SDK we can log both predefined and custom events. Predefined events are like app launches, in-app purchases, screen views etc. Custom events can be logged like below code:</p><pre>// For Android<br>Bundle params = new Bundle();<br>params.putString(&quot;parameter_name&quot;, &quot;parameter_value&quot;);<br>FirebaseAnalytics.getInstance(context).logEvent(&quot;custom_event&quot;, params);</pre><pre>// For iOS<br>Analytics.logEvent(&quot;custom_event&quot;, parameters: [<br>    &quot;parameter_name&quot;: &quot;parameter_value&quot;<br>])</pre><p><strong>Analytics Data on Firebase:</strong> Once the Firebase Analytics integrated in your app and users starts using it you can view the analytics data in Firebase Console. Go to the Firebase Console -&gt; Login -&gt; Select your Project -&gt; navigate to the “Analytics” section to see the reports and insights about the user activities.</p><p>Firebase Analytics is just not a tool, it is a spice rack which helps you in understanding your users desires which is a secret ingredient to success. I hope this helps you to experience Firebase Analytics with your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa3e1edc5f24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the secrets of Firebase Analytics: A beginner’s guide to tracking app usage and user…]]></title>
            <link>https://medium.com/@sneha14kumari/unlocking-the-secrets-of-firebase-analytics-a-beginners-guide-to-tracking-app-usage-and-user-52567ad0d313?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/52567ad0d313</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[firebaseanalytics]]></category>
            <category><![CDATA[appusage]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[real-time-analytics]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Tue, 23 Jan 2024 08:25:02 GMT</pubDate>
            <atom:updated>2024-01-23T08:25:02.640Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unlocking the secrets of Firebase Analytics: A beginner’s guide to tracking app usage and user behavior</h3><p>We launched a mobile app offering practice skill tests for UK licensing, with humble dreams. We knew the market needed it, but monetization? We blinked, our tired brains struggling to parse the information. Paying users? Intrigued, we dove into the analytics. Turns out, a niche within the niche had emerged. Professionals desperate to secure specific licenses, from hairdressers to electricians, were willing to pay for premium features: personalized study plans, advanced mock exams, expert video tutorials. They craved an edge, a guarantee, a golden ticket to their dream career. Our app transformed. Downloads soared, engagement skyrocketed. Our community buzzed with discussions, tips, and triumphant exam-passing stories. We weren’t just an app anymore; we were a lifeline, a beacon of hope in the licensing storm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lQfIVCxs8H19x7Hr_PM5Tg.jpeg" /></figure><p>Firebase Analytics is a part of the Firebase platform, which is a mobile and web application development platform developed by Firebase, a subsidiary of Google. Firebase Analytics allows developers to track and analyze user behavior in their applications.</p><p><strong>Features of Firebase Analytics:</strong></p><p><strong>Attribution:</strong> We can track the source of our app installs to understand the effectiveness of the marketing efforts.</p><p><strong>Event Tracking: </strong>Developers can log events in their app to track user interactions, such as button clicks, purchases, or custom events. This helps in understanding how users engage with the app.</p><p><strong>User Engagement: </strong>Firebase Analytics provides insights into user engagement metrics, including daily and monthly active users, user retention, and user engagement with specific app features.</p><p><strong>Audiences:</strong> We can define user properties to segment our user base. This can be useful to create audiences based on user characteristics or behavior. Audiences or specific groups of users can be targeted with notifications or other personalized content.</p><p><strong>Reporting:</strong> Firebase Analytics provides both real-time reporting and custom reports and dashboards to monitor user behavior as it happens and specific metrics that are relevant to the app’s goals.</p><p>So, to any developer staring at a stagnant download bar, I say this: open your eyes, embrace analytics, and let your app truly take flight. It’s a journey filled with data-driven insights, unexpected discoveries, and the ultimate reward: making your users smile 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52567ad0d313" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering SonarCloud Rules: A Developer’s Handbook]]></title>
            <link>https://medium.com/@sneha14kumari/mastering-sonarcloud-rules-a-developers-handbook-bcad7359c459?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcad7359c459</guid>
            <category><![CDATA[code-smells]]></category>
            <category><![CDATA[sonarcloud]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[sonar]]></category>
            <category><![CDATA[security-vulnerabilities]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Fri, 29 Dec 2023 00:14:22 GMT</pubDate>
            <atom:updated>2023-12-29T00:14:22.882Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ll learn how to implement SonarCloud into your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CoYeGmIdTxWKNcjOVovRmg.png" /></figure><p>Here’s a general guide to help you set up SonarCloud for your project:</p><h4>Create a SonarCloud Account:</h4><ul><li>Go to the <a href="https://sonarcloud.io/">SonarCloud website</a> and sign up for an account.</li><li>Follow the registration process to create a new organization and project.</li></ul><h4>Configure the Project:</h4><p>After creating account and project, configure the relevant settings such as project key, name and version.</p><h4>Generate a Project Token:</h4><p>Generate an authentication token for your project. This token is used to authenticate your CI/CD system with SonarCloud.</p><h4>Integrate with the Build System:</h4><p>Integrate the SonarCloud with the build system such as Maven, Gradle, MSBuild etc. To do this we need to update the build configuration files of our project with the SonarCloud plugin and provide the necessary configuration like project key and authentication token.</p><pre>sonar {<br>            description = &quot;Sonar properties task&quot;<br><br>            properties {<br>                property &quot;sonar.projectName&quot;, &quot;ProjectName&quot;<br>                property &quot;sonar.projectKey&quot;, &quot;ProjectKey&quot;<br>                property &quot;sonar.host.url&quot;, &quot;https://sonarcloud.io&quot;<br>                property &quot;sonar.organization&quot;, &quot;OrganizationKey&quot;<br>                // property &quot;sonar.token&quot;, &quot;$sonarToken&quot; // provided as ./gradlew sonar -Dsonar.token=$SONAR_TOKEN<br>                property &quot;sonar.test.inclusions&quot;, &quot;**/*Test*/**&quot;<br>                property &quot;sonar.sourceEncoding&quot;, &quot;UTF-8&quot;<br>                property &quot;sonar.java.coveragePlugin&quot;, &quot;jacoco&quot;<br>                property &quot;sonar.coverage.jacoco.xmlReportPaths&quot;, &quot;${project.buildDir}/reports/jacoco/jacoco.xml&quot;<br>                property &quot;sonar.coverage.exclusions&quot;, fileFilter.join(&#39;,&#39;)<br>                property &quot;sonar.kotlin.detekt.reportPaths&quot;, &quot;${project.buildDir}/reports/detekt/detekt.xml&quot;<br>                property &quot;sonar.androidLint.reportPaths&quot;, &quot;${project.buildDir}/reports/lint-results-${variantName}.xml&quot;<br>                property &quot;sonar.exclusions&quot;, &#39;**/*Test*/**,&#39; +<br>                        &#39;*.json,&#39; +<br>                        &#39;**/*test*/**,&#39; +<br>                        &#39;**/.gradle/**,&#39; +<br>                        &#39;**/R.class,&#39; +<br>                        &#39;build/**,&#39; +<br>                        &#39;**/gradlew,&#39; +<br>                        &#39;**/gradlew.bat,&#39; +<br>                        &#39;**/build.gradle.kts,&#39; +<br>                        &#39;**/bin/**,&#39;<br>            }<br>        }</pre><h4>Configure CI/CD Pipeline:</h4><p>In the workflow of project’s CI/CD pipeline we need to update the configuration to trigger SonarCloud analysis after each build. Include the necessary tasks or commands to run the SonarCloud analysis.</p><pre>name: SonarScanner Build<br><br>on:<br>  pull_request:<br><br>jobs:<br>  build:<br><br>    name: SonarScanner Coverage Report<br>    runs-on: ubuntu-latest<br><br>    steps:<br>      - uses: actions/checkout@v4<br>        with:<br>          fetch-depth: 0<br><br>      - name: Set up JDK 17<br>        uses: actions/setup-java@v1<br>        with:<br>          java-version: 17<br><br>      - name: Sonar Scanner Run<br>        env:<br>          SONAR_TOKEN: ${{secrets.SONAR_TOKEN}}<br>        run: ./gradlew sonar -Dsonar.token=$SONAR_TOKEN</pre><h4>Run SonarCloud Analysis:</h4><p>Trigger a build in CI/CD pipeline to run the SonarCloud analysis. SonarCloud will analyze the code and report the issues and metrics bases on the QualityGate rules.</p><p>I hope this gives you a good overview of SonarCloud. If you have any other questions, please let me know 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcad7359c459" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of Code Quality: How SonarCloud is Leading the Way]]></title>
            <link>https://medium.com/@sneha14kumari/the-future-of-code-quality-how-sonarcloud-is-leading-the-way-04dfd81ed3a2?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/04dfd81ed3a2</guid>
            <category><![CDATA[code-quality-tools]]></category>
            <category><![CDATA[sonarcloud]]></category>
            <category><![CDATA[security-vulnerabilities]]></category>
            <category><![CDATA[sonarqube]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Thu, 28 Dec 2023 05:49:12 GMT</pubDate>
            <atom:updated>2023-12-28T05:49:12.724Z</atom:updated>
            <content:encoded><![CDATA[<p>SonarCloud is a cloud-based code quality and security analysis service provided by SonarSource.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrJBogIrmDBNdfONspY8sA.png" /></figure><p>This would be a detailed breakdown of SonarCloud’s features and functionalities, ideal for developers new to the platform. Explain code analysis, issue detection, remediation suggestions, and integrations with popular CI/CD pipelines.</p><p><strong>Features of SonarCloud</strong></p><p><strong>Code Quality Analysis:</strong> SonarCloud performs static code analysis to identify code smells, bugs, and security vulnerabilities.</p><p><strong>Seamless Integration with Development Workflow:</strong> It can be integrated with popular CI/CD tools such as Jenkins, Bitrise, GitHub Actions, Azure DevOps etc. This automatically analyzes code on every build to ensure that issues are identified early in development process.</p><p><strong>Security Vulnerability Detection:</strong> SonarCloud helps to address potential threats before deployment by identifying Security Vulnerabilities in the code.</p><p><strong>Project Dashboards and Reports: </strong>SonarCloud offers dashboards and reports that provide an overview of code quality metrics, trends, and improvements over time.</p><p><strong>Benefits of using SonarCloud</strong></p><p><strong>Early Issue Detection: </strong>SonarCloud identifies issues such as bugs, code smells and security vulnerabilities early by performing static code analysis on every build. This allows to address issues before getting escalated and challenging to fix.</p><p><strong>Code Quality Metrics:</strong> Provides comprehensive code quality metrics, including code complexity, duplications, and maintainability. Developers gain insights into the overall health of their codebase and can make informed decisions to enhance code quality.</p><p><strong>Technical Debt Management:</strong> SonarCloud helps teams to prioritize and address critical issues as it calculates and presents technical debt based on issues.</p><p><strong>Custom Coding Rules and Policies:</strong> SonarCloud provides option to define custom coding rules and quality gates to ensure specific coding standards and policies, cultivate consistency across the team.</p><p>Overall, SonarCloud is a powerful tool that can help developers improve the quality and security of their code. If you’re looking for a way to take your code to the next level, SonarCloud is definitely worth checking out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04dfd81ed3a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bitrise — Workflow Editor]]></title>
            <link>https://medium.com/@sneha14kumari/bitrise-workflow-editor-8651802341b0?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/8651802341b0</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[bitrise]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[android-cicd]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 15:53:01 GMT</pubDate>
            <atom:updated>2023-12-18T15:53:01.987Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bitrise — Workflow Editor</h3><p>In my previous story, we have learnt about Bitrise DevOps Tools setup and configuration. Today I am going to elaborate about Workflow Editor in Bitrise.</p><p><strong>Workflow Editor</strong></p><p>Workflow Editor is the most important part of Bitrise as through this we can create the workflow which we want to run during build.</p><p>In this we need to add different steps to create the build (apk or ipa files), publish the builds on different platforms like TestFlight, Google Play Store, Appcenter, Bitrise Center, App Store etc.</p><p>Let’s see few important steps for Build:</p><p><strong>Android</strong></p><p><strong>Create a Bitrise Workflow:</strong></p><ul><li>Log in to your Bitrise account.</li><li>Open the project for your Android app.</li><li>Click on the “Workflow” tab.</li><li>Create a new workflow (e.g. “AppcenterRelease”).</li></ul><p><strong>Workflow Steps:</strong></p><p>Configure the workflow steps based on your requirements. Below is a basic example:</p><pre>format_version: &#39;7&#39;<br>default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git<br><br>workflows:<br>  version: 2<br>  android-build:<br>    steps:<br>    - activate-ssh-key:<br>        run_if: &#39;{{getenv &quot;SSH_RSA_PRIVATE_KEY&quot; | ne &quot;&quot;}}&#39;<br>    - git-clone: {}<br>    - script:<br>        title: &#39;Gradle Build&#39;<br>        inputs:<br>        - content: |<br>            #!/bin/bash<br>            set -ex<br>            ./gradlew assembleDebug<br>    - deploy-to-bitrise-io:<br>        inputs:<br>        - notify_user_groups: &#39;all&#39;</pre><p>This example workflow:</p><ul><li>Clones the Git repository.</li><li>Runs the Gradle build to assemble the debug APK.</li><li>Deploys the artifacts to Bitrise.</li></ul><p><strong>Customize Gradle Build:</strong></p><p>DevOps engineer can adjust the Gradle build script according to project requirements. This can contain tasks for linting, signing APK or running test cases.</p><p><strong>Test and Validate:</strong></p><ul><li>Save the workflow and run a build to validate that it works as expected.</li><li>Check the build logs for any errors or warnings.</li></ul><p><strong>Environment Variables:</strong></p><p>Set up any necessary environment variables in the Bitrise project settings. Common variables include API keys, passwords, and signing configurations.</p><p><strong>Notifications:</strong></p><p>Configure notifications to inform the team about the build status. Bitrise supports various notification channels, such as Slack, email, and others.</p><p><strong>iOS</strong></p><p><strong>Git Clone Repository:</strong></p><p>Clone the Git repository where your iOS project is hosted.</p><pre>- git-clone@4:<br>    inputs:<br>      - repository_url: $GIT_REPOSITORY_URL<br>      - commit: $BITRISE_COMMIT</pre><p><strong>Certificate and Profile Installer:</strong></p><p>Install the necessary code signing certificates and provisioning profiles for your iOS project.</p><pre>- certificate-and-profile-installer@1:<br>    inputs:<br>      - certificate_path: &quot;$BITRISE_CERTIFICATE_URL&quot;<br>      - profile_path: &quot;$BITRISE_PROFILE_URL&quot;</pre><p><strong>Xcode Archive:</strong></p><p>Build and archive the Xcode project.</p><pre>- xcode-archive@2:<br>    inputs:<br>      - project_path: &quot;$BITRISE_PROJECT_PATH&quot;<br>      - scheme: &quot;$BITRISE_SCHEME&quot;<br>      - configuration: &quot;$BITRISE_CONFIGURATION&quot;</pre><p><strong>Xcode Export:</strong></p><p>Export the Xcode archive to an IPA file.</p><pre>- xcode-ipa@4:<br>    inputs:<br>      - archive_path: &quot;$BITRISE_XCARCHIVE_PATH&quot;<br>      - export_method: &quot;$BITRISE_EXPORT_METHOD&quot;</pre><p><strong>Deploy to Bitrise.io:</strong></p><p>Deploy the artifacts (e.g., IPA file) to Bitrise for further distribution or testing.</p><pre>- deploy-to-bitrise-io@1:<br>    inputs:<br>      - is_enable_public_page: &quot;true&quot;</pre><p><em>“In conclusion, the Bitrise Workflow Editor stands as a testament to the power of simplicity and efficiency in the realm of continuous integration and delivery. With its intuitive visual interface, seamless integration with version control systems, and the ability to orchestrate complex workflows effortlessly, developers can navigate the intricacies of their Android or iOS projects with confidence. As the Bitrise Workflow Editor continues to evolve, it empowers teams to streamline their development pipelines, accelerate time-to-market, and embrace a future where building and deploying Android or iOS applications are not just tasks but opportunities for innovation. With Bitrise, the story of crafting robust, automated workflows for Android or iOS development unfolds with each line of code, promising a journey marked by efficiency, collaboration, and success.”</em></p><p>Let’s enjoy learning 😊…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8651802341b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile DevOps Tool — Bitrise]]></title>
            <link>https://medium.com/@sneha14kumari/mobile-devops-tool-bitrise-8b7a19048535?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b7a19048535</guid>
            <category><![CDATA[bitrise]]></category>
            <category><![CDATA[cicd-pipeline]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[mobile-devops]]></category>
            <category><![CDATA[devops-tool]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 01:12:27 GMT</pubDate>
            <atom:updated>2023-12-18T15:50:37.380Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mobile DevOps Tool — Bitrise</h3><p>In our previous story we have been through the different tools for Mobile DevOps, in this story I will tell you about Bitrise.</p><p>I am not sure how many of us are known to this tool, because I learnt it very late in my career. So, let’s start with the introduction to the Bitrise.</p><p><strong>Bitrise</strong> is a <strong>Continuous Integration</strong> and <strong>Continuous Deployment</strong> for <strong>mobile apps</strong>. It provides many features and tools for development and delivery process of Android and iOS applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*AzGFjtYTjGtZk3VyzN1aDg.png" /></figure><p>Let’s read about configuration of Bitrise for your Mobile DevOps:</p><p><strong>Bitrise Setup and Configuration</strong></p><ol><li>Sign up for a Bitrise account on <a href="https://bitrise.io/">https://bitrise.io/</a></li><li>Create a new project.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1DmlmgAcVSIKYZRthT_N6A.png" /></figure><p>3. Connect your code repository (Git, GitHub, Bitbucket) to your Bitrise. account, so that it will trigger the automatic build on pushing the new code changes or merging PR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*uzCX5BsMMJ4OTHm46RcNNA.png" /></figure><p>4. Now configure your build settings in Bitrise like Build Number, Build Variant, Build Tools Version and other dependencies.</p><p><strong>Workflow Editor</strong></p><ol><li>As a second important step we have to create the Workflow in Bitrise Workflow Editor to specify the steps required to build and test the app.</li><li>We can customize the steps as per our requirements like code lint check, unit test, code coverage analysis etc.</li></ol><p><strong>Code Signing and Files</strong></p><p>Under this step, we need to add all the required keys and certificates which is necessary to build or publish the builds on Play Store or App Store for public or internal testers.</p><p>The data inside this tab can be hidden by selecting hide button.</p><p><strong>Secrets</strong></p><p>The values under this tab are secret values which we don’t want to show to anyone like Access Key, Cloud Id, Tokens etc.</p><p>Following are the key features of this section in Bitrise:</p><ul><li>Your secrets are not shown in the bitrise.yml</li><li>Your secrets are stored encrypted</li><li>You can prevent exposing secrets on the UI by making them protected</li><li>Note that anyone might be able to do a workaround and log the value of secrets with a pull request, thus we advise <strong>not to expose secrets in PRs</strong></li></ul><p><strong>Env Vars</strong></p><p>Env Vars are Environmental Variables, which we can use either at App level or Workflow level. Under this section, we have two sections one is App Variables and another is Workflow Variables. If we will add variables Key-Value pair under app level, then we can use them anywhere in the app means in any workflow but if we will add the variables Key-Value pair under specific Workflow Variables means workflow level then we can use it only in that particular workflow.</p><p><em>Note: Workflow can be multiple as per your use.</em></p><p>In this section, we usually add our Project name, github path, project directory, package type, package name, build type and other important values but which we can show to other people. These are not secret.</p><p><strong>Triggers</strong></p><p>Triggers are required in order to run builds automatically. To set one up, you need to specify:</p><ul><li>the <strong>event</strong>: for example, code push or pull request.</li><li>the <strong>branch</strong> of your repository: for example, master or dev.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KPkmk4qv9oF-jfpo9N11Q.png" /></figure><p>To enable this trigger, we need to add Webhook in our Version Control System (git, github, bitbucket).</p><p><strong>Stacks &amp; Machines</strong></p><p>In this section, we select the Stack like Android or iOS and Machine Type like Ubuntu, Mac etc. and machine configuration like RAM, intel chip.</p><p>This is important to run the workflow.</p><p><strong>bitrise.yml</strong></p><p>This is the last tab of Workflow. This tab will let you know how your workflow will look like in a yml file. You can use this yml file to add in your code and then it will be easy to run the workflow every time you push, create PR or merge your code by default.</p><p>This is all about the configuration and workflow about Bitrise with mobile applications. We will learn more about the adding Webhook and creating Workflow and bitrise.yml file in next story.</p><p>Thank you for reading and keep reading….keep learning 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b7a19048535" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Streamlining Mobile DevOps Tools]]></title>
            <link>https://medium.com/@sneha14kumari/streamlining-mobile-devops-tools-d64331c2db57?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/d64331c2db57</guid>
            <category><![CDATA[bitrise]]></category>
            <category><![CDATA[devops-tool]]></category>
            <category><![CDATA[cicd-tools]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[mobile-devops]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Sat, 15 Jul 2023 23:07:09 GMT</pubDate>
            <atom:updated>2023-07-15T23:07:09.912Z</atom:updated>
            <content:encoded><![CDATA[<p>In the previous story we have read about the Mobile DevOps, now we are going to gain knowledge about few Mobile DevOps Tools.</p><p>Mobile DevOps tools facilitate the development, testing, deployment, and monitoring of mobile applications.</p><p>Let’s see few Mobile DevOps Tools:</p><ol><li><strong>Bitrise</strong>: Bitrise is a mobile CI/CD platform specifically designed for mobile app development. It offers a range of features like build automation, code signing, app testing, and deployment to app stores.</li><li><strong>Jenkins</strong>: Jenkins is a widely used open-source automation server that supports continuous integration and continuous delivery (CI/CD) pipelines. It can be extended with numerous plugins and integrations to support mobile app builds, testing, and deployment.</li><li><strong>Fastlane</strong>: Fastlane is an open-source toolset for automating the building, testing, and deployment of iOS and Android apps. It integrates with popular CI/CD platforms and provides a variety of useful features like automated screenshots, code signing, and beta distribution.</li><li><strong>CircleCI</strong>: CircleCI is a cloud-based CI/CD platform that supports mobile app development. It provides features like code compilation, automated testing, and deployment to multiple mobile platforms.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*iyuBVjsUg9bn4z6ikc6fWQ.png" /><figcaption>CI/CD Tools</figcaption></figure><p>These are just some examples of Mobile DevOps tools. The choice of tools may vary depending on the development team’s specific requirements and preferences.</p><p><em>That’s all for Mobile DevOps Tools, I will be back with more knowledge about these tools. Thank you for reading!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d64331c2db57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile DevOps]]></title>
            <link>https://medium.com/@sneha14kumari/mobile-devops-fd7f66e860af?source=rss-28828be62868------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd7f66e860af</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[mobile-devops]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Sat, 15 Jul 2023 21:05:32 GMT</pubDate>
            <atom:updated>2023-07-15T21:05:32.392Z</atom:updated>
            <content:encoded><![CDATA[<p>Mobile DevOps refers to the practice of applying DevOps principles and practices to mobile application development and delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*WYCTMI64n7bgi0wcEvw2mQ.jpeg" /></figure><p>In this article, we will learn more about Mobile DevOps.</p><p>DevOps, short for Development and Operations, is an approach that aims to streamline and automate software development, testing, and deployment.</p><p>Mobile DevOps focuses on mobile app development challenges and requirements. It combines software development, quality assurance, and operations to create a continuous integration and delivery pipeline that is tailored for mobile applications.</p><p><strong>Version Control</strong></p><p>Mobile DevOps relies on version control systems (e.g., Git, GitHub, BitBucket) to manage mobile applications’ source code. Developers can collaborate, track changes, and manage different versions effectively.</p><p><strong>Continuous Integration</strong></p><p>DevOps emphasizes frequent integration of code changes into a shared repository. To merge changes, run tests, and ensure the stability of an application, developers use automated build tools and processes.</p><p><strong>Continuous Deployment</strong></p><p>Delivering and deploying mobile apps is automated with mobile DevOps. In this process, the app is packaged, signed, and distributed to various app stores and enterprise distribution platforms. As a result of continuous delivery, new features and updates are released quickly and efficiently.</p><p><strong>Collaboration and Communication</strong></p><p>DevOps promotes collaboration among developers, testers, and operations teams. Shared tools, documentation, and cross-functional teams can facilitate this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd7f66e860af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>