<?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 Bianca Espinosa on Medium]]></title>
        <description><![CDATA[Stories by Bianca Espinosa on Medium]]></description>
        <link>https://medium.com/@biancaespinosa?source=rss-8ca1e0d2cd20------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XnBiwiwSZYOh__nV.</url>
            <title>Stories by Bianca Espinosa on Medium</title>
            <link>https://medium.com/@biancaespinosa?source=rss-8ca1e0d2cd20------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:28:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@biancaespinosa/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[Case Study: Redesigning the Navigation]]></title>
            <link>https://medium.com/@biancaespinosa/case-study-redesigning-the-navigation-0aa6eccd71db?source=rss-8ca1e0d2cd20------2</link>
            <guid isPermaLink="false">https://medium.com/p/0aa6eccd71db</guid>
            <dc:creator><![CDATA[Bianca Espinosa]]></dc:creator>
            <pubDate>Tue, 06 Aug 2024 14:06:13 GMT</pubDate>
            <atom:updated>2024-08-06T14:06:13.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*jaRvO6Cl__qMZkKN8ZPWyg.png" /></figure><h3>Background</h3><p>I was tasked with designing the navigation of the Parlon app. The challenge was to accommodate multiple features such as booking appointments, searching for a salon, browsing and buying deals, showcase blog articles, feature brand membership, and links to account, settings, vouchers in a user-friendly layout without overwhelming the users.</p><h3>Emphatizing with the users</h3><p>I conducted surveys to explore how users interacted with the previous version of the Parlon app and website. I interviewed 5 users, all females, around the ages of 25–40s and asked to rank their top five actions when they go to Parlon. Additionally, I asked them their thoughts about the current navigation of the mobile website. The result of the ranking are as follows (average):</p><p>1 — Browse deals<br>2 — View booking appointments<br>2 — Browse Parlons<br>2— Book an appointment<br>5 — Browse membership perks<br>6 — Read blogs</p><p>Aside from this, the users pointed out how the current navigation in the mobile site is confusing because Parlons and Booking have the same flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cw7SBjXln67j1ylwAdHwpQ.png" /></figure><p>Meanwhile, I researched other apps with similar navigation structures. I looked at how Grab, Sephora, FoodPanda, and even some e-commerce platforms like Shopee, did it. I examined how these apps organized their navigation and what elements were most prominent.</p><p>From here, I had a general idea of what items I should put in the navigation. This step really helped me understand the users’ preferences, pain points, and the actions they prioritized.</p><h3>Define</h3><p>Based on the research and survey results, I identified the top four actions users prioritized: browsing/buying deals, booking appointments, viewing their account/existing appointments, and reading blogs. This information was crucial in defining the problem: the need to streamline the navigation to make these actions easily accessible.</p><h3>Ideate &amp; Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZM4kox-yByCsDsyNy4Qew.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6uRGdcfMPKr4SWgvgng1g.png" /><figcaption>in this case, i tried combining deals and parlons under one action in order to make way for OG</figcaption></figure><p>With the users’ needs in mind, I brainstormed potential solutions. I considered various ways to incorporate the top four actions into the bottom navigation while maintaining a clean and intuitive interface. The goal was to balance the stakeholder (my boss)’s request for multiple features and the users’ desire for simplicity.</p><p>Booking can be easily seen at first load. They will be listed at the top with the date and time.</p><p>I thought about adding a “More” link so that all the other non-important items can be placed there.</p><p>After brainstorming, I created several wireframes, each emphasizing the key actions identified during the Define phase. These prototypes explored different layouts and arrangements, ensuring the most important features were easily accessible. The wireframes were designed to be intuitive, providing a seamless user experience.</p><h3>Testing &amp; Iteration</h3><p>After completing the high-fi prototypes, I showed them to my boss for approval. Their feedback was valuable because it helped further refine the navigation design. It was apparent that they value the blogs more than the membership perks. We also decided to hide the Account under More since in the Home page, the user will be able to see upcoming appointments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*sojxQJcwoD7DLhV1Qx85LQ.png" /></figure><h3>Conclusion</h3><p>The design thinking process was instrumental in redesigning the Parlon app’s bottom navigation. By empathizing with users, defining their needs, ideating possible solutions, prototyping various designs, and testing the outcomes, we were able to create a navigation system that enhanced user experience and satisfied the stakeholders’ requirements. The final design prioritized the most important actions, making the app more intuitive and efficient for users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0aa6eccd71db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning Full Stack Web Development While Working as a Designer]]></title>
            <link>https://medium.com/@biancaespinosa/learning-full-stack-web-development-while-working-as-a-designer-370d46b19f02?source=rss-8ca1e0d2cd20------2</link>
            <guid isPermaLink="false">https://medium.com/p/370d46b19f02</guid>
            <dc:creator><![CDATA[Bianca Espinosa]]></dc:creator>
            <pubDate>Sun, 18 Feb 2024 10:37:42 GMT</pubDate>
            <atom:updated>2024-02-18T10:37:42.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DNyAwt1P6jJrMOkk-u3sQ.png" /></figure><blockquote><em>This is not a guide nor a post that gives tips. This is just me compiling all my thoughts, reactions, and learnings as I begin my journey into web development.</em></blockquote><p>As a UI/UX designer, getting into full stack web development seems like an inevitability. Working with developers, I get to hear terms like “commit”, “push/pull”, “java”, etc. and I just end up wondering what those words mean in the development world. Add to this fact is the friction I get with front-end developers when I handoff my designs or perform quality checks. We’ll often discuss how something from the design isn’t feasible (either impossible to code or not be able to make it in time) or how this one particular element isn’t as pixel perfect as the one on the design. Curiously, I wanted to learn what was the reasoning behind the FE developers arguments (although to be fair, I just really wanted to know if I suck as a designer because are my designs really un-codeable/not feasible?). Hence, I’ve gathered courage and invested to learn development skills by joining a bootcamp. Here’s my journey so far:</p><h3><strong>Add, Commit, Push and Pull</strong></h3><p>Ah, so that’s what those terms are for. GitLab is a web-based platform that allows collaboration among dev teams through version control, issue tracking, deployment, etc etc. Memorizing the syntax used for CLIs and Gits can be tricky as well, like what do you mean there are other variations to a syntax?!</p><h3>HTML and CSS as foundations</h3><p>HTML and CSS serve as the building blocks of web development, providing the foundation upon which my design visions come to life. I’ve touched these subjects barely during a class elective in college…but that was about a decade ago. Apparently, there are new updates with the syntax! Float and clears aren’t used much anymore. Semantic elements are a thing in structuring a layout in HTML. Flex and grid are used in responsive layouts. It’s honestly both refreshing and challenging to learn these new things. At the same time, I now have a glimpse of what it’s like for the FE Devs I’ve worked with (I’d like to apologize to them for having hissy fits when something from the design isn’t as pixel perfect!)</p><h3>Conclusion…for now</h3><p>It’s been almost a month since I started embarking on the journey of learning full stack web development as a UI/UX designer. It’s a rewarding and transformative experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=370d46b19f02" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>