<?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 Emir Ceren on Medium]]></title>
        <description><![CDATA[Stories by Emir Ceren on Medium]]></description>
        <link>https://medium.com/@emirceren?source=rss-29fe0520f51e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1DgjDjfrFq57NOCbw37x5g.jpeg</url>
            <title>Stories by Emir Ceren on Medium</title>
            <link>https://medium.com/@emirceren?source=rss-29fe0520f51e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:25:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emirceren/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[A UX/UI Case Study: HakemPortal]]></title>
            <link>https://medium.com/@emirceren/hakemportal-8d34eef14f78?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d34eef14f78</guid>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 21:38:54 GMT</pubDate>
            <atom:updated>2025-07-23T07:03:51.204Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A Legal-Tech SaaS for Finding the Right Experts</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Os0dvbsgVXZqSGz7EtYTA.png" /><figcaption>Hakemportal case study cover image.</figcaption></figure><h3>Introduction</h3><p>HakemPortal is a legal-tech SaaS platform that helps people find and connect with independent arbitrators, legal experts, and technical professionals in Turkey.</p><p>I partnered directly with the founder to shape the product vision and deliver the entire UX/UI, from flows to interface, along with branding elements like logo, typography, and color. The challenge? Building a professional, searchable directory inside a WordPress environment, while integrating SaaS tools like Typeform and Airtable to support scalable workflows.</p><p>This case study breaks down our process, from early structure decisions to launch-ready UI.</p><h3>Defining the Opportunity</h3><p>Arbitrators and expert witnesses don’t typically have a dedicated space online. Most rely on bar associations, old-school PDF registries, or scattered firm listings. For clients, whether they’re legal professionals or individuals in dispute resolution. There’s no single, user-friendly place to search, compare, and contact trusted experts.</p><p>We saw an opportunity to bridge that gap:</p><ul><li>Make profile creation easy and professional</li><li>Build a filtering system that actually works in real-life use cases</li><li>Do all of this using lean, low-code tools that could be maintained without a full engineering team.</li></ul><h3>Empathize</h3><p>We began by mapping the needs of two core user groups:</p><ol><li><strong>Experts</strong> (arbitrators, lawyers, and technical consultants) who want visibility and credibility</li><li><strong>Searchers</strong> (legal professionals or business clients) who want to quickly find someone they can trust</li></ol><p>We spoke with people from both sides, informal interviews with experts already listed in traditional directories, and lawyers who frequently need to contact them. Common threads emerged quickly:</p><ul><li>Experts didn’t know how to stand out or even get discovered</li><li>Searchers found the current tools outdated, slow, or too vague</li><li>Everyone wanted something reliable, not flashy</li></ul><h3>Define</h3><p>From early interviews and internal research, we developed the core experience goals:</p><ul><li>Experts should feel guided and supported when creating a profile, no login walls or complex forms</li><li>Searchers should find a fast, structured way to filter and compare profiles</li><li>The entire platform needed to feel trustworthy but lightweight, especially on mobile</li></ul><p>We translated these into two focused problem statements:</p><ul><li><strong>For experts:</strong> “How might we help independent professionals create a credible presence online, without friction?”</li><li><strong>For searchers:</strong> “How might we simplify expert discovery for people navigating complex legal decisions?”</li></ul><h3>Ideate</h3><p>Instead of building from scratch, we explored how far we could push existing tools. WordPress gave us flexibility, but also limitations, especially when it came to form logic and dynamic search. We knew we had to get creative.</p><p>We used:</p><ul><li><strong>Typeform</strong> for profile creation, using conditional logic for a smoother onboarding flow</li><li><strong>Airtable</strong> as a CMS-lite for storing structured expert data</li><li><strong>WordPress</strong> as the shell and content delivery engine</li></ul><p>Labeling and categorization became one of the most critical parts. We brainstormed flexible but specific filters:</p><ul><li>Area of law</li><li>Sector experience</li><li>Role (e.g. arbitrator, lawyer, expert witness)</li><li>Language &amp; location</li></ul><h3>Prototype</h3><p>We mapped out core flows for both user groups:</p><ul><li>Profile creation: a no-login, form-based onboarding path</li><li>Expert discovery: landing &gt; filters &gt; profile detail &gt; contact</li></ul><p>Each step was translated into mid-fidelity wireframes to test layout, content hierarchy, and navigation logic. We kept interactions shallow, no distractions, no dead ends.</p><p>Because we worked with real content from the beginning, we were able to test early with sample data and adjust how categories and layouts responded.</p><h3>UI &amp; Branding</h3><p>The branding is deliberately restrained. We leaned into clarity over creativity and positioned the platform as professional and neutral.</p><ul><li><strong>Logo</strong>: A simple sans-serif wordmark that suggests legal formality without being rigid</li><li><strong>Colors</strong>: Calm blues and greys, signaling trust and neutrality</li><li><strong>Typography</strong>: Clean sans-serif for body text, paired with a high-contrast serif for names and roles</li></ul><p>UI components follow this same tone, minimal styling, sharp spacing, and a vertical rhythm that works across desktop and mobile.</p><h3>Test</h3><p>We tested key flows with a handful of experts and legal professionals. Because the UI was light and the structure intuitive, most feedback centered on small copy adjustments and category naming.</p><p>One insight: many users didn’t know what type of expert they needed until they saw categories. That validated our emphasis on labeling and helped us reword certain filter groups.</p><p>We also ran internal QA sessions to check form logic and edge cases, like users trying to submit incomplete data or search without selecting filters.</p><h3>Reflections</h3><p>Designing HakemPortal wasn’t about reinventing UX patterns; it was about respecting constraints and making the most of lean tools.</p><p>The real learning came in shaping trust through simplicity:</p><ul><li>Building a system that works even with limited content</li><li>Structuring information to feel professional, not overwhelming</li><li>Letting the experts — not the interface — take center stage</li></ul><p>Working closely with the founder gave me the space to own the product thinking while still focusing on details. It taught me how to design for credibility in a space where trust is everything, and where friction can lose a user instantly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d34eef14f78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A UX/UI case study for Wellness: “New Leaf”]]></title>
            <link>https://medium.com/@emirceren/a-ux-ui-case-study-wellness-new-leaf-e6c2cf14bb4c?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6c2cf14bb4c</guid>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Fri, 20 Jun 2025 08:20:54 GMT</pubDate>
            <atom:updated>2025-10-26T07:49:50.192Z</atom:updated>
            <content:encoded><![CDATA[<h3>A UX/UI case study for a Wellness app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Ed058E8wLyThJqBvEEj6A.png" /><figcaption>Cover image.</figcaption></figure><h3>Introduction</h3><p>The brief was clear: “Daily Health Organization” aims to enhance its services, products, and user base. And a smartphone app will be delivered in the chosen wellness category.</p><p>Within 13 people, we randomly teamed up in 2 and dived into the topic with haste. The process and the structure were clear. Design thinking with iterations in an agile approach, aligned with linear Kanban.</p><p>The challenge of <strong>quitting smoking</strong> as a team appealed to us, and we wanted to take it on.<br>The goal was to provide users with a more advanced experience during the process of quitting smoking and to tackle one of the most difficult challenges: the difficulty of quitting smoking. Kick-started the project with a very bold challenge.</p><h3>Defining the Opportunity, Research &amp; Synthesis</h3><p>Started with secondary research (desk research), deep-dived into this topic. Created a framework and built the stage. Focused on the users and the market.</p><p>Discovered:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jmsL2SnJDlyzEUiIS6yhQ.png" /><figcaption>Research synthesis.</figcaption></figure><blockquote>Key Takeaways:</blockquote><h3><strong>1. Health is the top reason smokers choose to quit <br>2. Emotional support is prior in smokers support expectations <br>3. Cravings and low motivation are key quitting barriers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bmtt2pbHcVPluHxRU-ou1w.png" /><figcaption>User Persona &amp; User Journey</figcaption></figure><h3>User Persona and Journey:</h3><p>We created Ash, based on a lack of empathy, relapse issues, and motivation points and have found Industry/design challenge characteristics as such;</p><p>Lack of support through the quitting process<br>Lack of user empathy<br>Lack of transparency (Data&amp;Privacy)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ztI6N6EXn7RbFNrjfgHiPg.png" /><figcaption>Definitions, Statements and How might we’s.</figcaption></figure><h3><strong>Features &amp; Solution Overview</strong></h3><p>Our solution prioritizes a seamless onboarding experience that requires minimal user input, making access to support quick and intuitive. Once onboarded, users benefit from continuous guidance through integrated cognitive behavioral therapy (CBT) tools, access to mentoring, and active community chat spaces.</p><p>We also ensured transparent, GDPR-compliant data practices, giving users full control over their personal data, including the ability to delete it at any time.</p><h3>User Flow</h3><p>To support users who experience a relapse during their stop-smoking journey, we designed a 7-step user flow that guides them through a short, emotionally supportive process. The flow focuses on recognizing the relapse without judgment, checking in on the user’s emotional state, and offering tailored cognitive behavioral tools to reframe negative thoughts. It then provides immediate coping strategies, helps the user identify their trigger, and connects them with mentorship or peer support. Finally, the flow resets their progress in a motivating way, framing the relapse as a learning moment and offering a fresh start. This structure aims to reduce shame, build resilience, and re-engage users without friction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBlYBR3uuXpfh0pQjV8RTQ.png" /><figcaption>User flow, Lo-Fi &amp; Mid-Fi wirefraomes and prototypes.</figcaption></figure><p>Once we prototyped, we started with internal and external concept testing. Found challenges on the journey, and addressed the correct moments and opportunities.</p><blockquote>Once again, design thinking showed up as a practical and flexible framework during my UX/UI training. With each project, I gained valuable insights and a deeper understanding, gradually strengthening my perspective on the process.</blockquote><blockquote>The more challenges that emerged, the more I learned to iterate and stay flexible. That’s when I realized we, as a team had truly started thinking in a user-centered way, and problem solving began to feel like a creative, engaging stretch.<br>So, iterations are fun lol.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crrI_W1kaPVCFWi5msoqzA.png" /><figcaption>Testing feedbacks.</figcaption></figure><p>Users needed comfort, empathy, and and calming presence of our solution and service. With the direction of gatherings iterated the journey to its final form. And moved on to Branding, UI &amp; Visual design.</p><h3>The Brand</h3><p>In our competitor analysis, <strong>Kwit</strong> stood out for its empathetic and calming approach and featuring a minimalistic layout, soft illustrations, and a dreamy pastel color palette that creates a gentle user experience. <strong>Headspace</strong>, on the other hand, uses bold, immersive visuals with a more structured layout. Its vibrant, flat color palette and expressive illustrations create an engaging and emotionally uplifting atmosphere. Both apps rely on illustration and color to shape tone, but with distinct emotional strategies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6I4i2NqJzdY8LZB7ELXW-Q.png" /><figcaption>Competitor Analysis</figcaption></figure><p>Our brand is built around five core values: <strong>emotional connection, efficiency, support, interactivity,</strong> and a <strong>soothing experience</strong>. Visually, we adopted a <strong>minimal, modern layout</strong> that balances clarity with warmth. The typography system pairs a <strong>grotesque typeface</strong> for headlines with <strong>Inter</strong> for body content and selected for its legibility and functional rhythm, especially when displaying dense or sensitive information.</p><p>The color palette was carefully refined through multiple iterations to achieve both emotional resonance and usability. Grounded in <strong>white</strong>, <strong>pistachio green</strong>, and <strong>dark green</strong>, it follows heuristic design principles while being complemented by <strong>Apricot Sand (#F0A36F)</strong> as an accent; a warm, balancing tone that guides user attention gently. We also experimented with a more expressive direction in iconography, integrating a soft 3D-inspired <strong>Lava icon style</strong> to add a tactile, contemporary feel to the visual system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZbBjUMPxgQRSoYPGw4J6g.png" /><figcaption>Brand’s visual style and art direction. Moodboard, color chart, and type scale.</figcaption></figure><blockquote>Among the many design risks we took :) , one of the most rewarding was experimenting with the <strong>3D Lava iconography trend</strong> <a href="https://medium.com/@waldobear002/airbnbs-new-lava-icon-format-a-technical-deep-dive-b2604626c7e0">inspired by Airbnb’s system</a> (which deplyoed early/mid 2025). It introduced a playful, fluid layer to our otherwise minimal UI, and turned out to be an effective way of adding emotional depth and a modern edge without distracting from the core experience.<br>Additional must-see resource: <a href="https://www.codelevate.com/blog/how-to-create-airbnb-lava-style-icons---step-by-step-guide-2025">https://www.codelevate.com/blog/how-to-create-airbnb-lava-style-icons---step-by-step-guide-2025</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spbU3i_ELuwiBBNjzQZ0oA.png" /><figcaption>Iconography iterations.</figcaption></figure><p>For the main grid and layout, we explored an anti-design approach letting visual elements breathe through generous white space and intentionally breaking away from rigid structure.</p><h3><strong>The High Fidelity Prototype</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hoaI3I1H7NpIYpE0Gdfm9Q.png" /><figcaption>Newleaf quit smoking app screens.</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2F5QfZLm3THeEEmSktqxB1xs%2Fwellness%3Fpage-id%3D0%253A1%26node-id%3D1-905%26viewport%3D4%252C-337%252C0.17%26t%3DuUFi30GIVAWBDQBZ-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D1%253A905&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2F5QfZLm3THeEEmSktqxB1xs%2Fwellness%3Fpage-id%3D0%253A1%26node-id%3D1-905%26viewport%3D4%252C-337%252C0.17%26t%3DuUFi30GIVAWBDQBZ-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D1%253A905" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0d55178e8f08257f1eeaca004cebc0e/href">https://medium.com/media/a0d55178e8f08257f1eeaca004cebc0e/href</a></iframe><h3>Key takeaways:</h3><p>For starters, Lean UX and UX strategy are very essential.</p><p>Designing for moments of relapse taught that the importance of creating a space that feels safe, non-judgmental, and easy to return to.<br>- Visual decisions matter when using a soft color palette and tactile iconography, which helps set the right emotional tone without overwhelming the user.<br>- Iteration was key. Whether it was the user flow, type pairing, or color system, things only started to click after testing and tweaking.<br>- I learned how to strike a balance between emotional design and functionality, making sure users feel supported, but also clearly guided.<br>- Taking a few visual risks, like trying out 3D Lava-style icons, turned out to be a great way to add personality and keep the experience fresh.</p><blockquote>This project was full of energy, curiosity, motivation, and a lot of learning along the way. At one point, I even tested what it’s like to be a digital nomad while managing the workload. This added a new layer to the experience.</blockquote><blockquote>I honestly enjoyed every phase of this project. There were challenges to tackle along the design thinking process, but they felt engaging, not overwhelming, once there was a good balance.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jYydetrBVOCj7Kk42AiYIQ.png" /><figcaption>End cover image.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6c2cf14bb4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RA Guide Redesign: Balancing Brutalist Aesthetics with Usability]]></title>
            <link>https://medium.com/@emirceren/ra-guide-redesign-balancing-brutalist-aesthetics-with-usability-e6ae2c817969?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6ae2c817969</guid>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Sun, 15 Jun 2025 21:16:30 GMT</pubDate>
            <atom:updated>2025-06-25T20:26:43.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Cover image, Current RA guide app screens, RA Guide Logo." src="https://cdn-images-1.medium.com/max/1024/1*6EQPgFe8vJCj7L8nafkNWQ.png" /><figcaption>Cover image: Current RA guide app screens, RA Guide Logo.</figcaption></figure><h3>Introduction:</h3><p>For my third Ironhack project, I redesigned the <strong>RA Guide</strong> mobile app. This challenge focused purely on UI, not UX research. We were asked to pick a well-known native mobile app and redesign a few screens to improve its usability and visual clarity using heuristic principles. No pre-made UI kits, no slides, just Figma, heuristics, and our own design decisions.</p><blockquote>Resident Advisor Guide: A platform to discover electronic music, artists and events.</blockquote><p>I focused on two key screens:</p><ul><li>The <strong>main event listing page</strong></li><li>The <strong>calendar/date picker</strong></li></ul><p>The biggest challenge? Keeping RA’s bold, brutalist, and anti-design style intact while fixing some real issues in dark mode. This wasn’t a total overhaul, but rather a design conversation: how can you push a refined and respected system a step further by focusing on the user?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8TGG72QSpVypM6AGWMArPw.png" /><figcaption>RA Guide iOS screens. May, 2025</figcaption></figure><h3>The Starting Point: RA Guide and Its Design Voice</h3><p>RA Guide is part of Resident Advisor’s ecosystem, an iconic name in electronic music culture. The app is designed to feel raw, poster-like, and editorial. It reflects the nightlife world it serves. Sharp contrasts, heavy type, minimal icons. It leans on brutalist aesthetics in a way few apps do.</p><p>But here’s the tension: that visual confidence sometimes creates friction in everyday use. Especially in <strong>dark mode</strong>, which should feel effortless at night when the app is most likely to be used.</p><p>RA’s dark mode used full black backgrounds and pure white text. Visually loud. High contrast, but not always readable or comfortable. That’s where I stepped in. <br>Let’s start with deep brand analysis to fully engage with the current product.</p><h3>Moodboard:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhVlbxJ2cqDsOP2fglgSrw.png" /><figcaption>Brand in-depth analysis &amp; moodboard.</figcaption></figure><blockquote>Discovering the brand and finding patterns is most flexing and satisfactory moment/stage for this project. Brutalist stairs and finding the link in between the logo was surprising.</blockquote><h3>Competitors:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOR8pJpcOTIVcQpXgfZmVg.png" /><figcaption>Competitor analysis &amp; overall look on their dark mode approach. Brands: Bandsintown &amp; Dice.</figcaption></figure><h3>Strategy and Competitive Analysis</h3><p>I started by analyzing two competitor apps: <strong>Bandsintown</strong> and <strong>Dice</strong>.</p><ul><li><em>Bandsintown</em> sticks to a light theme. Clean layout, traditional hierarchy.</li><li><em>Dice</em>, on the other hand, leans fully into dark mode. Its design is bold but legible. Dark gray backgrounds, white or neon highlights, poster-forward UI.</li></ul><p>What I learned: dark mode can feel premium and immersive if done with care. Dice gets that right. RA aims for the same energy, but the execution needed refinement. That became my entry point for fixing the way RA handles dark mode without losing its personality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2aZ3nrpYerpMTANHM390jg.png" /><figcaption>Heuristic Principles Analysis</figcaption></figure><h3>What I Changed and Why</h3><p><strong>1. Color Palette</strong><br> I replaced pure black (#000000) with a deep charcoal gray. Pure white text became soft off-white. These are small moves that make a big difference. They reduce eye strain and create a better reading experience in low-light environments.</p><p><strong>2. Typography</strong><br> I adjusted line height and letter spacing to improve clarity. I introduced a secondary typeface to balance out the aggressive editorial look. The visual hierarchy is still bold but easier to scan. It now supports the content instead of competing with it.</p><p><strong>3. System Feedback and Interaction States</strong><br> Before, the app often felt like a static poster. I added clear feedback states, active filters, loading indicators, and hover/focus styles. Users now get visual clues that guide them, which helps reduce hesitation.</p><p><strong>4. Layout and Components</strong><br> I rebuilt all components from scratch in Figma using auto-layout, atoms, and molecules. The structure is clean and flexible. Visual weight is now better distributed, making it easier to move through the interface without cognitive fatigue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T4WR48T6t8SiyHJeokOIdw.png" /><figcaption>Color Experiments 1.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*403ipaS2ncHU6QE1kJKGsg.png" /><figcaption>Color Experiments 2.</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FESG5KErNRZFgIQNU1oethb%2FFigma-Lab-Basics_Emir_CEREN_UXFT_MAY_2025%3Fpage-id%3D0%253A1%26node-id%3D2-23%26p%3Df%26viewport%3D572%252C428%252C0.12%26t%3D8TK6sU5qQp5wNsR8-1%26scaling%3Dmin-zoom%26content-scaling%3Dfixed%26starting-point-node-id%3D2%253A3&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FESG5KErNRZFgIQNU1oethb%2FFigma-Lab-Basics_Emir_CEREN_UXFT_MAY_2025%3Fpage-id%3D0%253A1%26node-id%3D2-23%26p%3Df%26viewport%3D572%252C428%252C0.12%26t%3D8TK6sU5qQp5wNsR8-1%26scaling%3Dmin-zoom%26content-scaling%3Dfixed%26starting-point-node-id%3D2%253A3&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FESG5KErNRZFgIQNU1oethb%2Fthumbnail%3Fver%3Dthumbnails%252F4f07e3ce-a562-45e8-88f6-aaa7f7f010e1%26t%3D8TK6sU5qQp5wNsR8-1&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf82a7186d57c79c61d8931a4979e0a0/href">https://medium.com/media/cf82a7186d57c79c61d8931a4979e0a0/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XEkc-erpK1-o_j8V0mIx_A.png" /><figcaption>Color palette, Typography iterations.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nHizHddbqJYtd_CQWm29fg.png" /><figcaption>Execution.</figcaption></figure><p>Execution: Top-left: Main event listing screen before &amp; after with heuristic markings. Top-right: Date picker screen before &amp; after with heuristic markings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rl4PE_bl9q2Cvku13UbZew.png" /><figcaption>Designed screens.</figcaption></figure><p><strong>Final deliverables. Left: Date picker screen, Right: Main event listing screen.</strong></p><h3>Heuristics I Focused On:</h3><p>Here are the key Nielsen principles I applied:</p><ul><li><strong>Aesthetic and Minimalist Design</strong><br> Cleaned up the typography. Reduced glare by softening whites. Less noise, more clarity.</li><li><strong>Consistency and Standards</strong><br> Aligned dark mode with common visual standards. Used familiar icons and color contrasts so users don’t need to guess.</li><li><strong>Error Prevention</strong><br> Removed unnecessary contrast that could cause eye fatigue. Optimized how filters and date selection behave to avoid dead ends.</li><li><strong>Visibility of System Status</strong><br> Improved how users track what’s happening, what’s loading, what’s active, what’s filtered. No more guesswork.</li><li><strong>Help Users Recognize and Recover from Errors</strong><br> Clear, visible labels. Friendly fallback messages. Clean calendar states. Small touches that make a big difference.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EkI5lVcJbD5hBEokqDZQTA.png" /></figure><h3>Reflections</h3><p>RA’s design is not broken. It’s strong. But even well-designed systems deserve to be challenged. Especially when user comfort and accessibility are at stake.</p><p>This project was about striking a balance. Keeping the brand’s boldness, but refining it just enough so the experience feels smoother. I didn’t want to mute its voice. I just made it a little easier to listen to.</p><p><strong>What I took away:</strong></p><ul><li>You can respect a brand and still question it.</li><li>Even one contrast adjustment can improve real-world usability.</li><li>Heuristics are a great design lens when you don’t have research data.</li><li>Accessibility doesn’t kill creativity. It sharpens it.</li></ul><blockquote>This redesign was a study in restraint. A challenge to polish something without over-designing it. Sometimes, the best redesigns don’t shout. They just let the user breathe.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6ae2c817969" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transforming Socks & Rocks: A Responsive Ecommerce Redesign]]></title>
            <link>https://medium.com/@emirceren/transforming-socks-rocks-a-responsive-ecommerce-redesign-ea7344c5b16a?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea7344c5b16a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Mon, 02 Jun 2025 05:57:33 GMT</pubDate>
            <atom:updated>2025-06-02T06:00:48.679Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>When we began the Responsive Ecommerce project for our Ironhack bootcamp, our goal was to design a modern, user-friendly online store that would stand out in Berlin’s competitive retail scene. Gathering as Team Socks &amp; Rocks Me, Ana, Julien, and Alexander. We set out to create an experience that not only showcased a curated selection of socks and accessories but also responded seamlessly to the needs of mobile and desktop shoppers alike.</p><p>Throughout the 9 days sprint, our daily check-ins guided us from market research through to a polished hi-fi prototype. Along the way, we held stakeholder interviews, ran surveys, crafted personas, mapped user journeys, and tested our assumptions with paper and digital prototypes. In this case study, I’ll walk through our process step by step, sharing key insights and calling out where visuals can illustrate our progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MO2Kp0I8Xkwh3LJz" /><figcaption>Photo by <a href="https://unsplash.com/@angelacompagnone?utm_source=medium&amp;utm_medium=referral">Angela Compagnone</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Defining the Opportunity</h3><p>Our first task was to confirm that our team would partner with an ecommerce client. We researched Berlin’s online retail landscape to understand where an independent sock brand could differentiate itself. We looked at local competitors, niche sock curators, and broader fashion marketplaces to see which features users expected — everything from detailed product filters to sleek checkout flows.</p><p>With that context, we prepared for a stakeholder interview. Drafting the questions proved more challenging than anticipated. We wrestled with the right mix of business-model inquiries and user-experience questions. We wanted to uncover the client’s priorities for branding, product categories, and shipping logistics, without over-focusing on “socks” or “buying” in our survey questions.</p><h3>Empathathize</h3><p>We began by conducting market research to understand Berlin’s small &amp; medium-sized e-commerce landscape. Our team confirmed an e-commerce client and prepared stakeholder interview questions. Drafting those questions was challenging because we had to balance inquiries about business models with inquiries about user experience. By the end of the day, we had a finalized interview guide and a plan to prepare and share a survey.</p><p>The next day, we learned about information architecture and sitemaps while finalizing our stakeholder interview and survey. Writing survey questions proved tougher than expected. We noticed our questions leaned heavily on product details rather than on broader user motivations. We completed the survey in time to deploy it end of the weekend.</p><p>On the third day, We deployed our survey via Slack channels and friends’ networks and interviewed our stakeholder. The interview was shorter than we expected but still provided useful context. We also finalized an interview guide for user interviews.</p><h3>Define</h3><p>After collecting survey responses, we organized insights using an affinity diagram. We grouped feedback into themes around product discovery, pricing expectations, and mobile shopping frustrations. In parallel, we conducted user interviews based on our guide.</p><p>Once we synthesized survey and interview data, we developed a user persona and a user journey map. The persona and journey map captured needs and frustrations, highlighting where users struggled on existing sites. From this, we crafted a clear problem statement that focused on delivering a faster, more trustworthy experience across devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0Pgif1ILviPlUieLxrH0A.png" /><figcaption>Responsive E-commerce, User Persona, Sue Stainable</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWNyrMYCKDdkIbezBYSicA.png" /><figcaption>Responsive E-commerce, User Journey Map</figcaption></figure><h3>Ideate</h3><p>Next, we attended a lecture on moodboards and created our own. Combining ideas from our persona and journey map, we developed “how might we” statements to guide ideation. We also revisited and refined our sitemap to reflect key pages and navigation flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJB1IoY5TLoMB5Y-1SSm_Q.png" /><figcaption>Problem Statements for The User &amp; The Stakeholder</figcaption></figure><p>We applied ideation techniques such as Crazy 8’s and the MoSCoW method to generate layout and feature ideas. From there, we sketched low-fidelity wireframes for the homepage, collections pages with filters, product detail pages, and a basic checkout flow. These sketches allowed us to iterate quickly without focusing on visual details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yCWUzp9wEz6UphR6D7up8w.png" /><figcaption>MoSCoW method Clusters</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ny9LhmgO1-s6QKQvF-qIrA.png" /><figcaption>User Flow</figcaption></figure><h3>Prototype</h3><p>We moved on to mid-fidelity wireframes, using what we learned about grids and layout. We mapped out user flows, refining spacing and alignment. State changes, such as filters opening and carts updating, were defined in these wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*inGwOGqcCX-ss2Ez.png" /><figcaption>Mid-Fi Wireframes &amp; Prototype</figcaption></figure><p>Once mid-fidelity screens were approved, we built a high-fidelity prototype. We applied the color palette, typography choices, and visual details from our moodboard. We focused on key interactions like updating the cart, filtering products, and navigating between pages. We also prepared our presentation narrative alongside the prototype work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_Skt_hJu8qB6P8kY.png" /><figcaption>Moodboard</figcaption></figure><h3>Test</h3><p>With a high-fidelity prototype in hand, we planned for concept testing and usability testing. Although our check-ins did not detail specific test participants, we designed tasks to validate key flows: finding a product, applying filters, and completing checkout. We used feedback from concept testing to make final adjustments to asset placement, interaction timing, and flow clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LtCaOu2tDAbuFKPrw5GJfw.png" /><figcaption>Hi-Fi Prototype</figcaption></figure><h3>Reflections</h3><p>Over nine days, our design thinking approach of empathize, define, ideate, prototype, and test guided us from market research to a polished responsive e-commerce prototype for Socks &amp; Rocks.</p><p>Our process included<br> • Market research and stakeholder interviews<br> • Survey deployment and affinity mapping<br> • Persona and journey mapping<br> • Moodboarding and low-fidelity wireframing<br> • Mid-fidelity wireframing and high-fidelity prototyping<br> • Concept testing and usability adjustments</p><p>This process allowed us to stay focused and user-centered, delivering a responsive design that addresses the challenges we uncovered in Berlin’s e-commerce environment.</p><p>Working on Socks &amp; Rocks wasn’t just about applying UX methods. It was a crash course in adapting quickly, balancing design ideals with constraints, and listening more closely to user signals than assumptions. One unexpected takeaway came from our usability testing: users consistently struggled with the product filter, even though we thought it was intuitive. That forced us to step back, simplify the flow, and rethink how we define “clean design.”</p><p>Designing mobile-first also reshaped how we approached layout and hierarchy. Elements that felt balanced on desktop became overwhelming on smaller screens, and it took several iterations to find a rhythm that worked across breakpoints.</p><p>Beyond the UI challenges, the biggest learning was in collaboration, aligning as a team, critiquing constructively, and learning when to push forward or step back. Those moments shaped not only the product, but how we think as designers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea7344c5b16a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wicked UX]]></title>
            <link>https://medium.com/@emirceren/wicked-ux-bfe543142f3a?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe543142f3a</guid>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Mon, 19 May 2025 02:20:17 GMT</pubDate>
            <atom:updated>2025-05-19T06:52:08.922Z</atom:updated>
            <content:encoded><![CDATA[<p>First project in my UX journey.</p><p>“Wicked Problems”, Ironhack’s UX/UI Bootcamp first project. Which branches into Immigration, City Mobility, Food Sustainability, and Culture &amp; Heritage. With random allocation, I landed on “City Mobility”. The rest of this article tells the story of how we tackled our first UX challenge with a team of three, within 7 days.<br>We were expected to develop an innovative solution that addressed a real urban challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ay6pVL7byhFzJxA" /><figcaption>Photo by <a href="https://unsplash.com/@simmerdownjpg?utm_source=medium&amp;utm_medium=referral">Jackson Simmer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Problem Statement</strong></h4><p>People who live in urban areas need a way to maintain active mobility in the city without worry or interruptions in the most sustainable way possible.</p><p><strong>Goal:<br></strong> Design a user-centered solution that enables urban residents to move around actively and sustainably, while minimizing daily interruptions, uncertainties and concerns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l-deHDdY3JhNnDgE" /><figcaption>Photo by <a href="https://unsplash.com/@ryoji__iwata?utm_source=medium&amp;utm_medium=referral">Ryoji Iwata</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Research &amp; Discovery</h4><p><strong>Secondary Research: </strong>We began by brainstorming and stretching on the broader image of city/urban mobility. It is followed by secondary research, which is the step that we dived deeper into resources. At this step, a nebulous cloud of ideas gets clustered, discussed, and distilled. If you image search for “UX designer” and see the <a href="https://www.fernakademie-klett.de/bilder/Teaser-Kurse/_1000x500_crop_center-center_none/618612/4940_web_Certified-UX-Designer.webp">shots</a> with post-its, Sharpies and glass meeting rooms, yeah, this is one of those steps and applied in iteration with the same method, the further you go in the process. :)</p><p>For further insights, the next stop is: the user interviews</p><p>It forms around; background of the broad scope of the problem, A Set of goals to fulfill our curiosity towards user pain points, priorities and user behaviour, target groups and assumptions come along with secondary research. With the consolidation and regrouping our thoughts, one major mutual goal was one step ahead of the others: Understanding the user. This was the first hint to the team from the process that we are on the right way. :)</p><p>Once we have a strong foundation of brainstorming and secondary research, even when we were individually studying, post-it clusters slowly become identical. This allowed us to gradually accelerate the speed. Once we gathered the interview questions, it took us to the next step: Interviews.</p><p>We conducted 5 interviews with the other BootCamp mates. Many pain points, many different journeys we gathered. It helped to resolve key points of; behavioural patterns, goals and frustrations. The same iteration of affinity diagram (gather &amp; cluster) is conducted, and the 3 major pain points and one common goal spearheaded:</p><p><strong>😭 Traveler flexibility, Safety, Unpredictability.</strong></p><p><strong>🤞 Efficient travel</strong></p><p>With these key insights, we moved on to User Persona development.</p><blockquote>Comment: At this point, I realized it becomes harder to float and isolate between the designer mind &amp; empathize with the users. There is a constant bounce back and forth between brainstorming &lt;-&gt;empathizing. Maintaining this balance was a challenge at first, but afterwards it was easy to adapt to this reflex. And i believe footprint and impact of the designer can be observed through the process.</blockquote><h4>User Persona &amp; User Journey</h4><p>At this step, we created individual user personas. And key learning is: keeping to the user-centered approach is very critical for creating a persona. The fundamentals of the persona must be addressed in the problem statement. Gathered the personality from the clusters we gathered. And then, we voted :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmLImYMHWd2qEVTjDswSig.jpeg" /><figcaption>Wicked problems, City Mobility, User Persona</figcaption></figure><p>Once we had Kim, we moved on to User Journey. Considering her goals, daily life, painpoints, and possibilities, and developed a scenario (nothing crazy) that we can find touchpoints and see the opportunities to ideate and offer solutions. These points are called “How might we”s or HMW. <br>Described a day in her life to contextualize her mobility needs below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NKVd71MZP13Q4fa5z5_uxw.jpeg" /><figcaption>Wicked problems, City Mobility, User Journey</figcaption></figure><h4>A Critical Path: Problem Statement</h4><p>The importance of this step comes with its crossroads. The decision of future ideation will be made here. What product/service, goals to achieve, success metrics, and so on. <br>Filtering down HMW’s refined our final <strong>problem statement</strong> into:</p><blockquote>People who live in urban areas need a way to maintain active mobility in the city without worry or interruptions in the most sustainable way possible.</blockquote><blockquote><strong>Goal:<br></strong> Design a user-centered solution that enables urban residents to move around actively and sustainably, while minimizing daily interruptions, uncertainties, and safety concerns.</blockquote><h4>Ideation</h4><p>At this step used worse idea &amp; crazy 8s methods to develop our ideas, and again gather/cluster/vote/filter down with MoSCoW method. MoSCoW method used to for Feature Prioritization &amp; MVP Vision (statement). It is easy to understand and efficient mini method that took us quickly to the User flow.</p><h4>User Flow &amp; Concept Testing</h4><p>With the MVP statement and prioritized features, we created userflows individually. And consolidated into one, which addresses to safety concerns of the user. Once we refined the final user flow, we ran concept testing within the team before moving on to the wireframing &amp; prototyping. It helped us with the final iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLjJq1RvBlYOrWdzHiXCcQ.png" /><figcaption>Wicked problems, City Mobility, User Flow</figcaption></figure><h4>Wireframing &amp; Prototyping</h4><p>Once we had a user flow, wireframing was a smooth step. I sketched super simple and user-friendly approach screens, we consolidated them into one set of screens within the user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7nW2xxMEgzG-Qf_x8BAyA.png" /><figcaption>Wicked problems, City Mobility, Wireframes</figcaption></figure><p>None of mine got into lucky screens :) lol</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WbhBlFdRrhTjWWRCYT9sA.png" /><figcaption>Wicked problems, City Mobility, Final (lo-fi) Prototype</figcaption></figure><blockquote>1. Reach a destination with your bike.<br>2. Check your app before locking your bike to see if it’s safe or not. (Safety score based on user ratings)<br>3. Select a safe parking/locking zone and go there.<br>4. Once you reached, Select “Save Location” in the app. <br>5. Now you locked your bike in a safe spot, and the app will keep your parking location and remind you if needed.</blockquote><p>Once we had the screens, I linked the screens and made a prototype with them in Figma. We tested a few, but iteration was not in the scope of the project. So the quest is completed. ✅</p><h4>Key Learnings</h4><blockquote>The Process is working highly efficient and easy to navigate from the problem to the solution. Discovering, exploring, understanding and being a human were primary fuels for my case.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe543142f3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mini UX Challenge]]></title>
            <link>https://medium.com/@emirceren/ironhacks-prework-emir-ceren-challenge1-8fd7a1f739c2?source=rss-29fe0520f51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fd7a1f739c2</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Emir Ceren]]></dc:creator>
            <pubDate>Mon, 05 May 2025 06:21:33 GMT</pubDate>
            <atom:updated>2025-09-09T10:26:45.033Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Adding One-Tap Ticketing to Citymapper: A UX Case Study</strong></p><h3>Background:</h3><p>Citymapper is a smart urban transit app that helps users get around cities quickly by combining subway, bus, train, bike, and walking routes. It shows travel times, costs, and transfers. But one thing it doesn’t fully solve: ticketing.</p><p>Users still need to buy separate tickets for different transport modes. That means switching apps, tapping into vending machines, or figuring out how to pay depending on the country. It’s a stressful experience, especially when you’re unfamiliar with the system.</p><h3>Define:</h3><p>I interviewed 3 users who’ve used Citymapper or similar apps abroad. Here’s defined keysights:</p><ul><li>People love that Citymapper shows all transport options but hate having to leave the app to buy tickets.</li><li>Switching between transport modes like metro to bus to tram usually means buying 2 to 3 separate tickets.</li><li>Most people feel confused, rushed, or uncertain at ticket machines, especially when the language isn’t familiar.</li><li>The idea of one button to handle everything like Apple Pay for transit got an immediate “yes.”</li></ul><h3>Problem:</h3><p>Citymapper users need an easy way to purchase all necessary public transport tickets for their selected route without leaving the app.</p><h3>Ideate: “One-Tap Ticket”</h3><p>I designed a new feature called One-Tap Ticket, directly embedded in the route results screen. It automatically bundles and purchases every required ticket for your selected multimodal journey like bus, train, and metro using saved payment info in the app.</p><p>This builds on Citymapper’s strengths in routing and live data and fixes its biggest gap: ticketing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_w4rZL7gLYCHRNRLInD-Q.png" /></figure><ul><li><strong>Route view (landing)</strong> — Just like Citymapper today, but now includes a bold “Get Tickets” button under the journey summary.</li><li><strong>Ticket Summary Screen</strong> — Confirms the ticket types needed, price, and time range they’ll cover.</li><li><strong>Payment Confirmation</strong> — Uses saved payment details. One tap to confirm.</li><li><strong>Ticket Wallet</strong> — A new tab where digital QR codes or transport passes appear for scanning.</li></ul><h3>Learnings:</h3><p>People want fewer decisions, not more options. Choosing a route is enough mental work. Buying tickets should be invisible.</p><p>Users trust Citymapper for planning, so why not also for paying? We’re just extending what users already rely on the app to do.</p><p>Design should reduce friction. One button. Zero stress. That’s good UX.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fd7a1f739c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>