<?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 Laura F Mato on Medium]]></title>
        <description><![CDATA[Stories by Laura F Mato on Medium]]></description>
        <link>https://medium.com/@laura.f.mato?source=rss-c92055c6ab0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JNzwBGMfSCpUGp0D</url>
            <title>Stories by Laura F Mato on Medium</title>
            <link>https://medium.com/@laura.f.mato?source=rss-c92055c6ab0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:29:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@laura.f.mato/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[Wireframing PlantNet: a user flow practice]]></title>
            <link>https://medium.com/@laura.f.mato/wireframing-plantnet-a-user-flow-practice-4ce364e2cf4d?source=rss-c92055c6ab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ce364e2cf4d</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[plantnet]]></category>
            <dc:creator><![CDATA[Laura F Mato]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 14:05:55 GMT</pubDate>
            <atom:updated>2026-10-03T14:05:55.506Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of the second prework challenge for Ironhack, I decided to wireframe the identification flow of PlantNet.</p><p>PlantNet is an app that uses the photos and data uploaded by its worldwide users to help you identify and cathegorize plants, as well as to educate and share knowledge on botany. I chose to analyze the identification flow as <strong>a</strong>) it is the most used feature of the app <strong>b</strong>) because its educational purpose and <strong>c</strong>) because I had the feeling that there were some parts of the flow that were not working but I couldn´t undertand why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*6DZPuNr8s55TxYJQ55P1Dw.png" /><figcaption><strong>PlantNet flow for identifying a plant with your picture 1</strong>. Feed (shown when you open the app) <strong>2</strong>.Identification screen (to upload your photo) <strong>3</strong>. Select the main plant organ for the recognition <strong>4</strong>.Screen with identification possibilities <strong>5</strong>. Identification card and option to share it <strong>6</strong>.Sharing Pop-up <strong>7</strong>. User´s profile screen uploaded contributions</figcaption></figure><p><strong>Task analysis</strong></p><ol><li><strong>Openning the app takes th</strong>e user to the <strong>Feed</strong> screen. By clicking on the camera icon (at the bottom), the user can start the identification of a plant.</li><li><strong>Identification screen</strong>. The user can <strong>upload a picture</strong> (by taking it with the camera or uploading it from the gallery). In this screen, there are already a few drop-down buttons that allow the user to change some preferences related to the identification search (such as the region of the world where the picture has been taken, GPS location, and other filters).</li><li>The user has to <strong>choose</strong> the main <strong>plant organ</strong> of the picture before proceeding with the identification.</li><li>A <strong>scrollable list of plants</strong> that match the user´s picture appear. The user can <strong>choose</strong> which one <strong>matches</strong> his own picture (by pressing on the <strong>“confirm”</strong> button), with the guidance of other users´pics and a percentage. Here, the user can also see the scientific name, common name (if none provided, there is an option to suggest one) and species of each matching option.</li><li>After the selection, the user can see a <strong>plant card</strong> that includes the user´s name and uploaded picture, date, plant name and species; there is also the posssibility to include the location and some commments, before “<strong>sharing</strong>” this card with the community.</li><li><strong>Notification</strong>: a reminder that by clicking the <strong>“sharing”</strong> buttton, the plant card created will be reviewed by the community.</li><li>The user is re-directed to the <strong>profile screen</strong>, where he can see a list of his <strong>contributions </strong>(plant pictures,names and species, date uploaded) and their state (reviewed by the community or not, location) or see more details of each contribution (by clicking the “details” button).</li></ol><h3>The low fi prototype</h3><p>I am currently loving the simple use of pen and paper! So much can be understood when trying to copy (and simplify) soemthing with your hands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nDF68oaMtntpS3wOIcHKaA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwCkm5P2by8mspRyRDHoIw.jpeg" /></figure><p><strong>Identification of the UI elements</strong></p><p>By drawing the lof fi wireframes I quickly realized that there were a lot of different UI elements: buttons and drop-down buttons, drop-down lists, toggles, date fields, pictures, dividers, a notification and many many icons.</p><h3><strong>Wireframes</strong></h3><p>It was while doing the wireframes with Figma that I started to notice how many variables the UI components have. Actually, some of the buttons seem to have quite a different visual weight in different screens, their position would vary noticeably, as well as their size or even text font.</p><p>In addition, I realized that despite the identification flow that I had selected seemed quite simple, there are many unexplored options within each screen. For example, in the wireframe 5, before sharing your contribution, you can change the region, swap the label species for other criteria, propose a common name for the plant if none suggested, select other filters by clicking on the funnel icon (which open a new window full of new possibilities)… and all of these possibilities seemed a distraction from the main flow intention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4oVc1iVJPof1oqD5d6I1w.jpeg" /><figcaption><strong>1</strong>. Feed screen <strong>2</strong>.Identification screen (upload picture) <strong>3</strong>. Selection of main plant organ of your picture <strong>4</strong>.Options that match your picture (select one)<strong> 5.</strong> Plant card generated <strong>6</strong>. Notification before sharing plant card <strong>7</strong>. User´s profile with last constributions</figcaption></figure><h3><strong>Here is the prototype of the identification flow</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*UZln-Q6NSOQTBTVUkqDVOg.png" /><figcaption>You can try it out by yourself <a href="https://www.figma.com/proto/HN1aiALxsf4ACJufZAptNR/Wireframes?node-id=8-196&amp;p=f&amp;viewport=-762%2C-530%2C0.4&amp;t=jHItIiDXL7V99ehL-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;starting-point-node-id=8%3A196&amp;page-id=8%3A188">here</a></figcaption></figure><p><strong>Some thoughts after completing the exercise</strong></p><p>This was a great exercise for me to start disecting an app flow. What seems simple might not be, and through the reverse engineering of the identification flow, I could experience the importamce of the design and the consistency of the UI elements.</p><p>When so many elements are included in each screen, it seems specially important to preserve consistency in their design (positioning, style, color, font, size…), to avoid adding an extra feeling of weight in the flow (perceived by me as distractions).</p><p>Would love to hear what was your experience!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ce364e2cf4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cittimaper re-imagined]]></title>
            <link>https://medium.com/@laura.f.mato/cittimaper-re-imagined-9f233b339d98?source=rss-c92055c6ab0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f233b339d98</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[citymapper]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Laura F Mato]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 08:44:18 GMT</pubDate>
            <atom:updated>2026-09-14T08:44:18.166Z</atom:updated>
            <content:encoded><![CDATA[<p>You know the story. Bussy city, bussy life. You need to go to this unfamiliar place. It´s rush hour, you are tired, and it´s suddenly raining. You open your travelling app to set the location and… 6 different options to arrive there. You can choose the trip by duration, type of transport and combinations, accesibility…</p><p><strong>BUT</strong></p><p>You don´t know how to buy the ticket for the first bus, and you don´t remember if you card pass covers the area of the metro line. You already spent 10 minutes choosing the best route and now you don´t know if you can actually take it.</p><p>Sounds familiar?</p><p>This post is part of an exercise for a UI/UX design course. The challenge is sharing the process of trying to design an improvement for a very common transport problem: getting the right tickets in the easiest way. Here we go.</p><p><a href="https://citymapper.com/?lang=en">Citymapper</a> is a free mobility app specialized in helping users commute by providing diverse routing options. The app integrates various public transit methods — such as buses, metros, trains, and trams — with services from private companies, including taxis, VTCs, and app based rental motorbikes or bicycles. Tailored specifically for major metropolitan areas, <a href="https://citymapper.com/?lang=en">Citymapper</a> is popular across European due to its multi-modal route optimization. You can choose between a single transport method or a flexible combination of multiple options. Routes can be easily filtered to prioritize the fastest travel time, a preferred transit mode, or simply the most straightforward, hassle-free path.</p><p>But what about the tickets themselves?</p><h3>Emphathizing</h3><p>After interviewing 5 people about their use of this app I came across few common pain points.</p><ul><li>If you don´t know very well the <strong>transport system in your area</strong> and you need tickets from different companies, it can be tricky to get the right ones (and time consuming!)</li></ul><p><em>Example Route 1: metro-tram-bus /35 min/1 ticket (all means of transport are from same company)</em></p><p><em>Example Route 2: metro-ferry/20 min/ 2 tickets</em></p><ul><li>That statement specially applies when <strong>travelling abroad </strong>(or out of you well known city).</li><li><strong>Non tech people</strong> can perceive the many route options (without the support for buying the needed tickets) as <strong>overwhelming</strong> (anyone buying card tickets for their visiting mum´s? )</li><li>People use <strong>monthly passes</strong> and blocks of tickets. Is not easy to remember how many are left and which areas they cover.</li></ul><h3>Defining the problem</h3><p>When researching a trip in the app, there are many variables involved that might infuence the user´s choice of route: type of transport, estimated time, user´s preferences, accesibility, public vs private transport…</p><p>But some other variables are not being taken into account:</p><ul><li><strong>Different companies</strong> own different means of transport</li><li>That fact impacts on the <strong>number of tickets needed</strong> in a route</li><li>Usual users tend to have a <strong>pass</strong> or a block of tickets but for only one transport company.</li><li>How <strong>easy</strong> is to get the tickets you need, whether you have already some in your transport card, or you have nothing.</li></ul><p>Here is an innitial sketch with ideas around the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*is4zlFBrhMKZEA_KrtwDaQ.jpeg" /></figure><h4>So this is the idea I chose to work with</h4><ul><li>Adding the route option “By Ticket”</li><li>Making this option to take into account the tickets you already have, because is often cheaper to use a monthly pass o a block of 10 tickets.</li><li>Adding the possibility of buying the tickets you need through the app</li></ul><p>Here is the sketch of a prototype</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wg5b_7Hrqkkl3AdjqcvQLw.jpeg" /></figure><p>These are some reflexions I had throughout the process:</p><p>While in the ideation stage, many other problems become evident and is easy to diverge and move the focus from the initial problem. In this exercise, I´ve been designing around the tickets. But other reflections kept coming to my mind, like there is no option for pet friendly routes (a problem that probably requests another route option) or the different prices that apply to children depending on their age (a problem that I thought of once I had finished the design).</p><p>These are valuable variables that need to be taken into account during reiterations.</p><p>Other adjustments are needed for some specific types of transport, such as the electric bikes or scooters, etc by adding estimated prices, as they are paid by minutes of use once you complete your trip (cannot buy through app in advance).</p><h3><strong>Conclusion</strong></h3><ul><li>Is a very reiterative process, developed through different days and perspectives, with some interviews and many informal chats about the topic.</li><li>It is important to define well the problem you are trying to solve before ideating solutions.</li><li>The skettching must be just that, sketches, so there is minimal attachment to initial ideas becuase of the time and effort put into the design.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f233b339d98" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>