<?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 Kingsley John on Medium]]></title>
        <description><![CDATA[Stories by Kingsley John on Medium]]></description>
        <link>https://medium.com/@johnogechukwu97?source=rss-de375b11bb64------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SCurPCpMLB72FG3WA_RBew.png</url>
            <title>Stories by Kingsley John on Medium</title>
            <link>https://medium.com/@johnogechukwu97?source=rss-de375b11bb64------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:57:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johnogechukwu97/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 Value of No-Code Tools: Should Designers Get on Board?]]></title>
            <link>https://medium.com/@johnogechukwu97/the-value-of-no-code-tools-should-designers-get-on-board-3c4c6c68c906?source=rss-de375b11bb64------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c4c6c68c906</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[no-code]]></category>
            <dc:creator><![CDATA[Kingsley John]]></dc:creator>
            <pubDate>Fri, 30 Aug 2024 21:33:58 GMT</pubDate>
            <atom:updated>2024-08-30T21:33:58.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Gf2f2IrdpoSVbMORCpNZA.png" /></figure><p><strong>The Story</strong><br>Sipping my coffee in the early hours of a Tuesday morning, I found myself trying to stay agile despite a restless night. I had to be present for <a href="https://beaverup.com/">Beaverup</a>’s first meeting, where I was assigned the task of developing the website using <a href="https://framer.com/">Framer</a>. Despite the challenge, I wasn’t too worried; I enjoy tackling new tasks and had prior experience with Framer during my time at <a href="https://zendtrax.co/">Zendtrax</a>. Although I hadn’t started from scratch there, I was familiar with the tool and had even built my previous portfolio using it. This time, however, the task was different — I had to design and ensure it was fully responsive. But more on that later.</p><p><strong>Understanding No-Code Tools</strong><br>Before diving into my experience, let’s clarify what a no-code tool is. Essentially, a no-code tool allows you to develop a product without needing to know how to code. Instead, you use drag-and-drop features to build what you need. Examples include <a href="https://wordpress.com/">WordPress</a>, <a href="https://wix.com/">Wix</a>, <a href="https://webflow.com/">Webflow</a>, <a href="https://framer.com/">Framer</a>, <a href="https://bubble.io/">Bubble</a>, and <a href="https://flutterflow.io/">Flutterflow</a>. These tools are invaluable for designers who want to bridge the gap between design and development, making it easier to bring ideas to life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-6rIVlzQ-tyra1U4D8tTqA.png" /></figure><p><strong>My “Hands-on” Experience</strong><br>As much as I’ve always loved design, I’ve also had a deep passion for building things with my hands. For over ten years, I ran a <a href="https://jadyndesignlab.com/">backpack company</a> where I made over a 100 backpacks and bags. I love getting hands-on in bringing ideas to life, which is why I’ve always been curious about the development side of product building — not because I want to transition to software engineering but to better relate to engineers and understand their challenges. This experience influences my designs, ensuring they are feasible and user-friendly.</p><p><strong>The Struggle with Responsiveness</strong><br>The project started smoothly — at least for the hero section and several other areas. For some sections, I had to watch YouTube tutorials and Framer guides to overcome obstacles, but there was always a solution. However, I faced a significant hurdle with responsiveness. After completing the designs, which looked great, I overlooked how they would perform on wider screens. When tested, the site failed the responsiveness check. Unfazed, I went back to refine the layout and positioning. It took several attempts, but eventually, I got it right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*TWrHX-f_wO_TvJ0KIM7hgA.jpeg" /></figure><p><strong>Conclusion: Should Designers Embrace No-Code?</strong><br>This brings us to an important question: should designers learn how to use no-code tools? There’s no one-size-fits-all answer; it depends on the company you work for and your passion for the craft. If I could advise my younger self, I’d suggest mastering a no-code tool early enough to understand the basics of development. Although it doesn’t come close to actual coding, but it offers a glimpse into the trial-and-error process developers go through. Plus, if you ever find yourself stranded with just a design in Figma or XD, knowing how to use these tools can help you bring your vision to life quickly. And in a fast-paced startup environment, this skill can be invaluable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*ZE-EmymIRcKik4SYvHFoSw.jpeg" /></figure><p>No-code tools provide designers with a unique opportunity to experience the development process and prototype rapidly, enhancing their designs and making them more practical. Whether or not you decide to delve into no-code, it’s all about improving your craft and being open to new challenges. After all, every new challenge is an opportunity to grow — just like my experience with Beaverup’s website taught me. If you have a different perspective, I’m all ears — let’s learn from each other’s experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c4c6c68c906" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing with Users in Mind: Working on Nezi]]></title>
            <link>https://medium.com/@johnogechukwu97/designing-with-users-in-mind-working-on-nezi-9192cf8a2a81?source=rss-de375b11bb64------2</link>
            <guid isPermaLink="false">https://medium.com/p/9192cf8a2a81</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Kingsley John]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 19:11:09 GMT</pubDate>
            <atom:updated>2024-08-29T22:44:38.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An image of the main screens on Nezi" src="https://cdn-images-1.medium.com/max/1024/1*2k-XV755So2vmxoVrbJLTA.png" /><figcaption>Preview of Nezi’s Key Screens</figcaption></figure><p>It all started when a friend came to visit me in the city. We were excited to explore new spots, especially restaurants, but there was one catch — we had to stay within a tight budget. As someone who’s lived here for a while, I thought finding the perfect places would be easy. But reality hit when we actually tried to search. We quickly realized that finding a restaurant that fit all our needs — clear pricing, a variety of cuisines, and an easy comparison — was much harder than we anticipated. That’s when I knew something had to change.</p><p>Like most designers, my initial instinct was to create a solution that covered everything. I envisioned a one-stop app where users could search for restaurants, parks, cinemas, and more. But as I started digging into user surveys and talking to people, it became clear that this wasn’t what they wanted. People didn’t need an app that did it all; they needed an app that did one thing really well — helping them find the right restaurant.</p><p>This realization was a turning point for me. I shifted my focus entirely, narrowing down the scope of the project to just restaurants. It wasn’t about spreading myself thin anymore; it was about solving a specific problem. This pivot was the key to unlocking the real potential of Nezi.</p><h4>The Power of Listening</h4><p>The research phase became the heart of the project. I spent hours chatting with people, asking them about their experiences and what they valued most when choosing a restaurant. The answers were diverse — some prioritized reviews, others were all about photos, and almost everyone mentioned cost as a big factor. Ambiance also came up frequently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*90hdUJ4CRt5J2o98EURy3g.png" /><figcaption>Visualized Survey Data Results</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dzla490EArH9j_nGyzz3ZQ.png" /><figcaption>Competitive Analysis</figcaption></figure><p>These conversations were eye-opening. They revealed not just the practical needs of users but also the emotional aspects of dining out. It wasn’t just about finding a place to eat — it was about creating an experience. And that’s what guided every design decision I made moving forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvdoJKTcPEMjKXvej_CSEg.png" /><figcaption>Key insight from research</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84MA-fJqEnKSS7FnddkNfw.png" /><figcaption>User Persona</figcaption></figure><h4>Bringing Nezi to Life</h4><p>Once the research was done, it was time to bring Nezi to life. I started with sketches, mapping out the core user flows — onboarding, restaurant search, comparison, and reservation screens. The low-fidelity phase was all about getting the structure right. I wanted to ensure that the app would be easy to navigate and that users could accomplish their goals without any friction.</p><p>Testing these wireframes with real users was crucial. It allowed me to validate the layout and functionality before diving into the visuals. And when it came time for the high-fidelity designs, I was ready. I refined the screens, incorporating brand elements and interactive features, and created advanced prototypes to simulate the user experience.</p><p>The results were impressive. After implementing the final designs, we saw a 25% increase in user satisfaction, and users were completing tasks 30% faster. It wasn’t just about making the app look good; it was about making it work better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCCH8jZ1cKr80sGyX5rN6Q.jpeg" /><figcaption>Sketch of key screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFBdUs_VOJCThJ3YDx8APQ.png" /><figcaption>Userflow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJ304E6OxFAUj2V0VX_NUw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bjwKOZ3_6HggfT_Via6wlg.jpeg" /><figcaption>User Testing Insights from Low-Fidelity Prototypes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ipczhb5ZwsZ23CwF_0JDSw.jpeg" /><figcaption>User Testing Insights from Low-Fidelity Prototypes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ssQ0IYlaYTTmwAP1u4y09w.png" /><figcaption>Final Low fidelity screens</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2pGCEGzrQIIQu-E5hGCIGg.png" /><figcaption>High fidelity components</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kic24W-7Fq_5dh-B5MW5mg.png" /><figcaption>High fidelity screens with metrics</figcaption></figure><h4>What’s Next?</h4><p>But the story doesn’t end here. Nezi was designed to solve a specific problem — helping users find and reserve seats at restaurants — but there’s so much more potential. Moving forward, I’m excited to explore new possibilities, like expanding the functionalities to include cafes and entertainment venues. I would also be considering features like seat layouts and options to share seats with others, making dining out even more social and interactive.</p><p>Looking back, the most important lesson I’ve learned is the power of research. It’s easy to assume we know what users want, but the real insights come from listening and observing. And that’s something I’ll carry with me into every future project.</p><p>So, to all the designers out there: Don’t skip the research. Don’t assume you know best. Let your users guide you, and you’ll create something truly meaningful - The best solutions come when we listen, learn, and design with empathy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9192cf8a2a81" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>