<?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 Adeyeye Adedamola on Medium]]></title>
        <description><![CDATA[Stories by Adeyeye Adedamola on Medium]]></description>
        <link>https://medium.com/@adeyeyeadedamola?source=rss-26d84c1f32f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mosuqXW1cL_N5EKNP9BN7g.jpeg</url>
            <title>Stories by Adeyeye Adedamola on Medium</title>
            <link>https://medium.com/@adeyeyeadedamola?source=rss-26d84c1f32f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:45:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adeyeyeadedamola/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[The Architecture of Trust — A Chronicle of Nigeria’s Mobile Finance Evolution, 2000–2026 Part II]]></title>
            <link>https://adeyeyeadedamola.medium.com/the-architecture-of-trust-a-chronicle-of-nigerias-mobile-finance-evolution-2000-2026-part-ii-41bb2ab3cacc?source=rss-26d84c1f32f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/41bb2ab3cacc</guid>
            <category><![CDATA[neobanks]]></category>
            <category><![CDATA[mobile-banking]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[financial-inclusion]]></category>
            <category><![CDATA[ussd]]></category>
            <dc:creator><![CDATA[Adeyeye Adedamola]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 13:13:29 GMT</pubDate>
            <atom:updated>2026-07-31T13:13:29.275Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>By Adeyeye Adedamola. Curated for Builders in Fintech | The African Fintech Library (AFL) Extended Feature — Part II of II</blockquote><h3>Introduction: What the History Doesn’t Show You</h3><p>Part I told the story of Nigerian mobile finance the way most people experience it from the outside, as a sequence of apps that got faster, prettier, and more reliable over two decades. But that’s the view from the customer’s side of the glass. Behind every version bump was a server somewhere in Lagos or Frankfurt straining under Christmas Eve traffic. Behind every “Instant” badge on a transfer screen was a compliance officer arguing with an engineer about how much friction a fraud check was allowed to add before customers gave up and called a bank teller instead.</p><p>This second half of the chronicle goes behind the glass. It examines the systems that had to be built for the story in Part I to be possible at all and the regulatory scaffolding, often invisible, occasionally suffocating, that shaped what builders were allowed to build. If Part I was about <em>what</em> changed, Part II is about how and at what cost.</p><h3>Section One: The Technical Architecture of the Neobank Era</h3><h3>From Monolith to Microservice — and Why It Nearly Broke the Old Guard</h3><p>To understand why OPay and Moniepoint survived the 2023 cash crunch while legacy banking apps crumbled, you have to understand what was actually running under the hood of each.</p><p><strong>The monolith problem.</strong> Most Tier-1 Nigerian banks built their digital channels as extensions of a core banking system designed in the 1990s, a single, tightly coupled application where the mobile app, the internet banking portal, the ATM switch, and the core ledger all leaned on the same aging infrastructure. It’s a bit like a house where the plumbing, wiring, and load-bearing walls were never meant to be separated. Adding a new feature meant touching the whole structure. Scaling for a traffic spike meant scaling everything at enormous cost, often on hardware physically sitting in a data center the bank owned and maintained itself.</p><p>When the Naira Redesign Policy hit in early 2023 and transaction volumes spiked overnight, these monoliths didn’t fail gracefully. They failed the way overloaded plumbing fails backing up everywhere at once, with no way to isolate the blockage.</p><p><strong>The microservices answer.</strong> The neobanks were built differently from day one, breaking the same functions — authentication, ledger, notifications, KYC, and fraud scoring — into independent services that could each scale on their own, fail on their own, and be updated on their own without bringing down the whole platform. A surge in transfer requests could pull more compute toward the ledger service without touching the notification service at all. This is the architectural equivalent of a house where you can renovate the kitchen without shutting off the water to the bathroom.</p><p>Cloud-native infrastructure like AWS, Azure, and increasingly African-hosted alternatives meant that “more capacity” was a configuration change, not a hardware purchase order. For a country where demand can triple overnight because of a single policy announcement, that elasticity wasn’t a luxury. It was survival.</p><p><strong>Event-driven design and the ledger’s quiet importance.</strong> Underneath the visible app sits the least glamorous, most critical piece of the stack: the ledger the system of record that decides, with total finality, whether money actually moved. Modern Nigerian fintech architecture increasingly treats transactions as <em>events</em> flowing through a message queue (Kafka and similar tools are common in the stack now) rather than as direct, synchronous database writes. That distinction matters enormously in practice. If a downstream service, say, the one that sends the SMS alert, is briefly unavailable, an event-driven system queues the notification and retries it, while the ledger itself has already safely recorded that the money moved. In a monolithic, synchronous system, that same hiccup can freeze the entire transaction, or worse, silently drop it.</p><p><strong>Designing for a weak signal.</strong> Perhaps the most distinctly Nigerian architectural decision in this era has been the deliberate degrading of the user experience for the network conditions Nigerians actually have, rather than the ones engineers wish they had. Apps like OPay and PalmPay are built lightweight by design — compressed assets, minimal data payloads, aggressive caching, and interfaces that render usably even on 2G. A banking app that assumes fast, stable Wi-Fi is a banking app that has quietly decided who it’s not for. The neobanks were built for the boda-boda rider on a shared data plan first and the executive on unlimited fibre second, and in doing so, they captured a market the legacy players had spent a decade ignoring.</p><p><strong>The API layer and the agent network’s hidden plumbing.</strong> The much-discussed “army of POS agents” is not just a marketing story; it’s a technical one. Each agent’s POS terminal is, functionally, an API client talking to the same core ledger the mobile app talks to, often over a GSM/SIM-based connection rather than Wi-Fi or broadband, specifically because that’s the connectivity available on a street corner in Ijebu-Ode or Kano. Building a system where a Lagos office worker’s tap-to-pay transaction and a rural agent’s cash-in transaction hit the <em>same</em> consistent ledger, with the <em>same</em> fraud and reconciliation rules, without ever colliding or double-counting, is one of the least appreciated engineering achievements of this entire era. It’s invisible specifically because it works.</p><p><strong>Security as a layered system, not a single gate.</strong> The hardware token era treated security as a single checkpoint: one code, one moment, pass or fail. The current standard treats it as continuous and layered: a PIN for intent; device fingerprinting to catch a stolen session; behavioral signals (typing speed, tap pressure, even the angle a phone is typically held at) to flag anomalies quietly in the background; and biometric checks Face ID and fingerprint for the moments that matter most. None of these layers is meant to be unbeatable alone. Together, they raise the cost of fraud high enough that most attackers move on to an easier target.</p><h3>Section Two: The Regulatory Milestones That Shaped the Machine</h3><h3>Building a Bank in a Country That Rewrites the Rulebook Mid-Construction</h3><p>Every architectural decision described above exists inside a regulatory perimeter that has shifted, sometimes gently and sometimes violently, roughly once a year for the past two decades. Understanding Nigerian fintech without understanding this timeline is like reading half a blueprint.</p><p><strong>2007–2011: The legal foundation.</strong> The Central Bank of Nigeria Act 2007 and the Banks and Other Financial Institutions Act (BOFIA) gave the CBN the statutory authority it would later use to license and supervise everything from mobile money operators to payment service banks. This is the unglamorous bedrock beneath everything that followed.</p><p><strong>2012: The Cashless Policy.</strong> As covered in Part I, this was the CBN’s opening shot at pulling Nigeria’s economy off physical cash, introducing transaction limits and charges on large cash withdrawals to nudge behaviour toward digital channels.</p><p><strong>2018: Payment Service Banks (PSBs) — the door opens for telcos and retailers.</strong> In October 2018, the CBN introduced draft guidelines allowing non-bank players, telecom companies, retail chains, postal operators, and mobile money operators to establish Payment Service Banks aimed squarely at financial inclusion in underserved, rural areas. These guidelines were revised in August 2020, and a fuller supervisory framework followed on <strong>8 July 2021</strong>, formalizing governance and IT-risk expectations for PSB operators. This is the regulatory pathway that eventually let telco-adjacent players like MoMo (MTN) and 9PSB compete directly with banks on deposit-taking without becoming full commercial banks themselves.</p><p><strong>2021: Open Banking gets its first framework.</strong> In February 2021, the CBN issued its first Regulatory Framework for Open Banking in Nigeria — a foundational document establishing the principle that customer financial data, with consent, should be shareable across institutions via standardized APIs, rather than locked inside whichever bank happened to hold the account. This was less a product than a promise: the operational detail would come later.</p><p><strong>2023: The year regulation caught up to reality.</strong> Few years in Nigerian fintech carried as much regulatory weight as 2023:</p><ul><li>On <strong>7 March 2023</strong>, the CBN issued the Operational Guidelines for Open Banking in Nigeria, making Nigeria the first African country to formalize end-to-end open banking covering API standards, participant categories, consent management, and data-sharing obligations between banks and licensed third parties.</li><li>The CBN also issued a Risk-Based Cybersecurity Framework and Guidelines for banks and PSBs, tightening expectations around vulnerability testing, encryption, and incident response, a direct response to the rising sophistication of fraud described in Part I.</li><li>On <strong>12 June 2023</strong>, President Bola Ahmed Tinubu signed the Nigeria Data Protection Act (NDPA) into law, replacing the older 2019 NDPR with binding legislation and establishing the Nigeria Data Protection Commission (NDPC) as an independent regulator. For any Builder handling biometric onboarding, transaction history, or location data — which is to say, every fintech in the country — the NDPA became the legal floor beneath every data-handling decision.</li><li>And, as chronicled in Part I, the <strong>Naira Redesign Policy</strong> triggered the cash scarcity that became the industry’s ultimate stress test.</li></ul><p><strong>2024: Tightening identity, loosening crypto.</strong> The mandate linking every financial account to a BVN and NIN — closing the door on anonymous wallets — was enforced with new urgency in 2024, a direct regulatory response to the fraud patterns of the preceding years. In the same year, the CBN’s posture toward cryptocurrency and virtual asset service providers softened considerably from the outright restrictions of 2021, reopening a channel that platforms like Bundle and Busha had been waiting years to legally operate through.</p><p><strong>2025: Open Banking finally goes live.</strong> Despite the 2021 framework and the 2023 operational guidelines, real-world implementation of open banking was delayed repeatedly, held back by limited public awareness, uneven technical readiness among smaller banks, and lingering security concerns. Full implementation was ultimately pushed to <strong>August 2025</strong>, alongside a General Application and Implementation Directive (GAID) from the NDPC clarifying how data protection law applies in practice. It is a useful reminder that in Nigerian fintech, the gap between a regulation being <em>announced</em> and a regulation being <em>lived</em> can stretch for years, and builders plan their roadmaps around that gap as much as around the regulation itself.</p><p><strong>The pattern underneath the timeline.</strong> Read end to end, this regulatory history reveals something the individual headlines don’t: the CBN has consistently regulated <em>behind</em> the market rather than ahead of it. USSD, instant transfers, agent banking, and even crypto adoption all emerged first as informal or semi-formal practices and only later received a formal rulebook. For builders, this has produced a durable, if uncomfortable, operating principle: build <strong>for the need</strong> first and <strong>be ready to retrofit for the regulation that will eventually arrive to govern it.</strong></p><h3>Closing the Loop: Architecture and Regulation as Two Halves of One Story</h3><p>It would be easy to read the technical section and the regulatory section as separate tracks, one about engineers and one about lawyers and central bankers. In practice, in Nigeria, more than almost anywhere else, they are the same conversation happening in two different rooms.</p><p>The microservices architecture that let Moniepoint scale through the 2023 cash crunch exists in service of a cashless policy first floated in 2012. The layered security stack protecting today’s Face ID logins exists because BVN and NIN mandates created a reliable identity layer to check against. The lightweight, 2G-tolerant app design exists because financial inclusion, a regulatory and social goal as much as a commercial one, pushed builders to serve customers the market alone might have deprioritized.</p><p>The next generation of Nigerian fintech infrastructure, embedded finance, AI-driven credit, and cross-border rails via PAPSS will follow the same pattern that has held for two decades. Someone will build the thing the market obviously needs. The regulation will follow later than anyone would like and usually more thoroughly than anyone expected. The builders who thrive will be the ones who treat that lag not as an obstacle but as the actual shape of the terrain they’re building on.</p><h3>Further Reading &amp; Resources from the AFL</h3><ul><li>CBN Supervisory Framework for Payment Service Banks (2021)</li><li>CBN Regulatory Framework for Open Banking in Nigeria (2021) and Operational Guidelines (2023)</li><li>Nigeria Data Protection Act, 2023 — full text and NDPC guidance</li><li>CBN Risk-Based Cybersecurity Framework for DMBs and PSBs (2023)</li><li>Case Study: How Moniepoint’s Infrastructure Held During the 2023 Cash Crunch</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41bb2ab3cacc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Architecture of Trust — A Chronicle of Nigeria’s Mobile Finance Evolution, 2000–2026]]></title>
            <link>https://adeyeyeadedamola.medium.com/the-architecture-of-trust-a-chronicle-of-nigerias-mobile-finance-evolution-2000-2026-4e7740b6a568?source=rss-26d84c1f32f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e7740b6a568</guid>
            <category><![CDATA[digital-payment]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[mobile-banking]]></category>
            <category><![CDATA[ussd]]></category>
            <category><![CDATA[neobanks]]></category>
            <dc:creator><![CDATA[Adeyeye Adedamola]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 13:10:03 GMT</pubDate>
            <atom:updated>2026-07-31T13:10:03.737Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Architecture of Trust —</h3><p>A Chronicle of Nigeria’s Mobile Finance Evolution, 2000–2026</p><blockquote>By <strong>Adeyeye Adedamola</strong>. Curated for Builders in Fintech | The African Fintech Library (AFL) Extended Feature — Part I of II</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LDlfYXw901CaXjE6" /></figure><h3>Introduction: The “Transaction Without Tears” Manifesto</h3><p>To understand the finance app in Nigeria, you first have to understand the trauma it was built to erase.</p><p>In the early 2000s, banking was not a service. It was a chore, sometimes a small ordeal. It meant queuing for a tally number at dawn, standing in a banking hall thick with heat and impatience, filling out a carbon-copied withdrawal slip in triplicate, and racing the clock before the doors closed for the day. A missed transfer might mean days of uncertainty: Was the money sent? Did it arrive? Who do you call?</p><p>Today, that friction has all but vanished from daily life. A grandmother in Osogbo can receive money from a grandson in London before she finishes her tea. A Gen-Z creative in Yaba can pay for a ride, buy a fraction of an agricultural bond, and hedge a little cash into stablecoins all before getting out of bed.</p><p>That shift didn’t happen by accident. It was a deliberate, often chaotic collision of policy, infrastructure, and stubborn engineering, built by people who rarely got the credit: product managers arguing over onboarding flows, engineers patching servers at 2 a.m., regulators trying to write rules for technology that changed faster than the ink could dry. Drawing on the archives of the African Fintech Library (AFL), this report traces four distinct epochs of that story. It is less a history of apps than a history of the Builders who paved the digital roads Nigerians now drive on without a second thought.</p><h3>Epoch I: The Infrastructure Layer (2002–2011)</h3><h3>From “Tally Numbers” to the “Credit Alert”</h3><p>The first era of Nigerian mobile finance had no apps and no smartphones. Its entire interface was a 160-character text message, and for a country starved of reliable information, that was revolutionary enough.</p><p><strong>The GSM spark.</strong> The licensing of MTN and Econet in 2001 detonated Nigeria’s mobile phone market. Before that year, the country had roughly 400,000 connected phone lines, a number so small it barely registered against the population. By 2010, that figure had exploded past 80 million. For the first time in Nigerian history, an individual’s identity could be tethered to a single, personal, always-on number. That was the network effect fintech had been waiting for.</p><p><strong>The psychology of the alert.</strong> It’s hard to overstate what the SMS alert meant to a generation raised on institutional distrust. In a low-trust environment where systems failed quietly and often, the buzz of a phone became a small, verifiable proof of truth.</p><p><em>“I sent the money.” “I haven’t seen it.”</em> That argument, repeated in a thousand variations across market stalls and living rooms, was finally settled by a vibration in someone’s pocket.</p><p>The lesson this era taught Builders has outlasted the technology that taught it: <strong>in Nigeria, visibility is as important as validity.</strong> People don’t just need a transaction to be correct; they need to <em>see</em> it happen.</p><p><strong>The silent giant.</strong> While phones handled the notifications, the actual plumbing of money movement was being laid by Interswitch, founded in 2002 under Mitchell Elegbe. By connecting every Nigerian bank to a central switch, Interswitch made it possible to withdraw cash from any ATM regardless of card issuer an unglamorous, invisible achievement that quietly became the protocol layer everything else would later be built on.</p><h3>Epoch II: The Usability Layer &amp; The Cashless Policy (2012–2016)</h3><h3>The Birth of “Mobile Banking” and the USSD Bridge</h3><p>If the first epoch was about infrastructure, the second was about policy. In 2012, under Central Bank Governor Sanusi Lamido Sanusi, the CBN launched its Cashless Policy, an attempt to pull physical currency out of circulation and force the country’s financial life online.</p><p><strong>Banking App 1.0: skeuomorphic and suspicious of its own users.</strong> The first generation of banking apps GTBank, Zenith, FirstMobile arrived in this window, and they were built with the anxious caution of institutions that had never trusted a screen with real money. Their interfaces tried to replicate the physical bank experience, right down to visual textures meant to look like leather and paper. Security was paranoid by design: even a small transfer required a physical hardware token, a fiddly little device that spat out a fresh number every thirty seconds. The apps were heavy, data-hungry, and useless the moment a 3G signal dropped, which, outside the major cities, was often.</p><p><strong>The accidental hero: <em>737#.</em></strong> <em>While the apps struggled, GTBank quietly rewired the entire market with Unstructured Supplementary Service Data USSD. By dialing</em> 737#, a user could move money with no internet connection, no smartphone, and no hardware token, authenticating instead with the last four digits of a debit card. Overnight, every feature phone in the country became a payment terminal. It reached the unbanked and underbanked who found apps too complicated, too expensive, or simply beside the point.</p><p>The takeaway for Builders was almost counterintuitive: <strong>the most advanced technology is not always the best solution.</strong> Accessibility beats sophistication when the alternative is exclusion.</p><p><strong>The game changer: NIP.</strong> The unsung hero of this era was NIBSS, the Nigeria Inter-Bank Settlement System and its Instant Payment product, NIP. At a time when a bank transfer in the United States or much of Europe could take two to three business days to clear through ACH rails, NIP made Nigerian transfers instant, account-to-account, in real time. That single feature reset user expectations permanently. It’s part of why global fintechs like PayPal or Wise, arriving years later with multi-day settlement windows, have often struggled to impress a Nigerian public that had already been spoiled by instant money.</p><h3>Epoch III: The Unbundling &amp; The Rise of Specialists (2016–2020)</h3><h3>Enter the Fintechs: Paystack, PiggyVest, Cowrywise, and the New Wave</h3><p>By 2016, a new cohort of Builders looked at the incumbent banking apps and saw the obvious flaw: banks were generalists. In trying to be everything to everyone, they had become mediocre at nearly all of it. The new wave’s answer was unbundling: pick one problem, and solve it obsessively well.</p><p><strong>Payments: fixing the merchant problem.</strong> Before 2016, wiring payment acceptance into a website could cost a small business close to ₦150,000 in setup fees, plus weeks of paperwork and waiting. Shola Akinlade and Ezra Olubi built Paystack to erase that friction almost entirely, a “Stripe for Africa” that reduced integration to a handful of lines of code and stripped away the setup cost. The ripple effect was enormous: thousands of small businesses could suddenly sell online, seeding a new digital economy that would, in turn, need mobile tools to run itself.</p><p><strong>Savings and wealth: the millennial wallet.</strong> Traditional banks offered savings interest so thin it was often eaten alive by maintenance fees, a quiet insult that millions of Nigerians had simply learned to accept. PiggyVest (originally PiggyBank) turned saving into something closer to a game, letting users “lock” funds away from their own temptation. Cowrywise did something similarly disarming with mutual funds, opening them up to anyone with as little as ₦1,000. Both apps spoke in a new visual language: warm colors, conversational copy, and a tone that sounded like a friend rather than a branch manager. They didn’t speak “Bank.” They spoke human.</p><p><strong>Credit: the instant loan and its shadow.</strong> Getting a loan from a Tier-1 bank meant collateral, guarantors, and months of waiting. Apps like Carbon (formerly Paylater) shortcut all of it, mining a user’s smartphone data, SMS history, location, and even device model to generate an instant credit score. Download the app, and ₦10,000 could land in your account within five minutes. It was a genuine breakthrough, but it came with a cost: aggressive lending practices and even more aggressive debt-recovery tactics left a scar the industry is still working to heal.</p><h3>Epoch IV: The Reliability Wars &amp; The Neobank Supremacy (2020–Present)</h3><h3>When “It Just Works” Became the Only Feature That Mattered</h3><p>COVID-19 accelerated Nigeria’s shift online, but the real stress test the event that separated the apps built for show from the apps built to last was the 2023 Naira Redesign Policy.</p><p><strong>The cash crunch as a system-wide exam.</strong> In early 2023, the CBN’s aggressive push to replace old naira notes triggered a severe cash scarcity almost overnight. Nigerians, with little choice left, funneled their entire financial lives through digital channels, and the legacy banking apps, many still tethered to on-premise servers built for a calmer decade, simply buckled. Downtime stretched into days, not hours, and a whole country learned exactly which apps it could trust in a crisis.</p><p><strong>The neobanks won by being boring, in the best sense.</strong> OPay, PalmPay, and Moniepoint, the last of which started as an agent-banking play, not a consumer app, absorbed the load that traditional banks couldn’t handle. They won for reasons that sound unglamorous but proved decisive:</p><ul><li><strong>Cloud-native from day one</strong>, able to scale capacity on demand rather than waiting on a data center upgrade.</li><li><strong>Lightweight apps</strong>, engineered to function on the patchy 2G and EDGE connections that still define much of the country outside its major cities.</li><li><strong>A relentless focus on transaction success rate</strong> over feature count because a beautiful app that fails at the moment of payment is worse than no app at all.</li></ul><p><strong>The rise of the agency network.</strong> This era also cemented a distinctly Nigerian hybrid: the “phygital” model, part physical, part digital. Moniepoint and OPay didn’t just build apps; they built armies of POS agents standing on street corners in every town, functioning as human ATMs and, more importantly, as human faces for people who still didn’t fully trust a screen with their savings. Having earned that trust, these platforms have since rebundled everything the earlier era unbundled: OPay is no longer “just payments,” but savings, loans, and airtime rolled into one super-app the very thing Nigeria’s telcos once dreamed of becoming and never quite managed.</p><h3>The Anatomy of a Modern Nigerian Finance App</h3><p><em>Based on current Builders in Fintech standards</em></p><p>Tear down a successful Nigerian finance app in 2025–2026, and you’ll find a consistent set of architectural choices that separate the leaders from the legacy players:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EuvkXySua-M8AUsiaF9mnw.png" /></figure><h3>Challenges &amp; The Scars of the Industry</h3><p>No honest history skips the failures, and the AFL archives are full of them.</p><p><strong>The fraud epidemic.</strong> As transaction speed rose, so did the sophistication of fraud. Social engineering, in particular, where a caller tricks a victim into revealing a PIN over the phone, remains stubbornly common. That epidemic is what forced the 2024 regulatory mandate tying every account to a National Identity Number (NIN) and Bank Verification Number (BVN), closing the door on anonymous wallets.</p><p><strong>Regulatory whiplash.</strong> Builders in Nigeria code with one eye on the screen and one eye on the CBN’s next circular. The industry’s relationship with crypto captures the volatility well: banned in 2021, permitted again by 2024. Planning a product roadmap around that kind of regulatory weather requires a specific, battle-tested kind of patience.</p><p><strong>The Japa exodus.</strong> The mass emigration of skilled professionals known locally as “Japa” pulled a generation of senior engineers and product managers out of Lagos and into Europe and North America. What’s left behind is a local industry locked in a constant, exhausting cycle of training junior talent, only to watch some of the best of them leave a few years later.</p><h3>Future Outlook: 2026 and Beyond</h3><p>Three trends are surfacing from the noise as the next horizon comes into view.</p><ol><li><strong>Embedded finance.</strong> “Fintech” is quietly disappearing as a standalone category. Logistics platforms like GIG Logistics, e-commerce players like Jumia, and mobility apps like Bolt and Uber are weaving wallets and lending directly into their existing flows. The finance app of the future may not look like a bank at all; it may not look like a finance app.</li><li><strong>Credit as a feature, not a product.</strong> As credit bureaus mature and AI-driven risk assessment improves, instant Buy Now, Pay Later credit at the point of sale is displacing the old, generic cash loan.</li><li><strong>Cross-border dominance.</strong> With the Pan-African Payment and Settlement System (PAPSS) coming online, Nigerian fintechs are setting their sights on the whole continent. Companies like LemFi and Grey are chipping away at the FX crisis facing freelancers and the diaspora, making global money move like local money again.</li></ol><h3>Conclusion: The Builder’s Mandate</h3><p>The story of Nigeria’s finance app is, at its core, a story about antifragility. When cash failed, builders built USSD. When the internet lagged, they built lightweight apps for weak signals. When trust was scarce, they built armies of human agents to stand where a screen couldn’t.</p><p>For the readers of <em>Builders in Fintech</em>, the mandate that emerges from this history is simple to state and hard to execute: the next billion-dollar opportunity will not come from copying Silicon Valley. It will come from sitting with the specific, local friction points of the African context until a solution presents itself. The question Nigerians ask of their financial tools has already evolved from <em>“Can I send money?”</em> to <em>“How fast, how cheap, and how smart can this money move?”</em></p><p>The evolution is far from finished. If anything, the foundation is only now finished being poured.</p><h3>Further Reading &amp; Resources from the AFL</h3><ul><li>CBN Circular on Mobile Money Operations (2012–2024)</li><li>The NIBSS Annual Fraud Report</li><li>Case Study: The Pivot of OPay, From Ride-Hailing to Fintech</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e7740b6a568" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native vs. Flutter: The Complete Breakdown for Companies and New Developers]]></title>
            <link>https://adeyeyeadedamola.medium.com/react-native-vs-flutter-the-complete-breakdown-for-companies-and-new-developers-30636bddb588?source=rss-26d84c1f32f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/30636bddb588</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[cross-platform]]></category>
            <dc:creator><![CDATA[Adeyeye Adedamola]]></dc:creator>
            <pubDate>Sun, 26 Jul 2026 21:59:56 GMT</pubDate>
            <atom:updated>2026-07-31T13:16:24.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P1lX-0zTVNPbIxCI" /></figure><h3>The Architecture of Trust — A Chronicle of Nigeria’s Mobile Finance Evolution, 2000–2026</h3><p>By Adeyeye Adedamola Curated for Builders in Fintech | The African Fintech Library (AFL) Extended Feature — Part I of II</p><h3>React Native vs. Flutter: The Complete Breakdown for Companies and New Developers</h3><p>Most “React Native vs. Flutter” content is written for nobody in particular. It throws a benchmark chart and a verdict at the reader and calls it a day. But a CTO deciding what three engineering teams will build on for the next five years and a bootcamp graduate deciding what to put on a resume are asking two completely different questions, and they need two different sets of information to answer them.</p><p>This piece is split accordingly. The first half is for the people making the <em>build</em> decision: engineering leads, founders, and product managers weighing cost and risk. The second half is for the people making the learning decision: new developers deciding where to invest their next six months. Read the half that applies to you or read both, because the two decisions inform each other more than most articles admit.</p><p>As covered previously, both frameworks are production-grade, both are used at massive scale, and neither is a wrong choice in the abstract. What follows is the detail underneath that conclusion.</p><h3>Quick-Reference Matrix</h3><p>Dimension</p><p>React Native</p><p>Flutter</p><p>Backed by</p><p>Meta</p><p>Google</p><p>Language</p><p>JavaScript / TypeScript</p><p>Dart</p><p>Market share (cross-platform apps)</p><p>~35%</p><p>~46%</p><p>Developer usage (Stack Overflow)</p><p>~8.4%</p><p>~9.4%</p><p>Job postings</p><p>Roughly 6x Flutter’s volume</p><p>Lower, but growing</p><p>Talent pool size</p><p>3–5x larger</p><p>Smaller, more specialized</p><p>Package registry size</p><p>2M+ (npm)</p><p>45,000+ (pub.dev)</p><p>Share of new free iOS apps (2025)</p><p>~15–18%</p><p>~30% (up from ~10% in 2021)</p><p>Best for</p><p>JS-experienced teams, deep native integration, web code-sharing</p><p>Custom pixel-perfect UI, multi-platform consistency, on-device ML</p><p>Salary premium</p><p>Baseline</p><p>10–15% higher, often offset by faster MVP timelines</p><p>Keep this table in your back pocket. Everything below is the reasoning underneath each cell.</p><h3>Part One: The Company’s Decision</h3><h3>1. Total Cost of Ownership, Broken Down</h3><p>“Which is cheaper?” is the wrong first question. Total cost of ownership has at least four separate components, and they don’t all move in the same direction.</p><p><strong>Hiring cost.</strong> React Native’s talent pool is three to five times larger than Flutter’s, which in practice means shorter hiring cycles and more competitive candidate pools at a given salary band. Flutter developers tend to command a 10–15% salary premium over React Native developers in markets where the talent is scarcer, though many teams find this offset by Flutter’s faster path to a working MVP.</p><p><strong>Ramp-up cost.</strong> React Native often provides a lower initial cost for JavaScript-fluent teams, since there’s no new language to learn — a meaningful advantage given that a clear majority of developers already know JavaScript. Flutter requires learning Dart, which is a smaller ask than it sounds (Dart is deliberately easy to pick up for anyone coming from a C-style or object-oriented language), but it is a real cost that shows up in the first sprint or two, not the tenth.</p><p><strong>Build cost.</strong> Both frameworks deliver a 30–60% cost saving compared to building separate native iOS and Android apps, so the “versus native” case is settled. Either way, the real comparison is Flutter against React Native, not either of them against two native codebases.</p><p><strong>Maintenance cost.</strong> This is where the two diverge more than most comparisons admit. React Native’s release cadence and its dependency on third-party native modules mean maintenance cost is closely tied to the health of whichever libraries your app depends on — a well-chosen dependency tree is cheap to maintain; a poorly chosen one accumulates debt quickly. Flutter’s more centralized, first-party toolchain (one language, one widget system, one first-party package registry) tends to produce a more predictable maintenance curve, at the cost of occasionally waiting longer for a niche third-party integration to catch up.</p><p><strong>The bottom line for a CFO:</strong> if your team is already staffed with JavaScript engineers, React Native’s TCO advantage is front-loaded (cheaper and faster to start). If you’re greenfield-hiring either way, the TCO gap narrows substantially, and the decision should shift to the technical and product factors below.</p><h3>2. Performance and Technical Scaling</h3><p>Both frameworks have shipped major architectural rewrites in the last few years specifically to put old performance criticisms to rest, and both have largely succeeded.</p><p>React Native’s new architecture, rolling out since 2023 and now the default for new projects, replaced the old JavaScript bridge with the Fabric renderer for synchronous, concurrent-capable UI updates and TurboModules for lazy-loaded, type-safe native module access. This eliminated the specific performance complaint (the bridge bottleneck) that dominated React Native criticism for years.</p><p>Flutter’s answer has been its own rendering pipeline: the Impeller engine, built to deliver consistent, high-frame-rate rendering, which is where Flutter’s reputation for pixel-perfect, jank-free animation largely comes from. For the large majority of standard mobile UIs, both frameworks now perform excellently. The performance gap that used to decide this argument has narrowed to the point where it only matters for a specific slice of apps: heavy custom animation, graphics-intensive interfaces, or apps pushing hard against device limits. If that’s not your app, don’t let performance benchmarks be the deciding factor — they’re increasingly a solved problem for typical business apps.</p><h3>3. Where Each Has Proven Itself in Production</h3><p>Case studies matter more than benchmarks because they tell you what kind of engineering organization each framework rewards.</p><p>React Native remains in production use at Meta itself, powering parts of Facebook, Instagram, and Messenger at a scale of billions of daily interactions, and at companies including Microsoft, Shopify, and Discord.</p><p>Flutter’s enterprise adopters include Google’s own Google Pay, Google Earth, and Google Classroom, along with BMW’s My BMW app, Alibaba’s Xianyu marketplace serving over 200 million users, and Toyota.</p><p>Notice what these lists have in common: both frameworks are trusted with genuinely high-stakes, high-traffic products by companies with the resources to build native apps if they wanted to. Neither list is a hobbyist’s list. That should settle any lingering “is this framework enterprise-ready” anxiety on either side.</p><h3>4. Roadmap Fit: Where Is Your Product Actually Going?</h3><p>This is the question company decision-makers skip most often, and it’s usually the one that should decide the framework.</p><ul><li><strong>If your roadmap includes web and desktop alongside mobile</strong>, Flutter was designed from the outset as a genuinely multi-platform framework, sharing one codebase across Android, iOS, web, Windows, macOS, and Linux. React Native can reach web and desktop too, but through additional, separately maintained frameworks rather than one unified toolchain.</li><li><strong>If your roadmap includes a companion React web app</strong>, or you already have one, React Native paired with React Native Web can share up to 70% of a codebase with an existing React web application, a specific, powerful advantage that has no real Flutter equivalent unless your web app is already something you’re prepared to rebuild.</li><li><strong>If your roadmap leans on on-device AI/ML features,</strong> offline inference, and privacy-sensitive processing, Flutter’s on-device machine learning support is the more mature path today. If your AI features call out to cloud APIs instead, React Native’s ecosystem of integrations is the deeper one.</li></ul><h3>5. A Simple Risk Checklist for Engineering Leadership</h3><p>Before signing off on either framework, an engineering lead should be able to answer:</p><ol><li>Do we already have in-house expertise in JavaScript/React or in Dart/Flutter? (Whichever answer is “yes” should weigh heavily — retraining an entire team is a real, recurring cost, not a one-time one.)</li><li>Does our product need pixel-identical UI across platforms, or is “feels native to each platform” acceptable or preferred?</li><li>Is our 18-month roadmap mobile-only, or does it include web/desktop?</li><li>How dependent will we be on a small number of specific third-party native integrations, and are they better supported on one side than the other?</li><li>What does our hiring pipeline actually look like in our specific market — not in aggregate global statistics, but in the city or region where we’re hiring?</li></ol><p>If the answers point in the same direction, the decision is easy. If they conflict, that conflict is useful information: it usually means the “soft” factors (existing team skill and roadmap direction) should outweigh the “hard” factors (raw benchmarks), because the soft factors compound over the life of the product and the hard factors mostly don’t.</p><h3>Part Two: The New Developer’s Decision</h3><h3>1. The Learning Curve, Honestly Compared</h3><p><strong>React Native</strong> asks you to learn React first (components, state, props, and hooks) and then layer mobile-specific concepts on top (navigation, native modules, and platform-specific code). If you already know JavaScript and some React, the on-ramp is short — you’re mostly learning the mobile-specific 20%, not the whole stack. If you’re starting from zero, you’re learning JavaScript, React, <em>and</em> mobile concepts all at once, which is a heavier lift than it first appears.</p><p><strong>Flutter</strong> asks you to learn Dart, which most developers pick up faster than they expect; it’s a clean, statically typed, C-style language with none of JavaScript’s more infamous quirks, and then Flutter’s own widget-based UI model, which is genuinely different from HTML/CSS thinking and takes a few real projects to feel natural. Many developers who make the switch describe Flutter’s hot reload and single, cohesive toolchain (one language, one widget system, one package manager) as unusually pleasant once the initial adjustment is done.</p><p><strong>The practical answer for a total beginner:</strong> if you don’t know JavaScript yet, Flutter’s learning curve is arguably more self-contained. Dart and Flutter’s widget system are learned together as one coherent thing, with fewer surrounding ecosystem decisions to make. If you already know JavaScript or plan to work across web and mobile, React Native lets you reuse a large amount of what you already know.</p><h3>2. The Job Market, Broken Down by What You’re Optimizing For</h3><p>React Native currently posts roughly six times more job listings than Flutter, which matters enormously if your priority is <em>volume of opportunity</em>, more open roles, more companies to apply to, and more geographic flexibility. This mirrors a talent pool that’s three to five times larger overall, so the job-to-candidate ratio isn’t wildly different from Flutter’s — there’s more demand, but also more supply.</p><p>Flutter, meanwhile, has overtaken React Native in raw developer adoption and commands a modest salary premium in many markets, a classic smaller-but-hungrier-market signal. Fewer roles, somewhat less competition per role, and companies specifically choosing Flutter tend to be ones making a deliberate, considered bet on it (rather than defaulting to “everyone knows JavaScript”), which can mean more design-forward, product-focused teams to work with.</p><p><strong>If you’re optimizing for your first job, fastest:</strong> React Native’s sheer volume of listings works in your favor, especially if you already know JavaScript from web development. You’re not starting from zero; you’re extending.</p><p><strong>If you’re optimizing for a specific kind of work</strong> — consumer apps with heavy custom design or teams that have made Flutter a deliberate long-term bet — learning Flutter can be a differentiator precisely because fewer developers have it, and the demand-to-supply ratio can favor you in specific companies and interviews.</p><h3>3. Transferable Skills: What You’re Really Investing In</h3><p>This is the question most new developers forget to ask, and it matters more over a ten-year career than over the next job search.</p><p>Learning <strong>React Native</strong> is really learning <strong>React</strong> with a mobile skin on top. That investment transfers directly to web development (React is the dominant frontend library on the web), to React-based meta-frameworks, and to any company running React anywhere in its stack. This is the single strongest argument for React Native as a first framework to learn: the skill underneath it is useful far beyond mobile.</p><p>Learning <strong>Flutter</strong> is really learning <strong>Dart and the Flutter widget model</strong>, which transfers cleanly across Flutter’s own multi-platform targets (mobile, web, desktop) but has a smaller footprint outside the Flutter ecosystem itself, since Dart isn’t widely used outside of it. The compensating factor is that the skill is <em>narrower but deeper</em> — you become fluent in one coherent, well-designed system rather than one layer of a much larger, more fragmented JavaScript ecosystem.</p><p><strong>A useful way to frame it:</strong> React Native teaches you a widely applicable skill (React) via a mobile use case. Flutter teaches you a mobile-and-multi-platform-specific skill exceptionally well, in a more self-contained way. Neither is the “wrong” investment; they’re different shapes of investment.</p><h3>4. What to Actually Build First</h3><p>Advice is only useful if it’s specific. Here’s a concrete on-ramp for each:</p><p><strong>If you’re starting with React Native:</strong></p><ol><li>Build a small habit tracker or to-do app using only local state — no backend yet. This forces you to learn React’s component and state model without other distractions.</li><li>Add a real backend (Firebase or a simple REST API) and handle loading/error states properly; this is where most junior developers’ apps fall apart and where you’ll actually learn something.</li><li>Add one native-feeling touch: push notifications, camera access, or a native navigation pattern. This is the moment “web developer” starts to feel like “mobile developer.”</li></ol><p><strong>If you’re starting with Flutter:</strong></p><ol><li>Build a small app using nothing but StatelessWidget and StatefulWidget to internalize Flutter’s core widget-tree mental model before reaching for state management libraries.</li><li>Introduce a state management approach (Provider or Riverpod are the most commonly recommended starting points) once the basic widget model feels natural, not before.</li><li>Ship it to both iOS and Android from the same codebase, and pay attention to the handful of places platform differences still leak through; this is where Flutter’s “write once” promise gets tested in practice.</li></ol><h3>5. A Decision Checklist for New Developers</h3><p>Ask yourself, honestly:</p><ol><li>Do I already know JavaScript from web development? If yes, React Native’s learning curve is dramatically shorter for me specifically, regardless of general averages.</li><li>Am I trying to maximize the number of jobs I can apply to in the next six months, or the distinctiveness of my skill set in a smaller pool?</li><li>Do I care about web development as a parallel or future path? If yes, React’s transferability is a meaningful long-term argument in React Native’s favor.</li><li>Am I drawn to highly custom, design-forward UI work? Flutter’s widget model rewards that instinct more directly than React Native’s more platform-native default styling.</li><li>Is there a specific local job market I’m targeting? Global statistics are a starting point, not a substitute for looking at actual listings in your city or target companies.</li></ol><h3>Closing: Two Audiences, One Underlying Truth</h3><p>Whether you’re a CTO signing off on a five-year engineering bet or a new developer deciding what to learn this quarter, the underlying truth doesn’t change: <strong>both frameworks are mature enough that the deciding factors are rarely about the frameworks themselves.</strong> For companies, it’s about existing team composition, product roadmap, and long-term maintenance appetite. For new developers, it’s about what you already know, what kind of work you want to be doing, and how much you value breadth of transferable skill versus depth in a more specialized, cohesive toolchain.</p><p>The frameworks have both done the hard work of becoming genuinely production-ready. What’s left is a decision about <em>you</em> and your organization, not a decision about which framework wins an argument on the internet.</p><p><em>Originally published at </em><a href="https://damscozy.hashnode.dev/react-native-vs-flutter-the-complete-breakdown-for-companies-and-new-developers"><em>https://damscozy.hashnode.dev</em></a><em> on July 26, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30636bddb588" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HNG8 Virtual Internship: My Goals, ambitions and expectations.]]></title>
            <link>https://adeyeyeadedamola.medium.com/hng8-virtual-internship-my-goals-ambitions-and-expectations-173298779688?source=rss-26d84c1f32f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/173298779688</guid>
            <category><![CDATA[hnginternship]]></category>
            <category><![CDATA[zuri-training]]></category>
            <category><![CDATA[hng]]></category>
            <category><![CDATA[hngi8-x-i4g]]></category>
            <category><![CDATA[hngi8]]></category>
            <dc:creator><![CDATA[Adeyeye Adedamola]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 11:26:28 GMT</pubDate>
            <atom:updated>2021-08-19T11:26:28.743Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*3yZTbjYD6cDzDQIg.png" /><figcaption>HNGi8 X I4G</figcaption></figure><p>HNG is an acronym for <a href="https://hotel.ng/">Hotel.ng</a>, a premier hotel booking platform owned by Mark Essien, a tech entrepreneur who is poised to train and empower talents in the tech ecosystem in Nigeria and beyond.</p><p>Mark Essien came up with an idea of a virtual(remote) <a href="https://internship.zuri.team/">internship programme</a> to solve the problem of distance and time. This means anyone anywhere can take part in the program at any time zone.</p><p><strong>HNG GOALS</strong></p><p>The programme is popular for the networking opportunity of bringing together thousands of software developers from all over the country. It gives you the feel of being in the same room with other professionals to share ideas and acquire skills.</p><p><strong>MY GOAL FOR HNG8</strong></p><p>(The 8th edition) is to ensure that I become a finalist and winning. Being a finalist means that you have survived all evictions by completing all tasks as at when due and you are not relenting. Also, being a finalist invariably means that I have acquired the skills to become a world-class software developer.</p><p>In particular, I wish to acquire competency in the following frameworks:</p><p><strong>CONCLUSION</strong></p><p>Since its inception, <a href="https://training.zuri.team/">HNG Internship</a> has turned out seven batches of world-class software developers each year through a competitive environment where only the best can survive till the last stage. Hopefully, I wish to join the eighth batch of elite software developers.</p><p>If you want to participate in HNG internship, this <a href="https://internship.zuri.team/">Link</a> will take you to the waiting arms of a team waiting to create talents out of you.</p><p>Below are some beginner resources for getting started with software development.</p><blockquote>· <a href="https://trydesignlab.com/figma-101-course/introduction-to-figma/">Introduction to Figma</a></blockquote><blockquote>· <a href="https://www.freecodecamp.org/news/what-is-git-and-how-to-use-it-c341b049ae61/">Introduction to GIT</a></blockquote><blockquote>· <a href="https://www.youtube.com/watch?v=qz0aGYrrlhU">Introduction to HTML</a></blockquote><blockquote>· <a href="https://www.youtube.com/watch?v=W6NZfCO5SIk">Introduction to JavaScript</a></blockquote><p><strong>APPRECIATION</strong></p><p>My appreciation goes to the <a href="https://zuri.team/">ZURI TEAM</a> for making this program available to all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=173298779688" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Relevance of Usability Heuristics for User Interface Design to User experience across device…]]></title>
            <link>https://adeyeyeadedamola.medium.com/relevance-of-usability-heuristics-for-user-interface-design-to-user-experience-across-device-1bbe4db56e0e?source=rss-26d84c1f32f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bbe4db56e0e</guid>
            <dc:creator><![CDATA[Adeyeye Adedamola]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 11:19:27 GMT</pubDate>
            <atom:updated>2021-03-15T11:19:27.700Z</atom:updated>
            <content:encoded><![CDATA[<h3>Relevance of Usability Heuristics for User Interface Design to User experience across device platforms.</h3><p><strong>What is Heuristics Evaluation?</strong><br>Heuristic evaluation is a process where experts use rules of thumb to measure the usability of user interfaces in independent walkthroughs and report issues.</p><p><strong>10 Usability Heuristic for User Interface Design .</strong></p><blockquote>1. Visibility of system Status: Keep users informed about its status appropriately and promptly using feedback.<br>2. Match between system and Real world: Show information in users language, ways users understand from how the real world operates by making the information appear natural and logical.<br>3. User control and Freedom: Users are meant to make mistake while performing actions, They need to be shown and offer users control and let them undo errors easily.<br>4. Consistency and Standards: Using a consistent platform and industry conventions so users are not confused over what different words or icons means.<br>5. Error Prevention: A system should have a good error message and either avoid conditions where errors arise or warn users before they take risky actions.<br>6. Recognition rather than recall: Reduce the information that users have to remember by being consistent with your designs.<br>7. Flexibility and efficiency of use: Creating a form of shortcut for users by allowing users to tailor frequent actions.<br>8. Aesthetic and minimalist design: Keep the content and visual design of UI focus on the essentials by making use of the relevant information.<br>9. Help users recognize, diagnose, and recover from errors: Error message should e expressed in plain language.<br>10. Help and Documentation: List concise steps to be carried out, provide necessary documentation to help users understand how to complete their tasks.</blockquote><blockquote><strong>How to Conduct Heuristic Evaluation</strong><br>1. Know what you will test and how<br>2. Understand your users<br>3. Conduct the heuristic walk-through<br>4. Collect results<br>5. Analyse the results<br>6. Brief the evaluators.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bbe4db56e0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>