<?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 Olawale Ajepe on Medium]]></title>
        <description><![CDATA[Stories by Olawale Ajepe on Medium]]></description>
        <link>https://medium.com/@praiseajepe?source=rss-a00285615ae3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oXrAqKQ82SBsZmRyQ00kXA.jpeg</url>
            <title>Stories by Olawale Ajepe on Medium</title>
            <link>https://medium.com/@praiseajepe?source=rss-a00285615ae3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:22:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@praiseajepe/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[Clean Code Fails if Business Flow Fails]]></title>
            <link>https://medium.com/@praiseajepe/clean-code-fails-if-business-flow-fails-bebe1660464f?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bebe1660464f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 18:47:46 GMT</pubDate>
            <atom:updated>2026-03-16T18:47:46.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W3yEad563VUMAmvOFvjAWA.png" /></figure><p><strong>How strictly should we follow clean code when business requirements demand flexibility?</strong></p><p>Writing clean code and following established architectural patterns is essential, it ensures readability, scalability, and maintainability. But what happens when business logic or user flow demands changes that don’t fit neatly into your preferred architecture?</p><p>I faced this dilemma on a recent project. My codebase was well-structured according to the initial product requirements. I typically follow <strong>BLoC</strong> with a touch of <strong>Feature-Driven Development (FDD), </strong>a combination that works beautifully for predictable, scalable apps.</p><p>Then came the challenge: mid-project, I was asked to implement changes that felt almost impossible within the current architecture. My first reaction? Pause. Doubt. And even decline the ticket. I thought, <em>“Why would anyone design a flow like this?”</em></p><p>But after a meeting with the business development team, everything clicked. They explained what customers truly wanted. In that moment, I realized:</p><blockquote><em>“The purpose of building a product is not to showcase my technical prowess in clean architecture; it’s to deliver the experience that end users need.”</em></blockquote><p>If I had rigidly stuck to my architectural standards, I would have felt technically proud, but the end users would have had a frustrating experience.</p><p>The key lesson here: <strong>flexibility within clean code is essential</strong>. Adapting to business needs doesn’t mean writing sloppy code. Even when stepping outside strict architectural patterns, your code should always be:</p><ul><li><strong>Readable</strong></li><li><strong>Scalable</strong></li><li><strong>Maintainable</strong></li><li><strong>Well-separated in concerns</strong></li></ul><p>Architecture is a guideline, not a cage. Delivering real value sometimes means bending the rules without breaking the code.</p><p>Have you ever faced a situation where business flow demanded bending clean code rules? How did you handle it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bebe1660464f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI Is Quietly Ending Developers Interpersonal Relationship]]></title>
            <link>https://medium.com/@praiseajepe/how-ai-is-quietly-ending-developers-interpersonal-relationship-f7c67df79f14?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7c67df79f14</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[humanity]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Wed, 26 Nov 2025 12:38:08 GMT</pubDate>
            <atom:updated>2025-11-26T12:38:08.328Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Looming Era of Solo Software Developers with AI Usage is here!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d1aGcWWIAWfekBFDZ6SSvg.jpeg" /><figcaption>Image by Innova Labs from Pixabay</figcaption></figure><p>I recall working in a co-working space that was filled with various startups back in 2021. At the time, I was a Mobile Application Developer building a product for SMEs. I spent long hours studying documentation and reading articles to complete my work.</p><p>Then came a moment when I needed to make an important architectural decision, a decision that would shape the long-term stability and management of the project. Luckily, I had access to three other developers who were familiar with my tech stack from other startups. I walked up to them and discussed my challenges. They offered valuable insights that reshaped my approach. Beyond the technical help, I also got to know them personally and how they approached difficult engineering problems.</p><p>That was the era before AI-assisted coding. We didn’t just exchange solutions, we built connections.</p><p>Fast-forward to today, where AI tools have become dominant in software development. Developers now turn to AI assistants for advice, debugging, and architectural guidance.</p><p>Everyone suddenly appears to be an expert, relying on AI like a secondary brain. The new skill is no longer collaboration, but learning how to craft the right prompt to get the right answer.</p><p>This shift is quietly diminishing interpersonal relationships among developers.</p><p>Yes, AI makes information and solutions more accessible than ever, but at what cost? Every benefit comes with a trade-off.</p><p>We shouldn’t ignore the subtle danger: AI is gradually eating away developers’ natural problem-solving and algorithmic reasoning skills, just like a weevil slowly consuming grain.</p><p>What began as machine learning where humans trained models to make machines intelligent now feels reversed. Humans are increasingly being “trained” by machines, trading deep reasoning for fast answers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7c67df79f14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using AI; Will Anyone Still Be Able to Reason in the Next 20 Years?]]></title>
            <link>https://medium.com/@praiseajepe/will-anyone-still-be-able-to-reason-in-the-next-20-years-9d990dbeba38?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d990dbeba38</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 12:04:20 GMT</pubDate>
            <atom:updated>2025-11-22T20:17:39.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cwFSsqXR-CRRc7jR0MeTA.jpeg" /></figure><p>A few days ago, I came across a post from a fellow software developer. He mentioned his desire to subscribe to a ChatGPT package and made a statement that really struck me: “𝐈 𝐧𝐞𝐞𝐝 𝐭𝐡𝐢𝐬 𝐭𝐨 𝐚𝐢𝐝 𝐚𝐝𝐯𝐚𝐧𝐜𝐞𝐝 𝐫𝐞𝐚𝐬𝐨𝐧𝐢𝐧𝐠 𝐢𝐧 𝐦𝐲 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐩𝐫𝐨𝐜𝐞𝐬𝐬.”</p><p>As a Mobile Application Developer myself, I also use ChatGPT, it has become the go-to platform for answers, gradually replacing <a href="https://www.linkedin.com/company/stack-overflow/">Stack Overflow</a> as the “old-school” way of solving problems or fixing bugs. <br>I’ve seen how useful even the free version of ChatGPT can be if you already have a strong foundation in your skills.</p><p>But this made me stop and reflect: 𝐰𝐡𝐲 𝐝𝐨 𝐰𝐞 𝐧𝐨𝐰 𝐟𝐞𝐞𝐥 𝐭𝐡𝐞 𝐧𝐞𝐞𝐝 𝐭𝐨 𝐨𝐮𝐭𝐬𝐨𝐮𝐫𝐜𝐞 “𝐚𝐝𝐯𝐚𝐧𝐜𝐞𝐝 𝐫𝐞𝐚𝐬𝐨𝐧𝐢𝐧𝐠” 𝐭𝐨 𝐀𝐈? Now, we even subject our own reasoning to AI for validation, we tend to lacking confidence in our reasoning.</p><p>I had the privilege of starting my programming journey before ChatGPT existed or any AI assisted platform become well known. Products were built successfully with well crafted logic, and problem-solving was an exercise in sharpening the mind.</p><p>Today, however, a shift is being observed, people are beginning to depend on AI not just for answers, but for the very process of reasoning itself.<br>A recent trend is what is called “vibe coding” where developers describe what they want in simple language (prompts), and AI generates functional code. This signals a drastic shift in how intelligence is cultivated.</p><p>In the early days of Machine Learning, humans trained models so that machines could learn. Now, we’re at a point where humans are learning from these trained models. And worse, humans are becoming dependent on them.</p><p>It is no longer just about using AI for support, we are beginning to treat human reasoning as incomplete unless verified or validated by AI.</p><p>This reminds me of the era before calculators. Mathematicians were celebrated for solving complex problems quickly and accurately using pure thought. Then calculators came along which was useful, but they eroded the drive to study the underlying methods. AI feels like a much larger version of this story.</p><p>Yes, AI will continue to accelerate problem-solving and innovation. But at what cost? Are we trading away human critical thinking? Are we raising a generation of builders who can only create with AI assistance?</p><p>𝐓𝐡𝐞 𝐀𝐈 𝐫𝐞𝐯𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐢𝐬 𝐧𝐨𝐭 𝐣𝐮𝐬𝐭 𝐚 𝐭𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐢𝐜𝐚𝐥 𝐬𝐡𝐢𝐟𝐭, 𝐢𝐭 𝐢𝐬 𝐚 𝐜𝐨𝐠𝐧𝐢𝐭𝐢𝐯𝐞 𝐬𝐡𝐢𝐟𝐭.</p><p><strong>If you find this article informative, please give some claps </strong>👏👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d990dbeba38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Beyond Building Mobile UIs and API Integration?]]></title>
            <link>https://medium.com/@praiseajepe/-8497c40c0dcf?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8497c40c0dcf</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 12:29:33 GMT</pubDate>
            <atom:updated>2025-09-28T08:04:20.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3lj-LRemBvpBMz1NMi54dg.png" /><figcaption>Image of Author</figcaption></figure><p>Beyond building beautiful mobile UIs and seamless API integrations is 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲.</p><p>Especially in industries like finance, 𝒔𝒆𝒄𝒖𝒓𝒊𝒕𝒚 𝒊𝒔 𝒆𝒙𝒑𝒆𝒄𝒕𝒆𝒅 𝒕𝒐 𝒃𝒆 𝒄𝒐𝒏𝒔𝒊𝒅𝒆𝒓𝒆𝒅 𝒃𝒚 𝒆𝒗𝒆𝒓𝒚 𝒕𝒆𝒂𝒎 𝒎𝒆𝒎𝒃𝒆𝒓 𝒂𝒔 𝒂 𝒄𝒖𝒍𝒕𝒖𝒓𝒆 𝒂𝒏𝒅 𝒏𝒐𝒕 𝒂𝒔 𝒂 𝒔𝒆𝒑𝒂𝒓𝒂𝒕𝒆 𝒇𝒆𝒂𝒕𝒖𝒓𝒆 or standalone process</p><p>𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐈𝐬 𝐄𝐯𝐞𝐫𝐲𝐨𝐧𝐞’𝐬 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲<br>From front-end developers to backend engineers, QA testers to DevOps, security isn’t just one person’s job, it’s a shared responsibility across the team.</p><p>One issue I keep noticing in financial apps (even enterprise-grade ones) is;<br>⚠️ 𝐋𝐨𝐠𝐠𝐢𝐧𝐠 <br>Logs are great during development for debugging, especially when external monitoring tools aren’t available, but in production, those same logs can unintentionally expose confidential information and open the door to security risks.</p><p>It’s also important not to ignore external packages<br>𝐈𝐬𝐬𝐮𝐞 𝐰𝐢𝐭𝐡 𝐄𝐱𝐭𝐞𝐫𝐧𝐚𝐥 𝐏𝐚𝐜𝐤𝐚𝐠𝐞𝐬<br>Sometimes, the vulnerability isn’t in developer’s written code, but from third-party packages or services. Some of these packages log data. That’s why reviewing external dependencies before pushing to production is just as important as reviewing your own written code.</p><p>In conclusion, “𝘈 𝘱𝘦𝘳𝘧𝘦𝘤𝘵𝘭𝘺 𝘴𝘦𝘤𝘶𝘳𝘦 𝘴𝘺𝘴𝘵𝘦𝘮 𝘮𝘢𝘺 𝘯𝘦𝘷𝘦𝘳 𝘦𝘹𝘪𝘴𝘵”, but every conscious step counts. Ensure;<br>✅ Removing unnecessary logs<br>✅ Auditing external dependencies<br>✅ Building with security in mind</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8497c40c0dcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Mobile App Performance with Caching and Preloading of API Data]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@praiseajepe/-6535b01a56a7?source=rss-a00285615ae3------2"><img src="https://cdn-images-1.medium.com/max/1290/1*HNTp9RqgRyXalRHXPND79w.png" width="1290"></a></p><p class="medium-feed-snippet">When building mobile apps, one of the biggest challenges is ensuring smooth data delivery from APIs without frustrating users with long&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@praiseajepe/-6535b01a56a7?source=rss-a00285615ae3------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@praiseajepe/-6535b01a56a7?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6535b01a56a7</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Mon, 15 Sep 2025 08:44:13 GMT</pubDate>
            <atom:updated>2025-09-15T08:46:31.038Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[FinTech App Security: 6 Data Formatting Best Practices]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@praiseajepe/fintech-app-security-6-data-formatting-best-practices-7aa3c82bc256?source=rss-a00285615ae3------2"><img src="https://cdn-images-1.medium.com/max/1400/0*TPpVuuyUV7Ka_lo8" width="1400"></a></p><p class="medium-feed-snippet">In this article, I&#x2019;m sharing key security-focused data formatting practices to help enhance FinTech app security and improve the user&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@praiseajepe/fintech-app-security-6-data-formatting-best-practices-7aa3c82bc256?source=rss-a00285615ae3------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@praiseajepe/fintech-app-security-6-data-formatting-best-practices-7aa3c82bc256?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aa3c82bc256</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 07:04:49 GMT</pubDate>
            <atom:updated>2025-04-26T06:46:19.927Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How Much I Earned on Medium in March — A Look at My Stats]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@praiseajepe/how-much-i-earned-on-medium-in-march-a-look-at-my-stats-e76c27b117fd?source=rss-a00285615ae3------2"><img src="https://cdn-images-1.medium.com/max/1192/1*KOGqDJFnYBDUSGvYs7VGJQ.png" width="1192"></a></p><p class="medium-feed-snippet">March turned out to be my biggest month in terms of audience reach!</p><p class="medium-feed-link"><a href="https://medium.com/@praiseajepe/how-much-i-earned-on-medium-in-march-a-look-at-my-stats-e76c27b117fd?source=rss-a00285615ae3------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@praiseajepe/how-much-i-earned-on-medium-in-march-a-look-at-my-stats-e76c27b117fd?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e76c27b117fd</guid>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[medium-earnings-report]]></category>
            <category><![CDATA[medium-earnings]]></category>
            <category><![CDATA[story-writing]]></category>
            <category><![CDATA[income]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Sat, 05 Apr 2025 08:02:14 GMT</pubDate>
            <atom:updated>2025-04-05T08:02:14.361Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Had My Medium Highest Read of the Year — So Far!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@praiseajepe/i-had-my-medium-highest-read-of-the-year-so-far-eef6e1f21d95?source=rss-a00285615ae3------2"><img src="https://cdn-images-1.medium.com/max/1410/1*fLFEsy1cZRRT85K40Szayg.png" width="1410"></a></p><p class="medium-feed-snippet">It&#x2019;s motivating to see steady improvements in my number of reads. Although my read ratio is still not as high as I would like, I&#x2019;m&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@praiseajepe/i-had-my-medium-highest-read-of-the-year-so-far-eef6e1f21d95?source=rss-a00285615ae3------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@praiseajepe/i-had-my-medium-highest-read-of-the-year-so-far-eef6e1f21d95?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/eef6e1f21d95</guid>
            <category><![CDATA[medium-earnings-report]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Wed, 02 Apr 2025 12:12:04 GMT</pubDate>
            <atom:updated>2025-04-02T12:12:04.825Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Don’t Overuse the Flutter Padding Widget]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@praiseajepe/dont-overuse-the-flutter-padding-widget-5ea447b5f331?source=rss-a00285615ae3------2"><img src="https://cdn-images-1.medium.com/max/2600/1*wL7Srg6GQ_LEtPhZ66Lq9A.jpeg" width="4814"></a></p><p class="medium-feed-snippet">While the padding widget is essential for layout structuring, overusing it can lead to unnecessary widget nesting, performance issues, and&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@praiseajepe/dont-overuse-the-flutter-padding-widget-5ea447b5f331?source=rss-a00285615ae3------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@praiseajepe/dont-overuse-the-flutter-padding-widget-5ea447b5f331?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ea447b5f331</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-tips]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Mon, 10 Mar 2025 16:42:56 GMT</pubDate>
            <atom:updated>2025-03-10T16:42:56.771Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Flutter Dropdown Refactoring; How I paid my Technical Debt]]></title>
            <link>https://medium.com/@praiseajepe/flutter-dropdown-refactoring-how-i-paid-my-technical-debt-9c906d5c4f5d?source=rss-a00285615ae3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c906d5c4f5d</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Olawale Ajepe]]></dc:creator>
            <pubDate>Wed, 05 Feb 2025 08:47:15 GMT</pubDate>
            <atom:updated>2025-02-08T08:09:49.430Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flutter Dropdown Refactoring; How I Paid My Technical Debt</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O481myXFeddkgGI5wccpXg.jpeg" /><figcaption>Image from Pixels: By <a href="https://www.pexels.com/@karolina-grabowska/">Kaboompics.com</a></figcaption></figure><p>Starting a project in a hurry to make delivery could create several technical debts, this was the hole I found myself.</p><p>As a mobile application developer,</p><ul><li>I convert UI/UX from Figma to a Mobile Application using a suitable framework,</li><li>Integrate Internal (Platform) and External APIs,</li><li>Ensure Application Performance by working with the Quality Assurance team</li><li>Ensure Application Security by working with the cybersecurity team for security evaluation.</li></ul><h4><strong>My Debt</strong></h4><p>My debt was simple, but massive. It’s an un-refactored component, a dropdown.<br>As it is known, if a component is not refactored for re-usability, making changes to the element means making changes across all files</p><h4>How was my dropdown component, and how did I go about refactoring it?</h4><p>I make use of two widgets as a refactored dropdown component.</p><p>Refactor widget 1: Notice there is a child widget here</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br><br>import &#39;../app_config/styles/styles.dart&#39;;<br><br>class CustomDropDownButton extends StatelessWidget {<br>  final Widget child;<br><br>  const CustomDropDownButton({Key? key, required this.child}) : super(key: key);<br><br>  @override<br>  Widget build(BuildContext context) {<br>    final width = MediaQuery.of(context).size.width;<br>    return Padding(<br>        padding: EdgeInsets.only(bottom: 12.0.sp),<br>        child: Container(<br>          height: 48.0.h,<br>          width: width,<br>          padding: EdgeInsets.symmetric(horizontal: 10.0.sp),<br>          decoration: BoxDecoration(<br>            color: AppColors.appWhite,<br>            border: Border.all(<br>              color: AppColors.appDeepGrey.withOpacity(0.2),<br>            ),<br>            borderRadius: BorderRadius.circular(7.0.r),<br>          ),<br>          child: child,<br>        ));<br>  }<br>}</pre><p>I then call this CustomDropDownButton and pass dropdown widget:</p><pre>return CustomDropDownButton(<br>  child: DropdownButton&lt;String&gt;(<br>    underline: const SizedBox(),<br>    isExpanded: true,<br>    iconSize: 16.0.sp,<br>    value: selectedApplianceType,<br>    itemHeight: 60.0,<br>    icon: Icon(<br>      Icons<br>          .keyboard_arrow_down_outlined,<br>      size: 22.0.sp,<br>      color: AppColors.appGrey5,<br>    ),<br>    elevation: 16,<br>    onChanged: (value) {<br>      setState(() {<br>        selectedValue = value!;<br>        deviceTypeController.text =<br>            value;<br>      });<br>    },<br>    style: AppStyles.smallOutfit<br>        .copyWith(<br>            color:<br>                AppColors.appDeepBlue),<br>    items: dropwdownList<br>        .map&lt;DropdownMenuItem&lt;String&gt;&gt;(<br>            (value) {<br>      return DropdownMenuItem&lt;String&gt;(<br>        value: value,<br>        child: Text(<br>          value,<br>          style: AppStyles.smallOutfit<br>              .copyWith(<br>                  color: AppColors<br>                      .appGrey5,<br>                  fontSize: 13.0.sp),<br>        ),<br>      );<br>    }).toList(),<br>  ),<br>);</pre><h4>Isn’t that too much to be replicated across screens?</h4><p>The refactor I made</p><pre>import &#39;package:flutter/material.dart&#39;;<br>import &#39;package:flutter_screenutil/flutter_screenutil.dart&#39;;<br><br>import &#39;../app_config/styles/styles.dart&#39;;<br><br>class CustomDropdown extends StatefulWidget {<br>  const CustomDropdown({<br>    super.key,<br>    required this.items,<br>    required this.hint,<br>    this.onChanged,<br>    this.defaultValue,<br>  });<br><br>  final List&lt;String&gt; items;<br>  final String hint;<br>  final ValueChanged&lt;String?&gt;? onChanged;<br>  final String? defaultValue; // Add this line<br><br>  @override<br>  State&lt;CustomDropdown&gt; createState() =&gt; _CustomDropdownState();<br>}<br><br>class _CustomDropdownState extends State&lt;CustomDropdown&gt; {<br>  String? _selectedItem;<br><br>  @override<br>  void initState() {<br>    super.initState();<br>    // Set the default selected item if provided<br>    _selectedItem = widget.defaultValue;<br>  }<br><br>  @override<br>  Widget build(BuildContext context) {<br>    final width = MediaQuery.of(context).size.width;<br>    return Container(<br>      height: 48.0.h,<br>      width: width,<br>      padding: EdgeInsets.symmetric(horizontal: 10.0.sp),<br>      margin: EdgeInsets.only(bottom: 12.0.sp),<br>      decoration: BoxDecoration(<br>        color: AppColors.appWhite,<br>        borderRadius: BorderRadius.circular(8.0),<br>        border: Border.all(<br>          color: AppColors.appDeepGrey.withOpacity(0.2),<br>        ),<br>      ),<br>      child: DropdownButtonHideUnderline(<br>        child: DropdownButton&lt;String&gt;(<br>          dropdownColor: AppColors.appWhite,<br>          value: _selectedItem,<br>          hint: Text(<br>            widget.hint,<br>           style: AppStyles.smallOutfit.copyWith(<br>              color: AppColors.appGrey5.withOpacity(0.6),<br>            ),<br>            // style: AppStyles.smallOutfit.copyWith(<br>            //   color: AppColors.appGrey5,<br>            //   fontSize: 13.0.sp<br>            // ),<br>          ),<br>          isExpanded: true,<br>          icon: Icon(<br>            Icons.keyboard_arrow_down_outlined,<br>            size: 22.0.sp,<br>            color: AppColors.appGrey5,<br>          ),<br>          items: widget.items.map((String value) {<br>            return DropdownMenuItem&lt;String&gt;(<br>              value: value,<br>              child: Text(<br>                value,<br>                style: AppStyles.smallOutfit.copyWith(<br>                  color: AppColors.appGrey5,<br>                ),<br>              ),<br>            );<br>          }).toList(),<br>          onChanged: (newValue) {<br>            setState(() {<br>              _selectedItem = newValue;<br>            });<br>            if (widget.onChanged != null) {<br>              widget.onChanged!(newValue);<br>            }<br>          },<br>        ),<br>      ),<br>    );<br>  }<br>}</pre><p>The usage across screens:</p><pre>List&lt;String&gt; genders = [&quot;Female&quot;, &quot;Male&quot;];<br>String selectedGender = &quot;&quot;;</pre><pre>CustomDropdown(<br>  items: genders,<br>  hint: &quot;Select an option&quot;,<br>  onChanged: (value) {<br>    setState(() {<br>      selectedGender = value!;<br>    });<br>  },<br>),</pre><p>Isn’t that straightforward and efficient?</p><p><strong>If you find this article informative, please give some claps </strong>👏👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c906d5c4f5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>