<?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 Princess Oviawe on Medium]]></title>
        <description><![CDATA[Stories by Princess Oviawe on Medium]]></description>
        <link>https://medium.com/@princessoviawe?source=rss-eebec536dc2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rgkKsp8MoKg8vKFmFH9SLw.jpeg</url>
            <title>Stories by Princess Oviawe on Medium</title>
            <link>https://medium.com/@princessoviawe?source=rss-eebec536dc2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:43:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@princessoviawe/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[Musings of a design team of one: #2]]></title>
            <link>https://princessoviawe.medium.com/musings-of-a-design-team-of-one-2-ffc16d7457fb?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffc16d7457fb</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 21:31:43 GMT</pubDate>
            <atom:updated>2022-12-06T21:34:24.026Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Some broodings and reflections of a solo product designer.</em></p><blockquote><em>For better context read the first part </em><a href="https://medium.com/@princessoviawe/musings-of-a-design-team-of-one-de0832513ebd"><em>here</em></a><em>, but if not, you’re welcome to the party.</em></blockquote><figure><img alt="A siluoette of a man standing on a rocky landscape" src="https://cdn-images-1.medium.com/max/1024/0*K7KX8xb3NXj3_5Er" /><figcaption>Photo by <a href="https://unsplash.com/es/@mabe12?utm_source=medium&amp;utm_medium=referral">Austin Mabe</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>This is a sign of progress, and I have mentally given myself a pat on the back for starting a second issue on this topic.</blockquote><blockquote>Also, I’m thinking of continuing this as a series, Anyways, we’ll see.</blockquote><p>Some miles from the beginning:</p><p>One characteristic about me is that I like structure and processes. Whatever activity it may be as far as I am aware of the process involved, I’ll follow it to the letter, But as work life would have it, I learned that one has to be open to new experiences, processes and structure. We can’t all work in one way all the time. Cost, certain circumstances and creativity have to be taken into account sometimes.</p><p>This realisation stood out when I joined my first startup, after rigorous self-learning about UX design processes and a few projects in my portfolio, I found out that not all design tasks start the text-book way, sometimes there’s little to no user research done due to time or budget constraints and sometimes, the management isn’t aware <em>(or doesn’t care) </em>that research is essential.</p><p><em>As a refresher, here’s a popular structure for design projects</em></p><figure><img alt="Double diamond design process poster" src="https://cdn-images-1.medium.com/max/1024/0*iqddVUMe2puSy4Bq.png" /><figcaption>Double diamond design process image on <a href="https://upload.wikimedia.org/wikipedia/commons/b/bd/Double_diamond.png">Wikipedia</a></figcaption></figure><p>One way I’ve tackled this over the years is to embrace flexibility and try always to find a walk-around.</p><p>Example:</p><p>When research is overlooked or tight on budget, resort to <a href="https://medium.com/front-line-interaction-design/digital-guerrilla-research-edf977b0479c">guerrilla research</a>: have quick interviews with 5 -10 persons, get insights fast, write a report, present and then utilise outcomes in design.</p><blockquote>In the long run, this is not a solid plan for most ideas, as nothing, I repeat, nothing beats in-depth research. I usually resort to this either as a last option or as a way to convince stakeholders of the importance of thorough research.</blockquote><p>Something to note about the beginnings is that it was riddled with poorly managed feedback. It used to be quite difficult to separate negative feedback from constructive feedback. <em>What’s even the difference you may ask?</em></p><p>Well, negative feedback focuses on everything you’ve done wrong <em>-although most times when this is received it’s often true. </em>This hurts because your flaws are exposed, and some people don’t say it nicely.</p><p>Constructive feedback is kind of mixed, your mistakes are clearly pointed out, but you are also given opportunities or ideas on how to be better, sometimes you are first appreciated for what you did well before your flaws and corrections are out.</p><p>In order to learn and improve better at this, I tried the following.</p><ul><li>Writing down any feedback I receive. If it’s constructive I’ll also note down suggested ways to improve.</li><li>Set a reasonable timeline to improve and …</li><li>If possible reach out again for more feedback</li><li>Document any new improvements.</li><li>Try as much as possible not to dwell on mistakes.</li><li>Try not to take harsh feedback too personally (preserve my mental health by selecting the main points to improve on.</li></ul><p>I’d like to say this has worked so far, and I’m still looking for more ways to improve, but if you’d like to put me to a test, the comment section is free for you.</p><p><em>Just kidding, please be nice, I’m only human.</em></p><p>Well, I’ll pen down here, to be continued…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffc16d7457fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Musings of a design team of one #1]]></title>
            <link>https://princessoviawe.medium.com/musings-of-a-design-team-of-one-de0832513ebd?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de0832513ebd</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Tue, 29 Nov 2022 19:00:55 GMT</pubDate>
            <atom:updated>2022-11-30T16:09:42.814Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A person running on a hilly landscape trail close to the ocean" src="https://cdn-images-1.medium.com/max/1000/0*tcHclZdlgjL7MaaJ" /><figcaption><a href="https://unsplash.com/photos/uZVtAixV8c8">Photo by Peter Vanosdall on Unsplash</a></figcaption></figure><p>It’s been two years since I last wrote an article and published it. Post-pandemic my life has been chiefly about honing my craft and earning a decent living, But during this time I have grown in my career, made mistakes, and learnt from them. Now, I’m in the process of reminiscing and reaccessing my journey so far.</p><p>In the process of thinking back, I’ve realised that 90% of my professional work experience as a product designer has been at early-stage startups and boutique companies while the remaining 10% I did freelance work. Digging deeper, I realised that I had been the only product designer in the entire company in most of the companies I&#39;ve worked at.</p><p>Well, since this is my comeback article and my shot at consistent journalling I’m going to share some of the experiences I’ve had being the only product designer at an early startup.</p><p><em>Sidenote: So, I’m just going with the flow writing this article and might not have all the words to describe all my experiences so far, so bear with me.</em></p><p>The Beginning:</p><p>The saying, <strong><em>“a new day, another opportunity to be world-class”</em></strong> was pretty much my mantra every morning before starting work, and I’ll be excited to go fire up Figma, google docs and the linear app/Jira/ClickUp to plan my tasks for the day and later on prepare for morning standup with the rest of the team.</p><p>I must say the beginnings were full of enthusiasm, for the product, its users and the rest of the team. Deliverables and tasks breakdown would either be on the Linear app, Jira or ClickUp, user research reports on google docs and I’d go over them, again and again, in order to think through the user flows while keeping the business deliverables in mind, I’ll also sketch designs and start with the high fidelity designs as well and sometimes I’ll have to present those designs almost immediately to the product manager and other developers for feedback and sometimes the designs get implemented the same day.</p><p>I remember in those times, I could sit poorly at my desk for 8+ hours at a stretch tweaking designs or brainstorming with the team on the next steps, I’ll entertain a few bathroom breaks and all the while I’ll be munching snacks and biscuits. By the time I look out, It was already dark outside and my family has had dinner without me but that doesn’t mean my meetings are over or that work was done.</p><p>It was an endless cycle, but the hard work paid off with a successful product launch amassing thousands of users at a go, with users leaving good and encouraging feedback. Of course, there were some minimal kinks around, but it was good enough, and I remember feeling so proud that I contributed a significant part and that my work had an impact, but at what cost? And how much did I have to pay for it?</p><p><strong>1.<br>Cost</strong>: Some serious back pains from bad sitting posture.</p><p><strong>Fix:</strong> I decided to invest in an ergonomic chair and softer mattress, My back hasn’t ceased to stop thanking me.</p><p><strong>2. <br>Cost:</strong> Spent endless time in meetings and feedback calls for the greater part of some days.</p><p><strong>Fix:</strong> Got better at async feedback by using tools like loom for recording flows and prototypes.</p><p>3.</p><p><strong>Cost:</strong> Creative block. (need I say more… It sucks)</p><p><strong>Fixing tools:</strong> Took a solo trip to Ouidah, a coastal province in Benin republic, slept by the lagoon and enjoyed nature.</p><p>- Took time out to visit friends and plan fun activities</p><p>- Went on self dates</p><p>- Slow living on weekends</p><p><em>(PS: I am still doing some of these activities, they help me see more of life outside work).</em></p><p>Asides from costs and fixes, I also realised along the way, that the fact that I’m a design team of one doesn’t mean I get to work alone. Collaboration is very important. Collaboration with product managers, product owners, Engineers, the marketing team and even the customer success team would go a long way to make my day-to-day work easier.</p><p>In my current team, there’s a lot of cross-communication across teams and async updates. I guess when you work with a company of fewer than 30 employees, cross-communication and collaboration are easier.</p><p>I’ll pen down here, for now, I hope to continue writing down my thoughts more often.</p><p>To be continued …</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de0832513ebd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing Alt Text for Images with Styled Typography]]></title>
            <link>https://medium.com/elly-for-a11y/writing-alt-text-for-images-with-styled-typography-adaa161f5fdd?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/adaa161f5fdd</guid>
            <category><![CDATA[alt-text]]></category>
            <category><![CDATA[image]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[text]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Wed, 16 Nov 2022 11:26:18 GMT</pubDate>
            <atom:updated>2022-11-16T11:26:18.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Writing Alt Text for Images with Styled Typography" src="https://cdn-images-1.medium.com/max/1024/1*JH4QJYPzLq_sz1unEaWvcA.png" /></figure><p><em>This section is part of a 4-part series — Alternate text and captioning by </em><a href="https://twitter.com/EllyOrg"><strong><em>team elly</em></strong></a></p><p>You’ve probably heard the common saying, &quot;A picture is worth a thousand words”. How could we then describe an image that is made up of words?</p><h3>Styled Typography</h3><p>Styled typography is an image composed of typography. It has been designed in a particular style with decorative effects (e.g. shadows, borders, etc.). Often, the text in the image has the exact meaning of the content of the image.</p><p>In this section, we will learn how to write alt text for these images:</p><ol><li><strong>Be descriptive: </strong>When writing alt text for images with styled typography, ensure they are descriptive.</li><li><strong>Content is key: </strong>Shadows and other design effects are usually not mentioned in the alt text, because they are not relevant in describing the main message the image carries.</li></ol><p>Consider the image below:</p><figure><img alt="A handwritten text on a lined notebook that reads “Dream anything then think what does it take?”" src="https://cdn-images-1.medium.com/max/480/1*36rrov8GtOaw73jeI9d-iQ.png" /><figcaption>Photo by <a href="https://www.pexels.com/@daria">Daria Shevtsova</a> on <a href="https://www.pexels.com/">Pexels</a></figcaption></figure><p>In this example, a descriptive alt text would be, A handwritten text on a lined notebook that reads “Dream anything then think what does it take?”</p><p>Consider another example below:</p><figure><img alt="A cursive text that reads “Savour every Moment”" src="https://cdn-images-1.medium.com/max/427/1*TEV0rna8QlOfjzxDhs28VA.png" /><figcaption>Photo by <a href="https://www.pexels.com/@ian-panelo">Nothing Ahead</a> on <a href="https://www.pexels.com/">Pexels</a></figcaption></figure><p>A suitable alt text can be: A cursive text that reads “Savour every Moment”</p><p>❗ If you are designing a website, it is more accessible to use CSS and web fonts for styling text, instead of using an image for text and adding alt text. CSS and web fonts allow one to easily resize, select and/or translate the text (using browser extensions), whereas, for an image, it is very difficult to do so. For example, if you are reading this online, try out this simple exercise: Try zooming into the two texts below. Notice how the image (left) becomes pixelated and blurry whereas the web font (right) remains clear? The former allows for easier resizing, text selection as well as easier translation to a different language (via browser add-ons/extensions).</p><p>Image:</p><figure><img alt="Elly logo" src="https://cdn-images-1.medium.com/max/171/0*IBVD13VxBQVuSzYk" /><figcaption>Elly logo</figcaption></figure><p>Web font:</p><p><strong>Elly</strong></p><h3>Logos</h3><p>Another use case is writing alt text for logos. It is important to convey the spirit and look of your brand to viewers of all abilities. While text logos might be easy to read and decipher, adding alt text helps make the content to be communicated much clearer.</p><p>Below are the key things to keep in mind when crafting alt text for logos:</p><ol><li><strong>Specify that the image is a logo:</strong> Most screen readers cannot tell if an image is a logo or not. Using the word “logo” helps users understand the image’s correct purpose.</li><li><strong>Include the text in the image: </strong>Like all other types of images, your alt text must include any written text in the logo so screen readers can read it.</li><li><strong>Alt text format: </strong>For logos, the format should be “[Organization name] logo.”</li></ol><figure><img alt="Elly logo" src="https://cdn-images-1.medium.com/max/398/0*8qv-aIwDfia1__pf" /><figcaption>Elly logo</figcaption></figure><p>Let’s look at some examples!</p><p><a href="http://www.joinelly.com/home">Elly</a></p><p>Alt Text: Elly logo</p><figure><img alt="Microsoft logo" src="https://cdn-images-1.medium.com/max/768/0*NASHRXyunrnwqkD2" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:Microsoft_logo_(2012).svg">Microsoft Corporation</a>, Public domain, via Wikimedia Commons</figcaption></figure><p><a href="https://commons.wikimedia.org/wiki/File:Microsoft_logo_(2012).svg">Microsoft Corporation</a>, Public domain, via Wikimedia Commons</p><p>Alt text: Microsoft logo</p><h3>Summary</h3><p>Most of the time you can simply copy the text directly, though you can choose to include additional details such as stylizations.</p><p>For logos, a rule of thumb is to just use the alt text “&lt;Organization Name&gt; logo”.</p><p><em>Thanks for reading my part in this series. I’m </em><strong><em>Princess Oviawe</em></strong><em>, a product designer and also an accessibility and open-source enthusiast. You can learn more about me on </em><a href="https://princessoviawe.design/"><strong><em>my website</em></strong></a><em>. Stay slaying 🌱</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adaa161f5fdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elly-for-a11y/writing-alt-text-for-images-with-styled-typography-adaa161f5fdd">Writing Alt Text for Images with Styled Typography</a> was originally published in <a href="https://medium.com/elly-for-a11y">Elly-for-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: Sub Buddy -Subscription Management app.]]></title>
            <link>https://princessoviawe.medium.com/ux-case-study-sub-buddy-subscription-management-app-75d76c868621?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/75d76c868621</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[subscription-management]]></category>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Tue, 17 Nov 2020 22:48:52 GMT</pubDate>
            <atom:updated>2020-11-30T17:18:56.636Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Case Study: Sub-Buddy-Subscription Management app.</h3><p>Your Subscriptions, your way!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCKgwgTSbmfico3-nD8I-w.png" /><figcaption>UX Case study cover image</figcaption></figure><p>We’ve all been there at one point in our lives, where we desire to take charge of our finances. That feeling of being in charge is something we all crave, but sadly not many of us have had the luxury of this. How about we have a hold on them. Introducing Sub-Buddy-Subscription Management app.</p><p>Some background story and Research.</p><h4><strong>Background</strong></h4><p>Studies show that subscription-based business models have seen exponential growth over the last decade. A subscriber commits to repeatedly pay for a good or service for a fixed or indefinite timeline, has been caused by the shift from the one-time selling of physical products to selling digital services on a subscription basis. While this may be good for the business and sales executives, users, on the other hand, are overwhelmed by this constant stream of deductions from their bank accounts due to the number of subscriptions they have and sometimes they may not need some of these subscriptions again.</p><h4><strong>Research Goal</strong></h4><p>The goal of this study is to find out ways users currently manage their subscriptions, understand how they would want to manage their subscriptions, find out unfortunate situations that may have happened to them when managing subscriptions and would they be interested in using a digital subscription manager.</p><blockquote><em>Want to read this story later? </em><a href="http://usejournal.com/app/signup?save_link=https://blog.usejournal.com/ux-case-study-sub-buddy-subscription-management-app-75d76c868621"><em>Save it in Journal.</em></a></blockquote><p><strong>User Research</strong></p><p><em>“It’s hard to keep track of all the products and services that we have subscribed to every month. All we see is money deducting from our accounts, sometimes from services that we don’t need anymore. How can you design a product which helps manage subscriptions?”</em></p><p><em>How do people record their subscriptions and what traditional methods have they adopted in the past?</em></p><p>In order to understand these challenges, I conducted an online survey with 43 results. These were the results;</p><ul><li>65% (28 persons) were male while the rest 35% (15 persons) were female.</li><li>95% were 18 to 30 years old.</li><li>81% of topmost subscription bills were data and App subscriptions.</li><li>70% (32 persons) don’t have a record of their subscriptions.</li><li>Only 5% (2 persons) write their current subscriptions down in a logbook.</li><li>45% (19 persons) have received unexpected deductions from their bank accounts due to automatic subscription renewals.</li><li>100% are smartphone savvy.</li><li>91% are interested in a subscription management app.</li></ul><h4>And more research...</h4><p>In order to get some qualitative responses, I interviewed a few persons and asked them the following questions</p><ul><li>Are there any services you’ve subscribed to, if yes, please give some examples?</li><li>How do you record your subscription payments?</li><li>Have you ever received some unexpected deduction from your account from subscription auto-renewal?</li><li>What are the challenges you’ve faced with keeping track of your subscription payments?</li></ul><p>From these questions I got some really interesting responses:</p><ul><li>“When I plan my finances, I want to be able to see all the services I have subscribed to in order to plan budgets for what’s a priority and what’s not …”</li><li>“…I have a lot of subscriptions, but sometimes when I am broke, I need to know what renewals need to be paid and the ones I don’t need. I want to plan better…”</li></ul><h4>Competitive Analysis:</h4><p><strong>Recall</strong>: from the survey analysis many participants were interested in a subscription management app which was exciting because the aim of the study was to Design one. With this in mind, I had to look into the market and check out existing solutions. I looked into the current app solutions used today (<em>especially in the Nigerian Market</em>) for managing subscriptions and expenses.</p><p>Below are some app examples:</p><h4><strong>REACH — Exclusively on Android.</strong></h4><p>Reach app is an automatic expense tracking, income, saving and budget manager.</p><p>Also used by a number of persons for tracking subscriptions.</p><p>PRO:</p><ul><li>Free app. Most features are free as well.</li><li>Gives a birds-eye view of all financial activities.</li></ul><p>CONS:</p><ul><li>Android only</li><li>A lot of features shown at once to users. Could be quite overwhelming at first.</li><li>No payment notification</li></ul><h4><strong>App Store — Subscription Manager (iOS):</strong></h4><p>PRO:</p><ul><li>Native solution</li></ul><p>CON:</p><ul><li>Only lets you manage subscriptions bought via the app store.</li></ul><p>Interestingly, I also found some reviews of these apps, that users were most pained about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqJGbildCagn5w8vDjqO9w.png" /><figcaption>Google play store review</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pl3aghmKMXRSr6AOTUidLQ.png" /><figcaption>Google play store review</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpkQ56_AJecsVtakQ3SToQ.png" /><figcaption>Google play store review</figcaption></figure><h4>User Persona</h4><p>Based on the generative user research I gathered, I created two user personas that capture the essence of my target users. Meet Jonathan and Grace.</p><p>The purpose of creating a user persona is to compare and contrast the two main features of the subscription process: the subscription and payment reminders.</p><p>The two personas are individually situated in contrasting environments. Jonathan’s case will demonstrate a subscriber who needs to manage all subscriptions, and Grace’s case will be displaying the situation of reminding a subscriber of their payment renewals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tr13I_BdsfzSYgsfhrGKOw.png" /><figcaption>user persona</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxLa4ICb2QJY2bIs5mRU7Q.png" /><figcaption>user persona</figcaption></figure><h3>Finding Solutions</h3><p>After brainstorming, researching and interviewing. I began to understand what problems people have, what I will be designing for and who I will be designing for.</p><p>I categorised them according to the most pressing pain points to the least and highlighted possible solutions.</p><p>These findings have helped me re-shape the direction of developing a subscription manager mobile app. These are the new adjustments as follows:</p><ol><li><strong>Reminders</strong></li></ol><p><strong>Send notifications about subscription renewals.</strong></p><p>In order to plan appropriately, users could receive notifications about their subscription before it auto-renews that way they plan appropriately ahead of time.</p><p>The mobile app would notify users about their subscription before it renews. Using post notifications, SMSs, and emails. (<em>all choices are dependent on the user preferences</em>)</p><p>2. <strong>Simple e-records</strong></p><p><strong>Manage subscriptions with a simple interface.</strong></p><p>One of the pains recorded by the interviewed participants was the complex nature of most subscription management apps.</p><p>“Most digital solutions look like accounting software, I don’t understand that”</p><p>To solve this my mobile app solution would have a simple yet intuitive interface that would manage users subscriptions (<em>after they allow the app to read their bank account summary</em>) and also input them manually.</p><p>3. <strong>Subscription payment statements (logs)</strong></p><p><strong>View past subscription payments and dates.</strong></p><p>People need to be able to see a history of all their subscription payments to solve this. The mobile app will give a detailed yet easy to understand summary about subscription details, dates of payment and next repayment dates.</p><h3>Introducing — Sub Buddy</h3><p>Recall: The goal of the study was to find out how users currently manage their subscriptions, After getting insights and drawing conclusions, I could see that they were interested in a subscription management app. With that, I started designing!</p><p><strong>Name</strong>: “Sub Buddy”</p><p>I choose the Sub Buddy as the Apps name to depict <em>a close and friendly</em> subscription manager.</p><h4>Architecture</h4><p>I created a simple architecture that will portray more details of the user’s journey upon 5 main stages: Onboarding, Home, Subscriptions, Analytics and New Subscription. While building the architecture, I took into consideration all the research I have gathered, including user personas, flows etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs_Uj7HJBkklvGS5I8eFtw.png" /><figcaption>Sub Buddy Arcihtecture</figcaption></figure><p><strong>Low-fi wireframes</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1wj_lknHqpedB1s7jz8W-A.png" /><figcaption>Wireframes</figcaption></figure><p><strong>Final designs!</strong></p><p><strong>Onboarding</strong></p><p>You get onboarded through some introductory screens then proceed to sign up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tmNKyQCDjsEHPDTVpmCMvQ.png" /><figcaption>high fidelity design</figcaption></figure><p><strong>Analytics</strong></p><p>One of the main aims of the app is to display analytics for payments and app time usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*grbg16T1fajHPxkosC_1dA.png" /><figcaption>App analytics for Sub buddy</figcaption></figure><p><strong>Reminders</strong></p><p>You don’t have to be afraid of forgetting your payment dates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*fUegQHzzyqH_CJXYfRtVAg.png" /><figcaption>lock screen notifications for Sub buddy</figcaption></figure><p><strong>Style Guide</strong></p><p>Overall while designing Sub-Buddy, I’ve used a style guide for an effective working process and consistent context of the brand story. These components could be consistently developed and will produce another significant one that fits for the better user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FgJ9Hz5BFCZ815Cv3JwM3g.png" /><figcaption>Style guide for Sub Buddy</figcaption></figure><h4>Reflections</h4><p>Although I have worked on a couple of UI designs before, Sub Buddy is the first personal project in the form of case studies to design and prototype in logical steps.</p><p>My overall experience throughout the whole process was really interesting, from researching the market, understanding user needs and matching them with design solutions. I found out that a lot of persons are looking for a better way to manage their subscriptions and I could see that there was and still is a high demand for solutions.</p><p>Next Steps…</p><p>I will continue to iterate on the designs already created, add new features to accommodate subscriptions like Data Subscriptions (Internet fees) and Electricity payments. And also possibly find a team to develop the app into the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HPCgk4gtQm5omRfkCcdYw.png" /><figcaption>sub buddy mockup</figcaption></figure><p>Special Thanks to <a href="https://twitter.com/newdinmaaniugbo">Dinma Aniugbo</a>, <a href="https://www.linkedin.com/in/duziem-ugoji/">Duziem Ugoji</a>, <a href="https://twitter.com/DearDesignr">Dear Designer Mentorship program</a>. I really appreciate your help in producing this. And also all my friends who helped proofread this work. I am grateful.</p><p>Thank you for reading my article :) I will really appreciate any comments and feedback below or just feel free to contact me via <strong>oviaweprincess2000@gmail.com</strong></p><h4>More from <a href="http://usejournal.com/">Journal</a></h4><p>There are many Black creators doing incredible work in Tech. This collection of resources shines a light on some of us:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fusejournal.com%2Fapp%2Fembed%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b&amp;display_name=Journal&amp;url=https%3A%2F%2Fusejournal.com%2Fapp%2Fspace%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b&amp;image=https%3A%2F%2Fimperio.usejournal.com%2Fimage%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b%2F1602668529%3Fclient%3Dfacebook&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=usejournal" width="900" height="710" frameborder="0" scrolling="no"><a href="https://medium.com/media/ca84c63a615be91123438987244ec06c/href">https://medium.com/media/ca84c63a615be91123438987244ec06c/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75d76c868621" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design language for data visualizations]]></title>
            <link>https://princessoviawe.medium.com/design-language-for-data-visualizations-ae196f9e1a86?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae196f9e1a86</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Sat, 14 Nov 2020 11:19:25 GMT</pubDate>
            <atom:updated>2021-01-28T15:02:07.424Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xstqO77hqnLZdrfb" /><figcaption>Img src: “ <a href="http://depictdatastudio.com/">depictdatastudio.com</a>”</figcaption></figure><p>Topics discussed in this article.</p><ol><li>Introduction to data visualisations.</li><li>Principles of data visualisation design</li><li>Types of Data visualisations and tips.</li></ol><p>Creating data visualizations for a presentation or just for practice only gets successful if your users understand what insights you are trying to bring to light.</p><p>Every business has a story to tell, and that can be conveyed through data visualizations, according to <a href="https://www.dataquest.io/blog/design-tips-for-data-viz/">dataquest.io</a> “data is only as helpful as it is understandable”.</p><p>Well, for most Data scientists, design is not at the forefront but creating effective charts and visualizations. Although most of the time, these visualizations end up as overdressed charts that confuse and disorient the users and audience.</p><p>Here are some design guidelines;</p><h3>## PRINCIPLES</h3><p>According to <a href="https://material.io/design/communication/data-visualization.html">Material Design</a>, data visualization depicts information in a graphical form and should follow these principles.</p><p>ACCURACY</p><p>Data visualizations should be accurate, of high integrity and should have a clear meaning.</p><p>HELPFUL</p><p>Data visualizations should help users understand the context of which a group of conditions exist, where and when something happens that emphasises exploration and comparison.</p><p>SCALABLE</p><p>Data visualizations should be created to adapt to different screen sizes in order to accommodate user needs on data dept, complexity and modality.</p><h3>## TYPES</h3><p>Data visualisations can be expressed in different forms. Charts (or graphs) are the most popular way of visualising data.</p><p><strong>Trend and over-time charts </strong>These charts show the trends and comparisons of data across multiple categories over a period of time.</p><p>These charts include:</p><ol><li>Line charts</li><li>Bar charts</li><li>Stacked bar charts</li><li>Candlestick charts</li><li>Area charts</li><li>Timelines</li><li>Horizon charts</li><li>Waterfall charts</li></ol><p>Use cases:</p><ol><li>Health statistics.</li><li>Stock price performance,</li><li>Educational statistics.</li><li>Chronologies.</li></ol><p><em>nuggets: Bar charts are very easy to read because they basically allow our eyes to simply compare the relative heights of the bars. For users to draw meaningful conclusions from a bar chart, it has to be presented in full and start from a vertical axis of zero.</em></p><p><strong>Categories comparison</strong>: These charts compare data between multiple, varying and distinct elements.</p><p>Category comparison charts include:</p><ol><li>Bar charts</li><li>Grouped bar charts</li><li>Bubble charts</li><li>Multi-line charts</li><li>Parallel coordinate charts</li><li>Bullet charts</li></ol><p><strong>Part-to-whole</strong></p><p>These show how partial elements add up to a whole.</p><p>Use cases:</p><ol><li>Analyzing sales of Items of a quarter.</li><li>Survey results.</li><li>Budgets.</li><li>Consolidated revenue of product categories.</li></ol><p>Part-to-whole charts include:</p><ol><li>Stacked bar charts</li><li>Pie charts</li><li>Doughnut charts</li><li>Stacked area charts</li><li>Treemap charts</li><li>Sunburst charts</li></ol><p><em>nuggets: Pie charts summarise the individual relationships among elements as a whole. This can be visualized using angles or arcs within a circle.</em></p><p><strong>Ranking</strong> This shows the positions of items in a list.</p><p>Use cases include:</p><ol><li>Election and poll results</li><li>Performance statistics</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*QqxpshOJyeBW-j5j" /></figure><p>Ranking charts include:</p><ol><li>Ordered bar charts</li><li>Ordered column charts</li><li>Parallel coordinate charts</li></ol><p><strong>Correlation</strong></p><p>Correlation charts are mostly used for showing and summarising the association between two variables.</p><p>correlation charts include:</p><ol><li>Scatterplot charts</li><li>Bubble charts</li><li>Column and line charts</li><li>Heatmap charts.</li></ol><p><em>nuggets: Heat maps are perfect for representing defined boundaries in a dataset.</em></p><p>……….</p><p>Alright Phew!</p><p>More data visualisation guidelines and resources used in this article can be found at</p><ol><li><a href="https://material.io/design/communication/data-visualization.html#types">material.io/design/communication/data-visua..</a></li><li><a href="https://www.dataquest.io/blog/design-tips-for-data-viz/">dataquest.io/blog/design-tips-for-data-viz</a></li><li><a href="https://www.geckoboard.com/learn/data-literacy/data-visualization-tips/">geckoboard.com/learn/data-literacy/data-vis..</a></li></ol><p>Also, feel free to add more guidelines to the list in the comments.</p><p>Thanks for reading…</p><p><em>Originally published at </em><a href="https://technuggets.hashnode.dev/design-language-for-data-visualizations"><em>https://technuggets.hashnode.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae196f9e1a86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A simple approach to understanding classes and objects with python .]]></title>
            <link>https://princessoviawe.medium.com/a-simple-approach-to-understanding-classes-and-objects-with-python-17f77bd9fa11?source=rss-eebec536dc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/17f77bd9fa11</guid>
            <category><![CDATA[object-oriented]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[python3]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[curators-university]]></category>
            <dc:creator><![CDATA[Princess Oviawe]]></dc:creator>
            <pubDate>Fri, 24 Aug 2018 00:42:25 GMT</pubDate>
            <atom:updated>2018-08-24T01:02:30.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*oAIbhZDvzQ4iQZe9EN97jg.png" /><figcaption>oop</figcaption></figure><p><strong>A new programmers’ dilemma in object oriented programming (OOP)</strong></p><p>Delving deeper into programming requires learning new paradigms like object oriented programming, but for a new programmer who is just getting solid on conditionals, iterations and other forms of structured programming may find OOP a little bit difficult to understand. Well some may understand but breaking it down for a non-technical person may be tasking.</p><p>Well, when discussing OOP words like objects, classes, encapsulation, etc are often heard, but for this article I am going to stick to the concept of objects and classes.</p><h3><strong>OBJECTS</strong></h3><p>Objects in simple terms are a representation of real world elements like cars, dogs, chairs and the like. Objects share two main characteristics: data and behavior.</p><p>Lets use this analogy, take a Dog for example, it has a variety of data like breed, size, age, colour etcetera and behaviours like run, sleep, eat, bark.</p><p>In OOP, data are referred to as attributes or instances and behavior as methods. Methods are simply functions that call these objects in our code.</p><p>Objects(instances/attributes) Methods(behaviours)</p><p>Breed….eat()</p><p>Size ….. sleep()</p><p>Age…… bark()</p><p>Colour …..run()</p><h3><strong>CLASSES</strong></h3><p>A class is a blueprint from which individual objects are created. It can be seen as a model or a way to define attributes and behavior of an element. A class sort of houses all objects and methods</p><p>Example: class Dogs:</p><p>pass</p><p>maltese = Dogs()</p><p>print maltese</p><p>Here <strong>maltese</strong> is an object (instance) of the class<strong> Dogs.</strong></p><p>Say we want to build a Dog management software.This would entail modeling real life entities.</p><p>i.e Dogs into software objects.</p><p>Lets go!</p><h3><strong>Dogs (attributes)</strong></h3><p>Breed</p><p>Size</p><p>Colour</p><p>Age</p><h3><strong>Methods (behaviours)</strong></h3><p>Eat()</p><p>Sleep()</p><p>Bark()</p><p>Run()</p><h3><strong>objects</strong></h3><p><strong>Dog1</strong></p><p>breed = alsetian</p><p>size = small</p><p>age = 2 years</p><p>colour = black</p><p><strong>Dog2 :</strong></p><p>breed = maltese</p><p>size = medium</p><p>age = 3 years</p><p>colour = white</p><p><strong>Dog3</strong></p><p>breed = chow chow</p><p>size = large</p><p>age = 5 years</p><p>colour = brown</p><p>So thus far, we have created objects from our data for three dogs. So lets code this in python. Yay!</p><p><em>Class Dogs:</em></p><p><em>def __init__(self, breed, size, age, colour)</em></p><p><em>self.breed =breed</em></p><p><em>self.size =size</em></p><p><em>self.age =age</em></p><p><em>self.colour =colour</em></p><p><em>def dogData_self(self):</em></p><p><em>print(“Dog details are: Dog breed- ” + breed + “Dog size: ” + size + “Dog age:” + age + “Dog colour: ” + colour)</em></p><p><em>Dog1 = Dogs(“alsetian”, ”small”, str(2)+”years”, ”black”)</em></p><p><em>Dog2 = Dogs(“maltese”, ”medium”, str(3)+”years”, ”white”)</em></p><p><em>Dog3 = Dogs(“chow chow ”,”large”, str(5)+”years”, ”brown ”)</em></p><p><em>Dog1.dogData_self()</em></p><p>The code outputs:</p><p><strong><em>Dog details are: Dog breed — alsetian Dog size: small Dog age: 2years Dog colour: black</em></strong></p><p>So here’s a breakdown of the code above:</p><p>So on the first line we created a class called <strong>Dogs.</strong></p><p>On the second line we defined a method with a constructor init. Which helps create several instances or objects in this case were breed, size, age ,and colour. ”self” is a general convention used in python to initialize objects, so that when they are called the value assigned to them is returned.</p><p>On lines 3 to 6 we assigned the objects that would be used to call them.</p><p>On lines 7 to 9 we created a function that prints out the breed, size , age and colours of the dogs.</p><p>On lines 10 to 12 we give values to the objects i.e like creating a variable.</p><p>On lines 13 to 15 we called the methods (functions) this will return the values stored in them .</p><p>So there it is easy-peasy right! Well , more practice helps commit this to memory. So get out your keyboards and get your hands dirty with some code!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17f77bd9fa11" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>