<?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 Tofunmi Adewuyi on Medium]]></title>
        <description><![CDATA[Stories by Tofunmi Adewuyi on Medium]]></description>
        <link>https://medium.com/@7ai?source=rss-33559ca92a5e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BeC9LX-KHiJQRB6MIXIYmw.png</url>
            <title>Stories by Tofunmi Adewuyi on Medium</title>
            <link>https://medium.com/@7ai?source=rss-33559ca92a5e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:08:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@7ai/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[Why I leant to code — a designer]]></title>
            <link>https://7ai.medium.com/why-i-leant-to-code-a-designer-32f4394d1284?source=rss-33559ca92a5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/32f4394d1284</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Tofunmi Adewuyi]]></dc:creator>
            <pubDate>Sat, 15 Jun 2024 13:24:37 GMT</pubDate>
            <atom:updated>2024-09-26T17:04:12.533Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I learnt to code — a designer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8RXruCH5FmxLeNQ4" /><figcaption>Photo by <a href="https://unsplash.com/@fazurrehman?utm_source=medium&amp;utm_medium=referral">Faizur Rehman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After spending the last few years working as a designer — sometimes in product, other times in disciplines I had no business — I had reached a point where I was confident in my skills. There is rarely a product design I can’t replicate, or do myself.</p><p>Something was lacking though, as always, since the beginning. Keep in mind, I have the utmost respect for all the engineers I’ve ever worked with. But this much was obvious;</p><blockquote>No one is likely to pay more attention to the design details than the designer.</blockquote><h4>Backstory</h4><p>Now let’s rewind to before I became a full-time designer. I was learning it all — as I, <em>unfortunately</em>, tend to do every time. I had picked up the basics of HTML, CSS and Javascript, and even some React. Granted, I was too excited to skip ahead. I may not have spent enough time with the basics as I should have. This cost me, but I was too excited by my new superpowers to notice. It all didn’t matter in the end — I got a full-time job as a designer.</p><p>I went all in, rapidly getting better, so much so that I couldn’t look at anything I worked on longer than 3 months ago without feeling <strong><em>deep shame.</em></strong> But it was a sign that I was growing, I was happy.</p><p>Then it happened the first time. I had worked on a product and sent it off to engineering. When I got the test link I was aghast, it was … ugly. Now, I must take primary responsibility as the designer for its ugliness (remember, deep shame). But man, did they take it all the way.</p><p>After my initial wave of <em>slight</em> annoyance. I thought to myself, it’s nothing a design review wouldn’t fix — I was right. So I put together a doc, taking screenshots of the differences between the live site and the design, with a brief comment on the difference, why it mattered and how to fix it, so the engineers didn’t have to go back and forth in Figma to resolve them. And it worked, for the most part. I found that the tinier the detail, the more reluctant the engineers were to fix it. “It doesn’t matter” they often said. But I was relentless, and eventually conceded on some so that peace would reign.</p><p>I’m certain no designer reading this is unfamiliar with that story, I could write a lot more about *this* topic, but then I would be derailing this article by just airing my beef, we move.</p><p>There were a couple of other things I noticed from my experience. I routinely saw other designers struggle to communicate with engineers in ways that I did not — I knew some of the lingo. More interestingly, I often saw other designers get into arguments with engineers about their design, and the possibility or impossibility of it. You see, designers had become so far removed from the actual building process that they were satisfied as long as they had used the most sophisticated technique in their arsenal, not caring how it got built, but then being upset at the inevitably bad outcome. I came to a conclusion; the more I knew how to code, the better I became as a teammate (and as a designer).</p><blockquote>Side note: I remember being very excited when Figma added the auto-layout feature. I remember saying to my friends “this is flexbox, amazing”.</blockquote><h4>Product Manager? K*** me now</h4><p>A few years down the line, I found myself working (unfortunately) as a product manager, still reaping the fruits of the little code I wrote. This move brought me much closer to the engineering team, and that did two things for me.</p><p>Firstly, it gave me insight into the entire process of building (an app).</p><blockquote>Like I said earlier, I was too excited to <strong>learn work</strong> correctly. So I had no mental model of how backends or APIs worked, just fighting with divs and buttons.</blockquote><p>I was in a lot more conversations with engineers about planning work, what to build, how to build and trade-offs. Suddenly my luck had run out, nobody was talking about divs!</p><p>The second thing it did was to make me see how much the final experience of the product came from what the engineers did (not the designer).</p><p>This made me uneasy, I know, as designers, we are always “solving problems” and “crafting experiences”. But in reality, maybe we did <em>some</em> problem-solving, but the engineers certainly did the crafting.</p><blockquote>The users will never experience the Figma file, what they experience though is the code written by the engineers.</blockquote><p>After working in a few teams and with a few people, I figured there are many ways to ensure your best “experience people” have the most sway on the final experience. Some examples are;<br>- <strong>A proper hand-off culture</strong>: where all screens are red-lined and annotated with all the important design details, forcing the engineers not to ignore them. <br>- <strong>Sign-off culture</strong>: where designers had to sign off on work done before it is approved/merged etc. This empowers the designers and makes them ultimately responsible for the outcome of the experience.<br>- <strong>A top-down culture of attention to detail</strong>: where the top people in the company are obsessed with the details, and this (naturally) trickles down since no one wants to lose their job, lol.</p><p>All these are certainly great to have as a company. But the best experiences I’ve had were the ones where the engineers themselves were enamoured by the design, and so they religiously coded every last detail. Obviously, being able to fall in love with a design as an engineer is a special trait which companies who care about design should hire for, but I digress.</p><h3><strong>Learning to Code</strong></h3><p>I could go on about all the noble reasons I learnt to code, but it was mostly to satisfy my curiosity. I had gaps in my knowledge that needed filling. So this time, I took a more systematic approach and started again from the basics (of javascript). I immediately went after the gaps I had identified over the years.</p><p>First up for me was <em>fetch</em>. This one was major for me, I just had to know. So I did the easiest-smallest thing. An “app” that did just one thing; making an API request and displaying the response.</p><p>I built a <a href="https://random-joke-generator-nine.vercel.app/">random joke generator</a>. It was simple, you hit a button, you get a new joke. I learnt how to work with async processes and altering UI based on the response, a fun little project.</p><p>Meanwhile, I decided to brush up on my CSS too. Lots had changed and I enjoyed the thrill of writing pure CSS — a purist, I know. So I decided to focus on that for a bit, making a simple <a href="https://expensemanagement-beta.vercel.app/">expense management app</a> which received much praise (for some reason). The thing doesn’t even work that well, only looked nice.</p><p>Then, a <a href="https://to-do-phi-lac.vercel.app/">to-do app</a>. Where I learned some new CSS features and old ones that I couldn’t be bothered to learn earlier.</p><h4>React</h4><p>Next up, I wanted something more complex. So I started re-learning react. This one was super hard because MANY things had changed in those few years, but the <a href="https://www.youtube.com/playlist?list=PLC3y8-rFHvwgg3vaYJgHGnModB54rxOk3">course I took on YouTube</a> was great.</p><p>After the course, I built my next app, a <a href="https://fuud-phi.vercel.app/">food recipe catalogue</a>. This time with more than one API request and even some advanced features — like search, favourites (using localStorage) and some CSS animations. This one was very fun and fulfilling and I could see it all coming together.</p><h4>Typescript</h4><p>I had heard a lot about it and wanted to give it a try. I immediately saw the benefits and I now refuse to write javascript unless I HAVE to. My first project with Typescript + React was tumultuous, but I survived. It was another fun project, an <a href="https://artinst.tofunmiadewuyi.com/">art gallery</a> with search and all (and debouncing? marvellous ).</p><h4>NextJS</h4><p>It took me a while to settle on which framework to learn but I chose NextJS in the end. After taking the course, I decided to build myself a new <a href="https://www.tofunmiadewuyi.com/?theme=dark">portfolio</a> site. This somehow led to me writing this article but deserves an article of its own. With my track record, I hope it doesn’t take me another year to get to it.</p><p>This journey has been great. I certainly now have more confidence talking to engineers, designing better web-based apps and managing the entire process.</p><p>Next up for me is tackling full-stack apps and I’m in the middle of figuring that out. Already working on my first one but using Convex as my backend. Started learning about Postgres but that is certainly a longer road. I think getting comfortable with how databases work will allow me to learn the backend better — so that&#39;s my strategy.</p><p><strong>Unsolicited advice, thoughts, and hot-takes</strong><br>- Designers should learn to code. Not to take an engineer’s job, but just enough so they communicate and design better.<br>- More teams should have a <strong>Design Engineer</strong>. Someone whose job it is to be a go-between. To ensure proper alignment and execution between both teams.<br>- Companies should care more about design, and empower designers in that regard.</p><p><em>Selah</em></p><p><em>Hi, from the present :)</em></p><p><em>This article was written much earlier this year (2024) and I now have more hot takes since I started learning Vue, Nuxt &amp; Supabase .</em></p><p><em>Stay tuned for the next article ;)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32f4394d1284" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: Snowy, an Ice-Cream app]]></title>
            <link>https://7ai.medium.com/ux-case-study-snowy-an-ice-cream-app-9efaf537b92d?source=rss-33559ca92a5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9efaf537b92d</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui-design-for-mobile-apps]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Tofunmi Adewuyi]]></dc:creator>
            <pubDate>Sun, 14 Mar 2021 23:58:04 GMT</pubDate>
            <atom:updated>2021-03-14T23:58:04.078Z</atom:updated>
            <content:encoded><![CDATA[<p>The UX design case study on the mobile application Snowy that lets customers order ice-cream and co-ordinate pickup.</p><p><em>by Tofunmi Adewuyi</em></p><figure><img alt="Cover image" src="https://cdn-images-1.medium.com/max/1024/1*ANGKv95dZoDEbjIuTl-e3g.png" /></figure><p>Among various types of mobile apps, the ones devoted to food present a very popular category. Solutions like this (co-ordinated pickups) are increasingly popular these days. And as a result of the pandemic (Covid -19), shops and restaurants can no longer have the same number of people in-shop as before. Today I am sharing a case study of one of them, the mobile app Snowy allows users order ice-cream and then co-ordinate pickup so they don’t spend so much time in the shop, and so business can go on as usual, without the in-shop traffic. Let’s dive into the creative process.</p><h3>Project</h3><p>UX design of a simple mobile app for ordering ice-cream and co-ordinating pickup.</p><h4>User research</h4><p>Firstly, I started out with surveys and interviews to determine what features customers would expect to see in an app like this. I also validated and tested some of my assumptions.</p><p>Some of the insights I received were on concepts like pricing, ordering, recommendations and so on. For example, 75% of customers interviewed said pricing was one of the major factors(if not the major factor) that determined what they bought, and knowing the prices of the items helped them make decisions faster and improved their experience. Also ~85% of customers were more likely to order something they have had before, and were only willing to try new stuff out once in while, so being able to easily re-order an item improved their experience.</p><h4>Personalization</h4><p>Personalization of applications and websites has been one of the <a href="https://blog.tubikstudio.com/15-hot-ui-design-trends-for-web-and-mobile-in-2018/"><strong>hot trends in user experience design</strong></a><strong> </strong>for a couple of recent years now. And even though it’s not enough to give users the product to solve their problem — it re-inforces the notion that you’re trying to solve their problems in particular. And this was a very important aspect of the design.</p><h4>Wire-framing and testing</h4><p>With the insights from my research, I quickly developed wireframes, that I tested out by asking customers how they would perform specific tasks, I also asked them what some terms meant to them and what type of feedback they expected from performing each task.</p><figure><img alt="Some of the wireframes I developed" src="https://cdn-images-1.medium.com/max/1024/1*46XFnI-IzIW9z3e6iY3CDA.png" /><figcaption>Some of the wireframes I developed and tested</figcaption></figure><p>After iterating, I finalized the wireframes and moved on to designing the high fidelity screens.</p><h4>High Fidelity design</h4><figure><img alt="High fidelity screens" src="https://cdn-images-1.medium.com/max/1024/1*vp78gAjqUD3KoB2gkyF9GA.png" /><figcaption>High-fidelity screens</figcaption></figure><p>I developed components using the atomic design principle, it helped with achieving consistency across the app, I also used illustrations on some screens to help convey the message of each screen better, and to make the users comfortable with their position anywhere in the app.</p><h4>Prototyping and interaction design</h4><p>After the high-fidelity design, I moved on to prototyping, where I also designed some of the micro-interactions and implemented them in the prototype.</p><figure><img alt="Gif of the prototype and some micro-interactions" src="https://cdn-images-1.medium.com/max/1024/1*VcZPIYIBF-A8uUY8Cmuu5w.gif" /><figcaption>Prototype and micro-interactions</figcaption></figure><p>You can view the <a href="https://www.figma.com/file/w283rdeCnSuULqo5JUIepB/snowy?node-id=117%3A4569">prototype</a> here.</p><p><em>Note: For a pleasurable experience, only use browser to view while on a computer, if you are on mobile, use the Figma mirror app.</em></p><h4>Bottom Line</h4><p>With competition and a constantly growing number of mobile apps , the first impression of apps can no longer be just nice and clean. The successful app, in this case, should instantly appeal to the customer, aesthetically and emotionally, and be simple to use. Also letting them interact according to their personal preferences.</p><p>View the project on my behance <a href="https://www.behance.net/gallery/114937123/Snowy">here</a>.</p><p>Stay tuned for my next case study.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9efaf537b92d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Chores Done]]></title>
            <link>https://7ai.medium.com/getting-chores-done-a89ede720a6b?source=rss-33559ca92a5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a89ede720a6b</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Tofunmi Adewuyi]]></dc:creator>
            <pubDate>Mon, 30 Nov 2020 13:25:54 GMT</pubDate>
            <atom:updated>2021-03-14T18:38:44.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*4A1Tt51pDy1Wn5iCOxBbFA@2x.jpeg" /></figure><h4>Tofunmi Adewuyi on Taskie</h4><p><strong>Taskie</strong> is an application that aids parents in teaching their kids the value of work, time and money. While it is not necessarily important that kids paid for helping out at home, it is a good way of letting them know that money is generally worked for, and when you provide value you get rewarded. Taskie also helps them in saving towards a specific goal.</p><h4>Coordinating chores at home can be a teachable moment</h4><p>The main goal of <strong>Taskie</strong> is to guide kids towards a financially healthy future, while also making them understand the value of work and reward. Having kids understand the value of money helps with explanations on why they don’t need certain things and helps them decide the things that they consider a priority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*ftPfnaVzm9-TNfoYJFc1pQ@2x.jpeg" /></figure><h4>User Persona</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*8RScfLiR61APOYdU88NyqQ@2x.jpeg" /></figure><h4>Survey</h4><p>Because of personnel constraints, I only conducted an online survey asking parents various questions regarding the dynamics around chores and delegating and how they would engage with the application.</p><h4>Sketching for the best Ideas</h4><p>In the sketching stage of my design process, after deciding who this app is being designed for and conducting my survey, the answers informed some of the decisions around features in the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WhvThe_Qy9XuM4QFjlLruw@2x.jpeg" /></figure><p>For example, the parents pointed out that making each task recurring easily was very important to them. They also said that they needed to review tasks performed by their kids before the points were assigned, according to them it is easier to prevent them from abusing the system than fishing out tasks they may not have completed but ticked as completed.</p><h4>The Final Result</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*ME_VH0u8DAawqVcrGuQg6Q@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*N6YuyShMjBAevFpAymW5SQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*u-6mWOnTuX7BlsHpEGSP1Q@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*6t_R0tMyhnFsh4cFpVzmxA@2x.jpeg" /></figure><h4>Design Principles</h4><p>For this project I adhered to the 8pt grid design principle to create a uniform design, and also help create a visual hierarchy making it easier on the eyes.</p><h4>Results</h4><p>This design is still subject to the final approval of the client, but this app has been designed for both android and iphones. There is no Tablet or desktop design at this time.</p><p>See some of the screens at https://www.behance.net/gallery/109100747/Taskie</p><p>Thank you for reading my case study, I want to work with you, shoot me an email at tiadewuyi@gmail.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a89ede720a6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>