<?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 Sylvester Marquant on Medium]]></title>
        <description><![CDATA[Stories by Sylvester Marquant on Medium]]></description>
        <link>https://medium.com/@King_Marquant?source=rss-23d5318fa885------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jmg3OoifsbMvBYxo2rIa0Q.jpeg</url>
            <title>Stories by Sylvester Marquant on Medium</title>
            <link>https://medium.com/@King_Marquant?source=rss-23d5318fa885------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:48:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@King_Marquant/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[From Visual Builder to React SPA: How I Made the Jump as a Designer Learning to Code]]></title>
            <link>https://medium.com/@King_Marquant/from-visual-builder-to-react-spa-how-i-made-the-jump-as-a-designer-learning-to-code-314254ac27e9?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/314254ac27e9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design-engineer]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 18:52:02 GMT</pubDate>
            <atom:updated>2026-03-09T18:52:02.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rGleu1A8kb11r9qwFw5VSw.jpeg" /></figure><p>I am a designer who codes. Or more accurately, I am a designer who is <em>learning</em> to code, and slowly closing the gap between those two things.</p><p>For a long time, Webflow was the bridge. It let me build real, production-quality sites without needing to touch a bundler or think about a component architecture. For client work, it is still one of the best tools I know. Fast to build, beautiful to design in, and powerful enough for most use cases.</p><p>But recently, a client came to me with a problem that pushed me past what Webflow could comfortably solve and in solving it, I learned more about frontend engineering in a few weeks than I had in months of reading documentation.</p><p>This is the story of that migration, what made it possible, and what I would tell any designer standing at the same edge.</p><h3>The Conversation That Started It</h3><p>My client was growing. Their Webflow plan was scaling with them, and the monthly hosting cost had become a real conversation. They were also running into friction with the product itself, wanting more control over how certain interactions worked, how data was handled, how the application behaved. Webflow is excellent, but it is a managed environment. At some point, managed environments cost you either money or flexibility. For this client, it was starting to cost both.</p><p>The question on the table was simple: <em>what would it look like to own the infrastructure ourselves?</em></p><p>I knew the answer technically , a React SPA, hosted on a modern edge platform, would give us full control and dramatically lower running costs. What I was less sure about was if I could actually build it. I was a designer who had been writing HTML and CSS for years and picking up JavaScript and React piece by piece. A full migration of a production site was a different level of commitment.</p><p>This is where AI changed the equation.</p><h3>Building With a Co-Pilot</h3><p>I want to be specific here, because I think the honest version of this story is more useful than the polished one.</p><p>There were parts of this migration I could not have done on my own, not yet. The Vite configuration, the bundle splitting strategy, the performance optimisations. I understood the <em>concepts</em>, but translating them into correct, production-ready code was beyond where my skills currently sit.</p><p>I used Gemini and Antigravity throughout the process, and the way I used them mattered. I was not copy-pasting solutions I did not understand. I was using AI as a combination of senior engineer, tutor, and debugging partner by asking it to explain <em>why</em> something worked, not just <em>what</em> to write. Every time I got a code snippet, I read it line by line and asked follow-up questions until I understood it. This approach is slower. It is also the only approach that actually builds skill. Here is what that looked like in practice across the five core challenges of the migration.</p><h4>1. Purge the Export Bloat</h4><p>When you export a Webflow project, you get a folder full of auto-generated image variants — files Webflow creates for its own CDN. On your own stack, they serve no purpose.</p><pre>/assets<br>  hero.jpg<br>  hero-p-500.webp    ← generated for Webflow&#39;s CDN<br>  hero-p-800.webp    ← not needed on your stack<br>  hero-p-1080.webp   ← delete these<br>  hero-p-1600.webp</pre><p>This was the simplest step, but it was a useful lesson: <strong>exported code is not clean code.</strong> It is code optimised for someone else’s infrastructure. The first job of the migration was to strip it back to what we actually owned.</p><h4>2. Take Control of the Bundler</h4><p>This is where I first leaned heavily on AI assistance.</p><p>I understood the problem — a default Vite build produces a single JavaScript bundle, meaning every update forces returning users to re-download everything, including libraries that have not changed. What I did not fully understand was how to configure Rollup to fix it.</p><p>I asked Gemini to explain the mental model first: <em>why</em> do we split chunks, <em>what</em> determines how we group them, <em>what</em> happens in the browser’s cache as a result. Only once I understood that did I ask for the actual configuration.</p><pre>// vite.config.ts<br>import { defineConfig } from &#39;vite&#39;;<br>import react from &#39;@vitejs/plugin-react&#39;;<br><br>export default defineConfig({<br>  plugins: [react()],<br>  build: {<br>    target: &#39;es2022&#39;,<br>    rollupOptions: {<br>      output: {<br>        manualChunks: {<br>          // Changes only when you upgrade React itself<br>          &#39;vendor-react&#39;: [&#39;react&#39;, &#39;react-dom&#39;, &#39;react-router-dom&#39;],<br><br>          // Changes on your release cycle<br>          &#39;vendor-ui&#39;: [&#39;react-hook-form&#39;, &#39;framer-motion&#39;],<br><br>          // Heavy, stable utilities — almost never changes<br>          &#39;vendor-heavy&#39;: [&#39;date-fns&#39;, &#39;zod&#39;],<br>        },<br>      },<br>    },<br>  },<br>  esbuild: {<br>    // Strip debug logs in production automatically<br>    pure: [&#39;console.log&#39;, &#39;console.info&#39;, &#39;console.debug&#39;],<br>  },<br>});</pre><p>The principle: group things that change together, separate things that change at different rates. A returning user whose browser has already cached vendor-react and vendor-heavy only downloads the small slice that actually changed. On a production application, this can mean the difference between a 600kB re-download and a 40kB one.</p><h4>3. Fix the Largest Contentful Paint</h4><p>As a designer, this one hit differently because it was a design pattern I had been using for years that turned out to be a performance anti-pattern. Webflow sets hero images via CSS background classes. It looks clean in the visual editor. But it means the browser cannot discover your most important image until <em>after</em> it has downloaded and parsed your entire stylesheet. On slow connections, that sequence costs seconds.</p><p>The fix is to move the hero image out of CSS entirely and place it directly in the HTML as a &lt;picture&gt; element:</p><pre>// ❌ The Webflow pattern — image hidden in CSS<br>// .hero { background-image: url(https://medium.com/&#39;/images/hero.jpg&#39;); }<br><br>// ✅ The correct pattern — image visible to the browser immediately<br>export function HeroSection() {<br>  return (<br>    &lt;section className=&quot;hero-section&quot;&gt;<br>      &lt;picture className=&quot;hero-background&quot;&gt;<br>        &lt;source<br>          media=&quot;(min-width: 1024px)&quot;<br>          srcSet=&quot;/images/hero-desktop.webp&quot;<br>        /&gt;<br>        &lt;img<br>          src=&quot;/images/hero-mobile.webp&quot;<br>          alt=&quot;&quot;<br>          fetchPriority=&quot;high&quot;<br>          decoding=&quot;async&quot;<br>          loading=&quot;eager&quot;<br>        /&gt;<br>      &lt;/picture&gt;<br><br>      &lt;div className=&quot;hero-content&quot;&gt;<br>        &lt;h1&gt;Your Headline Here&lt;/h1&gt;<br>      &lt;/div&gt;<br>    &lt;/section&gt;<br>  );<br>}</pre><p>fetchpriority=&quot;high&quot; tells the browser this is the most important asset on the page, start fetching it immediately, ahead of everything else. The browser finds it during the initial HTML parse, before it has touched a single stylesheet.</p><p>I understood intuitively <em>that</em> this was better. What I needed AI to help me understand was <em>why</em> — specifically, what the browser’s critical rendering path actually looks like and where CSS background images fall in that sequence. That explanation is what made the fix stick rather than just being something I copied. An extra tip, <strong>WEBP would save you some kilobytes, AVIF would save you more</strong> .Optimize your Images to be either WEBP OR AVIF formats.</p><h4>4. Build a Predictive Router</h4><p>Lazy-loading routes keeps the initial bundle small but it creates a subtle flicker of latency when a user clicks a link, while the browser fetches that route’s code.</p><p>The solution is to prefetch route code the moment a user shows intent: cursor entering a link on desktop, thumb touching the screen on mobile.</p><pre>// components/PrefetchLink.tsx<br>import { useRef } from &#39;react&#39;;<br>import { Link, LinkProps } from &#39;react-router-dom&#39;;<br><br>interface PrefetchLinkProps extends LinkProps {<br>  onPrefetch?: () =&gt; void;<br>}<br><br>export function PrefetchLink({ onPrefetch, ...props }: PrefetchLinkProps) {<br>  const hasPrefetched = useRef(false);<br><br>  const triggerPrefetch = () =&gt; {<br>    if (!hasPrefetched.current &amp;&amp; onPrefetch) {<br>      onPrefetch();<br>      hasPrefetched.current = true;<br>    }<br>  };<br><br>  return (<br>    &lt;Link<br>      {...props}<br>      onMouseEnter={triggerPrefetch}<br>      onTouchStart={triggerPrefetch}<br>    /&gt;<br>  );<br>}</pre><p>Wired to a lazy-loaded route:</p><pre>const PricingPage = lazy(() =&gt; import(&#39;./pages/PricingPage&#39;));<br><br>&lt;PrefetchLink<br>  to=&quot;/pricing&quot;<br>  onPrefetch={() =&gt; import(&#39;./pages/PricingPage&#39;)}<br>&gt;<br>  Pricing<br>&lt;/PrefetchLink&gt;</pre><p>By the time the click registers, the module is already in memory. The transition feels instant because the network work happened 200–400ms earlier.</p><p>This was one of the patterns where debugging with AI was most valuable. Getting the useRef guard right , ensuring prefetching only fires once per element no matter how many times a user hovers — took a few iterations, and having a tool that could both spot the bug and explain <em>why</em> it was a bug accelerated that loop significantly.</p><h4>5. Rebuild the Analytics Bridge</h4><p>This one breaks silently, which makes it the most dangerous.</p><p>GA4 only records full page loads. In an SPA, React swaps content without reloading the page so after the first landing, every subsequent navigation goes untracked. You can go weeks with completely wrong data before you notice.</p><p>The fix is a small hook that manually pushes a page_view event to the Google Tag Manager data layer on every route change:</p><pre>// hooks/usePageTracking.ts<br>import { useEffect } from &#39;react&#39;;<br>import { useLocation } from &#39;react-router-dom&#39;;<br><br>export function usePageTracking() {<br>  const location = useLocation();<br><br>  useEffect(() =&gt; {<br>    if (typeof window === &#39;undefined&#39; || !window.dataLayer) return;<br><br>    window.dataLayer.push({<br>      event: &#39;page_view&#39;,<br>      page_path: location.pathname,<br>      page_search: location.search,<br>    });<br>  }, [location.pathname, location.search]);<br>}</pre><p>Mount it once at your app root, inside the router:</p><pre>function AppContent() {<br>  usePageTracking();<br><br>  return (<br>    &lt;Routes&gt;<br>      &lt;Route path=&quot;/&quot; element={&lt;HomePage /&gt;} /&gt;<br>      &lt;Route path=&quot;/pricing&quot; element={&lt;PricingPage /&gt;} /&gt;<br>      &lt;Route path=&quot;/contact&quot; element={&lt;ContactPage /&gt;} /&gt;<br>    &lt;/Routes&gt;<br>  );<br>}</pre><h3>What the Client Got</h3><p>Lower hosting costs were the starting point of this conversation. They ended up getting that, and more faster load times, full control over the product architecture, and a codebase that can grow without hitting the ceiling of a managed platform.</p><p>But honestly, the outcome I care about most is more personal than that.</p><h3>What I Got</h3><p>I came into this migration as a designer who codes. I came out of it with a clearer picture of what design engineering actually means in practice, not just knowing how to use components, but understanding the infrastructure decisions that sit underneath them.</p><p>AI tools did not write this migration for me. They could not . The decisions about what to build, how to structure it, and how to explain the tradeoffs to a client were mine to make. What they did was compress the distance between where my skills currently are and what the project required. They helped me write code I was not yet fluent in, debug problems I did not have a mental model for, and understand concepts that would have taken me weeks to piece together from documentation alone.</p><p>That compression is real and worth talking about honestly. Not as a shortcut but as scaffolding that lets you build faster than you would otherwise be able to, while still doing the work of actually learning.</p><p>The gap between designer and engineer is not as wide as it used to be. Tools like Claude Gemini, Cursor and Antigravity are not closing it for you. They are just making it more crossable.</p><h3>What Comes Next</h3><p>That experience, closing the gap between a design idea and a working product is exciting and that is what led me to start building <strong>MockupReel</strong>.</p><p>One thing I kept running into while presenting this project and others to clients was the friction of showing off the work. You have a screen recording. You want it to look polished for a demo, a presentation, or a product launch. But dropping a raw screen recording into a slide or a portfolio feels unfinished and reaching for a design tool to wrap it in a device frame adds another step, another file, another back-and-forth.</p><p>MockupReel solves that in the browser, instantly. Upload your screen recording, and it wraps it in a stunning iPhone or Android mockup, no design software, no downloads, no friction. It is built specifically for the moment between finishing the work and showing it to the world.</p><p>It is going to be free, browser-based, no watermarks and built by a designer who got tired of of that gap existing.</p><p>The waitlist is live now at <a href="https://mockupreel.studio/"><strong>mockupreel.studio</strong></a> — if you build apps, ship products, or present work to clients, I think you will find it useful.</p><p>You can also follow the build in public on X at <a href="https://x.com/mockupreel"><strong>@mockupreel</strong></a>.</p><p>Are you on a similar journey ? A designer moving into engineering, or engineer picking up design depth? Building something of your own while sharpening your skills? I’d genuinely like to hear how you’re navigating it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=314254ac27e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The invisible Product]]></title>
            <link>https://medium.com/@King_Marquant/the-invisible-product-73661671fb12?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/73661671fb12</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 18:21:33 GMT</pubDate>
            <atom:updated>2025-08-26T18:21:33.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uHxRyDWouL-VfPIy2wEybg.png" /><figcaption>a motherboard architecture</figcaption></figure><p>Most times as designers we think of products as a series of features (I have been here too) . A checklist of what it does. We design for the “WHAT” and in doing that, we often times miss the “WHY”. Over the years with learning and designing experiences for users, I have come to understand that we just don’t design screens — we design for a calling, a purpose if I must say. People don’t want a camera app; they want to capture a memory. They don’t want a music player; they want to lose themselves in a song. They don’t want a phone; they want a direct line to the people they love.</p><p>The great products don’t just do something, they enable a purpose. Our job as designers isn’t to only draw boxes on a screen. Our job is to strip away every layer of complexity until all that’s left is pure purpose. We create an effortless path from a person’s intention to their action. It’s not about making a product that works. It’s about making a product that feels inevitable. It’s about designing a reality so simple, so elegant, and so obvious, that the user can’t imagine a world without it. That’s the ultimate product,and that’s the ultimate design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73661671fb12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Illustrator-to-Figma Pipeline: A Guide to Clean, Editable SVGs]]></title>
            <link>https://medium.com/@King_Marquant/the-illustrator-to-figma-pipeline-a-guide-to-clean-editable-svgs-cb71ba3d31d9?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb71ba3d31d9</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[illustration]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 17:49:51 GMT</pubDate>
            <atom:updated>2025-08-05T17:49:51.987Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bridging the gap between illustration and UI design without losing quality or control.</h4><p>You’ve spent hours perfecting your illustrations in Adobe Illustrator, the lines are clean, the colors pop, and the character is full of life. But when you drag it into Figma, something feels… off.</p><ul><li>The strokes are too thin.</li><li>The colors don’t match.</li><li>The layers are gone.</li><li>You can’t edit individual parts.</li></ul><p>Sound familiar?</p><p>You’re not doing anything wrong, you just need the right export settings and a smart workflow.<br>I recently picked up vector illustration about 2 weeks ago to add to my skill repository and it has been a bitter sweet experience. I am not writing to teach you about illustration, we have Ufot Ubon’s course for that which you can buy here: <a href="https://selar.com/713r72">https://selar.com/713r72</a> , I am writing for those that want to prepare, export, and import their Illustrator artwork into Figma so it stays clean, scalable, and fully editable.</p><h4>Why does this matter?</h4><p>Illustrator is the best tool for creating vector illustrations (if you illustrate on Figma, good for you but this article is for the Adobe Illustrator believers 😎, Amen? Amen). Moving artwork between Illustrator &amp; Figma isn’t always seamless, unless you know the hidden settings that make all the difference ( I didn’t initially, so if you are in the same boat right now, knowledge has come).</p><h4>Step 1: Prepare Your Artwork in Illustrator</h4><p>Before you export, your artwork must be clean, organized, and ready.</p><p>🔹<strong> 1.1 Outline All Strokes</strong><br>Thin strokes can disappear in Figma when scaled.<br> To fix it:<br>Select all stroked paths.<br>Go to:Object &gt; Path &gt; Outline Stroke<br>After outlining ensure to give a stroke color and stroke width then you can go ahead and use the shape builder tool to clean up overlapping lines. Now your lines are solid shapes, they’ll never vanish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQNsK676ORLu_u947QOkSg.gif" /><figcaption>outlining strokes using Adobe Illustrator</figcaption></figure><p>🔹<strong> 1.2 Expand Appearance &amp; Live Paint</strong></p><p>If you used:<br>Live Paint<br>Width profiles<br>Brushes<br>Effects (like drop shadows)</p><p>Expand them:<br>Select artwork → Object &gt; Expand Appearance<br>If Live Paint: Object &gt; Live Paint &gt; Expand</p><p>This converts everything into basic vector shapes which are Figma-friendly.<br><strong><em>Point to Note: Ungroup Everything</em></strong><br>Figma works best with flat, simple groups. so always ensure to ungroup after expanding.</p><p>To ungroup:<br>Object &gt; Ungroup (repeat until all groups are gone)<br>Or use Shift + Ctrl/Cmd + G multiple times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wgu32OqKEI1kWLuXOgkRXw.gif" /><figcaption>livepaint make and expand and ungrouping</figcaption></figure><p><strong>🔹 1.3 Use RGB Color Mode<br></strong>Figma uses RGB, not CMYK.</p><p>To Check your settings:<br>File &gt; Document Color Mode → must be RGB Color</p><p>If it’s CMYK, colors will look dull in Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRMU-MKzzndjVopUU-zAQw.gif" /></figure><h4>Step 2: Organize for Figma (Even If You’re Solo)</h4><p>Figma doesn’t preserve Illustrator layer names but group names often survive.</p><p>🔹 <strong>2.1. Name Your Groups Meaningfully<br></strong>Instead of importing a file with dozens of &lt;Group&gt; layers, you can have a clean panel.</p><p><strong>Best Practice:</strong> Rename your final, logical groups before exporting.</p><ul><li><em>Bad:</em> Group 1, Group 2, Copy of Group 1</li><li><em>Good:</em> Head, Left-Eye, Hair, Jacket</li></ul><p>To rename, select a group in the Layers Panel and double-click its name. This simple act of organization will save you immense time in Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*nOJlVwVyuBWgcAlAr47QhQ.png" /><figcaption>layers/groups named in Adobe Illustrator</figcaption></figure><p>🔹 <strong>2.2. Keep a backup Layer</strong></p><p>Once you outline strokes and expand appearances, your artwork is harder to edit in Illustrator. Always work on a copy.</p><p><strong>Best Practice:</strong></p><ol><li>Create two main layers in your .ai file.</li><li><strong>Original Art</strong>: Keep your original, editable illustration here. Lock and hide this layer before exporting.</li><li><strong>Figma Export</strong>: Duplicate your art onto this layer. Perform all the sanitization steps (outlining, expanding) here. This is your export-ready version.</li></ol><h3>Step 3: Exporting as SVG</h3><p>This is the most critical step. Using Illustrator’s default SVG settings will break your artwork in Figma.</p><p>Go to File &gt; Export &gt; Export As... and select SVG as the format. In the SVG Options dialog, apply these settings precisely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*9ipbbRRYhojHehYuRqLenQ.png" /><figcaption>SVG export settings</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*S3ZB-m_J9Mdu4MNGEeqlNg.png" /><figcaption>Settings values and why they matter</figcaption></figure><p><strong><em>Pro Tip:</em></strong> Use Decimal Places = 1 for icons, 2 for detailed art<br>Save these settings and then export</p><h3>Step 4: Import and Finalize in Figma</h3><p>Drag your newly exported .svg file directly onto the Figma canvas.</p><p><strong>What to Expect:</strong></p><ul><li>The SVG will import as a single frame, containing the groups you named in Illustrator. If you didn’t name them, you’ll see a list of generic &lt;Group&gt; layers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/228/1*fXRtRjWORnI9KPaO8fk-1w.png" /><figcaption>Unnamed groups exported and how they appear in figma</figcaption></figure><ul><li>All shapes will be true vectors, ready for modification. You can change fills, edit anchor points, and resize losslessly.</li></ul><p><strong>Immediate Actions:</strong></p><ol><li><strong>Ungroup and Conquer:</strong> Select the main SVG frame and press Shift + Ctrl/Cmd + G to release the contents. Now you can select and manipulate individual parts freely.</li><li><strong>Recolor with Styles:</strong> Use Figma’s selection color tools to update fills. For design system work, immediately apply your established Color Styles for consistency.</li><li><strong>Componentize Your Art:</strong> Turn recurring elements into Components. Select the “Head” group, right-click, and choose Create Component. Now you can create variants for different expressions (happy, sad, surprised) and build a scalable illustration system.</li></ol><h3>Common pitfalls and how to avoid them</h3><ul><li><strong>Problem: My lines look thin or vanish.</strong></li><li><strong>Solution:</strong> You forgot to Outline Stroke in Illustrator before exporting.</li><li><strong>Problem: My colors are muted and look wrong</strong></li><li><strong>Solution:</strong> Your Illustrator document was in CMYK mode. Switch it to RGB and re-export.</li><li><strong>Problem: I can’t find anything in Figma’s layers panel.</strong></li><li><strong>Solution:</strong> You didn’t name your <em>groups</em> in Illustrator. Naming layers is not enough.</li><li><strong>Problem: The SVG file is huge.</strong></li><li><strong>Solution:</strong> Ensure Minify is checked during SVG export. For further optimization, you can use a tool like <a href="https://jakearchibald.github.io/svgomg/">SVGOMG</a>.</li><li><strong>Problem: I can’t edit individual shapes.</strong></li><li><strong>Solution:</strong> Your artwork is still in a master group. Select it in Figma and ungroup (Shift + Ctrl/Cmd + G).</li></ul><h4>Some tips I have picked up that might come in handy for you:</h4><h4>1. Enforce Pixel-Perfect Alignment</h4><p>Any artwork for a digital screen, sharpness is non-negotiable. Snap to Pixel forces your vector paths to align with the underlying pixel grid, preventing the soft, anti-aliased edges that occur when anchor points land on sub-pixel coordinates.</p><ul><li><strong>How:</strong> In Illustrator, go to View &gt; Snap to Pixel.</li><li><strong>Why it matters:</strong> This ensures your icons and illustrations remain crisp and clean, especially when rendered at smaller sizes in a user interface.</li></ul><h4>2. Treat the Browser as Your Litmus Test</h4><p>Before importing into Figma, do a final check. A web browser’s rendering engine is the ultimate test for SVG compatibility. Since Figma is built on web technologies, how your SVG appears in the browser is an almost perfect indicator of how it will behave in Figma.</p><ul><li><strong>How:</strong> Simply drag and drop your .svg file into a new Chrome or Firefox tab.</li><li><strong>Why it matters:</strong> This five-second step can save you minutes of frustration. If it looks broken, distorted, or has missing elements in the browser, it will be broken in Figma. You can instantly spot issues this way.</li></ul><h4>3. Protect Your Master File: The Single Source of Truth</h4><p>Your exported SVG is a disposable, optimized <em>output</em>. Your original Illustrator (.ai) file is the editable, non-destructive <em>source</em>. Never confuse the two.</p><ul><li><strong>How:</strong> Always make edits in your original .ai file, which contains the live strokes, effects, and layers. Then, re-export a new SVG.</li><li><strong>Why it matters:</strong> Attempting to edit an exported SVG is a destructive process that works against a scalable workflow. Maintaining a master file ensures you always have full control and can make changes efficiently without rebuilding your artwork from a flattened state.</li></ul><h4>4. Optimize with Dedicated Tools (Optional)</h4><p>While Illustrator’s Minify setting is good, dedicated tools offer superior optimization for performance-critical applications.</p><ul><li><strong>How:</strong> Upload your SVG to a web-based tool like <a href="https://jakearchibald.github.io/svgomg/"><strong>SVGOMG</strong></a>. It provides a visual interface to surgically remove redundant code, clean up decimal precision, and strip out editor-specific metadata.</li><li><strong>Why it matters:</strong> For web projects, every kilobyte counts. A hyper-optimized SVG leads to faster load times and cleaner code, which is a best practice for front-end development and overall performance.</li></ul><p>Final thoughts:<br><strong><em>The Illustrator-to-Figma pipeline isn’t broken, it just needs the right settings.</em></strong></p><p>By following this guide, you’re no longer exporting blind. You’re exporting with confidence, knowing your illustrations will arrive in Figma exactly as you intended: sharp, vibrant, and ready to be integrated into any design system or prototype.</p><h4>Putting It Into Practice</h4><p>Here are some illustrations I’ve created using this exact workflow since I began learning two weeks ago, with most concepts inspired by finds on Pinterest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOIZaqqmIeGMg2a0zvAOTg.png" /><figcaption>My 2nd ever illustration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*eUemP-ZKSRY5fAW_sUjlgg.png" /><figcaption>my 3rd illustration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*xHb4chTMJ-eaQcWvP9-Wjg.jpeg" /><figcaption>My latest Illustration used as a desktop wallpaper, a great way to see your scalable art in action.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb71ba3d31d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From On-Ramp to Ecosystem: Designing the Payment Gateway for Africa’s Digital Future]]></title>
            <link>https://medium.com/@King_Marquant/from-on-ramp-to-ecosystem-designing-the-payment-gateway-for-africas-digital-future-056baad9b71a?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/056baad9b71a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Wed, 23 Jul 2025 18:36:47 GMT</pubDate>
            <atom:updated>2025-07-23T18:36:47.298Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Product Design Case Study</h3><h3>The Question That Started Everything</h3><p>In the bustling digital marketplaces of Africa, from Lagos to Nairobi, a revolution is happening. Millions of entrepreneurs are building businesses online. At the same time, a new generation of users is embracing cryptocurrency. Yellow Card has masterfully built the bridge between these two worlds with its trusted crypto on-ramp.</p><p>But I saw a gap. A question that wasn’t being answered: <strong>What happens next?</strong></p><p>What happens after you buy crypto? How do you use it? How does that Instagram vendor in Lekki, Nigeria accept a payment from a customer in Accra, Ghana without wrestling with volatility and complex wallet addresses?</p><p>The biggest opportunity wasn’t just in helping people <em>buy</em> crypto, but in helping them <em>use</em> it. I set out to design the answer: a product that could transform Yellow Card from a bridge into the very backbone of Africa’s emerging digital economy.</p><h3>The Solution: A B2B Gateway Built for Three People</h3><p>My solution was to conceptualize the <strong>“Yellow Card Pay” Gateway</strong> — a B2B product that lets any online business accept crypto payments from anyone, anywhere, and get settled instantly in their local currency.</p><p>To succeed, this product couldn’t just be a piece of technology. It had to be a seamless experience designed for three distinct people whose needs all had to be met at once:</p><ol><li><strong>The Merchant:</strong> The busy entrepreneur who needs simplicity and trust.</li><li><strong>The Developer:</strong> The builder who needs speed and reliability.</li><li><strong>The Customer:</strong> The end-user who needs confidence and clarity.</li></ol><h3>1. Empowering the Merchant: The 5-Minute Setup</h3><p>A merchant’s trust is hard-won and easily lost. They don’t have time for complex configurations. The dashboard I designed focuses on getting them from “What is this?” to “I’m ready to get paid” in minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Y1R_2wTIEHPQY32YWnyAA.jpeg" /><figcaption>merchant dashboard to setup crypto payment overview</figcaption></figure><p>My design philosophy was <strong>“guided control.”</strong> Instead of overwhelming them with options, I created a clean, step-by-step flow. The most critical decision was to provide curated, high-contrast button themes (Vibrant, Neutral, Light) instead of a free-form color picker and also the option to choose either rounded or sharp borders for the button. This ensures every &quot;Pay with Yellow Card&quot; button is accessible, professional, and builds brand recognition, while still giving merchants the flexibility to match their own site&#39;s aesthetic. The live preview gives them the confidence that what they see is what they&#39;ll get. Finally, to bridge the gap between the business owner and the builder, the page concludes with a simple <strong>Installation Guide</strong>. This provides a one-click “Copy Code” button for the technical founder who does it all, while also serving as a clear, foolproof handoff for a non-technical merchant to share with their developer. It’s a small detail that ensures a seamless transition from setup to implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XBIEnCNeFYed-O0LcunH0Q.jpeg" /><figcaption>neutral button color option</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnELjiYbBzDkt1v9ilvE7w.jpeg" /><figcaption>light button color option</figcaption></figure><h3>2. Building for the Developer: A Toolkit for Trust</h3><p>Developers build the web. If they don’t trust your tools, your product will never leave the ground. For them, a great experience means a complete toolkit that makes their job easy. I designed a developer experience focused on the entire integration lifecycle.</p><h4>From Learning to Debugging</h4><p>First, I designed a clear, interactive <strong>API documentation portal</strong> and a high-level <strong>monitoring dashboard</strong> to provide an at-a-glance overview of API health. When things go wrong, developers need immediate answers. To solve this, I designed a <strong>real-time request log</strong>, giving them a granular, live feed to debug individual API calls instantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwXFdyVzqMDeLvh6vxQpTw.jpeg" /><figcaption>Overview of the API usage &amp; performance</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P9LXQu-4Nv0luOxp2AAVFg.gif" /><figcaption>Design of the Real-time API request logs and monitoring</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0U82mlaBlQ_nlbt-mKP4w.gif" /><figcaption>sample API docs prototyped with loveable.dev</figcaption></figure><h4>Anticipating the Future</h4><p>A robust platform doesn’t just solve today’s problems; it anticipates tomorrow’s needs. While this project focused on building the fundamental tools for developers, my process also involved thinking about the next horizon.</p><p>A key area for future exploration would be a proactive, <strong>AI-powered monitoring assistant</strong>. The idea moves beyond simply showing data and asks: “How can we make this platform a true partner?” This could involve intelligently alerting a developer to a potential spike in failed transactions before it impacts their business, or offering contextual solutions to common errors. While I did not design this specific feature, identifying it as a strategic next step demonstrates a vision for a truly supportive and intelligent developer platform.</p><h3>The Result: A Product That Creates an Ecosystem</h3><p>By designing for the interconnected needs of the merchant, the developer, and their end-customer, the “Yellow Card Pay” gateway becomes more than just a product. It becomes an ecosystem.</p><ul><li>It gives <strong>Merchants</strong> a risk-free key to the global crypto economy.</li><li>It gives <strong>Developers</strong> a powerful and reliable platform to build on.</li><li>It gives <strong>Customers</strong> a tangible way to use their digital assets in the real world.</li></ul><p>This project is a blueprint for how Yellow Card can evolve. It’s a strategic vision for transforming a successful on-ramp into the central payment network for African e-commerce, proving that the future of finance is not just about access, but about utility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=056baad9b71a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From UX to Scale: 5.5 Years of Designing at PurplePay]]></title>
            <link>https://medium.com/@King_Marquant/from-ux-to-scale-5-5-years-of-designing-at-purplepay-c7c9bcf5a670?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7c9bcf5a670</guid>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 18:04:40 GMT</pubDate>
            <atom:updated>2026-06-01T19:43:09.328Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E03VxDzHRxP-el0gEFP51A.png" /><figcaption>A mockup of the current PurplePay app dashboard</figcaption></figure><h4>Role</h4><p>Over five and a half incredible years at PurplePay Technologies (September 2019 — July 2025), I didn’t just have a job ,I helped build something that changed people’s lives. I came on board when the company was still finding its feet, and got to completely reimagine our website and mobile app from scratch. What started as a basic platform became smooth, user-friendly experiences that our customers genuinely enjoyed using. I had the exciting opportunity to lead the design of game-changing features: virtual cards that let Nigerians shop globally, international money transfers AKA payment request, that connected families and businesses across borders, a streamlined in-house identity verification system, and our own comprehensive Design system (Payple Design System 1.0).My focus remained on empowering users and building a scalable, cohesive product suite that propelled PurplePay’s growth and market reach.</p><h4>Modernizing the Core User Experience &amp; Accessibility</h4><p><em>(Projects: </em><a href="https://purplepayapp.com/"><em>Full Website Redesign</em></a><em>, Mobile App Redesign)</em></p><p>Impact highlights:</p><ul><li>Gave PurplePay’s website a fresh look and feel, leading to over <strong>850+ app downloads </strong>from the site using the dynamic QR code.</li><li>Redesigned the mobile app from scratch, making it much easier for new users to sign up and get started successfully (currently serving 20,000+ users).</li><li>Improved the app’s appearance and how easy it was to use, making PurplePay’s services simpler for everyone to understand and access.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*GU8eiifcMfpYHbyO0GftFA.gif" /><figcaption>Snapshot of PurplePay website redesign before and after. redesigned by me in figma and developed with webflow</figcaption></figure><p>A snapshot of some redesigns done on the mobile since I joined till now</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vIxzVbRg-KaySE8VZ_3bMg.png" /><figcaption>Old App design of some screens on PurplePay</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l07mBq8UDj1GVWSNwqZjyg.png" /><figcaption>Current design of the PurplePay App</figcaption></figure><p>Working on the deep dive now, but if you’re curious I’d love to give you a sneak peek. Let’s talk design, impact, or how this could apply to your product.</p><p><strong>Expanding Payment Power &amp; Global Reach</strong> <br><em>(Projects: Virtual Card Feature, Payment Request, P2P Transfers)</em></p><p><strong>Impact Highlights:</strong></p><ul><li>Introduced Dollar Virtual Cards, allowing over <strong>250 users</strong> to easily pay for international services online (like music subscriptions and software renewals), processing over <strong>$30,000 USD</strong>.</li><li>Created a feature for users to request and send payments to other countries (Payment Request), moving over <strong>$200,000 USD</strong> for important needs like school fees abroad and payments to businesses in China.</li><li>Made it quick and easy for PurplePay users to send money directly to each other within the app.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*BnmAkm_L3aCzNKFGUDxcwQ.gif" /><figcaption>a demo of virtual card creation on the PurplePay Mobile App</figcaption></figure><p>Tap In: <a href="https://medium.com/@King_Marquant/beyond-borders-designing-purplepays-virtual-dollar-card-experience-3513a5144df7"><em>A Closer Look at How We built the Virtual card Experience</em></a></p><p><strong>Scaling Operations &amp; Building Foundational Systems</strong> <br><em>(Projects: Banking, Design System, POS App Design,KYC verification solution)</em></p><p><strong>Impact Highlights:</strong></p><ul><li>Designed PurplePay’s own system to confirm user identities, successfully verifying over <strong>15,000 people</strong> (with about 3 out of 4 valid IDs checked and approved), which helped keep the platform secure and meet legal requirements.</li><li>Developed a Design system (Payple Design System) for all PurplePay products on mobile and web. This sped up the creation of new features, improved teamwork between designers and developers, and ensured our products had a consistent look and feel.<br>“Payple” actually means <strong>Pay</strong>ing<strong> </strong>Peo<strong>ple</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eG3lLyRxw_pIOEuZeIq8w.png" /><figcaption>some components from the company design system (Payple Design System)</figcaption></figure><ul><li>Designed the easy-to-use screens for PurplePay’s payment machines (POS devices), now used by over <strong>1000+ businesses</strong> to take customer payments in their stores. <strong>This is why merchants love our POS system,<br> </strong>See a live transaction that happened in less than a minute</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.canva.com%2Fdesign%2FDAGpab6g274%2FLqt9poT-99Ev3H0wIa8Yeg%2Fwatch&amp;type=text%2Fhtml&amp;schema=canva&amp;display_name=Canva&amp;src=https%3A%2F%2Fwww.canva.com%2Fdesign%2FDAGpab6g274%2FLqt9poT-99Ev3H0wIa8Yeg%2Fwatch%3Fembed%26meta" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9885cb7502052e548771659cc2de959/href">https://medium.com/media/d9885cb7502052e548771659cc2de959/href</a></iframe><ul><li>Addressed escalating security concerns for large financial transactions on PurplePay by designing and implementing a robust dual OTP verification system. Despite initial launch hurdles, this proactive measure successfully mitigated fraud risks, resulted in higher user deposits and increased ₦100k+ transaction volumes, and turned initial user friction into strong positive feedback and heightened trust.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Icq1z4VsZ8I1bVcP1gKCQw.gif" /><figcaption>extra layer of security for transactions over ₦100,000</figcaption></figure><p><a href="https://medium.com/@King_Marquant/fortifying-trust-the-strategy-that-paid-off-5c85e941485d"><em>See how we did it</em></a></p><p>Impressed by what you’ve seen? I’m just getting started. Let’s discuss how I can help drive your next big win.</p><p><strong>Get in touch:</strong></p><ul><li><strong>Email 📧:</strong> slywestmarquant@gmail.com</li><li><strong>LinkedIn:</strong> <a href="http://www.linkedin.com/in/marquant-sylvester-a03260a9">linkedin.com/in/marquant-sylvester</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7c9bcf5a670" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Borders: Designing PurplePay’s Virtual Dollar Card Experience]]></title>
            <link>https://medium.com/@King_Marquant/beyond-borders-designing-purplepays-virtual-dollar-card-experience-3513a5144df7?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/3513a5144df7</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[cards]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 17:03:58 GMT</pubDate>
            <atom:updated>2025-06-04T17:03:58.153Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine trying to pay for something online and hitting an invisible barrier every single time. That’s what millions of Nigerians faced when trying to buy things from other countries . A Spotify subscription, an online course, software they needed for work, or clothes from international websites,their Nigerian bank cards simply wouldn’t work for international payments. What should have been a quick, simple purchase became a frustrating nightmare. People were locked out of a whole world of digital services and products, all because of payment restrictions.</p><h4>Our Solution: Breaking Down the Barrier</h4><p>PurplePay didn’t just add a new feature ,we threw our users a lifeline. We created the PurplePay Virtual Dollar Card, a simple and smart solution to this huge, widespread problem.</p><p>The results speak for themselves: in a short time, over 250 users successfully made international payments, spending more than <strong>$30,000 USD.</strong> Suddenly, paying for Spotify, renewing a Coursera subscription, shopping on ASOS, or buying game credits went from being a multi-step headache to something you could do effortlessly right from the PurplePay app.</p><p>What looked like a simple user experience was actually the result of months of careful planning and hard work behind the scenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a5PuAZbtYHSsj7mS4m98xQ.png" /><figcaption>simple flow screen for card request</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*BnmAkm_L3aCzNKFGUDxcwQ.gif" /><figcaption>card request prototype</figcaption></figure><h4>Why This Mattered: Beyond Convenience, It Was About Empowerment and Strategic Growth.</h4><p><strong>For Our Users:</strong> The frustration of not being able to pay for things online was real and painful. This wasn’t just about buying things ,it was about accessing education, getting tools to grow professionally, and simply being able to participate in the global digital world like everyone else.</p><p>We aimed to give them a world where paying for an international service was an afterthought, not a roadblock. The response from users was immediate: relief, gratitude, and a feeling of finally having control again.</p><p><strong>For PurplePay:</strong> This was a make-or-break moment for us. The Nigerian social media landscape buzzed daily with users desperately seeking reliable virtual card solutions. Successfully launching an efficient, trustworthy Virtual Dollar Card meant a significant <strong>competitive edge, substantial user acquisition, and revenue growth</strong></p><p>But if we failed? It wouldn’t just mean scrapping a feature ,it would mean wasted resources, damaged credibility, and missing a huge opportunity to solve a problem everyone was talking about. The pressure was enormous.</p><h4>The Challenges: Why Simple Isn’t Always Easy</h4><p>Making this look “simple” for users was actually incredibly complex behind the scenes. We faced major obstacles at every turn:</p><h4>Finding the Right Partner</h4><p>Our biggest challenge was finding a reliable company to actually create and manage the virtual cards. Many international companies didn’t want to work with a Nigerian business, and even fewer could promise the excellent, smooth service we demanded. This meant countless meetings, thorough background checks, and working hard to build trust across borders.</p><h4>Planning for What Users Really Needed</h4><p>We didn’t just want to enable payments, we wanted to give users peace of mind and handle different ways people might want to use their cards. This thinking led to some smart design choices:</p><p><strong>Two Different Card Types:</strong> We realized users had different needs and worries, so we created two distinct virtual card options:</p><ul><li><strong>PurplePay Prime Cards:</strong> Perfect for everyday use. Users could add money to these cards and use the same card details for ongoing services and regular international shopping. This was great for people who wanted reliable recurring payments like monthly subscriptions.</li><li><strong>PurplePay Disposable Cards:</strong> Ideal for one-time purchases. Once you spent all the money on a Disposable Card, it automatically self-destructs. This was perfect for users who were worried about leaving their card details on lots of different websites, or who simply didn’t want the hassle of managing another permanent card. It offered extra security and made card management super simple.</li></ul><p><strong>Preventing Fraud:</strong> While the disposable cards naturally reduced some fraud risks, we also built strong monitoring systems and created clear guidelines for users which included a minimum balance requirement for the PurplePay prime cards to prevent unexpected freezes, and clear email notifications for any failed transactions, coupled with a fair penalty system to encourage timely funding.</p><h4>Building Everything From Scratch</h4><p>Once we found a reliable partner with well-documented APIs, the real sprint began. As the lead designer, I carefully mapped out every step of the user’s journey. The development team and I spent two intense weeks building the backend systems, designing an easy-to-use interface, and making improvements based on feedback from stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hjcd8WYGZj4us-CEUkPtSw.png" /><figcaption>an image of the customer journey map we used to map out the what and why</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wm52kfZd22N4ct7HLuBzKg.png" /><figcaption>User Persona for the virtual card feature</figcaption></figure><p><strong>Our Design thought process:</strong></p><p><strong>Clear Card Choice:</strong> Since we had Prime and Disposable cards, our interface needed to clearly explain the benefits of each type, helping users make the right choice when creating their card. We focused on simple cards and easy-to-understand explanations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PcHrIHRIdNY2e5mkWG3Ttw.png" /><figcaption>A mock up of the the two card options available on the PurplePay App</figcaption></figure><p><strong>Super Simple Funding:</strong> We made adding money to cards as easy as possible. Users could fund their Virtual Dollar Cards directly from their existing PurplePay USD wallet. The process was:</p><ol><li>Add money to their main PurplePay Naira wallet</li><li>Convert Naira to USD easily within the PurplePay app</li><li>Instantly move USD from their PurplePay USD wallet to their chosen Virtual Dollar Card (Prime or Disposable)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_CEk58QgIa6SwLoL9mi1NQ.png" /><figcaption>card funding flow</figcaption></figure><p>Even though this was a complex process behind the scenes, we presented it as a clear, guided experience that users could easily follow</p><p><strong>Card Details &amp; Security:</strong> We had to balance showing card information (number, expiry date, security code) with keeping things secure. We used “tap to reveal” for sensitive information on Prime cards and temporary cards, and users had to confirm their pin to have access to the card information</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.canva.com%2Fdesign%2FDAGpY0drVZo%2FyzoLeZMkFGqNyQVyPjzexQ%2Fwatch%3Fembed%26meta&amp;display_name=Canva&amp;url=https%3A%2F%2Fwww.canva.com%2Fdesign%2FDAGpY0drVZo%2FyzoLeZMkFGqNyQVyPjzexQ%2Fwatch&amp;image=https%3A%2F%2Fwww.canva.com%2Fdesign%2FDAGpY0drVZo%2FyzoLeZMkFGqNyQVyPjzexQ%2Fscreen%3Ftype%3Dthumbnail&amp;type=text%2Fhtml&amp;schema=canva" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/dde0287994d85dc3e238daaaf9f79033/href">https://medium.com/media/dde0287994d85dc3e238daaaf9f79033/href</a></iframe><p><strong>Transaction History:</strong> We created a unified, detailed transaction history for both card types so users could easily track their spending and feel confident about their purchases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qQ1UDXROPnMbIfpM-sBIA.png" /><figcaption>a screenshot of the card transaction page</figcaption></figure><p>Throughout this entire process, our guiding principle was always putting users first. We constantly asked ourselves: “How can we make this as easy, secure, and empowering as possible for someone who has been frustrated by payment problems for so long?”</p><h4>The Amazing Results: Proof That Listening to Users Works</h4><p>The launch of the PurplePay Virtual Dollar Card was more than just releasing a new feature, it proved that our approach worked. By really understanding what frustrated users, proactively designing for different needs and security concerns (shown by our Prime and Disposable card strategy), and never losing focus on creating a simple and reliable solution, we turned a major problem into an opportunity for user empowerment and business growth.</p><p>The key lesson? The best solutions often come from thoughtfully addressing the complex details of what users really need and what could go wrong. This project proves our team’s ability to design and deliver solutions that make a real impact, keep users safe, and are genuinely easy to use.</p><h4>What This Means Going Forward</h4><p>By breaking down the invisible barrier that was blocking Nigerians from global commerce, we didn’t just solve a payment problem ,we opened up a world of possibilities. Users can now access education, professional tools, entertainment, and shopping opportunities that were previously out of reach.</p><p>For PurplePay, this success has established us as a trusted partner for Nigerians who want to participate fully in the global digital economy. It’s shown us that when we listen carefully to user pain points and work hard to solve them thoughtfully, we can create solutions that truly change people’s lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3513a5144df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fortifying trust: The strategy that paid off]]></title>
            <link>https://medium.com/@King_Marquant/fortifying-trust-the-strategy-that-paid-off-5c85e941485d?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c85e941485d</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 14:17:05 GMT</pubDate>
            <atom:updated>2026-10-10T13:49:15.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xN-Q7PA7DdE8_NcVseOSWw.png" /><figcaption><strong>trust through interface and features</strong>.</figcaption></figure><p>Picture this: people who were once nervous about moving large amounts of money online suddenly felt safe doing it. That’s exactly what happened with PurplePay users. After we added a new security feature, something amazing occurred. More people started putting bigger amounts into their PurplePay accounts. They began making transactions over ₦100,000 without fear.</p><p>But here’s the best part, users who were initially worried about our new security step ended up asking for even MORE security features, like fingerprint verification. They went from being scared to being excited about staying safe. This told us we had done something right. We hadn’t just added a feature; we had earned their trust.</p><h4>The Scary Problem: Why We Had to Act Fast</h4><p>The online money world is always changing, and unfortunately, so are the tricks that criminals use to steal money. We started noticing something frightening, more and more fraudsters were targeting big money transfers across digital banks. People were sharing heartbreaking stories on Twitter about waking up to find their accounts completely emptied by thieves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4ZqxtAmya0ixn7iFL1X6A.png" /><figcaption>some screenshots on X (formerly twitter) of people complaining about transactions that happened without their authorization</figcaption></figure><p>This wasn’t just someone else’s problem ,it was a wake-up call for us. Our system at the time was pretty good, but it only asked for a PIN to approve transactions, even for users who had gone through all our verification steps (including BVN/NIN Verification, taking selfies, and proving their address). These trusted users could move up to ₦5 million in one transaction.</p><p>The scary truth hit us: if someone figured out a user’s PIN, they could steal huge amounts of money in seconds. Imagine losing millions because of one weak point in the system. We couldn’t let that happen. Our mission became crystal clear: make sure no big amount of money could leave someone’s account without them really, truly confirming it multiple times.</p><h4>It’s More Than Money: The Fear is Real</h4><p>Losing money is deeply personal and terrifying. We had seen this fear up close. One user forgot their PIN and couldn’t access their recovery email. Panicking about being stuck without money in an emergency, they sent us over 50 desperate emails in just two hours. You could feel their anxiety through every message.<br>Another story really opened our eyes. A woman quietly told us that her husband knew her PIN and could access her banking apps. This meant he could move her money without asking her. She wasn’t worried about hackers from the internet, she was worried about someone in her own home having too much control over her finances.<br>These stories reminded us why this project mattered so much. We needed to protect all our users — young people, middle-aged folks, and the elderly from all kinds of threats. The trust they had in us was precious, and we had to protect it.</p><h4>Locking It Down — Without Locking Users Out</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*UO1yvREv51v1Be8GPV5utQ.jpeg" /><figcaption>a pen and paper wireframe of some solutions we explored</figcaption></figure><p>the team and decision-makers, sat down to figure out the best way to keep users safe without making their lives difficult. We considered several options:</p><p><strong>Text/Email Codes:</strong> Everyone knows how these work, but phone numbers can be hijacked and emails can be hacked.</p><p><strong>Authentication Apps:</strong> Very safe, but confusing for people who aren’t tech-savvy, especially older users who would need help installing and learning new apps.</p><p><strong>Fingerprint/Face Recognition:</strong> Highly secure and convenient, but dependent on device hardware and faced a longer implementation timeline</p><p><strong>Security Questions: </strong>Simple, but often weak and guessable</p><p><strong>Separate Transaction Password:</strong> An extra layer of protection, but people might get confused and forget another password.</p><p>We had two big challenges: we needed to launch quickly, and we couldn’t create something that would frustrate our diverse group of users. So we decided to ask the users themselves what they preferred.</p><p>Beta testing links were sent to a selection of frequent users across different demographics, here’s what we learned:</p><ul><li>Email and phone codes were the easiest to understand</li><li>Security apps confused people — they didn’t even know what they were</li><li>Separate passwords made people try their regular PINs or start password recovery by mistake</li><li>Fingerprint verification sounded great, but we couldn’t build it fast enough</li></ul><p>The clear winner was a two-step code system: for transactions over ₦50,000, users would get one code on their phone and another code in their email, and they’d need both codes to complete the transfer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*YN57PHn237LQImNZRiobvA.jpeg" /><figcaption>A wireframe of the final solution we settled for.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XgTWyZgk0RT6AcD3tt2QeA.png" /><figcaption>a flowchart showing the transfer process with the new flow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Icq1z4VsZ8I1bVcP1gKCQw.gif" /><figcaption>prototype of the new security feature in action</figcaption></figure><h4>Launch Day Chaos: When Everything Went Wrong Before Going Right</h4><p>We picked our solution and got ready to launch. We sent one email to all users explaining the change and why we were making it. The feature went live as a required update and users had to update their app to keep using it.</p><p><strong>Then everything exploded</strong>.</p><p>Customer support was flooded with complaints and confused questions. To make matters worse, the company providing our text message OTP codes failed completely. Some users couldn’t get their phone codes at all. It was a nightmare.<br>Luckily, not everyone updated their app right away, which gave us time to fix things. Our support team worked around the clock to calm frustrated users. Meanwhile, our technical team quickly switched to a different, more reliable company for sending OTP’s to mobile numbers. The best part? We could make this switch without asking users to download another app update, so the main problem was fixed relatively fast.</p><p>But we still had issues. Some users couldn’t get text codes because they were away from their phones or had blocked promotional messages. We immediately started an education campaign on social media, teaching users how to allow these important security messages through. Find attached below a link to the campaign on Instagram.<br><a href="https://www.instagram.com/p/Cf6AE7vtd_I/?img_index=2&amp;igsh=MWo3ZnRxZHE2bGl6Nw==">Link to Campaign on Instagram</a></p><h4>The Turning Point: From Frustration to Fandom</h4><p>After about five days of intense customer support and user education, the complaints stopped. Users got used to the two-step verification process. Then something incredible happened ,they didn’t just accept it, they loved it.</p><p>This was our proudest moment. Positive feedback started pouring in. Users thanked us for making their money safer. Even better, they started asking us to add fingerprint verification, proof that they now trusted our security decisions and wanted even more protection.</p><p>The woman who was worried about her husband’s access to her account later told us how happy she was. The new system gave her the control she needed. For our entire team, getting through those difficult first days to reach this point felt amazing and proved we had made the right choice.</p><h4>The Big Results: Building Trust and Growing Business</h4><p>The two-step verification system for large transfers did more than just add security, it built trust and grew our business:</p><p><strong>More Big Transactions:</strong> We saw a clear increase in users depositing larger amounts and making more transactions over ₦100,000.</p><p><strong>Confident Users:</strong> The feature obviously made users feel much safer when moving significant amounts of money on our platform.</p><p><strong>Better Reputation:</strong> Successfully launching this feature, despite the rocky start, strengthened PurplePay’s image as a forward-thinking, user-focused, and secure financial partner.</p><h4>What We Learned for Next Time</h4><p>This whole experience taught us valuable lessons:</p><p><strong>Fix Problems Fast:</strong> Being able to quickly switch to a better text message provider during the crisis was crucial for solving our launch problems.</p><p><strong>Communicate Better:</strong> While we did send an initial email, we learned we need even more comprehensive communication across multiple channels for big changes, starting earlier in the process.</p><p><strong>Teach Users Everything:</strong> Active and ongoing user education, especially through easy-to-access channels like social media, was essential for helping users overcome obstacles like blocked messages (DND).</p><h4>Looking Forward: Security Never Stops</h4><p>Adding the two-step verification system for large transfers was a major milestone in PurplePay’s commitment to keeping users safe and earning their trust. By listening to the market, testing directly with users, and staying strong through launch challenges, we didn’t just make our platform safer, we built a stronger relationship with our customers.</p><p>The journey continues. We’re planning to explore fingerprint verification and even sending security codes through WhatsApp for users who have it. For PurplePay, making things more secure is an ongoing promise to always do better for our users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c85e941485d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Emotional Intelligence into AI: A UX Approach to Processing Grudges]]></title>
            <link>https://medium.com/@King_Marquant/building-emotional-intelligence-into-ai-a-ux-approach-to-processing-grudges-85bd6817a4ca?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/85bd6817a4ca</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[behavioral-psychology]]></category>
            <category><![CDATA[conversational-ai]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Mon, 05 May 2025 12:37:14 GMT</pubDate>
            <atom:updated>2025-05-05T12:37:14.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="a screenshot of the question that motivated this blog post by @dnaijatechguy.it reads, Alright quick UX conversation — You’re designing an AI assistant that helps people let go of grudges.
 
 What input data would it need?
 How would you design a trust loop?
 What are the states in a typical emotional processing model you’d build?" src="https://cdn-images-1.medium.com/max/522/1*OcqAbQ1figVvcV09PXcuBw.png" /></figure><h3>1. The Challenge</h3><p>While scrolling X (formerly Twitter), I came across this post: <a href="https://x.com/dnaijatechguy/status/1911400536722513986">https://x.com/dnaijatechguy/status/1911400536722513986</a> with screenshot above. What if AI could help users process deeply personal emotional pain,not by replacing therapy, but by providing empathetic, structured support? <br>I decided to explore how I would design an emotionally intelligent AI that guides users through the process of letting go of a grudge; safely, respectfully, and effectively.</p><h3>2. Understanding the Problem Space</h3><p>Grudges are complex. They’re not just memories of being wronged; they involve recurring thoughts, emotional pain, disrupted relationships, and even identity conflicts. Designing an AI to help with this means deeply understanding:</p><ul><li>The emotional and psychological landscape of a grudge</li><li>How users talk about pain and betrayal</li><li>The sensitive balance between therapeutic support and ethical boundaries</li><li>Building and maintaining trust in a digital tool handling raw emotions</li></ul><h3>3. Input Design: Gathering Meaningful Emotional Data</h3><p>The first step is helping the AI truly understand what the user is going through. This means collecting nuanced, deeply personal data with full transparency, user control, and empathy.</p><h3>What the AI Needs to Know</h3><p><strong>a. Grudge Narrative</strong></p><ul><li><strong>Event Details:</strong> What happened, when, where, and who was involved?<br> <em>Example:</em> “My sister publicly criticized my parenting at a family event.”</li><li><strong>The Target:</strong> Who is the grudge against and what’s the relationship?</li><li><strong>Impact:</strong> How did this affect the user’s life, self-esteem, or relationships?</li></ul><p><strong>b. Emotional &amp; Cognitive Landscape</strong></p><ul><li><strong>Current Emotions:</strong> Anger, shame, sadness, etc, and their intensity.</li><li><strong>Repetitive Thoughts:</strong> Loops or intrusive memories.</li><li><strong>Beliefs Formed:</strong> What meaning does the user attach to the grudge?</li></ul><p><strong>c. Historical Context</strong></p><ul><li><strong>Previous Attempts to Let Go:</strong> What worked or failed?</li><li><strong>Related Experiences:</strong> Past betrayals or emotional wounds.</li><li><strong>Coping Style:</strong> How does the user typically handle conflict?</li></ul><p><strong>d. User Motivation</strong></p><ul><li><strong>What Letting Go Means:</strong> Peace? Forgiveness? Indifference?</li><li><strong>Motivation Level:</strong> How committed are they to change?</li></ul><p><strong>e. Passive Interaction Data (with consent)</strong></p><ul><li><strong>Usage patterns, tone shifts, progress markers.</strong></li></ul><blockquote><strong><em>Why it matters:</em></strong><em><br> Personalized input makes support feel human. It also enables tailored exercises, emotional insights, and progress tracking.</em></blockquote><h3>4. Sample Use Case</h3><p><strong>User Input:</strong><br> “I can’t stop thinking about how my best friend, Tega, lied to me about applying for the same design gig. I feel so betrayed and angry.”</p><p><strong>AI Response Flow:</strong></p><ol><li><em>Event Inquiry:</em> “Can you tell me what happened with Tega?”</li><li><em>Impact Check:</em> “How has it affected your work and your friendship?”</li><li><em>Emotions Exploration:</em> “What emotions come up most often when you think about this?”</li><li><em>Goal Clarification:</em> “What would feeling better look like to you?”</li><li><em>Passive Analysis:</em> Track recurring topics, tone, and check-in patterns.</li></ol><h3>5. Designing for Trust: The Trust Loop</h3><p>Trust is the foundation of emotional design. Users must feel safe, heard, and in control,especially when sharing sensitive stories.</p><h4>Components of the Trust Loop</h4><p><strong>a. Empathy from the Start</strong></p><ul><li>Onboarding starts with listening, not solutions.</li><li><em>Example:</em> “It makes sense you’re feeling this way. Your feelings are valid.”</li></ul><p><strong>b. Transparency &amp; User Control</strong></p><ul><li>Clear privacy policies and user choices before every prompt.</li><li><em>Example:</em> “You can skip anything you’re not ready to share.”</li></ul><p><strong>c. Consistency &amp; Reliability</strong></p><ul><li>Tone, memory, and helpful behavior must feel stable.</li><li><em>Example:</em> “Welcome back. Last time, you mentioned anger toward Tega. How have you been?”</li></ul><p><strong>d. Demonstrating Understanding</strong></p><ul><li>Reflecting back user input.</li><li>Offering useful, tailored tools.</li><li><em>Example:</em> “You said it affects your trust. Want to try a reframing exercise to unpack that?”</li></ul><p><strong>e. Adaptive Feedback Response</strong></p><ul><li>Adjust when tools don’t help.</li><li><em>Example:</em> “That exercise didn’t help? Thanks for telling me. Want to try a different one?”</li></ul><h3>6. Emotional Processing Journey</h3><p>I designed the AI flow based on a five-stage emotional healing model,from awareness to integration.</p><h4>1. Acknowledgment &amp; Exploration</h4><ul><li>User feels overwhelmed or angry.</li><li>AI listens, validates, and starts mapping the emotional landscape.</li><li><em>Example:</em> “It’s brave to say that. When did you start feeling this way?”</li></ul><h4>2. Understanding &amp; Insight</h4><ul><li>User starts unpacking what happened and why.</li><li>AI introduces multiple perspectives, cognitive patterns, and values.</li><li><em>Example:</em> “Sometimes people act from pain. How does not knowing <em>why</em> affect you?”</li></ul><h4>3. Reframing &amp; Shift</h4><ul><li>User challenges beliefs and shifts focus from pain to growth.</li><li><em>Example:</em> “It was unfair. Would it help to look at how you’ve grown through it?”</li></ul><h4>4. Acceptance &amp; Integration</h4><ul><li>The story becomes just a part of their journey, not a defining moment.</li><li><em>Example:</em> “That’s real progress. What can you do now that was harder before?”</li></ul><h4>5. Maintenance &amp; Relapse Prevention</h4><ul><li>Continued support for flare-ups, like seeing the person again.</li><li><em>Example:</em> “Seeing Tega again must be tough. Want to try that technique we practiced?”</li></ul><h3>7. The System Behind the Scenes</h3><p>This AI isn’t trying to be a therapist. It’s designed to:</p><ul><li>Understand nuanced emotional narratives</li><li>Identify patterns of thinking and feeling</li><li>Suggest relevant tools (journaling, mindfulness, cognitive reframing)</li><li>Stay emotionally consistent, safe, and responsive</li><li>Track long-term progress and adapt dynamically</li></ul><h3>8. The Outcome</h3><p>By approaching this challenge with a human-first design lens, I mapped out how an AI system can:</p><p>✅ Create psychological safety<br> ✅ Support emotional healing without overstepping ethical lines<br> ✅ Build long-term engagement through empathy and adaptability<br> ✅ Empower users to move forward in their own time</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85bd6817a4ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HERE to THERE]]></title>
            <link>https://medium.com/@King_Marquant/here-to-there-53a4b641b474?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/53a4b641b474</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 14:32:14 GMT</pubDate>
            <atom:updated>2024-06-03T14:32:14.900Z</atom:updated>
            <content:encoded><![CDATA[<p>HERE to THERE</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*zg6RmuDiNSsOQBMjAh4MmQ.jpeg" /><figcaption>An image depicting progress upwards and forwards</figcaption></figure><blockquote>I will never regret doing more of what’s important to me, I will only regret not doing it sooner. Someday is not a day in the week.</blockquote><p>INTRO<br>I&#39;m excited to announce that I&#39;m taking a break from my mental health to focus on DESIGNING and DEVELOPING and DEPLOYING digital products. My goal is to learn as much as possible in the shortest amount of time to optimally accelerate. There are 2 things that we can leverage for the rest of our lives: [knowledge, skills], everything else is temporary.</p><h3>Aim of this goal?</h3><p>• To pick back coding (front end development) .<br>• To improve on design/research and take up more design projects around ERP, health,Social commerce, agriculture etc for mobile/web.<br>• Get fully into web3 design space .</p><h3>What do I need in order to be able to do this ?</h3><p>Spend at least 4+ hours in figma &amp; Visual studio code and then another 2 hours for lowcode tools (webflow) everyday with undistracted focus, and another 2hours reading.</p><h3>Resources I&#39;ll be using :</h3><p>• <a href="https://university.webflow.com/">Webflow University</a> <br>• YouTube<br>• Chatgpt,Google bard ,Claude AI<br>• <a href="https://www.freecodecamp.org/">freecodecamp</a><br>• Google Search <br>• <a href="https://www.udemy.com/course/freelance-web-design-from-design-to-development-to-making-money">Complete Web Design: from Figma to Webflow to Freelancing (vako shvili) </a><br>• medium / PDFs</p><p>OUTRO<br>The purpose of a fight is not to be seen fighting or just to fight for the sake of itself. The only purpose of fighting is to win. I’m not interested in losing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53a4b641b474" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Black Screen Of Death]]></title>
            <link>https://medium.com/@King_Marquant/black-screen-of-death-a981b7d5f9e1?source=rss-23d5318fa885------2</link>
            <guid isPermaLink="false">https://medium.com/p/a981b7d5f9e1</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[hacks]]></category>
            <category><![CDATA[engineer]]></category>
            <dc:creator><![CDATA[Sylvester Marquant]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 12:14:47 GMT</pubDate>
            <atom:updated>2017-09-06T12:16:09.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*4QEYslm5NPLSFufis_5cXg.png" /></figure><p>Ok been quite a while I posted something here,not to worry you would get to hear from me more often now…</p><blockquote>The <strong>black screen of death</strong></blockquote><p>Ok before I go into the main gist,it was actually my fault but I conquered *smiles*.My device was running low and because of the circumstances around I HAD TO CHARGE with a “not so reliable”phone charger,and then the horror began.I could recieve touch feedbacks but my device”s screen was just black,it was devastating because I was working on a project which had to be completed before the end of day.So i had to do what I know how to do best…..</p><h4>“GOOGLE FOR SOLUTIONS”</h4><p><strong>So what really is the black screen of death?</strong></p><p>The black screen of death simply means the device hit a serious issue and couldn’t load the operating system.</p><p><strong>What really is the root cause ?</strong></p><ol><li>Making use of an Incompatible charger to charge the device</li><li>installation of applications with virus on the device.</li><li>System cache error/inconsistencies</li></ol><p><strong>How will I know if my device is facing the black screen of death nightmare?</strong></p><p>1.The light of the phone will keep on blinking but it will not respond.</p><p>2.The phone will crash/reboot automatically and you would notice severe battery consumption</p><p>3.You will notice that your phone start to freeze/hang more frequently.</p><p><strong>So how can I fix this issue?</strong></p><p>Well there are several methods you can apply to get your device back to its working state.</p><ol><li><strong>Remove and Re-Insert The Battery,sd card &amp; sim card</strong></li></ol><p>Remove the cover of your phone and remove the battery,sd card and sim card and wait for about 5minutes then re-insert properly.this is an easy fix but if it doesn’t work proceed to step 2</p><p>2.<strong>Disable/Uninstall Apps</strong></p><p>May be your phone has an app that is infected or have a bug that is creating a problem. To check, <strong>boot your Android device into Safe Mode. </strong>Here, how to do this:</p><ul><li>Switch OFF your phone and then again switch it ON</li><li>When your device displays the logo while restarting, press and hold the Volume down button until the lock screen shows up.</li><li>Safe mode will displayed at the lower left corner on the phone’s screen.</li></ul><p>Once you enter into safe mode. Select and uninstall recently installed applications before the issue started and reboot the device</p><p>3.<strong>Clear System cache/dalvik cache</strong></p><p>a.Power off your Android device.</p><p>b.Hold the volume <strong>DOWN</strong> and power button until the recovery menu appears</p><p>c.Press volume down until the word<strong> Recovery</strong> is highlighted, then press the power button to reboot into recovery.</p><p>d.You should now see a black screen. Hold down the power button and press the <strong>volume UP</strong> until you see the recovery menu</p><p>e.Using the <strong>DOWN</strong> key, navigate until you have wipe cache partition highlighted. Press the power button to erase the system cache. Once the cache is cleared, use the volume <strong>DOWN</strong> button to navigate to reboot to bootloader, and press the power button. Your device should reboot back to the original menu.Using the volume down button highlight <strong>REBOOT</strong> and press the power button. Your device should now reboot into Android and the issue fixed.</p><p>4. <strong>Perform Hardware Factory Reset</strong></p><p>Note that performing this process will erase all the data stored on your device internal memory. Also remove your SD card while performing hard factory reset process.</p><p>Here how to perform hard factory reset:</p><ul><li>Press and hold <strong>Volume Up button + Power button</strong> and <strong>Home button</strong> altogether to boot the phone in <strong>recovery mode</strong>.</li><li>Once you enter into recovery mode, select the <strong>factory reset/wipe data</strong> using <strong>volume button</strong>. Press <strong>Power button</strong> to start the hard factory reset process.</li></ul><p>If all processes fail,and you are not able to get your device working,the best bet would be to take it to an engineer,it may be your screen has developed a hardware issue.If you are like me,and you use a phone with a non removable batttery,allow the phone to drain completely,then try recharging itand try options 3 or 4 or rather both.</p><p><strong>So how can I avoid this horror?</strong></p><ul><li>Always install apps from trusted sources and avoid installation of apps from un-trusted sources.</li><li>Always take backup of your phone data at regular interval.</li><li>Always keep your Android OS updated and ensure your apps are up-to-date.</li><li>Never charge your device with an incompatible charger</li><li>If your battery is not working properly then replace it.</li></ul><p>Kindly share this article to help a friend</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*C5CF7qQktXx7J0i_qdyvWA.gif" /></figure><p>This gif best describes how I feel at the moment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a981b7d5f9e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>