<?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 cecilia jos on Medium]]></title>
        <description><![CDATA[Stories by cecilia jos on Medium]]></description>
        <link>https://medium.com/@ceciliajosviel?source=rss-c04c3a817ed3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6b7IvpovyA03l6wSSVHKoQ.jpeg</url>
            <title>Stories by cecilia jos on Medium</title>
            <link>https://medium.com/@ceciliajosviel?source=rss-c04c3a817ed3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:58:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ceciliajosviel/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[I don’t want more messages]]></title>
            <link>https://medium.com/@ceciliajosviel/i-dont-want-more-messages-1506edf46ffd?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1506edf46ffd</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 15:25:30 GMT</pubDate>
            <atom:updated>2026-11-08T15:25:30.255Z</atom:updated>
            <content:encoded><![CDATA[<p>Designing ColeApp, a school app for overloaded parents</p><h3>The problem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vl9XwUcTDghorig_18onCQ.jpeg" /></figure><p>I’m the mother of a 7-year-old, and keeping up with everything that happens at school can feel like mission impossible: homework, absence notes, deadlines to sign up for school lunches, after-school activities… The information arrives through several channels at once: my son’s planner, a note stuffed in his folder, the parents’ WhatsApp group. And the constant feeling is that you’re finding out about things too late.</p><p>Over the years I’ve realised it’s not just me. At both public schools my son has attended, the websites were rarely up to date and almost never had useful information for families. So parents end up asking each other at drop-off or pick-up whether the holiday childcare info is out yet, or when the spring festival is. And more than once, someone has missed something important because the information never reached them, or got buried in the group chat.</p><p>School apps already exist, but they’re either designed for very young children (they tell you what your child ate and how many times they went to the toilet) or they don’t meet what families really need: all the important information in one place. That’s how the idea for ColeApp was born.</p><h3>The team</h3><p>When I pitched the idea in class, Denis joined the project. We were two UX/UI designers and did everything together, from research to prototype.</p><h3>Research</h3><p>We started with secondary research: we looked at educational apps and what their users said about them, and went through the websites of several public schools. From there we built a survey (Ana, our instructor, helped us fine-tune a couple of questions) and an interview script for parents.</p><p>52 families answered the survey, and the numbers spoke for themselves. The interviews, with two mothers and two fathers, were the slowest part, but also the one that taught us the most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANvjt800XA8Y-Wy9U1ryYQ.jpeg" /></figure><p>We didn’t use AI for the affinity diagram. Reading the interviews carefully, pulling out what matters and grouping it by theme takes longer, but it’s the best way to put yourself in your users’ shoes and really understand their problems. Six main themes came out of it: lack of clear information (the biggest), late information, complicated registration, uncertainty across channels, sense of belonging, and language. The last two only showed up in the interviews, which is why we needed both methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-Cxf8ByZ6ZZM-fKg-wo5w.jpeg" /></figure><p>All of this shaped Anna, our user persona: 41, works full time on an inflexible schedule, and squeezes school matters into her spare moments. Her words sum up the project: “I don’t want more messages. I want to spend less time figuring out what I need to do.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wC4Tq2KkmopsbC7imQ_gsw.jpeg" /></figure><h3>From idea to screens</h3><p>In a single day we went from the problem statement and the user journey map to ideation, MoSCoW, the task flow, the site map and our first low-fidelity wireframes.</p><p><strong>A cat born from a bad idea.</strong> For ideation we did Crazy 8s with a twist: first we sketched deliberately bad ideas, like a cat that lives in the classroom and sleeps at a different family’s house every night. Then we turned one of them into a good one: the cat became Cole help, an AI assistant families can ask when they don’t understand a school process.</p><p><strong>Prioritising with Anna in mind.</strong> With MoSCoW, our must-haves were the home dashboard, the calendar, a staff directory with photos and contact details, simple requests (reporting an absence, booking a meeting with a teacher) and the assistant. Daily notifications didn’t make the cut: Anna doesn’t want more messages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOdxIJX9Z3zOiLyasOULxA.jpeg" /></figure><p><strong>What testing taught us.</strong> The hardest part was deciding what went on the home screen, the first thing families would see. Sarah had told us several times not to be afraid of scrolling, since everyone is used to it. We didn’t listen, and our first tester told us the class screen was crammed with information.</p><p>They also taught us a lesson I won’t forget: what’s obvious to you isn’t necessarily obvious to anyone else. Denis had designed a yellow and blue data visualisation linked to the calendar events, but nobody could tell how the two were connected. We needed to give users more information without overloading them. With that feedback and the input from two more testers, we moved on to mid-fidelity wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9SN15oYjkYoyVfCYO0TabA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kzqj4_sl6qbSFM6cEjE6-g.jpeg" /></figure><p><strong>The UI.</strong> To take a break from UX, we turned to the visual side: we defined our core values (trust, fun, caring, friendly and easy) and, based on them, chose our colour palette. Since the app is for every family, we built accessibility in from the start: we checked contrast with Figma’s Contrast plugin to make sure every colour met accessibility guidelines. And we chose Lexend, a typeface designed to improve readability and <a href="https://www.designyourway.net/blog/best-fonts-for-accessibility/">especially recommended for educational apps</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvLU0vlDyyT54BJLZUgCjw.jpeg" /></figure><p>Then came a whole day wrestling with Figma to build the mid-fi screens with all the testing feedback. The design critique went quite well, and left us with a few details that we applied when moving to high fidelity:</p><ul><li><strong>Consistent icons.</strong> The notifications icon looked like a chat where you could write, so we swapped it for a bell.</li><li><strong>Clearer actions.</strong> The pencil icon became a text button that says EDIT.</li><li><strong>More context on the home screen.</strong> The progress rings now say “20 of 66 days” or “4 of 12 exams”, not just a number.</li><li><strong>The child’s name</strong> now appears under their photo on the home screen.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4u527uZZll_4ZkNLN9vymw.jpeg" /></figure><h3>The pitch</h3><p>The project ended with an investor pitch to the Sharks, where we presented ColeApp as a product each Spanish region could roll out in its public schools. Despite the nerves, it went well: one of the Sharks invested in ColeApp, and it was the most valued idea in the class vote. We were over the moon.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1244874913%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1244874913&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2223786109-de50bbe8783cecdbc328e284e2a596feec80c5401a0f86fa31daf458ffe441dd-d_1280%3Fregion%3Dus&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1373" frameborder="0" scrolling="no"><a href="https://medium.com/media/693956d91c48d178ff2b008c1cca9ba1/href">https://medium.com/media/693956d91c48d178ff2b008c1cca9ba1/href</a></iframe><h3>What I’m taking away</h3><ul><li><strong>Test early, even if it hurts.</strong> Our first tester saw the problems we couldn’t.</li><li><strong>There are no shortcuts to understanding users.</strong> Doing the synthesis by hand is slower, but the problem becomes much clearer.</li><li><strong>Scrolling isn’t a flaw; a crowded screen is.</strong> I should have listened to Sarah from the start.</li></ul><h3>Next steps</h3><p>Bring the Cole help assistant to every screen (right now it’s only on the home screen), add the parents’ chat that stayed as a <em>Could have</em>, and keep improving the visual design based on the Shark’s feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1506edf46ffd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Less maze, more shelves]]></title>
            <link>https://medium.com/@ceciliajosviel/less-maze-more-shelves-b042943008ba?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b042943008ba</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[heuristics]]></category>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 15:30:36 GMT</pubDate>
            <atom:updated>2026-11-08T09:03:59.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXZr1Vlyz2NXVEp1gzrVOw.jpeg" /></figure><p>In this Ironhack project we had 12 hours to redesign between 3 and 7 screens of an app, applying Nielsen’s heuristics and information architecture principles. Quality over quantity.</p><p>I chose the app for the public libraries of Castilla y León, in Spain. To give you an idea: if you want to change your password, you have to go to the library in person. When I did, they told me they were having problems “with that” and were giving everyone the same password. Good thing it’s only books…</p><h3>Heuristic evaluation</h3><p>I analysed three screens: the login, the home screen and the two menus. Each issue has a number, the Nielsen heuristic it breaks (#1–#10) and its severity, from 1 (low) to 3 (high). Spoiler: the app broke the severity-meter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wR1IL8Jv9gNCMXJgfEp6kA.jpeg" /></figure><h3>Login</h3><p>“Entrar con el último usuario logueado” (“Log in with the last logged-in user”) is a button. It took me ten minutes to realise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtfy7ELpMMUxMA3YfN_BUw.jpeg" /></figure><ol><li><strong>Fields don’t look like fields</strong> · #4 · Severity 2: they read as banners, not inputs.</li><li><strong>Two login paths, unclear which is which</strong> · #2 #6 · Severity 3: no explanation of the difference, and the shortcut uses jargon.</li><li><strong>The last-user button doesn’t look like a button</strong> · #4 · Severity 3: it reads as a heading.</li><li><strong>Low-contrast button</strong> · #8 · Severity 2: the main action barely stands out.</li><li><strong>Placeholder used as label</strong> · #6 · Severity 2: the instructions disappear when you type.</li><li><strong>No account recovery or sign-up</strong> · #3 · Severity 3: users who are stuck have no way out.</li></ol><h3>Home screen</h3><p>Opening the app, you get the feeling you need to be very clever to use it. And nobody wants to feel stupid looking for a book.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwC5UZR80EaxctQVhDZ9Og.jpeg" /></figure><ol><li><strong>No back button or breadcrumbs</strong> · #3 · Severity 3: no way to retrace your steps.</li><li><strong>Two navigation menus</strong> · #4 #8 · Severity 3: which one do you use?</li><li><strong>Help hidden inside the menu</strong> · #10 · Severity 1: not where users first need it.</li><li><strong>Information overload</strong> · #8 · Severity 2: everything competes, and the search gets lost.</li><li><strong>Unfamiliar terminology</strong> · #2 · Severity 2: “RABEL” means nothing to a reader.</li></ol><h3>The two menus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GKseyUpVkYufWvfMTlgMw.jpeg" /></figure><ol><li><strong>No indication of current section</strong> · #1 · Severity 2</li><li><strong>No close button</strong> · #3 · Severity 2</li><li><strong>Unclear labels</strong> · #2 · Severity 2: “BiblioMapa”? “Biblioteca Digital” vs “Libros Electrónicos”?</li><li><strong>Two completely different menus</strong> · #4 · Severity 3: two navigation systems for one app.</li><li><strong>Technical vocabulary in capitals</strong> · #2 · Severity 2</li><li><strong>Help buried at the bottom</strong> · #10 · Severity 2</li></ol><h3>The redesign</h3><p>My inspiration was Tidal, the app I use most by far. It’s a music app, but its search screen suits a book app really well: genres you scroll horizontally, without overwhelming you, and a “See all” for anyone who wants more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vksf41aS1C7c9twjn3erlA.jpeg" /></figure><p>To choose the genres, I used an <a href="https://www.heraldodiariodesoria.es/soria/260411/206533/son-diez-libros-prestados-biblioteca-soria.html">article about the most borrowed books at the Soria Public Library</a> (in Spanish).</p><p><strong>Visual identity.</strong> I replaced the dark background with a light one to improve readability. I reduced the palette to navy blue (the original app’s main colour, and, I won’t deny it, my favourite) and orange for the actions; the book covers bring the rest of the colour. I switched the typeface to Akshar, more legible and contemporary, and simplified the logo: I kept the book and the serif B, a nod to printed books. The regional government logo disappeared from the home screen because it added nothing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ga1B44fGUVd-0yAeHtqwWQ.jpeg" /></figure><p><strong>Information architecture.</strong> I applied six of Dan Brown’s principles: <em>objects</em> (every book with the same card), <em>choices</em> (short selections), <em>disclosure</em> (“See all”), <em>multiple classification</em> (several ways to reach a book), <em>focused navigation</em> (one menu to search, another for personal things) and <em>growth</em> (the home screen grows row by row).</p><p><strong>Design critique.</strong> In the critique session, classmates pointed out that the personal menu icons were too small, that the menus should take up the full screen, and that the login button was narrower than the email field. I changed all of it in the final version.</p><h3>My screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kaea3713DpzxYOmcvTDNbQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eniVBC2pDt7sArr_mnz5aQ.jpeg" /></figure><p><strong>Login.</strong> The field now looks like a field, with an always-visible “Iniciar sesión” (Log in) label and an example of what to type, and there’s a single, high-contrast login button. No more two paths, no more button that didn’t look like a button. I removed the password from the entry point: you don’t need to identify yourself to search for books, so it would move to the Private Area, where there is personal data to protect. Besides, they were giving everyone the same one. And anyone without an account finally has a way forward: “Create account”.</p><p><strong>Home screen.</strong> Four layers of headers and logos became one, with the menu, the logo and personal access. Search moves to the top, visible as soon as you open the app, and the content is organised in rows, with the book covers in the spotlight. “RABEL” and “Catálogo Colectivo” are gone, and sections are named the way a reader would look for them: “By genre”, “New arrivals”, “Readers’ favourites”. Users explore instead of decoding.</p><p><strong>Menus.</strong> The two menus no longer compete: one is for finding books, the other gathers everything personal (Private Area, Events, My books), and both share the same style. You don’t need to be a librarian to understand the categories: “Fiction”, “Non-fiction”, “eBooks”, “Audiobooks” or “Books in English”. And goodbye to all caps.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F1243388284%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F1243388284%3Fshare%3Dcopy%26fl%3Dsv%26fe%3Dci&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F2221894078-c5800be3cf1cd19ee483a7a4dd72d9466391a5487bddb9d174dfe018063d2d8e-d_1280%3Fregion%3Dus&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/72b27ee043f9aefc445e95eb0f6eb842/href">https://medium.com/media/72b27ee043f9aefc445e95eb0f6eb842/href</a></iframe><h3>Next steps</h3><p>12 hours isn’t enough for everything. Next would be: inner screens with a back button and breadcrumbs, menus with a close button and the active section highlighted, more visible help, and a Private Area so nobody has to go to the library to change their password.</p><h3>Conclusion</h3><p>My takeaway: prioritise and, above all, go from small to big. It’s the part of design thinking I find hardest, and with 12 hours there was no other way.</p><p>Finding a book should be as easy as wandering through the shelves of a library. With this redesign, I wanted the app to feel more like that: less maze, more shelves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b042943008ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Baobi: building trust before the first visit]]></title>
            <link>https://medium.com/@ceciliajosviel/baobi-building-trust-before-the-first-visit-6506240909eb?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6506240909eb</guid>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 21:05:21 GMT</pubDate>
            <atom:updated>2026-10-15T12:40:08.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nf5nIgt5aT6nsEudLuiCqQ.jpeg" /><figcaption>Baobi Café in Almendralejo, Badajoz, Spain.</figcaption></figure><p><strong>Project:</strong> Responsive website for Baobi, a specialty coffee shop in Almendralejo (Badajoz) · <strong>Team:</strong> Juliano, Clara, Felicia and me · <strong>Role:</strong> UX/UI Designer · Keeping the team focused and on process · <strong>Duration:</strong> September 24 to October 6, 2026</p><h3>Starting with Sandra</h3><p>When I heard “specialty coffee shop”, I rolled my eyes. Another one. But after talking to Sandra, owner of Baobi, my first impression disappeared. She knew exactly what she wanted: quality local products at an affordable price, and a place that becomes the neighbourhood bar people actually want to go back to. I liked that. I am a bit tired of nostalgia for “the places of before”, which were often dirty, shabby and did not even treat you well.</p><p>We divided the work: Juliano and Clara found the people to interview among Baobi’s Instagram followers, Felicia took the competitive analysis, and I built the presentation template. Divide and conquer, as Sarah told us.</p><h3>When AI took us in the wrong direction</h3><p>After the interviews, we used AI to help us find patterns for the affinity mapping. It did not go well. The prompt we used pointed towards solutions, so the answers jumped straight to features instead of staying with what users had actually said.</p><p>We asked Sarah for help, and she helped us see the mistake. Her advice was not to rely too much on AI in these early phases, where the goal is to understand people, not to go faster. So we took a step back, and each of us drew our own conclusions from the interviews. Then we compared them and agreed on the patterns. It took more time, but the insights came from what people said, not from what a tool assumed.</p><h3>Lucía, and where we could lose her</h3><p>From these interviews, we noticed that people don’t only want good coffee, they want to feel sure before they go. So we built Lucía around that idea. She checks everything online first, and if something is unclear, she chooses another place. For her, trust comes before the visit.</p><p>Her journey shows where we can lose her. The weak point is the first step: the search. Once she is at the café, the experience is positive. So the problem is not the café. It is what people see before they arrive. That led to our problem statement: <em>coffee lovers need to find a way to trust that a café is what it appears to be before visiting, because they want a calm and welcoming place where they feel looked after.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nFcauIa3h4gFNTTJNR-k0Q.jpeg" /><figcaption>Lucía, our User Persona.</figcaption></figure><h3>Going back to fix the journey</h3><p>Midway through the project, while putting everything into the presentation, I noticed something was off. Our journey map assumed that Lucía would go to the coffee shop. But we were designing a website, so her steps were completely different.</p><p>We asked for advice again. After talking to Sarah, Ana confirmed that we could keep the journey we had made, but that we also needed one that matched our actual solution. Sarah had told us in class that the user persona, the journey map and the problem statement have to tell the same story. Now we understood why.</p><p>We then had to choose between two happy paths: Lucía browsing the site to see photos and information about the café, or Lucía signing up for an event. Ana and Sarah recommended the second one, and it made sense to me too: signing up for an event was the only real action she could take on the website. So we went with events and started on the mid-fi wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0YmtE_Qu_IY1YZavdqhpw.jpeg" /><figcaption>Can’t wait to go to Baobi!!</figcaption></figure><h3>The happy path</h3><p>In the final design, Lucía opens the menu and goes to Events, where each activity has its own space: a cacao ceremony, a ceramics workshop and more. She opens the cacao ceremony page, reads what to expect and taps “Inscribirse”. A short pop-up asks only for what is needed: name, day and email. After confirming, she sees a message telling her she will receive an email with the details, and a button to add the event to her calendar. She leaves with a reason to visit and knows what to expect when she arrives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qgb5c4-gMQxPzuAX83czEA.jpeg" /><figcaption>Lucía is very happy.</figcaption></figure><h3>Finding a shared look, and learning from the feedback</h3><p>We made a moodboard as a team, and in class we did an exercise: our classmates had to guess Baobi’s core values just by looking at it. They got most of them right: <strong>fun, approachable, creativity, local and warm.</strong> But they also told us that our moodboard had two very different visual lines. Felicia redid the whole thing to give it a single, consistent tone, and the result worked really well.</p><p>The wireframes were harder. We called them mid-fi, but Ana pointed out that they looked more like low-fi. We were stuck, the Design Board was that same day, and honestly, I was not sure how it would go. Working fast is not the same as working well.</p><p>We showed the wireframes and got a lot of feedback. That is both good and bad, but that is what we are here for. We applied every suggestion and spent a full day unifying the pages so they shared the same look and feel, checking that every link in the prototype worked, and testing the site to note errors and improvements.</p><h3>The home page</h3><p>I made the first sketch of the home page, which Felicia then improved and built out. At the mid-fi stage we were told the frames still looked more like low-fi and that the page needed more content, and she added more elements, like the image carousel, until it became its final version: real photos of the café, “About us”, the coffee, the merch and the location with a map.</p><p>Sandra gave us Baobi’s brand elements (logo, tags and illustrations), made by a designer, so our job was to bring that identity into the website, not to reinvent it. The text styles had been set up at the start of the project, and I adapted them to the design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPsCTT2Ml4sThADuchtP3Q.jpeg" /><figcaption>Home page.</figcaption></figure><h3>Making the presentation match the product</h3><p>I built the presentation template early on, and once the website design was settled, I adjusted the slides to it: typography, colours and overall look, so the presentation felt like part of the same project. From there, the rest of the team added content and edited the texts on top of that design. I also presented slides 6 to 8: the user persona, the journey map and the problem statement. The presentation went really well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FoCp8vjPCD3C_ExwEURF2A.jpeg" /><figcaption>Page 2 from our Figma presentation slides.</figcaption></figure><h3>What I take from this project</h3><p><strong>Fast is not the same as good.</strong> The mid-fi wireframes showed it: we were working quickly, but the feedback told us the result was not where it needed to be. The same happened with AI. It gave us answers fast, but they were the wrong ones. Both times, stepping back and doing the slower work was what moved the project forward.</p><p><strong>Tools help, but they don’t replace listening.</strong> The best decisions came from what Sandra and the users told us, and from going back to fix our own assumptions, like the journey map.</p><p>It was not always easy to find my place in the team. I learned that being useful is not always about the biggest piece of work, but about noticing what is missing, like the journey that did not fit a website, and making sure it gets fixed.</p><p>There are things I would still improve. Two of the pages we designed do not share the same look and feel, and I would have liked to unify them. We ran out of time, and Sarah pointed it out in her feedback. Consistency does not happen at the end: it has to be checked as you go.</p><p>But I’m taking away a way of working I want to keep: understand first, then design, and don’t be afraid to go back.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6506240909eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DIARY OF A BOOTCAMP]]></title>
            <link>https://medium.com/@ceciliajosviel/diary-of-a-bootcamp-cf4de14af534?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf4de14af534</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[ui-ux-case-study]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[wicked-problem]]></category>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 17:57:58 GMT</pubDate>
            <atom:updated>2026-09-28T21:00:01.964Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxqNW_R5ZSixKjnf729qPA.jpeg" /></figure><h3>WEEK 1. DAYS 1 &amp; 2</h3><p>So, the fun begins.</p><p>After dropping Pedro, my son, off at school in the early-bird program so I could make it to class on time, today was our first class in the UI/UX Ironhack bootcamp.</p><p>Sarah Bombaywala (from now on, Sarah), our teacher, welcomed us, scared us a little too, and gave us tons of information. I felt a little overwhelmed, but then she reassured us and gave us lots of encouragement.</p><p>She divided us into groups for our first project: the <strong>Wicked Problem</strong>. I was assigned to Team Autumn, together with Denis Budonnyi and Jacques Dong, and out of the topics she offered us, we chose <strong>Food Sustainability</strong>.</p><p>The first thing we learned is that the most important thing in UI/UX is empathy. So, Ana Albertini, our other teacher, if you’re reading the Medium posts from this new cohort, here we go. I’ll try not to make this terribly boring, but I’m not a writer, so I can’t promise anything. At least I’ll try not to make it too long.</p><p><strong>Back to the Wicked Problem</strong></p><p>Keeping the following topic in mind:</p><p><strong>FOOD SUSTAINABILITY</strong></p><ul><li>Supermarket chains and big food corporations benefit more from the rise of the organic food market than local producers do. Instead of fixing the problem, they are harming the environment through unsustainable models.</li><li><strong>How Might We help people access local seasonal produce, while also fostering fair and honest relationships between producers and customers?</strong></li></ul><p>We did a first round of ideas, talking between the three of us about what we thought about the topic, and decided that each of us would research a different area for the secondary research: farmers, consumer habits and large supply chains.</p><p>We also used the <strong>CSD Matrix</strong> to talk about what we knew, what we didn’t know and what we weren’t sure about. This led to some really interesting conversations about whether people actually care about sustainability and how we each understood it.</p><p>With the data we collected, we started brainstorming possible questions. That’s when we realised we’d come across a whole bunch of problems and didn’t know which ones to prioritise.</p><p>We asked Ana Albertini, our other teacher (from now on, Ana), for help. She gave us some really good advice on how to slightly modify the questions so that they were more open-ended and allowed the interviewee to elaborate.</p><p>We did a test interview with me to see how the questions worked. We were pretty happy with the result, so we started interviewing five people.</p><p>It was quite an intense day. It had been a long time since I’d been a student, so it was really rewarding to learn so many new things.</p><p>More tomorrow.</p><h3>WEEK 1. DAY 3</h3><p>Today we finished the interviews we still had left to do, and honestly, it was pretty fun reading through the answers.</p><p>I loved Pierre’s honesty. He’s from Paris, a friend of Jacques, and he joined a consumer group but ended up getting fed up with eating turnip soup. He also openly admitted that his carbon footprint didn’t really matter that much to him:</p><blockquote><em>“…if I buy a fruit from the other side of the world, I know it took the plane. Do I have any complaints to make? Not at all.”</em></blockquote><p>The truth is, being sustainable isn’t easy. Sometimes it’s not even fun.</p><p>We were able to move on to the <strong>Affinity Diagram</strong>. I loved this part: creating thematic groups with the interviewees’ answers. I wish we could have done it live with Post-it notes in every colour, markers, pencils… I love stationery!</p><p>Actually, my ideal shop would be a stationery shop. Well, my ideal shop would have stationery, shoes, books and records. I don’t know if it would be very successful…</p><p>I’m getting off-topic.</p><p>Back to the Wicked Problem diary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WAmHMAivMBkmSsKfkiDXfQ.jpeg" /></figure><h3>WEEK 1. DAY 4</h3><p>Another really entertaining part to work on: our <strong>User Persona</strong>.</p><p>We each created our own by mixing the data from the five interviewees, and then together we created <strong>Julio Mercier.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cvxro9lMVWe4Xrra0Tg-kA.jpeg" /></figure><p>We finally had someone to think about when developing our app!</p><p>We also completed our <strong>UJM</strong>, putting ourselves in Julio’s shoes and empathising with his emotions throughout his shopping journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JDay-n-FMGoZkQL8-XXi-A.jpeg" /></figure><p>We continued with the <strong>Problem Statement</strong>. This was where we got a little stuck, so we asked Ana for help again to make sure we were heading in the right direction.</p><p>She also gave us some advice about our User Persona, so that it would be clearer what his <strong>Goals &amp; Needs</strong> and <strong>Pain Points</strong> were.</p><h3>WEEK 1. DAY 5</h3><p>Finally, Friday.</p><p>I had no idea how I was going to make it to today.</p><p>I’ve been dreaming about Figma, Zoom and everything we’ve been learning all week. I guess that’s normal, but this first week has definitely been intense.</p><p>Even though the class is online and there isn’t much interaction between classmates outside our individual groups, I’m really happy with the people I’ve ended up with in this bootcamp.</p><p>At least for now. Let’s see what happens in Week 9…</p><p>After defining and finalising our <strong>Problem Statement</strong>, we did a <strong>Round Robin</strong> for ideation. I would have loved to do a <strong>Worst Idea</strong> exercise and have a few laughs, but time was starting to stress us out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5ZU_8AyIsGxybGwU1jrlg.jpeg" /></figure><p>We then worked on our <strong>User Flow</strong>. We each created one and then put them together. I have to admit that, being Friday and with my brain completely fried, I missed quite a few important steps.</p><p>None of us remembered the <strong>AHA! moment</strong> either. Luckily, we’d asked Ana to take a look at our User Flow, and she reminded us about it.</p><p>That was quite an AHA! moment itself.</p><h3>WEEK 2. DAY 1</h3><p>Second week of the bootcamp!</p><p>So far, I’m still very motivated. I’m probably not understanding half of what’s going on, but I take lots of notes and use lots of colours, so something must be getting into my brain…</p><p>Today we worked on our <strong>lo-fi wireframes</strong> as a team. First, we each made our own based on our <strong>Happy Path</strong>, and then we created one together, deciding which elements from each version we wanted to keep and combine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3xOTbcRCOW7BaA6cvbNzQ.jpeg" /></figure><p>Once again, we asked Ana to have a look at it. After incorporating her suggestions, we moved on to prototyping.</p><p>Jacques made the connections at an astonishing speed.</p><p>This part was really fun too: putting ourselves in the shoes of our User Persona and following them through their journey, and, above all, seeing the result of a week and a half of work with our brains practically smoking.</p><p>Now it’s time to test it and find out whether this app could actually be useful for connecting users with fresh, local produce in their area.</p><h3>WEEK 2. DAY 2</h3><p>Today we’re going to spend the whole day preparing the presentation.</p><p>Choosing a template, adapting it to our project and putting all the information into it. Honestly, working with Jacques and Denis has been really comfortable. We get along well and work well together.</p><p>It took us the whole day to get the template ready for tomorrow’s presentation. We’ve rehearsed quite a lot, with a stopwatch, to make sure we don’t go over the 10-minute limit.</p><p>But let’s see how it goes tomorrow when it’s actually live…</p><h3>WEEK 2. DAY 3</h3><p>The presentation day finally arrived!</p><p>I’m really proud of all the work we’ve done, and also super nervous, of course.</p><p>The order is: first Denis, presenting up to <strong>Affinity Insights</strong>; then me, from <strong>User Persona</strong> to <strong>Concept Sketches</strong>; and finally Jacques, from <strong>Concept Testing Insights</strong> to the end.</p><p>Even though we’d rehearsed quite a lot, it felt a little rushed and wasn’t very smooth.</p><p>Sarah congratulated us and gave us some advice for future presentations: rehearse more, adjust some of the text sizes on the slides, and use more images and less text.</p><p>And that’s a wrap for Team Autumn!</p><p>It’s been a pleasure working with you, Jacques and Denis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf4de14af534" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CHALLENGE 2: WIREFRAMING]]></title>
            <link>https://medium.com/@ceciliajosviel/challenge-2-wireframing-72bcc9b39f22?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/72bcc9b39f22</guid>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Sat, 05 Sep 2026 17:19:55 GMT</pubDate>
            <atom:updated>2026-09-05T17:19:55.838Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of the pre-work before starting the UI/UX course at Ironhack, we have to complete a wireframing exercise. Although we were given some app suggestions, I chose Tidal because it is the app I use the most. If you don’t know it, I highly recommend it. It is a music streaming app similar to Spotify. The main difference is that it doesn’t have a free plan, but it pays artists significantly more than other music streaming platforms.</p><p>I really like music, so when I usually open the app, I immediately type in the name of the band or artist I want to listen to, either because I have read some news about an artist releasing new music or simply because I feel like listening to someone in particular.</p><p>For this exercise, we had to choose a route to develop the wireframing process. I decided to do something I had never really done before: go to the Explore tab. I was pleasantly surprised by how simple yet effective the experience is. There aren’t millions of options displayed at once. Instead, there are three main ways to explore music:</p><p><strong>1. By genre</strong></p><p>They don’t go crazy with extremely specific genre classifications like “neo-techno-folk-chill-industrial”, so it is easy to choose a genre.</p><p>Personally, I was a little (actually, quite a lot) disappointed that there is no “punk” category and that the first Ramones album is classified under the same category (“rock”) as Pink Floyd’s clearly progressive <em>The Dark Side of the Moon</em>. But anyway, we are here to talk about wireframing, not music.</p><p><strong>2. Moods / Activities</strong></p><p>There are also several categories here, without going overboard with the number of options.</p><p>I would personally like to see some more everyday activities alongside categories such as “wellness” or “workout”, such as “songs to iron to” or “songs to clean the bathroom to”. But again, we are here to talk about wireframing.</p><p><strong>3. Music by decade</strong></p><p>No objections here. In fact, this is the route I chose: discovering albums by decade.</p><p>Within this section, there are three options:</p><ol><li>Playlists</li><li>Milestone Year Albums</li><li>Albums of the decade</li></ol><p>I decided to go with the third option. Among all the albums available, I chose <em>Blood on the Tracks</em> by Bob Dylan, which I had never listened to before. This is the music playing while I continue working on the exercise.</p><p><strong>4. Lyrics</strong></p><p>I also went to the “Lyrics” tab, which is by far my favourite feature. But I didn’t add that feature to the prototype.</p><p>I am old enough to remember listening to music before the internet and how difficult it could be to find the lyrics to songs if they weren’t included with the vinyl or CD. So being able to see what the artists are singing about at any moment is absolutely wonderful.</p><h3>User flow</h3><p>The navigation flow is:</p><p><strong>Home → Explore → Decades → 1970s → Albums of the decade → Blood on the Tracks</strong></p><h3>UI elements</h3><p>The main UI elements I identified are:</p><ul><li>Title</li><li>Search bar</li><li>Slider for browsing genres, moods and decades</li><li>Bottom icons accompanying the different categories:</li><li>New Releases</li><li>Top</li><li>Dolby Atmos</li><li>Videos</li><li>HiRes</li><li>Clean Content</li></ul><p>Once an album is selected, the album cover is displayed. Below it, there are the <strong>Play</strong> and <strong>Shuffle</strong> buttons.</p><p>Underneath these, there are additional buttons for:</p><ul><li>Add</li><li>Credits</li><li>Download</li><li>Share</li></ul><p>I have already made the initial sketches with pen and paper. The next step is to recreate the screens in Figma and build the prototype.</p><h3>Tidal Screens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*5HP-oHGApuVY-m-7qvQlrg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*W1IfPGUj0AgtpcsITtIOcA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*bYDnxvb5fceUnhvJDbn03w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*1eeaiKnpnkJAYEGQj8yTaw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*8FjsiBaeiyRnKDD_WxPSjQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*Z_8J9hBfL_vNygzYgkKZFQ.jpeg" /></figure><h3>Lofi Sketches</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XhoM_cHA021FtsNYjhrFg.jpeg" /></figure><h3>Wireframing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMLQMkYT0HW9FbjizJjhQQ.jpeg" /></figure><h3><strong>Prototype</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDGrC_x94XF8%3Flist%3DPLb88hGv8FDiQ&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDGrC_x94XF8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDGrC_x94XF8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0cdbd1d75482b7219188c501279fe9b3/href">https://medium.com/media/0cdbd1d75482b7219188c501279fe9b3/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72bcc9b39f22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Citymapper: One App to Rule Them All]]></title>
            <link>https://medium.com/@ceciliajosviel/citymapper-one-app-to-rule-them-all-d4543ef119ad?source=rss-c04c3a817ed3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4543ef119ad</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[cecilia jos]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 23:57:36 GMT</pubDate>
            <atom:updated>2026-08-27T23:57:36.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YPLGVD-HCvRSO6Nx5z6-gQ.jpeg" /></figure><h3>Introduction</h3><p>Hi! My name is Cecilia Jos, and I am a future Ironhack student taking the intensive UI/UX course. As part of the pre-work for the course we have to complete an exercise related to Design Thinking.</p><p>For this challenge we were asked to add a new feature to Citymapper that would help solve a common problem when using public transport in different cities: having to use and pay for different tickets, cards and transport systems depending on where we are.</p><p>But before getting into the problem, what exactly is Citymapper?</p><p>Citymapper is a British public transport app and mapping service that helps users find the best way to get from one place to another. It combines information from different modes of transport, including public transport, walking, cycling and driving, often providing real-time information. The app is available on mobile devices as well as through its website.</p><p>Its closest competitors include Google Maps, Moovit and Chipi. One of the main differences between Citymapper and these alternatives is its focus on urban mobility and the way it presents transport information. Its interface is visual, simple and intuitive, making it easy to compare the different options available in a city.</p><h3>What did I discover by talking to users?</h3><p>To better understand the problem, I talked to five people about their mobility habits, the apps they use to get around and their experience with different public transport systems.</p><p>One of the first things I discovered was that <strong>Citymapper is still relatively unknown to many people</strong>. Both in their home cities and when travelling, most of the people I interviewed said they usually use Google Maps to find out how to get somewhere or to determine the best route.</p><p>However, a common problem did come up: <strong>dealing with different transport systems when travelling to another city can be complicated.</strong></p><p>The people I interviewed mentioned how difficult it can be to know which transport card or ticket is the best option for each situation. This becomes even more complicated when visiting several cities during the same holiday.</p><p>The result can be a wallet full of different transport cards, some of which we do not know if we will ever be able to use again, while others still have unused trips or credit on them.</p><h3>Defining the problem</h3><p>As public transport users, we usually know how to get around our home cities. We know which pass we need, how much it costs, where to buy it and how to use it.</p><p>But what happens when we arrive in a city we don’t know?</p><p>All five people I interviewed lived in large cities such as Madrid or Barcelona, where they were familiar with their local public transport systems. But imagine someone who lives in a small town or village with little or no public transport and then travels to a large city.</p><p>Suddenly, they may be faced with multiple transport options, combinations, fares and types of passes that they are not familiar with.</p><p>This led me to define the main problem I wanted to solve:</p><p><strong>How might we help both residents and visitors easily find and manage the transport option that best suits their needs within Citymapper?</strong></p><h3>One app to rule them all</h3><p>This is where my little <em>Lord of the Rings</em> reference comes in.</p><p>The idea is simple: instead of one ring to rule them all, <strong>one app to manage them all.</strong></p><p>One app to rule them all.<br>One app to find them.<br>One app to bring them all.<br>And in the darkness, when there’s no cell service, bind them.</p><p>The idea behind this is that Citymapper could become more than just a tool for <strong>finding the best route</strong>. It could also become the place where users can <strong>discover, choose and manage their public transport options</strong>, regardless of the city they are visiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lr7KXdA7NhJb14MQfnuKYQ.jpeg" /></figure><h3>Three possible solutions</h3><p>Once I had identified the problem, I came up with three possible solutions.</p><h3>Option 1: Use our usual transport card</h3><p>The first option would be to add a new feature to Citymapper called <strong>“Load Card”</strong>, allowing users to use their usual transport card and load the trips they want to take in another city.</p><p>The main problem with this solution is that <strong>not every user has a physical transport card</strong>, and different cities also use different systems that may not be compatible with each other.</p><h3>Option 2 : Pay per use</h3><p>The second option would be to create a virtual card within Citymapper that users could add money to and then use directly from their phone to pay for individual journeys on the metro, bus, train, etc.</p><p>This would eliminate the need to buy a physical card in every city and allow users to use their phone as their transport payment method.</p><p>However, this solution does not necessarily solve the initial question users may have: <strong>Which transport option or pass is actually the best one for me?</strong></p><h3>Option 3: A virtual transport card adapted to each user</h3><p>This is the solution I decided to develop.</p><p>The idea is to create a <strong>virtual transport card within Citymapper </strong>that brings together the different transport options available in each city.</p><p>When selecting a city, users would see two options:</p><p><strong>VISITOR</strong> | <strong>RESIDENT</strong></p><p>Depending on the option they choose, Citymapper would display the different transport alternatives available in that city.</p><p>For example:</p><p><strong>As a visitor:</strong></p><ul><li>One-day multimodal pass</li><li>48 hours multimodal pass</li><li>72 hour multimodal pass</li><li>4 days multimoda pass</li></ul><p><strong>As a resident:</strong></p><ul><li>Monthly pass</li><li>Zone-based passes</li><li>Passes for specific lines</li><li>Other transport options available in that city</li></ul><p>The key idea is that <strong>users should not need to understand the city’s transport system beforehand</strong>. Citymapper would present the available options in a simple and understandable way and help them choose the one that best fits their needs.</p><p>The goal is not simply to create a virtual transport card. <strong>The goal is to remove the uncertainty around public transport in an unfamiliar city.</strong></p><p>Citymapper would bring together the available options, explain them in a simple way and recommend the most suitable one depending on whether the user is a resident or a visitor.</p><h3>What I learned from the process</h3><p>One of the main things I learned from this process is the importance of <strong>not making assumptions about users</strong>. At the beginning, I thought the main problem would be having to use different physical transport cards in every city. However, after talking to users, I realised that the problem goes beyond the physical card itself. <strong>Choosing the right transport option can be just as confusing as paying for it.</strong></p><p>I also discovered that a solution that seems simple from a designer’s perspective does not necessarily solve the user’s real problem. For example, creating a virtual card could eliminate the need to carry several physical cards, but it would not necessarily help someone who does not know which pass or ticket they should buy in the first place.</p><p>Another important learning was the value of <strong>designing for different types of users</strong>. A resident who knows their city and uses public transport every day has very different needs from a visitor who is using the transport system for the first time. This is why I decided to differentiate between <strong>“Resident” and “Visitor”</strong> in my proposed solution.</p><p>Finally, this exercise made me realise that <strong>good UX is not only about making an interface simple and attractive</strong>. It is also about reducing uncertainty, helping users make decisions and providing the right information at the right moment.</p><p>And now, it’s time to turn this idea into a prototype!</p><h3><strong>VISITOR OPTION</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bGXERt9dIZaXxZZP9pjsIA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EU0HvSERFvOGO_O8GCYVHg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xg-INpvfkzywyKea_8Gc1g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxU34sh9RwO9WB4ccFFsvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sts4bG58PZZQ_p8y6STXAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsYJO1lHWoDWuLurz6ckAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9u-FQIF3NJJED87IwFgBdw.jpeg" /></figure><h3>RESIDENT OPTION</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nj4Ch6ws4BHga5qLdSUAWA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlV57omYywsOPZnEHTKFDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*whp-gszzPJvOJJXX3J_WFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1D3CqH9d40ucnYguvv5HQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aUN6YtJcaqCme6orYSW9Qw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhfjCgiMrKWjvFqB8r7tDQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4543ef119ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>