<?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 Lucía Venturini on Medium]]></title>
        <description><![CDATA[Stories by Lucía Venturini on Medium]]></description>
        <link>https://medium.com/@studio_21586?source=rss-66ed17edfe5b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*43MTMZErswqDsiW6</url>
            <title>Stories by Lucía Venturini on Medium</title>
            <link>https://medium.com/@studio_21586?source=rss-66ed17edfe5b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:51:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@studio_21586/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[Taking Vinted apart: my first wireframing exercise]]></title>
            <link>https://medium.com/@studio_21586/taking-vinted-apart-my-first-wireframing-exercise-837266fd1324?source=rss-66ed17edfe5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/837266fd1324</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[vinted]]></category>
            <dc:creator><![CDATA[Lucía Venturini]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 08:23:55 GMT</pubDate>
            <atom:updated>2026-11-13T08:23:55.293Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P81jMeoLUNqH8CB1.png" /></figure><p>As part of the second prework challenge of the UX design course, I decided to wireframe the buy flow of the Vinted app.</p><p><strong>Vinted</strong> is an online marketplace where people buy and sell second-hand clothes and accessories.</p><p>I chose this flow because Vinted is an app I use quite often, particularly for buying kids’ clothes, which need to be renewed quite a lot. I think its dynamics and navigation are clear, and I enjoy its simplicity compared to other apps of this kind, which constantly try to distract you with other products, offers, etc. I wanted to analyze how this flow works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXMP0T9HB7aviKTR1Owiyw.png" /></figure><h4><strong>Short description of the screens selected</strong></h4><ol><li><strong>Home (Inicio).</strong> The user sees a search bar with a camera icon, filter chips (All, Women, Men, Designer fashion) and a grid of item cards. Each card has a photo, a favorite heart with a counter, brand, size, condition, the price and the price including buyer protection. The tab bar at the bottom has Home, Browse, Sell, Messages and Profile. The user taps an item.</li><li><strong>Item detail.</strong> A large photo carousel with a back arrow, a menu and a heart. The two main actions at the bottom are “Make an offer” and “Buy” (primary), with a link about buyer protection underneath. Eventhout, if you scroll down on this same screen, there is a button to “Create bundle”, which is a feature I check often, in order to make the best of my purchase.</li><li><strong>Create bundle.</strong> A grid of the seller’s other items, each with an “Add” or “Remove” button, a check mark on the selected item, and a bottom bar with the selected items, the price and a “View bundle” button.</li><li><strong>View bundle.</strong> The number of items, then a price breakdown: price, Vinted fee, shipping and total. The actions are “Buy”(primary), “Send message” and “Make an offer”.</li><li><strong>Process order.</strong> The item summary, the delivery address with an edit icon, the delivery type (pickup point selected), the total to pay, a green “Pay” (<em>Pagar</em>) button and a note that payment data is encrypted.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCYMqueQIP3kHtmDL88Kcg.png" /></figure><h4><strong>Elements for my UI inventory</strong></h4><ul><li>Search field with camera icon</li><li>Item cards with a favorite icon and counter</li><li>Bottom tab bar with a notification dot</li><li>Photo carousel with dots, and a menu button</li><li>Primary, secondary and outlined buttons (including a red “Eliminate product”)</li><li>Text links and “info” icon</li><li>Selection check mark and a bottom action bar</li><li>Price breakdown rows</li><li>Address card with an edit icon, and a selectable delivery option</li><li>A security note under the payment button</li></ul><p>Below you can take a look at my wireframe on <a href="https://www.figma.com/design/XPMES5SicSjjAK9apGklTo/Exercises_Ironhack?node-id=8-41&amp;t=SglKRqLN97FhiF8y-1">Figma</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cvwz0VLaNg45tyfW55Jyng.png" /></figure><p>I enjoyed doing this exercise. It was the first time I analyzed an app in this way, and I particularly enjoyed trying to understand the flow behind it. Coming from industrial design, taking something digital and analyzing its user experience from a digital perspective made me realize how used we are to following certain steps without noticing them, and at the same time how important it is for users that the actions leading to their original purpose are as simple as possible.</p><p>I found it interesting to notice how many small conventions can be hidden in such a simple app. For example, the main action is a single colored button that fills the width of the screen, while secondary actions are smaller, outlined, or just text links.</p><p>This also connects to why I chose Vinted. Its flow keeps the user focused on the purchase, without constantly distracting them with other products or offers, and breaking it down into five screens helped me see how each step takes the user closer to paying.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=837266fd1324" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public transport: the ride is easy, the ticket is the hard part]]></title>
            <link>https://medium.com/@studio_21586/public-transport-the-ride-is-easy-the-ticket-is-the-hard-part-51f708506e0a?source=rss-66ed17edfe5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/51f708506e0a</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Lucía Venturini]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 12:04:25 GMT</pubDate>
            <atom:updated>2026-11-09T12:37:09.206Z</atom:updated>
            <content:encoded><![CDATA[<h4>Design thinking process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4IT0cr017sERbpIkmjZMOA.jpeg" /><figcaption>Source: Pexels.com</figcaption></figure><p>Citymapper is a free app for planning and navigating trips in big cities. It puts all the transport options (buses, trains, subways, trams, walking, cycling, ride-hailing) side by side with live departures, wait times and arrival times. Its “GO” button gives step-by-step guidance, tells you when to get off, and even suggests the best train car or station exit.</p><h4>The problem</h4><p>The app already does a lot: you enter where you are and where you are going, and it shows you different routes with time and cost. But there’s one thing it doesn’t solve: all the different tickets you may need to buy. Public transport tickets come as paper or plastic cards, and getting from A to B often means buying more than one. Add queues and broken vending machines, and it gets worse when you’re abroad and have to figure out prices and which ticket is the right one. My challenge was to design a feature that takes that pain away.</p><h4>Talking to real people</h4><p>To approach this problem, I started by running a short interview with five people. I thought they could help me understand the user experience better and point me toward possible solutions.</p><p>An important part of this research was deciding who could give me the most useful insights, meaning people who had run into this problem in a range of situations. So I focused on adults who regularly use public transport particularly when they are abroad, who travel in different arrangements (alone, or as a group or family), and who have been to quite different places, as I’m aware that what you find in public transport depends a lot on the country and region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jFAPcgY5g9B6ubRKofrsYA.jpeg" /><figcaption>Source: Pexels.com</figcaption></figure><p>These were my questions:</p><ol><li>How do you usually get around by public transport, in your own city and when you travel? Who do you usually go with?</li><li>How do you figure out which ticket you need and how to pay?</li><li>What was the most frustrating moment you’ve had with tickets or paying? (Follow-up: What did you do about it?)</li><li>Do you use any app or other technology along the way, from planning the trip to paying? Tell me how. (Follow-ups: What works? What doesn’t?)</li><li>What works well when you use public transport?</li><li>If you could change one thing about buying tickets, what would it be?</li></ol><h4>What they told me</h4><p>They brought up a few things I hadn’t thought of as being so important:</p><ul><li><strong>It’s not only about saving money.</strong> Many said they choose public transport first to save money, but especially when travelling, to get a feel for the local culture and to meet people in a new place. That gave me an idea I’ll come back to later (idea C).</li><li><strong>Understanding the ticket system is the worst part.</strong> Which zone do I need? How do I pay? Do I have to validate the ticket?</li><li><strong>It gets harder because of the moment.</strong> Having to walk around before you can even sort out your ticket, often with luggage, sometimes with kids, or in a hurry.</li><li><strong>What worked well.</strong> Once they’d figured out the process, the rest of the trip was easy, especially after getting a card or a system. They also found maps and service information on the app accurate and up to date.</li><li><strong>What they want.</strong> Many said they’d like paying to be as simple as possible, with no unnecessary steps.</li></ul><h4>The problem I’m solving</h4><p>People who use public transport, especially in a city they don’t know, need a way to find out which tickets they need and how to get them, because working out zones, payment and validation on the spot, often with luggage or children in unfamiliar streets, makes the start of the trip the most frustrating part.</p><p>Three ideas:</p><p><strong>A. One-tap ticket guide.</strong> One button on your selected route tells you every ticket you need for that trip (one, or a combination) and guides you through getting them all in one go. It shows where the ticket machines are and which exact ticket to pick.</p><p><strong>B. Pre-loaded balance.</strong> You add money to the app ahead of time and use it as you go. When you pick a route, the app works out the exact ticket you need and buys it for you. You might still need to go to a vending machine or scan the ticket at the validator, but you wouldn’t have to choose the ticket or pay.</p><p><strong>C. Ask a local.</strong> Instead of having the app handle every variation of every ticket system, this one builds on what I heard: many people actually like talking to locals when they arrive. In a playful approach, the app could show you the exact question you need to ask, in the local language, and read it aloud so you can show or play it to anyone nearby.</p><h4>My paper prototype</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjmxdJaUdttTgh5KME54mQ.png" /></figure><blockquote><em>I chose to develop option B a bit further: you add credit to the app and pay for your tickets directly from it. I also added option C as an alternative suggestion. In this one, the app helps you ask questions to real people, in their local language if needed, so you get to interact with locals while finding your way around :)</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m8d1EJ_m2GpKU80z06JHTg.png" /></figure><h4>What I learned</h4><p>This was a fun exercise, and it let me approach a problem through an app, which I hadn’t done before.</p><p>I tried to focus on the design process itself and to understand, as much as possible, the real problem people face and the context where they need this solution the most. Talking to real users showed me things I hadn’t considered, like the fact that many people choose public transport not only to save money, but also to get to know a place and its people.</p><p>We live in a world where we are quite used to apps and technology in our daily lives. I think it is important to focus on how apps can connect us to the real world and simplify our problems, without losing sight of what we have around us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51f708506e0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>