<?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 Nyonggodwill on Medium]]></title>
        <description><![CDATA[Stories by Nyonggodwill on Medium]]></description>
        <link>https://medium.com/@nyonggodwill11?source=rss-6898a45287ab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xZZhuxNYvkQF2j8mVAZ9gw.jpeg</url>
            <title>Stories by Nyonggodwill on Medium</title>
            <link>https://medium.com/@nyonggodwill11?source=rss-6898a45287ab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:00:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nyonggodwill11/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[Measuring and Interpreting Token Usage in LLMs]]></title>
            <link>https://nyonggodwill11.medium.com/measuring-and-interpreting-token-usage-in-llms-cf9bcc8962f5?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf9bcc8962f5</guid>
            <category><![CDATA[token-usage]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 23:40:04 GMT</pubDate>
            <atom:updated>2026-02-02T23:40:04.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*6-3efVJdMXz5ZaQzqQ-s7A.jpeg" /></figure><p>Let’s look at evaluating LLMs beyond just accuracy, focusing on how they use resources, how their outputs change with different settings, and how to spot unusual or incorrect responses. One important evaluation feature is Token Usage.</p><p><strong>Why Token Usage Matters</strong></p><p>Tokens are the basic units of text that LLMs process — think of them as pieces of words or characters. Every time you send a prompt to an LLM, it counts the number of tokens in your input and its output.</p><p>In benchmarking, efficiency matters as much as accuracy. Tracking token usage helps you understand not only how “smart” a model is, but how resource-hungry it is — something crucial for real-world applications and cost management. How do you actually go about measuring token usage? Let’s look at the context window.</p><p><strong>The Role of the Context Window</strong></p><p>When working with LLMs, it’s important to understand the concept of a context window. The context window is the maximum number of tokens (including both your input prompt and the model’s output) that the model can process in a single request. For example, the GPT-3.5-turbo model has a context window of 4096 tokens, while newer models like GPT-4 can handle up to 128,000 tokens.</p><p>The context window determines how much information the model can “see” at once. If your prompt and the expected completion together exceed this limit, the model will either truncate the input or cut off the output. This can affect the quality and completeness of the responses.</p><p>When benchmarking or designing prompts, always keep the context window in mind:</p><p>* If your prompt is very long, you may need to shorten it to leave enough room for the model’s response.</p><p>* If you expect a long answer, make sure your prompt is concise enough to fit within the context window.</p><p>* Exceeding the context window can lead to incomplete outputs or errors.</p><p>Monitoring token usage helps you stay within the context window and ensures that your prompts and completions are processed as intended.</p><p><strong>Practical Implementation: Measuring Token Usage</strong></p><p>To measure token usage effectively, we’ll use the OpenAI Python client library. This library allows you to interact with OpenAI’s models and track resource consumption.</p><pre>import openai<br>from openai import OpenAI<br><br># Initialize the client<br>client = OpenAI(api_key=&quot;your-api-key&quot;)<br><br>def measure_token_usage(prompt, model=&quot;gpt-3.5-turbo&quot;):<br>    &quot;&quot;&quot;<br>    Measure token usage for a given prompt and model response<br>    &quot;&quot;&quot;<br>    try:<br>        response = client.chat.completions.create(<br>            model=model,<br>            messages=[{&quot;role&quot;: &quot;user&quot;, &quot;content&quot;: prompt}],<br>            max_tokens=150<br>        )<br>        <br>        # Extract token usage information<br>        usage = response.usage<br>        <br>        return {<br>            &quot;prompt_tokens&quot;: usage.prompt_tokens,<br>            &quot;completion_tokens&quot;: usage.completion_tokens,<br>            &quot;total_tokens&quot;: usage.total_tokens,<br>            &quot;response&quot;: response.choices[0].message.content<br>        }<br>    <br>    except Exception as e:<br>        return {&quot;error&quot;: str(e)}<br><br># Example usage<br>prompts = [<br>    &quot;Explain machine learning in simple terms&quot;,<br>    &quot;Write a Python function to calculate fibonacci numbers&quot;,<br>    &quot;What are the benefits of using LLMs in software development?&quot;<br>]<br><br>for i, prompt in enumerate(prompts, 1):<br>    result = measure_token_usage(prompt)<br>    if &quot;error&quot; not in result:<br>        print(f&quot;Prompt {i}: {result[&#39;total_tokens&#39;]} tokens&quot;)<br>        print(f&quot;  Input: {result[&#39;prompt_tokens&#39;]} tokens&quot;)<br>        print(f&quot;  Output: {result[&#39;completion_tokens&#39;]} tokens&quot;)<br>        print(f&quot;  Response: {result[&#39;response&#39;][:100]}...&quot;)<br>        print(&quot;-&quot; * 50)</pre><pre>Prompt: Summarize the history of the Roman Empire.<br>Prompt tokens: 17<br>Completion tokens: 137<br>Total tokens: 154<br><br>Prompt: Summarize the plot of the movie Titanic in two sentences.<br>Prompt tokens: 20<br>Completion tokens: 47<br>Total tokens: 67<br><br>Prompt: Summarize the process of photosynthesis.<br>Prompt tokens: 16<br>Completion tokens: 130<br>Total tokens: 146</pre><p><strong>Understanding the Output</strong></p><p>Now, let’s break down what these numbers mean. The prompt tokens value tells you how many tokens were in your input prompt. The completion tokens value shows how many tokens the model used to generate its response. The total tokens is simply the sum of the two.</p><p>But what do these numbers actually mean in practice?</p><ul><li>Prompt tokens: This number reflects the length and complexity of your input. For example, a short question like “What is photosynthesis?” might use only a few tokens, while a detailed instruction or a multi-part question will use more. If you see a high prompt token count, it means your input is long or complex.</li><li>Completion tokens: This number tells you how much the model “said” in response. A low number means a short answer; a high number means a longer, more detailed answer. If you ask for a summary in one sentence, you’ll see fewer completion tokens than if you ask for a detailed explanation.</li><li>Total tokens: This is the sum of prompt and completion tokens. It represents the total resources used for the request. Most LLM providers, including OpenAI, charge based on this total token count.</li></ul><p><strong>What Can Token Numbers Inform Us?</strong></p><ul><li>Cost: Since providers charge per token, higher total token counts mean higher costs. Monitoring token usage helps you manage expenses, especially at scale.</li><li>Efficiency: If you notice that similar prompts produce very different token counts, it may indicate that some prompts are less efficient or that the model is being unnecessarily verbose.</li><li>Model Limits: LLMs have maximum token limits per request (the context window, for example, 4096 tokens for some models). If your prompt and expected completion together approach this limit, you may need to shorten your input or expect shorter outputs.</li><li>Benchmarking: By comparing token usage across prompts and models, you can benchmark not just accuracy, but also efficiency. For example, if two models give similar answers but one uses fewer tokens, it may be more efficient for your use case.</li></ul><p>Understanding these numbers helps you see how much information you are sending and receiving, estimate costs, and optimize your prompts for both quality and efficiency.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf9bcc8962f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Your First AI Agent]]></title>
            <link>https://nyonggodwill11.medium.com/building-your-first-ai-agent-3d74b824e4f5?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d74b824e4f5</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[kaggle]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[llm-agent]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 12:40:32 GMT</pubDate>
            <atom:updated>2025-11-11T12:40:32.705Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agent Architectures</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*774OV-Lf1qwUU53Q86JKxw.png" /></figure><p>Yesterday marked the first day of the 5-Day AI Agents Intensive Course with Google! We covered an introductory section on AI Agents. I recommend you check out this white paper: <a href="https://www.kaggle.com/whitepaper-introduction-to-agents">https://www.kaggle.com/whitepaper-introduction-to-agents</a>. <br>AI is changing direction! 🧭 Over the years, the focus has been on models that excel at passive, discrete tasks: answering a question, translating text, or generating an image from a prompt. While this has been a groundbreaking development in the AI space, it requires constant human direction for every step.<br>The new shift in AI is moving from systems that just predict or create content to a new class of software capable of autonomous problem-solving and task execution. This new focus is on building AI agents. 🤖<br>An agent is not simply an AI model in a static workflow; it’s a complete application that makes plans and takes actions to achieve goals. It combines a Language Model’s (LM) ability to reason with the practical ability to act, allowing it to handle complex, multi-step tasks that a model alone cannot.</p><p>Let’s look at it this way:</p><p>LLMs Such as Gemini, ChatGPT:<br>Prompt -&gt; LLM -&gt; Text</p><p>An AI Agent takes this one step further. An agent can think, take actions, and observe the results of those actions to give you a better answer!</p><p>💡<br>Prompt -&gt; Agent -&gt; Thought -&gt; Action -&gt; Observation -&gt; Final Answer</p><p>From above, the shift is clear! Let’s go a little further to look at some properties that make up an agent. These are the properties we assign to the agent.</p><p><strong>Agent Properties 💡:</strong><br><strong>Name and description</strong>: A simple name and description to identify our agent.<br><strong>Model</strong>: The specific LLM that will power the agent’s reasoning.<br><strong>Instruction</strong>: The agent’s guiding prompt. This tells the agent what its goal is and how to behave.<br><strong>Tools</strong>: A list of tools that the agent can use, for example, a google_search tool to find up-to-date information online.</p><p><strong>Types of Agents</strong> 🤔<br><strong>Single Agent</strong>:<br>A single agent operates independently to achieve a specific goal or perform a defined task, without collaborating with other agents. For example, a ResearcherAgent that searches for papers and a SummaryAgent that summarizes the research from the ResearcherAgent. A single agent can do a lot! But what happens when the task gets complex? A single “monolithic” agent that tries to do research, writing, editing, and fact-checking all at once becomes a problem. Its instruction prompt gets long and confusing. This is where multi-agents come into play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*PdYDwpyBa_2B4hIX3J8J_Q.png" /><figcaption>Single Agent</figcaption></figure><p><strong>Multiple Agents</strong>: 👥<br>Instead of one “do-it-all” agent, we build a multi-agent system. This is a team of simple, specialized agents that collaborate, just like a real-world team. Each agent has one clear job (e.g., one agent only does research, another only writes). This makes them easier to build, easier to test, and much more powerful and reliable when working together.<br>Another important aspect is Agent Workflow. Workflow refers to the way in which agents execute their tasks. Below are some examples of agent workflows. A multi-agent system can be unreliable without a workflow. A complex LLM might decide to skip a step, run them in the wrong order, or get “stuck,” making the process unpredictable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*Fe1ONIBoVgkvUhrxrTE04w.png" /></figure><p><strong>Agent Workflows</strong> 🔄<br><strong>Sequential Workflows — The Assembly Line:</strong> 🏭<br>When you need tasks to happen in a guaranteed, specific order, you can use a SequentialAgent. This agent acts like an assembly line, running each sub-agent in the exact order you list them. The output of one agent automatically becomes the input for the next, creating a predictable and reliable workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bphAxD9WgLRGIEMjSaSXJQ.png" /><figcaption>Sequential Workflows</figcaption></figure><p><strong>Parallel Workflows — Independent Researchers: ⚡</strong><br>The previous sequential agent is great, but it’s an assembly line. Each step must wait for the previous one to finish. What if you have several tasks that are not dependent on each other? When you have independent tasks, you can run them all at the same time using a ParallelAgent. This agent executes all of its sub-agents concurrently, dramatically speeding up the workflow. Once all parallel tasks are complete, you can then pass their combined results to a final ‘aggregator’ step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*Cp4i_gSc07p11jRrddwFBg.png" /></figure><p><strong>Loop Workflows — The Refinement Cycle: 🔁</strong><br>All the workflows we’ve seen so far run from start to finish. The SequentialAgent and ParallelAgent produce their final output and then stop. This ‘one-shot’ approach isn’t good for tasks that require refinement and quality control. What if the first draft of our story is bad? We have no way to review it and ask for a rewrite.</p><p>The Solution: Iterative Refinement<br>When a task needs to be improved through cycles of feedback and revision, you can use a LoopAgent. A LoopAgent runs a set of sub-agents repeatedly until a specific condition is met or a maximum number of iterations is reached. This creates a refinement cycle, allowing the agent system to improve its work continually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*VAJ0u0syNj1QiVfWdrtSfg.png" /><figcaption>Loop Workflows — The Refinement Cycle</figcaption></figure><p>We have seen different Agent workflows such asSequentialAgent, ParallelAgent, and LoopAgent Their use depends on what we want to achieve. Comment Implementation, let’s dive into seeing how we can implement this different Agent workflow in our Agent development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d74b824e4f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey To Open Source With Outreachy.]]></title>
            <link>https://nyonggodwill11.medium.com/my-journey-to-open-source-with-outreachy-0ccfcbaf5d9b?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ccfcbaf5d9b</guid>
            <category><![CDATA[mboalab]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[outreachy]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Thu, 18 Jan 2024 06:11:02 GMT</pubDate>
            <atom:updated>2024-01-18T06:11:02.623Z</atom:updated>
            <content:encoded><![CDATA[<p>Setting the Stage for Change, Embracing Growth and Empathy at Outreachy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Gg_g2wR4oTR2FPiikNpkw.jpeg" /></figure><p>Hi, there! Welcome to my first internship blog post. I’m supper excited to have this opportunity to share my experience and insights as I begin an exciting journey as a Outreachy intern for MboaLab!. Outreachy is a non-profit organization that provides paid, remote internships to open source software (OSS) projects for people from underrepresented groups in technology.</p><p>I’m Nyong Godwill a Product designer, Flutter Developer, Backend Developer, and a blogger. I am so passionate about open-source projects especially those that have as goal for creating a community for everyone. I believe a lot in technology with it positive changes it is bringing to the community, and I’m eager to bring more changes that will solve community related problems. Is all about the community, being able to solved community related problems through tech has always being my passion. With Outreachy bridging the gap between interns and Organization that get involved with communities makes it easier to get close to these communities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wnhE0lE-onE01Pbb" /><figcaption>Photo by <a href="https://unsplash.com/@theandrewteoh?utm_source=medium&amp;utm_medium=referral">Andrew Teoh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Core Values:</h3><p>As I start this internship episode, I’d like to reflect on some few core values that resonate deeply within me that gives me guidance in every actions I take. These values are so important to who I am as an individual and outline the way I approach my work:</p><ol><li>Growth: Growth is one of the key value that is constantly improving every single second of my life. This is easy and very possible through online courses that is, my best movies l love to follow and with the help of Udemy and Coursera as my movie sites, it have made it more easier. I believe in the power of continuous learning and self-improvement. Taking up challenges and moving out of my comfort zone has been a key tool in my personal and professional development. Is all about doing the hard things, challenging myself, acquiring new skills, and growing as a person. I believe this will be of great help through out my stay as an Outreachy intern.</li><li>Empathy: One of the features of a good product designer is Empathy. Empathy is all putting others in the same position as you and being able to experience a product like them. Designing and developing product base on the ability to understand and share the user feelings is one of the greatest skill I have developed and am still developing it. By cultivating and improving my empathy skills, I aim to promote inclusivity, respect, and compassion in all my interactions. As an Outreachy intern, I’m happy to contribute to one of its mission of empowering underrepresented individuals in the tech world through empathy and understanding.</li></ol><h3>Motivation to Apply to Outreachy:</h3><p>What made me to apply for the Outreachy internship program was driven by many values. Here are a few key motivations that power my desire to become a part of this incredible initiative:</p><ol><li>Diversity and Inclusion: I have always wanted to be in community that provide equal access to everyone regardless of the individual ability. I believe a lot in the power of team work and when it comes team it all about everybody. With Outreachy providing that atmosphere where everyone is welcome, where everyone voice is heard, where everyone is accepted for who they are was one of the push factor to apply for this internship. I believe that diversity brings about innovation and leads to better outcomes with positive changes in the community. By offering internships specifically designed for underrepresented individuals, Outreachy provides a platform for voices that is difficult to be heard in the community. I wanted to be a part of this transformative journey toward a more inclusive tech community.</li><li>Mentorship and Support: To attain the growth level I have always dream of , I need to go an extra mile. This can only be possible through mentorship and support by someone who is already ahead of you and already in the field. My search for a community where I can be mentored have been one of my goal. With Outreachy’s providing this mentorship and support, interest me greatly to apply for the internship. Being part of a supportive community where I could learn from experts in my field will improve my growth a lot.</li><li>Impactful Projects: The ability to contribute to open-source projects attracted me to Outreachy. Working on projects that have real-world impact and benefit the community is one of my desire. The opportunity to collaborate with like-minded individuals on projects that align with my interests is incredibly exciting.</li></ol><h3>Conclusion:</h3><p>As I take off on this transformative journey with Outreachy, embracing growth, empathize with others, and make a positive impact is my goal. Through this blog, I hope to document my progress, share insights, and inspire others to pursue their passions fearlessly. Stay tuned for more updates as I navigate this internship adventure with Outreachy, and thank you for joining me on this exciting path of discovery!.</p><p>To know more about Outreachy and Open Source? Check out the following resources.</p><p>Outreachy Website: <a href="https://www.outreachy.org/"><strong>https://www.outreachy.org/</strong></a></p><p>Open-source initiative website: <a href="https://www.outreachy.org/"><strong>https://opensource.org/</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ccfcbaf5d9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Node.js and npm]]></title>
            <link>https://nyonggodwill11.medium.com/installing-node-js-and-npm-269ba670a571?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/269ba670a571</guid>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Mon, 23 Oct 2023 05:30:05 GMT</pubDate>
            <atom:updated>2023-10-23T05:30:05.051Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/254/1*KeGyagrQhe0G2_Q4OQXFFg.png" /></figure><h3>Introduction to Node.js and NPM</h3><p>Node.js is an open-source, cross-platform, JavaScript runtime environment that allows developers to run JavaScript code outside of a web browser. Node.js was created in 2009 by Ryan Dahl and has since become a popular choice for building web applications and command-line tools.</p><p>One of the key features of Node.js is its ability to use packages and modules that are available through the Node Package Manager (NPM). NPM is the default package manager for Node.js and is used to install and manage packages that provide additional functionality to your Node.js applications.</p><p>NPM makes it easy to install and manage packages from the NPM registry, which contains over 1 million packages created by developers from around the world. These packages can be used to add functionality to your application, such as database connectivity, image processing, or even full-stack web development frameworks.</p><h3>Understanding the Installation Process</h3><p>Before we dive into the specifics of how to install Node.js and NPM on various operating systems, it’s helpful to understand the installation process and what’s happening behind the scenes.</p><p>When you install Node.js, you’re essentially installing a program that allows you to run JavaScript code outside of a web browser. The installation process involves downloading and installing the Node.js runtime, which includes the V8 JavaScript engine (the same engine used in Google Chrome), as well as various libraries and dependencies that Node.js needs to run.</p><p>NPM, on the other hand, is installed as part of the Node.js installation process. When you install Node.js, NPM is included as a package that allows you to easily install and manage packages for your Node.js projects.</p><p>Once you have Node.js and NPM installed, you can start using NPM to install packages for your Node.js projects. When you install a package using NPM, it downloads the package from the NPM registry and installs it in a node_modules directory in your project&#39;s directory. NPM also creates a package.json file in your project&#39;s directory, which contains information about your project and its dependencies.</p><p>In the following sections, we’ll go through the steps for installing Node.js and NPM on Windows, macOS, and Linux, and show you how to verify that they’re installed correctly.</p><h3>Installing Node.js and NPM on Windows</h3><p>Installing Node.js and NPM on Windows is a straightforward process.</p><ol><li>First we need to download the Windows installer for the LTS (Long-term Support) version of Node.js from the official website(<a href="https://nodejs.org/en/">https://nodejs.org/en/</a>). The LTS version is recommended for most users, as it provides a stable and supported version of Node.js.</li><li>Once the installer is downloaded, we can run it and follow the prompts to install Node.js. During the installation process, we can choose the installation directory and select any additional features we may need. The default installation settings should be fine for most users.</li><li>After the installation is complete, we need to add the Node.js and NPM directories to our system environment variables. This will allow us to run Node.js and NPM from the command line.<br>To do this, we need to open the <strong>System Properties window</strong>, click on the <strong>Advanced </strong>tab, and then click on the <strong>Environment Variables </strong>button. From here, we can add the Node.js and NPM directories to the PATH variable.</li><li>To verify that Node.js and NPM are installed correctly, open a command prompt or PowerShell window and run the following commands:</li></ol><pre>node -v<br>npm -v</pre><p>These commands should return the version numbers of Node.js and NPM, respectively.</p><h3>Installing Node.js and NPM on Mac</h3><p>Installing Node.js and NPM on a Mac is also a straightforward process.</p><ol><li>First we need to download the macOS installer for the LTS (Long-term Support) version of Node.js from the official website(<a href="https://nodejs.org/en/">https://nodejs.org/en/</a>). The LTS version is recommended for most users, as it provides a stable and supported version of Node.js.</li><li>Once the installer is downloaded, we can run it and follow the prompts to install Node.js. The default installation settings should be fine for most users.</li><li>After the installation is complete, we need to verify that Node.js and NPM are installed correctly by opening a <strong>terminal window </strong>and running the following commands:</li></ol><pre>node -v<br>npm -v</pre><h3>Installing Node.js and NPM on Linux</h3><p>Installing Node.js and NPM on Linux is a bit more involved than on Windows or Mac, as there are many different Linux distributions and installation methods. However, the official Node.js website provides detailed instructions for installing Node.js and NPM on various Linux distributions.</p><h3>Using Terminal</h3><p>To install Node.js and NPM using <strong>Terminal</strong>, the steps vary depending on the Linux distribution you are using. Here, we’ll cover the general steps that should work for most distributions.</p><ol><li>First, open a terminal window and update your package manager’s cache by running the following command:</li></ol><pre>sudo apt update</pre><p>This will ensure that you have the latest package information before you install Node.js.</p><p>2. Next, install Node.js and NPM by running the following command:</p><pre>sudo apt install nodejs npm</pre><p>This will install the LTS (Long-term Support) version of Node.js and NPM from the default package repository for your distribution.</p><p>3. Once the installation is complete, verify that Node.js and NPM are installed correctly by running the following command:</p><pre>node -v<br>npm -v</pre><h3>Troubleshooting Common Installation Errors</h3><p>Even if you follow the installation steps correctly, you may still encounter errors during the installation process. Here are some common errors and their solutions:</p><ol><li>“<strong>Node.js and/or NPM is not recognized as an internal or external command</strong>”<br>If you see this error message after installing Node.js and NPM, it may be because they were not added to your system’s PATH environment variable. To fix this, you can add the Node.js and NPM directories to your PATH variable manually. The directories can usually be found in the following locations:<br>- Windows: C:\Program Files\nodejs\<br>- macOS and Linux: /usr/local/bin/</li><li>“<strong>Error: EACCES: permission denied, access…</strong>”<br>If you see this error message when running an NPM command, it may be because you don’t have the necessary permissions to write to a certain directory. To fix this, you can try running the command with elevated privileges using the <strong>sudo </strong>command (e.g., sudo npm install -g package_name).</li><li>“<strong>Error: ENOENT: no such file or directory…</strong>”<br>If you see this error message when running an NPM command, it may be because the package you’re trying to install doesn’t exist in the NPM registry. Double-check the package name and try again.</li><li>“<strong>Error: SSL certificate problem: unable to get local issuer certificate</strong>”<br>If you see this error message when running an NPM command, it may be because your system’s SSL certificate is not configured correctly. To fix this, you can try updating your system’s SSL certificate bundle or disable SSL verification using the -insecure flag with your NPM command (e.g., npm install -insecure package_name).</li></ol><p>If you encounter any other errors during the installation process, try searching online for solutions or consulting the documentation for your specific operating system and package manager.</p><h3>How to Update Node.js and NPM</h3><p>Node.js and NPM are constantly evolving, with new features and bug fixes being added in each version release. It’s important to keep your Node.js and NPM installations up to date to take advantage of these improvements. Here’s how you can update Node.js and NPM to the latest versions:</p><ul><li><strong>Updating Node.js</strong><br>To update Node.js, you can use a package manager like NPM. First, open a terminal window and run the following command to update NPM to the latest version:</li></ul><pre>npm install -g npm@latest</pre><ul><li><strong>Updating NPM</strong><br>If you want to update NPM independently of Node.js, you can run the following command:</li></ul><pre>npm install -g npm@latest</pre><h3>Best Practices for Managing Node.js and NPM Versions</h3><p>Managing Node.js and NPM versions can be challenging, especially when working on multiple projects that require different versions. One best practice is to use a version manager like NVM, as mentioned earlier. This allows us to easily switch between different versions of Node.js and NPM without affecting other projects.</p><p>Another best practice is to specify the required versions of Node.js and NPM in our project’s package.json file. This ensures that everyone working on the project is using the same versions of Node.js and NPM, which can prevent compatibility issues and make it easier to maintain the project in the long run.</p><h3>Conclusion</h3><p>In conclusion, installing and managing Node.js and NPM is an essential part of web development. By following the steps outlined in this guide, you can install Node.js and NPM on your local machine and start building powerful web applications. Remember to keep your versions up to date, use a version manager, and specify your project’s dependencies in the package.json file.</p><p>If you are interested in learning more about web development and other tech-related topics, feel free to visit my profile to read more articles and tech-related news.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=269ba670a571" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flutter: SQFLite]]></title>
            <link>https://nyonggodwill11.medium.com/flutter-sqflite-323c035dcffe?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/323c035dcffe</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[provider]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[sqflite]]></category>
            <category><![CDATA[localstorage]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Thu, 24 Aug 2023 11:57:06 GMT</pubDate>
            <atom:updated>2023-08-29T12:18:23.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*biRf6YgpBpVDcpS-yrUjDg.jpeg" /></figure><p>In this article we will be focusing on <strong>sqflite</strong>, which is the SQLite plugin for Flutter (yes the “f” of the name stands for Flutter 😄). SQLite is the most used database engine for mobile application, because it’s reliable, small and fast.</p><p>On this example we will create a little database to store TV Series you can’t wait to binge watch (yes, I know you have all the major streaming services subscriptions but 24 hours per day is too little time for using all of them, let’s try not to forget any of them).</p><p>The first thing to do is to add the following packages to your pubspec.yaml file, we will use path_provider to find the correct path to save the database.</p><pre>dependencies:<br>  sqflite: ^1.3.2<br>  path_provider: ^1.6.27</pre><p>Once you’ve added those up install the packages running a good old flutter pub get.</p><p>Now let’s create our helper class that will manage all the database functions. it is not “essential” to do that in a single class, you can also have initialization and data creation on Widgets or other places, but I’m sure you’ll need a bit of order in your code.<br>Create the todoDatabase.dart class with this content.</p><pre>import &#39;dart:io&#39;;<br>import &#39;package:sqflite/sqflite.dart&#39;;<br>import &#39;package:path/path.dart&#39;;<br>import &#39;package:path_provider/path_provider.dart&#39;;<br><br>class NoteDatabase{<br>NoteDatabase.internal();<br>  static final NoteDatabase instance = NoteDatabase.internal();<br>  factory NoteDatabase() =&gt; instance;<br>  static String noteTable = &quot;noteDatabase&quot;;<br>  final _version = 3;<br>  Database? _db;<br>  Future&lt;Database?&gt; get db async {<br>    if (_db != null) {<br>      return _db;<br>    }<br>    _db = await initDb();<br>    return _db;<br>  }<br><br>  Future&lt;Database&gt; initDb() async {<br>    Directory directory = await getApplicationDocumentsDirectory();<br>    String dbPath = join(directory.path, &#39;noteDatabase.db&#39;);<br>    log(dbPath);<br>    var openDb = await openDatabase(dbPath, version: _version,<br>        onCreate: (Database db, int version) async {<br>      await db.execute(<br>          &#39;CREATE TABLE $noteTable(id INTEGER PRIMARY KEY,title TEXT NOT NULL,description TEXT,created_at TEXT,)&#39;);<br>    }, onUpgrade: (Database db, int oldVersion, int newVersion) async {<br>      if (oldVersion &lt; newVersion) {<br>        log(&quot;Version Upgrade&quot;);<br>      }<br>    });<br>    log(&#39;db initialize&#39;);<br>    return openDb;<br>}<br>}</pre><p>This is the singleton class that we will use to interact with the database, using NoteDatabase.instance. We&#39;ve created the singleton and added the code to create the Note table.</p><p>Now let’s create the model class that will represent a NoteApp in our app (note.dart). Each Note series will have an id, a title, the description, the created_at. The functions fromDbMap and toDbMap will be used to save and retrieve Note objects from the database. See that&#39;s good practice to have these methods on the class.</p><pre>class Note{<br>  int id;<br>  String title;<br>  String description;<br>  String created_at;<br>Note ({required this.id, required this.title, required this.description, required this.created_at});<br><br> factory Note.fromJson(json) {<br>  return Note(<br> id : json[&quot;id&quot;],<br>title: json[&quot;title&quot;],<br>description: json[&quot;description&quot;],<br>created_at: json[&quot;created_at&quot;]<br>)<br>}<br>     <br><br> Map&lt;String, dynamic&gt; toJson()=&gt; {<br>   <br>    &#39;id&#39; :id;<br>    &#39;title&#39; :title;<br>    &#39;description&#39; :description;<br>    &#39;created_at&#39;:created_at;<br>    <br>  }<br>}</pre><p>The last thing that we have to do is to add functions to fetch, add, edit or delete Note in the NoteDatabase class.</p><p>Below you’ll see some useful methods you can integrate on your helper class:</p><h3>Fetch all Notes, Add Notes, Update Notes, Delete Note</h3><pre>class NoteController {<br>  final conn = NoteDatabase.instance;<br><br>  Future&lt;int&gt; addNote(Note noteinfoModel) async {<br>    var dbclient = await conn.db;<br>    int result = 0;<br>    try {<br>      result = await dbclient!.insert(NoteDatabase.noteTable,<br>          noteinfoModel.toJson());<br>    } catch (e) {<br>      print(e.toString());<br>    }<br>    return result;<br>  }<br><br>  Future&lt;int&gt; updateNote(Note noteinfoModel) async {<br>    var dbclient = await conn.db;<br>    int result = 0;<br>    try {<br>      result = await dbclient!.update(<br>          NoteDatabase.noteTable, noteinfoModel.toJson(),<br>          where: &#39;id=?&#39;, whereArgs: [noteinfoModel.id]);<br>    } catch (e) {<br>      print(e.toString());<br>    }<br>    return result;<br>  }<br><br>  Future fetchAllNote() async {<br>    var dbclient = await conn.db;<br>    List noteList = [];<br>    try {<br>      List&lt;Map&lt;String, dynamic&gt;&gt; maps = await dbclient!<br>          .query(NoteDatabase.noteTable, orderBy: &#39;id DESC&#39;);<br>      for (var item in maps) {<br>        noteList.add(item);<br>      }<br>    } catch (e) {<br>      print(e.toString());<br>    }<br>    return noteList;<br>  }<br>}<br></pre><p>Well, you got to the bottom, was it hard? It wasn’t, right?<br>Be aware that there’s not really a “wrong” method to store data, you can absolutely have thousands of files saved, but SQFLite is not only the most used data persistence method but also the one recommended by Flutter team, so it will mean something… Ain’t it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=323c035dcffe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firestore Database: CRUD (Flutter)]]></title>
            <link>https://nyonggodwill11.medium.com/firestore-database-crud-flutter-f7465acaf268?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7465acaf268</guid>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[firestore]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Wed, 02 Aug 2023 13:14:29 GMT</pubDate>
            <atom:updated>2023-08-02T13:14:29.750Z</atom:updated>
            <content:encoded><![CDATA[<p>This article covers the most important aspects you need to know when working with Flutter and Firebase Firestore. We will walk through the basics of Firestore, and later, we will build a complete application that lets a user create, update, read, and delete some fiction products.</p><p><strong>Note</strong>: CRUD stands for <strong>C</strong>reate, <strong>R</strong>ead, <strong>U</strong>pdate, and <strong>D</strong>elete, the four basic operations of persistent storage.Advertisements</p><p>This article was recently updated to work well with the latest versions of Flutter and fix some minor bugs.Advertisements</p><p><strong>Table Of Contents</strong></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#Prerequisites">1 Prerequisites</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#Overview">2 Overview</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#The_Complete_Example">3 The Complete Example</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#App_Preview">3.1 App Preview</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#Creating_a_Firestore_database">3.2 Creating a Firestore database</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#Installing_cloud_firestore">3.3 Installing cloud_firestore</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#The_Full_Code">3.4 The Full Code</a></p><p><a href="https://www.kindacode.com/article/flutter-firestore-database/#Conclusion">4 Conclusion</a></p><h3>Prerequisites</h3><p>To get the most out of this tutorial, you need the following:</p><ul><li>Basic knowledge about Flutter.</li><li>Flutter version 3.3.10 or higher.</li><li>A registered Firebase account with a ready-to-use project.</li><li>A clean Flutter project with the <a href="https://pub.dev/packages/firebase_core">firebase_core</a> plugin installed and correctly configured. If you don’t, see the following guide before moving to the next section: <a href="https://www.kindacode.com/article/flutter-configure-firebase-for-ios-and-android/">Flutter: Configure Firebase for iOS and Android</a>.</li><li>Knowing Firebase’s terms of service.</li></ul><h3>Overview</h3><p>Cloud Firestore is a NoSQL document database from Google that lets you easily store, sync, and query data. It gives us the ability to quickly build applications of all sizes, from small to large, without having to worry too much about the backend stuff.</p><p>Firestore is Firebase’s newest database for mobile development. It builds on the successes of the Realtime Database with a new, more intuitive data model. If you have some experience with Realtime Database, you will absorb this article quickly. If you don’t, you will also absorb this article quickly (I guess that).</p><p>Besides <strong>firebase_core</strong>, we need another plugin named <a href="https://pub.dev/packages/cloud_firestore">cloud_firestore</a> for the project we are going to build.Advertisements</p><h3>The Complete Example</h3><h3>App Preview</h3><p>As said above, this example app lets a user create, update, read, and delete fiction products. Its UI is neat and clean, with a single screen, a ListView, a bottom sheet, and a floating button. Here’s how it works:Advertisements</p><p><strong>Note:</strong> If you’re using Safari, this demo video might not work nicely or not start at all. Please use Chrome, Edge, Firefox, or another web browser instead.</p><p>As you can see, Firebase is so wonderful. Any changes will be presented on Firebase without refreshing the browser.</p><h3>Creating a Firestore database</h3><p>This section is intended to be as clear as possible. If you feel tedious, just move faster.</p><p>1. Go to your Firebase project’s dashboard, select “Build” &gt; “Firestore Database” from the left sidebar, then click on the “Create database” button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*nOtP7GH_k6ae_8Bd" /></figure><p>2. Select “Start in test mode” and then click on the “Next” button (you can change to “production mode” later if you want).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*ca3F3DOw_LpKEwP6" /></figure><p>3. Select a location, then click the “Enable” button. The closer the location is, the lower the latency will be and the faster your app will function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*lj2Zz9717OyuTmnj" /></figure><p>4. Click “+ Start Collection” to create a new collection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/0*tb7R4IApxuyL5uVj" /></figure><p>5. Enter “products” and click “Next”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*p3OUJc6dAhblZJDR" /></figure><p>6. Add the first documents to our “products” collection. It has 2 fields: “name” (string) and “price” (number).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*LrTV-vALbmkVUHtu" /></figure><p>Fill in the fields, then click “Save”.</p><p>7. Now, we get a Firestore database ready to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*M7WSUlQ1JXfJNAiQ" /></figure><h3>Installing cloud_firestore</h3><p>Advertisements</p><p>You can add <strong>cloud_firestore</strong> to your project by executing the command below:</p><pre>flutter pub add cloud_firestore</pre><p>Then execute this:</p><pre>flutter pub get</pre><p>Import it into your Dart code:</p><pre>import &#39;package:cloud_firestore/cloud_firestore.dart&#39;;</pre><h3>The Full Code</h3><p>Advertisements</p><p>The final code with explanations within the comments:</p><pre>// main.dart<br>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:firebase_core/firebase_core.dart&#39;;<br>import &#39;package:cloud_firestore/cloud_firestore.dart&#39;;</pre><pre>void main() async {<br>  WidgetsFlutterBinding.ensureInitialized();<br>  await Firebase.initializeApp();<br>  runApp(const MyApp());<br>}</pre><pre>class MyApp extends StatelessWidget {<br>  const MyApp({Key? key}) : super(key: key);</pre><pre>  @override<br>  Widget build(BuildContext context) {<br>    return const MaterialApp(<br>      // Remove the debug banner<br>      debugShowCheckedModeBanner: false,<br>      title: &#39;Kindacode.com&#39;,<br>      home: HomePage(),<br>    );<br>  }<br>}</pre><pre>class HomePage extends StatefulWidget {<br>  const HomePage({Key? key}) : super(key: key);</pre><pre>  @override<br>  State&lt;HomePage&gt; createState() =&gt; _HomePageState();<br>}</pre><pre>class _HomePageState extends State&lt;HomePage&gt; {<br>  // text fields&#39; controllers<br>  final TextEditingController _nameController = TextEditingController();<br>  final TextEditingController _priceController = TextEditingController();</pre><pre>  final CollectionReference _productss =<br>      FirebaseFirestore.instance.collection(&#39;products&#39;);</pre><pre>  // This function is triggered when the floatting button or one of the edit buttons is pressed<br>  // Adding a product if no documentSnapshot is passed<br>  // If documentSnapshot != null then update an existing product<br>  Future&lt;void&gt; _createOrUpdate([DocumentSnapshot? documentSnapshot]) async {<br>    String action = &#39;create&#39;;<br>    if (documentSnapshot != null) {<br>      action = &#39;update&#39;;<br>      _nameController.text = documentSnapshot[&#39;name&#39;];<br>      _priceController.text = documentSnapshot[&#39;price&#39;].toString();<br>    }</pre><pre>    await showModalBottomSheet(<br>        isScrollControlled: true,<br>        context: context,<br>        builder: (BuildContext ctx) {<br>          return Padding(<br>            padding: EdgeInsets.only(<br>                top: 20,<br>                left: 20,<br>                right: 20,<br>                // prevent the soft keyboard from covering text fields<br>                bottom: MediaQuery.of(ctx).viewInsets.bottom + 20),<br>            child: Column(<br>              mainAxisSize: MainAxisSize.min,<br>              crossAxisAlignment: CrossAxisAlignment.start,<br>              children: [<br>                TextField(<br>                  controller: _nameController,<br>                  decoration: const InputDecoration(labelText: &#39;Name&#39;),<br>                ),<br>                TextField(<br>                  keyboardType:<br>                      const TextInputType.numberWithOptions(decimal: true),<br>                  controller: _priceController,<br>                  decoration: const InputDecoration(<br>                    labelText: &#39;Price&#39;,<br>                  ),<br>                ),<br>                const SizedBox(<br>                  height: 20,<br>                ),<br>                ElevatedButton(<br>                  child: Text(action == &#39;create&#39; ? &#39;Create&#39; : &#39;Update&#39;),<br>                  onPressed: () async {<br>                    final String? name = _nameController.text;<br>                    final double? price =<br>                        double.tryParse(_priceController.text);<br>                    if (name != null &amp;&amp; price != null) {<br>                      if (action == &#39;create&#39;) {<br>                        // Persist a new product to Firestore<br>                        await _productss.add({&quot;name&quot;: name, &quot;price&quot;: price});<br>                      }</pre><pre>                      if (action == &#39;update&#39;) {<br>                        // Update the product<br>                        await _productss<br>                            .doc(documentSnapshot!.id)<br>                            .update({&quot;name&quot;: name, &quot;price&quot;: price});<br>                      }</pre><pre>                      // Clear the text fields<br>                      _nameController.text = &#39;&#39;;<br>                      _priceController.text = &#39;&#39;;</pre><pre>                      // Hide the bottom sheet<br>                      Navigator.of(context).pop();<br>                    }<br>                  },<br>                )<br>              ],<br>            ),<br>          );<br>        });<br>  }</pre><pre>  // Deleteing a product by id<br>  Future&lt;void&gt; _deleteProduct(String productId) async {<br>    await _productss.doc(productId).delete();</pre><pre>    // Show a snackbar<br>    ScaffoldMessenger.of(context).showSnackBar(const SnackBar(<br>        content: Text(&#39;You have successfully deleted a product&#39;)));<br>  }</pre><pre>  @override<br>  Widget build(BuildContext context) {<br>    return Scaffold(<br>      appBar: AppBar(<br>        title: const Text(&#39;Kindacode.com&#39;),<br>      ),<br>      // Using StreamBuilder to display all products from Firestore in real-time<br>      body: StreamBuilder(<br>        stream: _productss.snapshots(),<br>        builder: (context, AsyncSnapshot&lt;QuerySnapshot&gt; streamSnapshot) {<br>          if (streamSnapshot.hasData) {<br>            return ListView.builder(<br>              itemCount: streamSnapshot.data!.docs.length,<br>              itemBuilder: (context, index) {<br>                final DocumentSnapshot documentSnapshot =<br>                    streamSnapshot.data!.docs[index];<br>                return Card(<br>                  margin: const EdgeInsets.all(10),<br>                  child: ListTile(<br>                    title: Text(documentSnapshot[&#39;name&#39;]),<br>                    subtitle: Text(documentSnapshot[&#39;price&#39;].toString()),<br>                    trailing: SizedBox(<br>                      width: 100,<br>                      child: Row(<br>                        children: [<br>                          // Press this button to edit a single product<br>                          IconButton(<br>                              icon: const Icon(Icons.edit),<br>                              onPressed: () =&gt;<br>                                  _createOrUpdate(documentSnapshot)),<br>                          // This icon button is used to delete a single product<br>                          IconButton(<br>                              icon: const Icon(Icons.delete),<br>                              onPressed: () =&gt;<br>                                  _deleteProduct(documentSnapshot.id)),<br>                        ],<br>                      ),<br>                    ),<br>                  ),<br>                );<br>              },<br>            );<br>          }</pre><pre>          return const Center(<br>            child: CircularProgressIndicator(),<br>          );<br>        },<br>      ),<br>      // Add new product<br>      floatingActionButton: FloatingActionButton(<br>        onPressed: () =&gt; _createOrUpdate(),<br>        child: const Icon(Icons.add),<br>      ),<br>    );<br>  }<br>}</pre><p>A good way that many people have applied and succeeded is to copy the entire code above and paste it into the <strong>main.dart</strong> file, then edit or remove some lines of code and see what happens, and so on, so little by little.</p><h3>Conclusion</h3><p>We built a simple Flutter application that uses the Firestore database as a backend. You also learned how to perform the four most important tasks when working with a database: creating data, updating data, reading data, and deleting data. From now on, you can make more complicated and complex apps with that tech stack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7465acaf268" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using ListView or PageView variants?]]></title>
            <link>https://nyonggodwill11.medium.com/using-listview-or-pageview-variants-eb89cd3455eb?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb89cd3455eb</guid>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Sat, 20 May 2023 05:39:18 GMT</pubDate>
            <atom:updated>2023-05-20T05:39:18.199Z</atom:updated>
            <content:encoded><![CDATA[<h3>ScrollPhysics in Flutter!</h3><p>Using ListView or PageView variants? How about changing the nature of the scroll in it so that your users can feel more real while using it? Let’s see how you can do that using different ScrollPhysics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4m0chXdNgfX8aYN5.png" /></figure><p>Image copyright to respective owner.</p><p>So if you are using any widget which has scrolling functionality, like ListView, ListView.builder, ListView.separated, PageView, PageView.builder, SingleChildScrollView, etc., you will get a parameter inside it called physics which takes up a ScrollPhysics . This parameter defines how users will see the scroll of your widget. Let’s see each type of ScrollPhysics one by one!</p><h3>1. NeverScrollableScrollPhysics:</h3><p>This physics will disable the scroll of your widget completely. It will render a non-scrollable list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*I3tQUBZ_u7ip6keh.gif" /></figure><h3>2. BouncingScrollPhysics:</h3><p>This physics gives a bouncing effect when a user reaches the end of the list. This physics is also a bit smoother to scroll compared to other types of physics. A similar effect is used in iOS. <strong>Tip:</strong> If you wish to have a less bounce effect, you can go into the code of BouncingScrollPhysics and make changes in the offset parameter. If you decrease the value of offset , the space behind the list when the bounce effect comes will decrease and hence you will feel like the bounce effect is less compared to earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*W-BMEP2-Oz8ynVUh.gif" /></figure><h3>3. ClampingScrollPhysics:</h3><p>This physics basically stops the list when the user reaches the end and shows a glow to indicate it. You can definitely remove the glow if you wish using ScrollConfiguration. This is the default scroll for Android. This scroll may sometimes feel a little choppy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*3XU8GSFS8Y9POeFT.gif" /></figure><h3>4. FixedExtentScrollPhysics:</h3><p>This physics is somewhat different from others. If you use this with ListView or PageView, you will notice your scroll lags a lot. FixedExtentScrollPhysics only scrolls to items instead of any offset in between. This is usually used with FixedExtendScrollControllers and the widget that use them. Most commonly, FixedExtentScrollPhysics is used with ListWheelScrollView which gives a wheel kind of effect when used with FixedExtentScrollPhysics.</p><p><strong>FixedExtentScrollPhysics</strong> with ListView:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*8qxsiUT0HjUdDTOt.gif" /></figure><p><strong>FixedExtentScrollPhysics </strong>with ListWhellScrollView:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*Se_HJBigyiFKc2YL.gif" /></figure><h3>5. PageScrollPhysics:</h3><p>This ScrollPhysics is mainly used with PageView and its variant. This makes the scrolling of pages smoother compared to any other ScrollPhysics. This can also be used with other scrollable widgets but you will notice it made your scroll smoother than required!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*5muZQaJDmZYHTI-C.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb89cd3455eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A beginner’s guide to Git — how to start and create your first repository]]></title>
            <link>https://nyonggodwill11.medium.com/a-beginners-guide-to-git-how-to-start-and-create-your-first-repository-19fb630728eb?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/19fb630728eb</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Mon, 15 May 2023 06:29:51 GMT</pubDate>
            <atom:updated>2023-10-03T05:37:47.054Z</atom:updated>
            <content:encoded><![CDATA[<h3>A beginner’s guide to Git — how to start and create your first repository</h3><p>After a short introduction on what is Git and how to use it, you will be able to create and work on a GitHub project.</p><h3>What is Git?</h3><p><a href="https://git-scm.com/">Git</a> is a free and open source software created by <a href="https://en.wikipedia.org/wiki/Linus_Torvalds">Linus Torvalds</a> in 2005. This tool is a version control system that was initially developed to work with several developers on the Linux kernel.</p><p>Many control systems exist, like CVS, SVN, Mercurial and others, but today Git is the standard software for version control.</p><h3>Version control, right?</h3><p>If you are new in the development world, these words will not tell you anything. However, don’t worry after this short paragraph, you will exactly know what a “<em>Version Control System (VCS)</em>” is.</p><p>Version control is a management system that takes into consideration modifications you’ve made on a file or a set of files (<em>example:</em> a code project). With this system, developers can collaborate and work together on the same project.</p><p>A branch system is carried by version control and allow developers to work individually on a task (<em>example: </em>One branch, one task or one branch, one developer) before to combine all changes made by the collaborators into the main branch.</p><p>All changes made by developers are traced and saved in a history. It can be beneficial to track modifications made by every collaborator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*9YMCKR5xei1PrmzZ.png" /></figure><p>Version Control System (VCS) change history — Copyright to <a href="https://www.toolsqa.com/git/version-control-system/">ToolsQA</a> post</p><h3>Where to find Git repositories</h3><p>If you want to start using Git, you need to know where to host your repositories. There are many hosting platforms where you can put your code free of charge. Some options aren’t free, but mostly you don’t need them except in specific cases.</p><p>Here the three most popular Git hosting services:</p><ul><li><a href="https://github.com/"><strong>GitHub</strong></a><strong>: </strong>Owned recently by Microsoft — Launched in 2008 (31 million users in October 2018).</li><li><a href="https://about.gitlab.com/"><strong>GitLab</strong></a><strong>: </strong>Owned by GitLab Inc. — Launched in 2011.</li><li><a href="https://bitbucket.org/product/"><strong>BitBucket</strong></a><strong>: </strong>Owned by Atlassian — Launched in June 2008.</li></ul><blockquote><em>Note: Hosting platforms are available in two ways, on the cloud (hosted online) or self-installed on your server (private hosting).</em></blockquote><h3>Why use Git as a developer</h3><p>This tool is inescapable for worldwide developers. Here is a list of advantages of this tool:</p><ul><li>No more copies, when you finish your work on a significant update for your application or a bug fix, you just need to “<em>push</em>” your project online to save it.</li><li>Delete and break your code; you just need to type a command to come back to the previous version and continue your work.</li><li>Work with your friends without sending an e-mail with the compressed project each time the code changes.</li><li>You can afford to forget what you did. A simple command is necessary to check your changes since the last time you saved your work.</li></ul><p>I just told you the main advantages if you don’t use Git at the moment. Believe me; this tool can become paramount. As an example, you can configure services to work with Git and automatically deploy and test your code.</p><h3>Now, let’s practice with Git and GitHub</h3><p>Now that you know what Git and Github are, it’s time to practice with concrete exercises.</p><p>After these exercises, you will be able to create and manage your projects via GitHub with all the basic features of Git.</p><blockquote><em>Note: I chose GitHub as our hosting service for Git because it’s the most used in the world. Don’t be afraid; the procedure is quite the same on other services.</em></blockquote><blockquote><strong><em>Please remember this article take into consideration you know at all the basics SHELL commands. If not, some parts of this article will be confusing.</em></strong></blockquote><h3>#1 step — Time to start!</h3><p>Looking forward to getting started? Let’s do it!</p><p>This first exercise is not very complicated; it’s divided into two steps. The Git installation and GitHub account creation.</p><p><strong>a. GitHub account creation</strong></p><p>To create your account, you need to connect on <a href="https://github.com/">the main GitHub page</a> and to fill in the registration form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*RYNV6xq8G-Z81VN_.png" /></figure><p>GitHub main page with registration form</p><p>Nothing more! You are officially a new member of GitHub!</p><p><strong>b. Git installation</strong></p><p>Now you need to install Git tools on your computer. There are different Git software, but it’s better to install the basic one to start. We will use the command line to communicate with GitHub.</p><p>Once you are more comfortable with the command line, you can download Git software with a user interface.</p><ul><li><em>For Ubuntu:</em></li></ul><p>First, update your packages:</p><pre>$ sudo apt update</pre><p>Next, install Git with apt-get:</p><pre>$ sudo apt-get install git</pre><p>Finally, verify that Git is installed correctly:</p><pre>$ git --version</pre><ul><li><em>For MacOSX:</em></li></ul><p>First, download the latest <a href="https://sourceforge.net/projects/git-osx-installer/files/">Git for Mac installer</a>.</p><p>Next, follow instructions on your screen.</p><p>Finally, open a terminal and verify that Git is installed correctly:</p><pre>$ git --version</pre><ul><li><em>For Windows:</em></li></ul><p>First, download the latest <a href="https://gitforwindows.org/">Git for Windows installer</a>.</p><p>Next, follow instructions on your screen (you can leave the default options).</p><p>Finally, open a terminal (example: powershell or git bash) and verify that Git is installed correctly:</p><pre>$ git --version</pre><ul><li><em>For all users:</em></li></ul><p>One last step is needed to complete the installation correctly! You need to run in your terminal the following commands with your information to set a default username and email when you are going to save your work:</p><pre>$ git config --global user.name &quot;Gaël Thomas&quot;<br>$ git config --global user.email &quot;example@mail.com&quot;</pre><h3>#2 step — Your first GitHub project!</h3><p>Now that you’re ready, you can return to the main GitHub page and click on the “<em>+</em>” icon in the menu bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*yKngcRwUDApk8Juc.png" /></figure><p>GitHub menu bar with “+” icon</p><p>Once you click on this button, a new menu appears with a “<em>New repository</em>” entry. Click on it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*JqVHWRJBr3HaJwYhKze3RA.png" /></figure><p>Submenu with “New repository” entry</p><p><a href="https://github.com/new">The repository creation page</a> will appear. Choose a cool name for your first repository and put a small description before clicking on the “<em>Create repository</em>” button.</p><blockquote><em>Note: In the context of this article, please don’t tick “Initialize this repository with a README”. We will create a “README” file later!</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6IeLWoRycB3YNE7RFF8dfg.png" /></figure><p>Repository creation menu</p><p>Well done! Your first GitHub repository is created. If you want to see all your repositories, you need to click on your profile picture in the menu bar then on “<em>Your repositories</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*Slt4EbJaMEqaGLl1KAzTBA.png" /></figure><p>Submenu with “Your repositories” entry</p><h3>#3 step — A good cover</h3><p>It’s time to make your first modification to your repository. What do you think about creating a cover for it, a kind of welcome text?</p><p><strong>a. A local version of your project</strong></p><p>Your first mission is to get a copy of the repository on your computer. To do that, you need to “<em>clone</em>” the repository. On the repository page, you need to get the “<em>HTTPS</em>” address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ansOakUxKXjv3Zkfu2R3SA.png" /></figure><p>Repository page with “HTTPS” address</p><p>Once you had the address of the repositories, you need to use your terminal (through shell commands) to move in the place where you want to put the directory copy (for example you can move in your “<em>Documents</em>” folder). When you are ready, you can enter:</p><pre>$ git clone [HTTPS ADDRESS]</pre><p>This command will make a local copy of the repository hosted at the given address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*DKJlgt9BmwKJ1iPC.png" /></figure><p>Output message of “git clone” command</p><p>Now, your repository is on your computer. You need to move in it with:</p><pre>$ cd [NAME OF REPOSITORY]</pre><blockquote><em>Note: When you clone, Git will create a repository on your computer. If you want, you can access your project with the computer user interface.</em></blockquote><p><strong>b. Repository edition</strong></p><p>Now you can create a file named “<em>README.</em>md” in your folder (through the terminal or user interface on your computer). I’m not giving you any more details about this step, nothing in particular. Open your folder and add a file as if it were a standard folder.</p><p>If you want to do something cool, copy and paste this template in your “<em>README.md</em>” file. You can replace information between the hooks to personalize the output.</p><p><strong>c. Let’s share our work!</strong></p><p>Now that you have modified your project, you need to save it. This process is called committing.</p><p>To do this, get back to your terminal. If you have closed it, go back in your folder.</p><p>When you want to save your work, four steps are required. These steps are called: “<em>status</em>”, “<em>add</em>”, “<em>commit</em>” and “<em>push</em>”. I have prepared a standard procedure for you to perform each time you want to save your work.</p><blockquote><em>Note: All the following steps must be performed within your project.</em></blockquote><ul><li>“<em>status</em>”: The first thing you need to do once your work is to check the files you have modified. To do this, you can type the following command to make a list of changes appear:</li></ul><pre>$ git status</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*s80TMajKddXc1FIO.png" /></figure><p>“git status” output in our project</p><ul><li>“<em>add</em>”: With the help of the change list, you can add all files you want to upload with the following command:</li></ul><pre>$ git add [FILENAME] [FILENAME] [...]</pre><p>In our case, we are going to add “<em>README.md</em>” because we want to save this file.</p><pre>$ git add README.md</pre><blockquote><em>Note: If you type again “git status”, the “README.md” will appear now in green. This means that we have added the file correctly.</em></blockquote><ul><li>“<em>commit</em>”: Now that we have added the files of our choice, we need to write a message to explain what we have done. This message may be useful later if we want to check the change history. Here is an example of what we can put in our case.</li></ul><pre>$ git commit -m &quot;Added README.md with good description in it.&quot;</pre><ul><li>“<em>push</em>”: You’re there, you can now put your work online! If you type the following command, all your work will be put online and visible directly on the repository page.</li></ul><pre>$ git push origin master</pre><p>You did it! If you come back on your repository page on GitHub, you are going to your “<em>README.md</em>” file with a beautiful preview of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*4mT8AG1ptbjHJobk.png" /></figure><p>Repository page with “README.md” file</p><h3>Useful commands for Git</h3><p>You are still missing some essential commands as a beginner with Git. Here is a list that will be useful to you during your project.</p><ul><li>Display the history of commits (all modifications made on the project).</li></ul><pre>$ git log</pre><ul><li>Revert back all your changes since the last commit.</li></ul><pre>$ git checkout .</pre><ul><li>Revert all changes on a specific file since the last commit.</li></ul><pre>$ git checkout [FILENAME]</pre><ul><li>Display the last changes on a file since the last commit.</li></ul><pre>$ git diff [FILENAME]</pre><ul><li>Remove all unexpected files in your project (not committed).</li></ul><pre>$ git clean -dfx</pre><ul><li>Add all files and make a commit at the same time.</li></ul><pre>$ git commit -am [MESSAGE]</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19fb630728eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s new in Flutter 3.10]]></title>
            <link>https://nyonggodwill11.medium.com/whats-new-in-flutter-3-10-c54124eee63b?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/c54124eee63b</guid>
            <category><![CDATA[mobile-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[andriod-app-development]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Sun, 14 May 2023 12:48:29 GMT</pubDate>
            <atom:updated>2023-05-14T12:48:29.503Z</atom:updated>
            <content:encoded><![CDATA[<h3>Seamless web and mobile integration, breakthrough graphics performance via Impeller in stable, and more</h3><p>Welcome to Flutter 3.10! We can’t wait to show off the huge efforts of our amazing Flutter community. This Flutter release runs the incredible <a href="https://medium.com/dartlang/announcing-dart-3-53f065a10635">Dart 3</a> also available <em>today</em>!</p><p>Flutter 3.10 includes many improvements to web, mobile, graphics, security and so much more. Let’s get down to business!</p><h3>Framework</h3><h3>Material 3</h3><p>The Material library now matches the latest <a href="https://m3.material.io/components">Material Design spec</a>. Changes include new components and component themes, updated component visuals and more. Developers must “opt in” to these changes using the useMaterial3 theme flag. <em>In the next stable release, </em><em>useMaterial3 defaults to </em><em>true.</em></p><p>To opt in to the M3 version of the Material library, set useMaterial3 : true in your MaterialApp theme. The flutter create command adds this to your theme when creating a new app.</p><p>To preview these changes, check out the <a href="https://flutter.github.io/samples/material_3.html">demo app</a>. The demo lets you toggle useMaterial3 on and off.</p><h3>ColorScheme.fromImageProvider()</h3><p>All M3 components configure the default colors of the theme’s ColorScheme. The default color scheme uses shades of purple. You can create a custom color scheme either from a single “seed” color or from an image. Try both variations with the demo. Color schemes generated should look good and be accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sp5KR8COUncvd44S.gif" /></figure><h3>NavigationBar</h3><p>This provides an M3 version of BottomNavigationBar widget. While <a href="https://m3.material.io/components/navigation-bar/overview">M3</a> uses different colors, highlighting, and elevation, it works as it did before. To override the default appearance of the NavigationBars widget, use the NavigationBarTheme widget. Though you don’t need to migrate existing apps to this component, you should use it for new apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*akpMzHjVAaoJCKf-.gif" /></figure><h3>NavigationDrawer</h3><p>This provides an <a href="https://m3.material.io/components/navigation-drawer/overview">M3</a> destination selection widget based on the Drawer widget. NavigationDrawer shows a single-selection list of NavigationDestinations widgets. You can include other widgets in this list as well. The NavigationDrawer can scroll when needed. To override the default appearance of the NavigationDrawers widget, use the NavigationDrawerTheme widget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*OqY6QYHrUptwmyle.gif" /></figure><h3>SearchBar and SearchAnchor</h3><p>These components provide predictive text for search queries. When the user enters a search query, the app computes a list of matching responses in a “search view”. The user either selects one or adjusts the query. To override the <a href="https://m3.material.io/components/search/overview">M3</a> design of these components, use the SearchBarTheme and SearchAnchorTheme widgets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*6teD0lH1l70y2SHB.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*siPoG30Uc3dtzuBp.gif" /></figure><h3>Secondary Tab Bar</h3><p>M3 allows you to create a second tier of tabbed content. To distinguish this second TabBar, use <a href="https://m3.material.io/components/tabs/overview#34192702-8a18-4da7-b2cf-d1579632cb96">TabBar.secondary</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*XRTy-AlsvOkZXGw_.gif" /></figure><h3>DatePicker updated for <a href="https://m3.material.io/components/date-pickers/overview">M3</a></h3><p>The M3 DatePicker updates the colors, layout, and shape for both the calendar and textfield versions of the widget. This doesn’t change the API, but adds a new DatePickerTheme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/0*ozdDfWrc4HodZn0_.gif" /></figure><h3>TimePicker updated for <a href="https://m3.material.io/components/time-pickers/overview">M3</a></h3><p>The M3 TimePicker, like the DatePicker, updates the colors, layout, and shapes for both the regular and compact versions of the widget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/0*GjzfQZz1O-EBe3ZI.gif" /></figure><h3>BottomSheet updated for <a href="https://m3.material.io/components/bottom-sheets/overview">M3</a></h3><p>Beyond M3 color and shape updates, the bottom sheet now adds an optional drag handle that’s included when you set showDragHandle to true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*w34hFwXjTcd7OT3L.gif" /></figure><h3>ListTile updated for <a href="https://m3.material.io/components/lists/overview">M3</a></h3><p>The M3 ListTile updates positioning and spacing of this widget. This includes content padding, leading and trailing widget alignment, minimum leading width, and vertical spacing. The API remains unchanged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*qAkUcGJkSfDs5fW2.gif" /></figure><h3>Drawer updated for M3</h3><p>The M3 Drawer updates the colors and elevation while making some small layout changes.</p><h3>TextField Updates</h3><p>M3 updates all TextField widgets to support native gestures. Double clicking or triple clicking with a mouse work the same as double tapping or triple tapping on a touch device. By default, the TextField and CupertinoTextField widgets use these features.</p><h3>TextField double click/tap gestures</h3><ul><li><strong>Double click + drag:</strong> Extends the selection in word blocks.</li><li><strong>Double tap + drag:</strong> Extends the selection in word blocks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*WjUy9bwA5b5sTDWn.gif" /></figure><h3>TextField triple click/tap gestures</h3><h3>Triple click</h3><ul><li>Selects a paragraph block at the clicked position when inside of a multi-line TextField (Android/Fuchsia/iOS/macOS/Windows).</li><li>Selects a line block at the clicked position when inside of a multi-line TextField (Linux).</li><li>Selects all text in a single-line TextField.</li></ul><h3>Triple tap</h3><ul><li>Selects a paragraph block at the clicked position when inside of a multi-line TextField.</li><li>Selects all text in a single-line TextField.</li></ul><h3>Triple click + drag</h3><ul><li>Extends the selection in paragraph blocks (Android/Fuchsia/iOS/macOS/Windows).</li><li>Extends the selection in line blocks (Linux).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*MK8wKLqAkTbu_Bsi.gif" /></figure><h3>Flutter supports SLSA level 1</h3><p>Flutter Framework now compiles with Supply Chain Levels for Software Artifacts (<a href="https://slsa.dev/">SLSA</a>) Level 1. This acknowledges the implementation of many security features including:</p><ul><li><strong>Scripted build process</strong>. The build scripts for Flutter now allow automated builds on trusted build platforms. Building on protected architecture helps prevent artifact tampering which improves supply chain security.</li><li><strong>Multi-party approval with audit logging</strong>. Flutter release workflows execute only after multiple engineers approve. All executions create auditable log records. These changes ensure that no one can introduce changes between source code and artifact generation.</li><li><strong>Provenance</strong>. Beta and stable releases now build with <a href="https://slsa.dev/provenance/v0.1">provenance</a>. This means trusted sources with expected contents built the framework release artifacts. Each release publishes links to view and verify provenance on the <a href="https://docs.flutter.dev/release/archive">SDK archive</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*3UsG7ugkNrd1HGF9.png" /></figure><p>This work also allows the team to advance toward SLSA L2 and L3 compliance. These two levels focus on protecting artifacts during and after the build process.</p><h3>Web</h3><h3>Flutter web apps improved load times</h3><p>This release reduces the file size of icon fonts. It pruned unused glyphs from both Material and Cupertino.</p><h3>CanvasKit reduced size for all browsers</h3><p>Chromium-based browsers can use an even smaller custom CanvasKit “flavor”. The hosted CanvasKit serves from Google’s industry-leading CDN. This should improve performance further.</p><h3>Element embedding</h3><p>You can now <a href="https://docs.flutter.dev/deployment/web#embedding-a-flutter-app-into-an-html-page">serve Flutter web apps from a specific element in a page</a>. Before this release, your apps could either fill the entire page body or display within an iframe tag. <a href="https://github.com/flutter/samples/tree/main/web_embedding">Sample code</a> can be found in GitHub.</p><h3>Shader support</h3><p>Web apps can use Flutter’s <a href="https://docs.flutter.dev/development/ui/advanced/shaders">fragment shader support</a>.</p><h3>Engine</h3><h3>Impeller</h3><p>In the 3.7 stable release, we previewed <a href="https://docs.flutter.dev/perf/impeller">Impeller</a> on iOS. Since then, we received and addressed a lot of great feedback from users. With over 250 commits to Impeller in this release, we set Impeller as our default renderer on iOS. By default, all apps built for iOS with Flutter 3.10 use Impeller. These iOS apps will have less jank and better consistent performance.</p><p>Since the 3.7 release, Impeller on iOS has improved its memory footprint. Impeller uses fewer render passes and intermediate render targets. On newer iPhones, enabling lossy texture compression reduced memory footprint without affecting fidelity. These advances also made a marked improvement in performance on iPads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/236/0*BnrAoMe-m_4doBLj.png" /></figure><p>Consider a complex screen like the “pull quote” screen in the <a href="https://flutter.gskinner.com/wonderous/">Wonderous</a> app. Together, these improvements cut the memory footprint of those screens almost in half. The reduction in memory usage also gives a modest drop in GPU and CPU load. The Wondrous app may not register that drop in load. Its frames had rendered under budget before, but this change should extend battery life.</p><p>Impeller also unlocks the team’s ability to deliver popular feature requests faster. One example results in support for the wider P3 color gamut on iOS. Look elsewhere in this post for a description of that feature.</p><p>Community contributions accelerated our progress, in particular GitHub users <a href="https://github.com/ColdPaleLight">ColdPaleLight</a> and <a href="https://github.com/luckysmg">luckysmg</a>. They authored several Impeller-related patches that improved fidelity and performance.</p><p>While Impeller meets the rendering needs of most Flutter apps, you can opt-out of Impeller. If you choose to opt-out, consider <a href="https://github.com/flutter/flutter/issues/new/choose">filing an issue on GitHub</a> to tell us why. App users may notice that Skia and Impeller render with minor differences. These differences could be bugs, so don’t hesitate to file issues. In a future release, we will remove the legacy Skia renderer for iOS to reduce Flutter’s size.</p><p>Progress continues on a Vulkan backend for Impeller. Impeller on Android remains under active development but not ready for preview. We plan to share more about it in the near future.</p><p>To follow along with our progress, check out <a href="https://github.com/orgs/flutter/projects/21">our GitHub project board</a>.</p><h3>Performance</h3><p>This release covers more performance improvements and fixes aside from Impeller.</p><h3>Eliminating Jank</h3><p>We want to thank open-source contributor <a href="https://github.com/luckysmg">luckysmg</a>. They discovered they could slash the time to get the next drawable layer from the Metal driver. To get that bonus, you need to set the FlutterViews background color to a non-nil value. This change eliminates low frame rates on recent iOS 120Hz displays. In some cases, it <em>triples</em> the frame rate. This helped us close over half a dozen GitHub issues. This change held such significance that we backported a hotfix into the 3.7 release.</p><p>In the 3.7 stable release, we shifted loading of local images from the platform thread to the Dart thread to avoid delaying vsync events from the platform thread. However, <a href="https://github.com/flutter/flutter/issues/121525">users</a> <a href="https://github.com/flutter/flutter/issues/121351">noticed</a> that this additional work on the Dart thread also caused some jank. In this release, we moved the opening and decoding of local images from the Dart thread to a <a href="https://github.com/flutter/engine/pull/39918">background thread</a>. This change eliminates potential long pauses on screens with a lot of local images, while avoiding delaying vsync events. In our local testing and automated benchmarks, this change cut the load time for several simultaneous images in half.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/0*QiMBCj1n5Hqkjdlq.png" /></figure><p>We continue to build optimizations on top of Flutter’s new internal DisplayList structure. In this release, we added an <a href="https://github.com/flutter/engine/pull/38429">R-Tree based culling</a> mechanism. This mechanism removes the processing of drawing operations much earlier in our renderer. This optimization accelerates, <a href="https://github.com/flutter/flutter/issues/92366">for example</a>, a custom painter whose output fails offscreen. Our <a href="https://flutter-engine-perf.skia.org/e/?begin=1671661938&amp;end=1671754421&amp;keys=X789f7ff76f30f8ccc672464f335fe09b&amp;num_commits=50&amp;request_type=1&amp;xbaroffset=31974">microbenchmarks</a> showed a decreased DisplayList processing time of up to 50%. Apps with clipped custom paints could see differing improvements. The degree of improvement depends on the complexity and number of hidden draw operations.</p><h3>Reducing iOS startup latency</h3><p>An <a href="https://github.com/flutter/flutter/issues/37826">inefficient strategy</a> for identifier lookups in app bundles increased app startup latency. This startup latency grows in proportion to the app’s size. In this release, <a href="https://github.com/flutter/engine/pull/39975">we fixed the bundle identifier lookup</a>. This reduced startup latency by 100ms or about 30–50% in a large production application.</p><h3>Reducing Size</h3><p>Flutter uses SkParagraph as the default library for text shaping, layout, and rendering. We included a flag to fall back on the legacy libtxt and minikin libraries. As we have full confidence in SkParagraph, <a href="https://github.com/flutter/engine/pull/39499">we removed</a> libtxt and minikin and their flag in this release. This reduces Flutter’s compressed size by 30KB.</p><h3>Stability</h3><p>In the 3.0 release, we enabled an Android feature late in our rendering pipeline. This Android feature used advanced GPU driver features. These driver features repaint less of the screen when only one “dirty” region changes. We added this to earlier optimizations to our graphics pipeline with similar effects. Though our benchmarks results encouraged us, two issues surfaced. First, the most improved benchmark might not represent practical use cases. Second, the set of devices and Android versions that supported this GPU driver feature proved <a href="https://github.com/flutter/engine/pull/37493">hard to find</a>. Given the limited advances and support, we <a href="https://github.com/flutter/engine/pull/40898">disabled</a> the partial repaint feature on Android.</p><p>The feature remains enabled on iOS when using the Skia backend. We expect to <a href="https://github.com/flutter/flutter/issues/124526">enable it with Impeller</a> in a future release.</p><h3>API Improvements</h3><h3>APNG Decoder</h3><p>Flutter 3.10 addresses one of our most <a href="https://github.com/flutter/flutter/issues/37247">promoted issues</a>. It <a href="https://github.com/flutter/engine/pull/31098">adds the ability</a> to decode APNG images. You can load APNG images with Flutter’s existing image loading APIs.</p><h3>Image loading API improvements</h3><p>Flutter’s esteemed Director of Engineering <a href="https://github.com/tvolkert">tvolkert</a> has landed improvements to dart:ui’s image loading APIs. We have added a <a href="https://master-api.flutter.dev/flutter/dart-ui/instantiateImageCodecWithSize.html">new method</a> instantiateImageCodecWithSize. This supports the <a href="https://github.com/flutter/flutter/issues/118543">use case</a> of loading an image that meets these three conditions:</p><ul><li>an aspect ratio unknown at load time</li><li>a bounding box constraint</li><li>an original aspect ratio constraint</li></ul><p>An example would be when an app tries to display one image from a pool of possibilities loaded from the network.</p><h3>Mobile</h3><h3>iOS</h3><h3>Wireless debugging</h3><p>You can now run and hot reload your Flutter iOS apps without a cable! After a successful wireless pairing of your iOS device in Xcode, you can deploy your app to that device using flutter run. If you encounter issues, verify the network icon appears next to your device under <strong>Window &gt; Devices</strong> and <strong>Simulators &gt; Devices</strong>. To learn more, check out our <a href="https://docs.flutter.dev/get-started/install/macos#ios-setup">documentation</a>.</p><h3>Wide gamut image support</h3><p>Flutter apps on iOS can now support accurate rendering for wide gamut images. To use wide gamut support, the app must use Impeller and add the <a href="https://github.com/flutter/flutter/blob/a463bb82c413af319c8b715deedd7f2c345becd6/dev/integration_tests/wide_gamut_test/ios/Runner/Info.plist#L52">FLTEnableWideGamut</a> flag in the Info.plist file.</p><h3>Spellcheck support</h3><p>The SpellCheckConfiguration() widget now defaults to supporting <a href="https://developer.apple.com/documentation/uikit/uitextchecker">Apple’s spell check service</a> on iOS. To use this widget, set it using the spellCheckConfiguration parameter in CupertinoTextField.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/0*BhzFw0s3V78HQWmQ.gif" /></figure><h3>Adaptive checkbox and radio</h3><p>This release adds the CupertinoCheckBox and CupertinoRadio widgets to the Cupertino library. They create checkbox and radio button components that match Apple’s styling.</p><p>The Material checkbox and radio widgets added the .adaptive constructors. On iOS and macOS, these constructors use the corresponding Cupertino widgets. On other platforms, they use Material widgets.</p><h3>Refining Cupertino animations, transitions and colors</h3><p>Flutter 3.10 improved some animations, transitions, and colors to match SwiftUI. These improvements include:</p><ul><li><a href="https://github.com/flutter/flutter/pull/122275">Updating</a> the CupertinoPageRoute transition</li><li><a href="https://github.com/flutter/flutter/pull/110127">Adding</a> a title magnification animation to CupertinoSliverNavigationBar</li><li>Adding several <a href="https://github.com/flutter/flutter/pull/118971">new iOS system colors</a> to CupertinoColors</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/248/0*qlp4RTxjt7aRUkKR.gif" /></figure><h3>PlatformView performance</h3><p>When PlatformViews appear on screen, Flutter <a href="https://github.com/flutter/engine/pull/39172">throttles the refresh rate</a> on iOS to reduce jank. App users will notice this when the app displays animated or scrollable PlatformViews.</p><h3>macOS and iOS can use shared code in plugins</h3><p>Flutter now supports the <a href="https://docs.flutter.dev/development/packages-and-plugins/developing-packages#shared-ios-and-macos-implementations">sharedDarwinSource</a> key in the pubspec.yaml file for plugins. This key indicates that Flutter should share iOS and macOS code.</p><pre>ios:<br>  pluginClass: PathProviderPlugin<br>  dartPluginClass: PathProviderFoundation<br>  sharedDarwinSource: true<br>macos:<br>  pluginClass: PathProviderPlugin<br>  dartPluginClass: PathProviderFoundation<br>  sharedDarwinSource: true</pre><h3>New resources for app extensions</h3><p>We added <a href="https://docs.flutter.dev/development/platform-integration/ios/app-extensions">documentation</a> for Flutter developers to use iOS app extensions. These extensions include live activities, home screen widgets, and share extensions.</p><p>To simplify creating home screen widgets and sharing data, we added new methods to the <a href="https://github.com/flutter/packages/pull/3450">path_provider</a> and homescreen_widget plugins.</p><h3>New resources for cross-platform design</h3><p>The documentation now includes cross platform design considerations for specific <a href="https://docs.flutter.dev/resources/platform-adaptations#ui-components">UI components</a>. To learn more about each of these UI components, check out the <a href="https://github.com/flutter/uxr/discussions">discussions in the Flutter UX GitHub repository</a>. We appreciate any input or feedback!</p><h3>Android</h3><h3>Android CameraX support</h3><p><a href="https://developer.android.com/training/camerax">Camera X</a>, a Jetpack library, simplifies adding rich camera functionality to your Android app. This functionality applies across a wide selection of Android Camera hardware. With this release, we add preliminary support for CameraX to the Flutter Camera plugin. This support covers the following use cases:</p><ul><li>Image Capture</li><li>Video Recording</li><li>Display live camera preview</li></ul><p>To give it a try, opt in to using the CameraX implementation. To opt in, add the following line to your pubspec.yaml file.</p><pre>Dependencies:<br>  camera: ^0.10.4 # Latest camera version<br>  camera_android_camerax: ^0.5.0</pre><p>We would love your feedback as we continue to add more CameraX features then make CameraX the default implementation.</p><h3>DevTools</h3><p>We continue to improve DevTools, the suite of performance and debugging tools for Dart and Flutter. Some highlights include:</p><ul><li>The DevTools UI uses Material 3. This both modernizes the look and enhances accessibility.</li><li>The DevTools console supports evaluations for a running app in debug mode. Before this release, you could only do this when you paused an app.</li><li>An embedded <a href="https://perfetto.dev/">Perfetto trace viewer</a> replaces the previous timeline trace viewer. Perfetto handles larger datasets and performs better than the legacy trace viewer. Perfetto includes more features, such as:<br>- Allowing you to pin threads of interest.<br>- Clicking and dragging to select multiple timeline events from multiple frames.<br>- Using SQL queries to pull specific data from the timeline events.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*Rbfyq80kKNZZXVMa.png" /></figure><p>To learn more, check out the release notes for <a href="https://docs.flutter.dev/development/tools/devtools/release-notes/release-notes-2.23.1">DevTools 2.23.1</a>, <a href="https://docs.flutter.dev/development/tools/devtools/release-notes/release-notes-2.22.2">DevTools 2.22.2</a>, and <a href="https://docs.flutter.dev/development/tools/devtools/release-notes/release-notes-2.21.1">DevTools 2.21.1</a>.</p><h3>Deprecations &amp; Breaking Changes</h3><h3>Deprecated APIs</h3><p>Breaking changes in this release include deprecated APIs that expired after the release of v3.7. To see all affected APIs, along with additional context and migration guidance, check out <a href="https://docs.flutter.dev/release/breaking-changes/3-7-deprecations">the deprecation guide for this release</a>. <a href="https://docs.flutter.dev/development/tools/flutter-fix">Dart Fix</a> can remedy many of these issues, including quick fixes in the IDE and bulk apply with the dart fix command.</p><h3>Android Studio Flamingo upgrade</h3><p>After you upgrade Android Studio to Flamingo, you might see an error when you try to flutter run or flutter build your Flutter Android apps. This error occurs because Android Studio Flamingo updates its bundled Java SDK from 11 to 17. Gradle versions <a href="https://docs.gradle.org/current/userguide/compatibility.html#java">earlier than 7.3</a> can’t run when using Java 17. We <a href="https://github.com/flutter/flutter/pull/123916">updated</a> flutter analyze --suggestions to validate if this error occurs due to incompatibility between your Java SDK and your Gradle version.</p><p>To learn different ways to fix this error, check out <a href="https://docs.flutter.dev/go/android-java-gradle-error">our migration guide</a>.</p><h3>Window singleton deprecation</h3><p>This release deprecates the window singleton. Apps and libraries relying on it should <a href="https://docs.flutter.dev/release/breaking-changes/window-singleton">migrate</a> away from it. This prepares your app for multi-window support when it launches in a future version of Flutter.</p><h3>Thanks to the community</h3><p>As always, many thanks to the community for <a href="https://github.com/flutter/tests/blob/master/README.md">contributing tests</a>, they help us identify these breaking changes. To learn more, check out <a href="https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes">our breaking change policy</a>.</p><h3>Wrapping it up</h3><p>As we wrap up this release, the Flutter team at Google wants to thank all the contributors who have made this release possible. Your dedication and hard work have helped to make Flutter a game-changer in the industry and continue to revolutionize application development. We encourage you to start exploring this latest stable version of Flutter to take advantage of all the amazing features it has to offer. To do so, just flutter upgrade! Stay tuned for more exciting updates from Flutter in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c54124eee63b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Figma vs Adobe XD: An In-Depth Comparison for UX/UI Designers]]></title>
            <link>https://nyonggodwill11.medium.com/figma-vs-adobe-xd-an-in-depth-comparison-for-ux-ui-designers-40f2d7554b7d?source=rss-6898a45287ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/40f2d7554b7d</guid>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nyonggodwill]]></dc:creator>
            <pubDate>Wed, 10 Aug 2022 22:48:34 GMT</pubDate>
            <atom:updated>2022-08-10T22:48:34.854Z</atom:updated>
            <content:encoded><![CDATA[<p>The great showdown: which tool is better for your UX/UI design needs?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ph42h3Gu74k0fvG1.jpg" /></figure><p>Introduction:</p><p>Figma and Adobe XD are two of the biggest names in UX design, and every search for the ideal interface design app will likely bring you to one or both of these tools.</p><p>In this article, we’re comparing Figma and Adobe XD in depth, so that you can make an informed decision about which tool is best for you. We’ll cover all the essential features that affect design, responsive auto layouts, components and design systems, as well as prototyping and developer handoff.</p><p>In a Figma vs. Adobe XD showdown, who comes out ahead?</p><p>Let’s take a look.</p><h3>What is Figma?</h3><p>Figma is a vector interface design and prototyping tool that is primarily browser-based, with a desktop app available for macOS and Windows. In recent years, Figma has quickly become one of the most popular UX design tools, thanks to its intuitive interface, comprehensive feature set, and rich collaboration features.</p><p>With a robust free tier that’s perfect for individuals and small teams, Figma is an easy choice for UX/UI designers who are looking for a tool that is easily adaptable to their design flow.</p><p><em>You can read our in-depth </em><a href="https://designlab.com/blog/ux-designer-guide-to-figma/"><em>Figma review here</em></a><em>.</em></p><h3>What is Adobe XD?</h3><p>Adobe XD is a vector-based design tool that’s mainly used for designing user interfaces (UI) for mobile and web applications. While the team at Adobe has been rapidly deploying new features for this tool, it remains fairly lightweight when compared with other Adobe products like Photoshop or Illustrator. For interface designers interested in rapid design and prototyping iterations, lightweight isn’t a bad thing.</p><p>In its early years, Adobe XD offered a free version as well. However, that is being phased out in favor of a 7-day free trial, followed by a paid subscription.</p><p><em>You can read our in-depth </em><a href="https://designlab.com/blog/ux-designer-guide-to-adobe-xd/"><em>Adobe XD review here</em></a><em>.</em></p><h3>Figma vs Adobe XD: Features Comparison</h3><p>At a first glance, the Figma vs Adobe XD showdown seems fairly similar. So let’s dive into some of the specific features, and how the subtle (or not-so-subtle) differences might help you decide which UX/UI design tool will best suit your design needs.</p><h3>Supported Platforms</h3><p>One of the most obvious differences between Figma and Adobe XD is that Figma is primarily a web-based program, while Adobe XD is designed to work locally as a desktop app.</p><p>This means that Figma can be used on any platform (Windows, macOS, and Linux), as long as you’re connected to the internet. You can design in the browser itself, or download a desktop app. Keep in mind that, while you can use the desktop app offline, you’ll want to make sure you’re connected to the internet for full access to all of Figma’s features.</p><p>Adobe XD, on the other hand, was created primarily as a desktop app that is currently available for Windows and macOS users. However, all of the collaboration features are reliant on an online connection that will let you save your files to Creative Cloud. If you do want to change a local file to the Cloud (or vice versa), you’ll have to create a “Save as” version of the file in the new location. While this is a minor step, it does require a quick check to make sure that the old file is deleted, to avoid confusion further on about which file is the most up to date.</p><p><strong>Winner:</strong></p><p>Tie. Both tools offer desktop apps, and require you to be online to take advantage of the full feature set.</p><h3>Interface</h3><p>Log into either tool and you’ll be pleasantly surprised at how similar the interfaces are, with minimal toolbars along the left and top, and a more detailed panel on the right that changes based on what you’re currently working on. If you’re currently using text, for example, the right hand panel will give you your font, color, spacing, and other options. But as soon as you switch it to the pen or shape tool, the options will change to correspond with that particular tool.</p><p>In Figma, you’ll spend the majority of your time working from the top toolbar, with the left sidebar reserved for organizing layers and reusable assets, called <strong>components</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NZs74aT_HFXgOKln.jpg" /></figure><p>A mockup of the Figma interface layout</p><p>In Adobe XD, all your design tools are found in the left sidebar, whether you’re looking for document assets, UI kits, or are simply creating your work from scratch with shapes and the pen tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rwu8H9NbTQ9rF4b3.jpg" /></figure><p>A mockup of the Adobe XD app interface</p><p><strong>Winner:</strong></p><p>If you tend to do a lot of back-and-forth work with your layers (or are working with complex designs), you might enjoy the way you can keep them front and center with Figma.</p><p>However, Adobe XD’s concept of keeping all design tools in one place makes the interface slightly more intuitive and easy to use.</p><h3>Design and Layout Tools</h3><p>Both Figma and Adobe XD offer a wide range of design tools, including vector drawing with a pen tool, shape tools, text, and various color and effects options.</p><p>This is where Figma really stands out, with vector drawing options that are extremely flexible and remain fully customizable.</p><p>Let’s take a cube, for example:</p><p>In Figma, you can simply use the pen tool to draw the lines of a cube to create a compound vector shape that can be customized as needed.</p><p>In Adobe XD, you’ll still use the pen tool to create the cube, but with a caveat: each vector point can only be connected once. To create a moveable shape, you’ll either move the lines into a group, or perform a complex Boolean operation to merge the lines into a single element.</p><p><strong>Winner:</strong></p><p>Figma is the clear winner in this category, with more flexible vector design tools that can create complex shapes and elements without requiring Boolean operations.</p><h3>Responsive Design</h3><p>Adobe XD and Figma both support a design process that encompasses desktop and mobile app design — and, more importantly: responsive interfaces.</p><p>When using Figma, you’ll find the <strong>Auto layout</strong> tool invaluable. Auto layout is a property that you can apply to elements, frames, and components that will designate how they grow, shrink, or otherwise behave as their contents change.</p><p>For example, you can use Auto layout to design versatile buttons that will expand or decrease automatically based on how much text you add to the label. You can also combine various frames to create full interface designs that illustrate exactly how the elements should behave, based on screen size.</p><p>Auto layout gives you control over vertical and horizontal padding, padding between items, as well as independent padding control (so you can have more padding on the left and top, for example, and less on the right and bottom). It also lets you decide whether you want strokes included in the layout (versus sitting outside them), and the stacking order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f_OYaBPsByUHYtLy.jpg" /></figure><p>A screenshot of the Figma Auto layout settings for responsive design</p><p>Adobe XD’s equivalent is called <strong>Responsive Resize</strong>, which is automatically applied to each component that you create in your design project.</p><p>While the auto settings can be adequate for simple designs, you might find yourself gravitating towards the manual options to designate where you want an item to be anchored (left, top, right, bottom, or a mix of two) as well as if it should have a fixed height or width.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k5BEqSsjUHCz6wxS.jpg" /></figure><p>A screenshot of the Responsive Resize settings in Adobe XD</p><p><strong>Winner:</strong></p><p>Figma is the clear winner in this category, with its Auto layout feature that allows designers to create responsive interfaces that can shrink or scale following a set of rules.</p><h3>Creating and Managing Design Systems</h3><p>Whether you’re working on a single client project as a UX design freelancer, or are a part of an in-house design team, having a design system that’s fully integrated in your workspace can save time and energy.</p><p>At a basic level, design systems include a color palette and font styles, but for UX/UI designers, they also include UI elements like cards, buttons, and other styles that can be reused within your project.</p><p>You can create design systems that are local to each of your Figma files by global styles for colors, fonts, and other attributes which can be easily applied to different components. Or, you can go a step further when part of a Team in Figma. Within each team, you can create a dedicated design system file, which houses all of your global styles. These styles can then be pulled into the different design files for that team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GpN4rys4da8tyO83.jpg" /></figure><p>A screenshot of a Figma design system file with Color Styles</p><p>With Adobe XD, you have the same options to create color palettes, font styles, and components. However, if you’d like to share your design system with a team at large, you’ll want to publish the assets as a Creative Cloud <strong>Library</strong>.</p><p>Here, the Adobe ecosystem really pulls its weight, since you can utilize Creative Cloud libraries saved from other programs like Photoshop, which makes it much easier to ensure that all your design files are always pulling the latest design elements.</p><p><em>Learn more about how you can uplevel your design systems in Adobe XD in this webinar…</em></p><p><strong>Winner:</strong></p><p>Adobe XD. While Figma’s components and design system are perfectly usable, they remain limited to the Figma app. Adobe XD opens up new collaboration and organization possibilities between your various design programs, all centralized in Creative Cloud.</p><h3>Collaboration and Sharing</h3><p>As a web based design app, Figma is built with team collaboration front and center. Each project serves as its own hub, with an at-a-glance look at who has access to the project and when a file was last updated.</p><p>Once inside the file, you can design in real time with your teammates, follow someone’s cursor, and leave comments/threaded replies within the file. Worried about version control? You can utilize the file history to see who changed what, and to revert back to an earlier version, if necessary.</p><p>Adobe XD offers collaboration features when you save your design file in the Cloud. We’ve already mentioned the ease of using Libraries, but you can also coedit in real time with anyone who you’ve invited to the design file. If you’re looking primarily for comments and feedback, you can use the share option to create a link that can be viewed in a browser. Comments can then be edited, resolved, or simply deleted.</p><p>The share links are where Adobe XD truly stands out, since you can create multiple share links depending on whether you need the viewer to review and leave comments, review the design specs, or simply watch in presentation mode.</p><p><strong>Winner:</strong></p><p>Tie. Figma’s real time collaboration features stand out for teams who don’t want to have to re-invite each designer individually for every file and are looking for a streamlined experience of being able to see the design specs within the file itself. However, Adobe XD’s customizable share links are incredibly helpful for delivering the correct view to each stakeholder or team member, without accidentally giving them too much (or too little) access.</p><h3>Developer Handoff</h3><p>Both Figma and Adobe XD include design specs for CSS, iOS, and Android.</p><p>With Figma, the developer(s) can hop straight inside the design file to inspect individual elements, layers, components, and the interactions that are set up in prototyping mode. Any auto layout settings will also appear in the developer’s inspect panel.</p><p>With Adobe XD, the code is not visible within the app interface. Instead, you’ll want to go to <strong>Share &gt; Development</strong>, and select the <strong>Export for Web</strong> to generate the CSS code. This will generate a shareable link that you can then access in the browser and inspect each component to uncover the CSS code.</p><p><strong>Winner:</strong></p><p>Figma. The handoff specs are much more robust and easier to use within the design file as a whole, making it easier for developers to gain a more holistic understanding of how your design is intended to function.</p><h3>Pricing</h3><p>Figma offers a free plan for individuals and small teams, with a Professional plan that starts at $12/editor per month.</p><p>Adobe XD offers a free 7-day trial, paid plans starting at $9.99 per month for the standalone app subscription.</p><p><strong>Winner:</strong></p><p>Tie. While Figma’s free version stands out, their paid plans start at a higher cost per month than Adobe XD.</p><h3>Takeaway: Should You Use Figma or Adobe XD?</h3><p>Figma and Adobe XD are both incredible user experience design tools, which offer a full suite of features that take you from the initial wireframe through design prototyping and hand off to developers.</p><p>You might gravitate towards Figma if …</p><ul><li>You often want to collaborate within a design file</li><li>You prefer a browser based design tool</li><li>You want to offer quick access to prototypes for review or testing purposes</li><li>You are looking for more flexibility in your vector design graphics</li></ul><p>You might gravitate towards Adobe XD if…</p><ul><li>You want to stay within the Creative Cloud ecosystem</li><li>You prefer a desktop app to a web based program</li><li>You don’t mind paying a per month (or per year) subscription</li></ul><p><em>I hope this article has helped you make a decision about which option is best for you. Still undecided? Check out our free courses to get a firsthand experience of what each app feels like as a user:</em></p><p><a href="https://designlab.com/figma-101-course/"><em>Figma 101: a 7-day email course</em></a></p><p><a href="https://designlab.com/adobe-xd-101-course/"><em>Adobe XD 101: a 7-day email course</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40f2d7554b7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>