<?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 Eugene Belyakov on Medium]]></title>
        <description><![CDATA[Stories by Eugene Belyakov on Medium]]></description>
        <link>https://medium.com/@eu.belyakov?source=rss-edb6c32d3baa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cHKLn05GbfWICo5gsaFrGQ.png</url>
            <title>Stories by Eugene Belyakov on Medium</title>
            <link>https://medium.com/@eu.belyakov?source=rss-edb6c32d3baa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:43:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eu.belyakov/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[They Offered $10K/Month for a Fintech Design Role — Then Demanded Free Work. I Refused. Here’s Why.]]></title>
            <link>https://medium.com/@eu.belyakov/they-offered-10k-month-for-a-fintech-design-role-then-demanded-free-work-i-refused-heres-why-97c0323b89c9?source=rss-edb6c32d3baa------2</link>
            <guid isPermaLink="false">https://medium.com/p/97c0323b89c9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Eugene Belyakov]]></dc:creator>
            <pubDate>Fri, 16 May 2025 03:21:11 GMT</pubDate>
            <atom:updated>2025-05-16T07:56:19.955Z</atom:updated>
            <content:encoded><![CDATA[<h3>7 red flags every product designer should recognize</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBLgs4PlDUttsfkVoV2PKg@2x.png" /></figure><h3>They offered $10K/mo for a fintech design role — then demanded free work. I refused. Here’s why: a real breakdown of my messages with a “recruiter”.</h3><p>The world of freelancing and remote work is full of exciting opportunities — but it’s also riddled with traps. One of the most common? <strong>Scam-hunting</strong>: when companies pretend they’re hiring, but all they really want is free labor disguised as a “test task.”</p><p>I’m a senior product designer with over 10 years of experience, and I recently ran into one of these situations myself. In this post, I’ll walk you through a real exchange I had with a recruiter (names and details changed for privacy, but the messages are real). I’ll break down what raised red flags, and share tips to help junior designers avoid falling into the same trap.</p><h3><strong>The Exchange: Step-by-Step Breakdown</strong></h3><h4><strong>Message 1: Job Opportunity</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vtwnrfbxLup3b2XXQLJuEw.png" /></figure><p><strong>Tamas B.</strong><br>It’s great to connect with you.<br>We are excited to announce an opportunity for experienced developers to work on an exciting decentralized exchange (DEX) platform.<br>We are specifically looking for designers, frontend, backend, blockchain developers, and QA engineers who are open to collaboration.<br>This position will be a long-term contract, and the best part is, it allows for full remote work.<br>If you’re currently employed, we’re open to considering a part-time arrangement for this project.<br>So, let me know if you’re interested and how you think you could contribute.<br>Looking forward to staying in touch.</p><p><strong>What raised a red flag<br></strong>At first glance, it sounds great — long-term project, remote-friendly, flexibility. But it was <em>too</em> generic.<br>Who’s the company? What’s the project? Why me?<br>It read like a mass message sent to dozens of people.</p><blockquote>💡 Pro tip: <strong>Lack of specifics is the first red flag.</strong></blockquote><p><strong>Red flags: </strong>🚩</p><h4><strong>My response</strong></h4><p>“Thanks for reaching out!<br>I’m a senior product designer with over 10 years of experience, including key roles in fintech — from mobile banking to subscription products and cybersecurity platforms.</p><p>Your DEX project sounds interesting, and I believe my fintech background could be especially valuable here.</p><p>I’m currently employed full-time, but open to part-time collaboration with the possibility of transitioning to full-time if there’s a strong mutual fit.</p><p>Could you please share more about the designer role — your expectations, current design challenges, the type of engagement you’re offering (full-time/part-time/flexible), and the compensation range?</p><p>Thanks again, and looking forward to your reply.”</p><p><strong>Why I responded this way</strong></p><p>I made it clear from the start that I’m an experienced professional, so the recruiter would understand I’m not a beginner. I mentioned fintech to tie my background to their project. That’s the professional way to go — you’re not just agreeing, you’re showing your value. I also honestly said that I’m currently employed and not actively looking, but open to a conversation since it doesn’t commit me to anything.</p><blockquote>💡 Pro tip: Always show how you can add value, but wait for their response.</blockquote><h4>Message 2: Link to job description</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycMh_u-_ChEZiHH9jPteyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPmS25aql-occICryeZLGg.png" /><figcaption>The links to the job description were publicly available, and no terms of confidentiality or a Non-Disclosure Agreement (NDA) were discussed.</figcaption></figure><p><strong>Tamas B.<br></strong>“Please check this JD” (sends a Google Doc link).</p><p><strong>What raised concerns:<br></strong>Sharing a job description is normal — but again, zero context. Not a word about the company, the project goals, or even who’s behind it.</p><p>When a recruiter doesn’t provide basic info, it’s a red flag.</p><p><strong>Red flags: </strong>🚩🚩</p><h4>My response</h4><p>“Thank you for considering my profile — I truly appreciate your interest.<br>After reviewing the opportunity, I believe the current scope and compensation level may not be the right fit for me at this stage. For remote roles, I usually consider longer-term engagements (18+ months) with a monthly rate starting at $10K.</p><p>That said, if the project’s terms evolve or you’re looking for senior design support on a different basis, feel free to reach out. I’d be happy to reconnect.</p><p>Wishing you success with the product!”</p><p><strong>Alright, so here’s why I handled it that way:<br></strong>I was straight with ’em — told them their current offer wasn’t a match for me right now, but I definitely left the door open to keep talking. I put my number out there ($10K a month) to weed out the non-serious players right off the bat. For a senior designer with my kind of experience, that’s a totally fair ask, and I wanted to see how they’d respond.</p><blockquote>💡 Pro tip: Lay your cards on the table early. Saves a ton of time.</blockquote><h4>Message 3: They met my number.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iZvPcj_LFFJ3ZagrM7JLQ.png" /></figure><p><strong>Tamas B.<br></strong>“We will consider about your monthly salary as $10k. Shall we go on to the next step?”</p><p><strong>So, what threw me off was this:<br></strong>They jumped on the $10K right away, no discussion, even though it was above their initial salary range. Normally, companies will want to clarify the budget, negotiate a bit, or at least ask a few questions. Getting that quick ‘yes’ was a definite red flag. It felt like they were just trying to reel me in and get me invested in the process, whether they could actually swing it or not.</p><blockquote>💡 Pro tip: If they agree <em>too</em> easily to a higher rate without any pushback — that’s a big red flag.</blockquote><p><strong>Red flags: </strong>🚩🚩🚩</p><h4>So, my question was:</h4><p>“Could you please share what the next steps would look like?”</p><p><strong>Here’s why I asked that:<br></strong>I wanted to get a clear picture of what was coming next. A serious employer will lay out the process for you: an interview, a test assignment, timelines. This was basically a test of their transparency.</p><blockquote>💡 Pro tip: Always ask about the next steps — it shows you how organized they are.</blockquote><h4>Message 4: The test assignment.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1sZkPJTV4CS_J2hLWQL1g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZiRneIJd6i-dHax7O3FZ_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ZhPt2VCj9KoL7wUq8eVZg.png" /><figcaption>The links for the test assignment were publicly available, and no terms of confidentiality or a Non-Disclosure Agreement (NDA) were discussed.</figcaption></figure><p><strong>Tamas B.<br></strong>Okay,<br>Here are the four steps we have planned:<br>1. Simple Assessment (A straightforward mini-task)<br>2. Technical Interview<br>3. Final Interview<br>4. Onboarding</p><p>If you are ready to go on to the process, I’d like to have you complete a quick simple assessment that should take around 20 to 30 minutes of your time.</p><p>It isn’t an online interview, just a take-home task. Link.<br>Please check this test requirement and then do the assessment task.<br>After done, let me know. okay?</p><p><strong>So, here’s what really bugged me:<br></strong>A ‘quick and easy’ 20–30 minute assignment for a <em>senior</em> designer? Are you serious? Design tests, <em>especially</em> for a DEX platform, take hours at a minimum. This was either a flat-out lie, or they just don’t get what they’re asking for. Also, get this: in the message, he says 20–30 minutes, but inside the actual assignment, it suddenly became 50–60 minutes.</p><blockquote>💡 Pro tip: Unrealistic timelines for a test assignment — that’s a major red flag.</blockquote><p><strong>Red flags: </strong>🚩🚩🚩🚩</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bW0rM20Gg5JiJEAv1-Ch8g.png" /></figure><h4>My Questions About the Assignment</h4><p>“I’ve taken a close look at the test assignment — thanks for sharing it.</p><p>Before I jump into the design part, I wanted to clarify a few important things. What’s the main goal of the redesign? Is there any user feedback, or are you seeing drops in certain metrics that triggered the need for an update? Even if the current UI looks outdated, design for the sake of aesthetics doesn’t always lead to better outcomes — it’s important to understand what you’re aiming to improve.</p><p>It would also help to know more about the users of this dashboard — their roles, typical tasks, and what kind of problems they’re solving with it.</p><p>Another thing: is the target platform desktop web, or do you expect a mobile version as well? And in terms of output — are you looking for polished mockups or more rough concepts at this stage?</p><p>Lastly, to be honest, the time estimates seem significantly underestimated. Even just understanding the context and preparing thoughtful design directions would take at least a full day of focused work — not 20 or 60 minutes. And developing three solid variations takes even more. That’s not really feasible without more input, and in general, feels like too much effort for a test task — especially without confidence that the scope is clearly understood from your side.</p><p>So at this point, I wouldn’t be able to move forward unless these questions are clarified and the format is more balanced.</p><p>Let me know if you’re open to discussing it further.”</p><p><strong>Here’s why I asked those questions:<br></strong>You just can’t do quality design work without context — goals, users, metrics, all that stuff. It’s impossible. I asked those questions to see if they actually knew what they wanted and if they were willing to provide that information. That’s standard practice for a pro — it’s what separates experienced designers from those who just jump straight into designing without getting even the basic info they need.</p><blockquote>💡 Pro tip: Ask questions. It’s your best filter to see if they’re actually serious and know what they’re doing.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mo-M7M0BtiBVkElRnD91wg.png" /></figure><h4>Tamas B.</h4><p>“This isn’t redesign.</p><p>I just want to know your skills.</p><p>And checking current project is mandatory for any designers and developers who will work in this project.”</p><p><strong>So, here’s what really set me off:<br></strong>He didn’t answer a single one of my questions. He claimed it wasn’t a redesign, just a ‘skills check,’ but <em>still</em> insisted I do the assignment.</p><p>Design at least three different dashboard options by <em>redesigning</em> the current one — I mean, how is that <em>not</em> a redesign? Seriously.</p><p>The lack of context and his sheer stubbornness — those are huge red flags. It felt like a blatant attempt to squeeze free work out of me.</p><p>I’d give this whole exchange at least three red flags:<br>1 🚩 He didn’t answer any of my questions.<br>2 🚩 He denied it was a redesign.<br>3 🚩 He tried to manipulate me by saying all the other candidates were doing it.</p><blockquote>💡 Pro tip: If they won’t give you the info you need but still demand you do the assignment — run. Just run.</blockquote><p><strong>Red flags: </strong>🚩🚩🚩🚩🚩🚩🚩</p><h4><strong>My Final Reply</strong></h4><p>“Thanks for getting back. I’ve carefully reviewed the test task and completely understand your intent to evaluate skills before moving forward — that’s absolutely fair.</p><p>That said, I want to be upfront: the current assignment feels too heavy for an unpaid test. Producing three thoughtful dashboard concepts — with proper attention to hierarchy, UX, and visual quality — would require significantly more than 1–2 hours. Without clear goals, user feedback, or business context, it’s difficult to deliver work that reflects real value.</p><p>I believe my skills can be better assessed through my portfolio, recommendations from former colleagues on LinkedIn, and the scale of the companies and products I’ve contributed to.</p><p>Wishing you the best of luck in finding the right designer for the role.”</p><p><strong>Why I Replied This Way:<br></strong>I politely declined but offered an alternative — my portfolio and testimonials. This shows I value my time and I’m not willing to waste it on questionable tests. I wished them luck to end the conversation without any conflict.</p><blockquote>💡 Pro tip: Know how to say “no” professionally; don’t get drawn into pointless arguments.</blockquote><h3>🚩 7 <strong>Red Flags: When to Skip the Test Assignment</strong></h3><ul><li><strong>Lack of specifics about the project or company</strong> — No info on who they are, what they do, or their goals.</li><li><strong>Agreeing too quickly to a higher rate</strong> — If they don’t negotiate or even clarify the budget, it could be a trap.</li><li><strong>Unrealistic timelines for the test</strong> — “20–30 minutes” for a complex task? That’s manipulation.</li><li><strong>Devaluing your work</strong> — “It’s not a redesign, I just want to check your skill level.”</li><li><strong>Refusal to provide context</strong> — They won’t answer questions about goals, users, or metrics? Bad sign.</li><li><strong>Insistence without compromise</strong> — If they demand the task “as is” and won’t engage in dialogue, it’s disrespectful of your time.</li><li><strong>Using manipulative pressure tactics</strong> — Like claiming “all other candidates are doing it” or creating false urgency.</li></ul><h3><strong>Advice for Designers</strong></h3><ul><li><strong>Vet the company:</strong> Google them, check reviews, look at their social media. No trace? Probably a fake.</li><li><strong>Ask questions:</strong> Clarify details about the project, team, and goals. No answers? Walk away.</li><li><strong>Evaluate test assignments:</strong> Is it too extensive or unpaid? That’s a risk of them just wanting free labor.</li><li><strong>Trust your gut:</strong> Something feels off? It’s better to decline right away.</li></ul><h3>This whole exchange is a classic example of a recruitment scam. If a recruiter promises you the moon but can’t answer simple questions — run!</h3><h3>An inexperienced designer who’s eager for work might actually waste their time on a shady assignment like this! I hope my experience helps you, especially younger or early-career designers, be more vigilant. Share this article with your colleagues — together, we can make the industry fairer!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97c0323b89c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Chaos to Clarity: How I Redesigned the Raymarine Autopilot Interface Screen]]></title>
            <link>https://medium.com/@eu.belyakov/from-chaos-to-clarity-how-i-redesigned-the-raymarine-autopilot-interface-screen-1b650c085c21?source=rss-edb6c32d3baa------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b650c085c21</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Eugene Belyakov]]></dc:creator>
            <pubDate>Fri, 29 Nov 2024 12:47:57 GMT</pubDate>
            <atom:updated>2024-11-30T12:28:16.879Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>3 Steps From Chaos to Clarity: How I Redesigned the Raymarine Autopilot Interface Screen</em></h3><p>Hi there! My name is Eugene, and I’m a product designer.</p><p>I often get frustrated with how outdated, clunky, and unintuitive the interfaces of devices like marine autopilots — such as Raymarine — can be. In this article, I’ll reflect on how I approached redesigning this interface, turning it from chaotic and overloaded to functional and visually appealing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b91GKWyswM-BUAkY1PdnSw.png" /></figure><h3><strong>Step 1. Identifying the Problems in the Current Interface</strong></h3><h4>Before diving into the redesign, I asked myself one key question: <em>What exactly is frustrating for users?</em> Here’s a breakdown of the main issues I found.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GV9KZOYzlWDWwthTYKYtOw.png" /></figure><h4><strong>Problem 1: Lack of Clear Hierarchy</strong></h4><p>All elements on the interface compete for attention with equal weight, making the screen feel cluttered. Buttons and indicators are scattered randomly across the screen with no apparent logic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bANhqC54shoiemfDmOvUyw.png" /><figcaption>Hierarchy &amp; colors problems</figcaption></figure><h4><strong>Problem 2: Overloaded Design</strong></h4><p>Gradients, shadows, bright buttons, poor typography, and the lack of a proper grid system all create visual noise. The screen space is inefficiently utilized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qA8q6qU24eflM0VZRyB2iA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVTy3bHyPpTefH2vYVc0SQ.png" /><figcaption>Grid and arrangement of elements</figcaption></figure><h4><strong>Problem 3: Accessibility Issues</strong></h4><p>The color scheme hinders usability, especially in low-visibility conditions or for users with visual impairments. For example, button colors and text fail basic <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">🔗 WCAG</a> contrast tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjV7jjGtiNIECR8mGRwkcQ.png" /><figcaption>WCAG problems proof</figcaption></figure><h3><strong>Step 2. Defining the Goals for the Redesign</strong></h3><p>After pinpointing the issues, I set specific goals for the redesign:</p><p>• <strong>Enhance readability</strong> by creating a clear hierarchy and maximizing the efficiency of screen space.</p><p>• <strong>Simplify the visual style</strong> by adopting a minimalist approach.</p><p>• <strong>Optimize data grouping</strong> to make information faster and easier to process.</p><p>• <strong>Improve accessibility</strong> with high-contrast colors and usability for all users.</p><p>• <strong>Reduce visual noise</strong> by rethinking the entire layout.</p><h3><strong>Step 3. </strong>Solving the problems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hi21tHR1cH0FqIbBGeuXfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKUANXVBNzEISuAQ7obz4A.png" /><figcaption>Redesign concept</figcaption></figure><p><strong>1. Simplified Visual Style<br></strong>I removed gradients, messy shadows, and unnecessary decorative elements. The color palette was reduced to a minimal and functional set of basic colors. The layout was simplified and structured.</p><p><strong>2. Streamlined Navigation<br></strong>I relocated the control buttons to the bottom of the screen, similar to the navigation bars found in streaming apps.</p><p><strong>3. Organized Key Metrics<br></strong>Important metrics like heading, depth, COG, and SOG were placed around the central compass, making them easier to locate and memorize. I added more spacing around these values to ensure they stand out visually.</p><p><strong>4. High-Contrast Colors<br></strong>I chose high-contrast colors for text and essential elements to improve visibility, even in poor lighting conditions.</p><p><strong>5. Updated Typography<br></strong>The entire typography system was overhauled. I used the font <em>Anton</em> from <a href="https://fonts.google.com/specimen/Anton">🔗 Google fonts</a>, which is highly legible and visually clean.</p><p><strong>6. Accessibility Improvements<br></strong>I resolved contrast issues where they mattered most, ensuring a balance between readability and aesthetics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CRfvxpgD1ShM7gWhxCikwQ.png" /><figcaption>Addressing accessibility issues</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dE1G4qHwRXW5BUxJ8D0xQ.png" /><figcaption>Heatmap</figcaption></figure><p><strong>Impact of the Redesign metrics Improvement</strong></p><p><strong>Clarity</strong> 26 ➝ 52 (+26%)<br><strong>Heading</strong> 16% ➝ 28% (+11%)<br><strong>Secondary CTA</strong> 7% ➝ 12% (+5%)<br><strong>Primary CTA</strong> 19% ➝ 44% (+24%)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wKF6YlXT6uO9Bx-Ltf1PWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyLfPSiQjQgikd7AM-RbEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hO1cXTJWqdnpAUynwi3V2w.png" /><figcaption>Updated Layout</figcaption></figure><p>The new grid system feels much more symmetrical, aiding smoother navigation. The interface now strikes a balance between functionality and aesthetics. Where previously elements were scattered and space was wasted, the redesigned version is logically divided and visually “breathable.”</p><h4><strong>Autopilot Mode</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPhk_GXMgptH9nzW0RvLrg.png" /></figure><p>An additional improvement could include clearer indications for whether the autopilot is engaged or not.</p><h4><strong>What Could Be Improved Further</strong></h4><p>While I didn’t redesign the compass arrows in this iteration (it’s a bigger task requiring further research), the following things can also be improved:</p><p>• Add icons next to the values for heading, depth, COG, and SOG.<br>• Experiment with a light theme or alternative color palettes in future versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNBKS7a0oqiY0j4zDfExqg.png" /><figcaption>Random colors variations just for fun)</figcaption></figure><h3><strong>Conclusion</strong></h3><ol><li>The redesigned interface is now minimalist and user-friendly:</li><li>Key data grabs the user’s attention immediately.</li><li>Buttons no longer distract and harmonize with the overall style.</li><li>The screen feels more balanced and efficient.</li></ol><p>Please note that I did not redesign the UX of the whole application, mostly focused on improving the UI. I would also like to pay my respects to the Raymarine design team ❤️ I wrote this article purely for fun!</p><p><strong>For Beginner Designers</strong></p><p>Always start with a deep problem analysis, work closely with users, and test your designs under real-world conditions.</p><p>What do you think about this redesign? Feel free to share your redesign variations thoughts, questions, or suggestions for further improvements in the comments.</p><p>You can also post a comment if you want the original design file in figma!</p><p>Thanks for reading and let’s subscribe!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b650c085c21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Onboarding Is Losing Users: Lessons from Redesigning a Weather App]]></title>
            <link>https://medium.com/@eu.belyakov/weather-application-onboarding-payment-screen-analysis-289ded2dba1d?source=rss-edb6c32d3baa------2</link>
            <guid isPermaLink="false">https://medium.com/p/289ded2dba1d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Eugene Belyakov]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 04:54:53 GMT</pubDate>
            <atom:updated>2024-12-03T06:17:08.296Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>A step-by-step breakdown of windy.app </strong>(<a href="https://apps.apple.com/us/app/windy-app-wind-weather/id997079492">appstore</a> &amp; <a href="https://play.google.com/store/apps/details?id=co.windyapp.android">google play</a>)<strong> onboarding process with practical solutions to boost engagement</strong>.</h4><p>Hi there! My name is Eugene, and I’m a product designer.</p><p>Imagine downloading an app with high expectations — it promises the best weather forecasts, convenient tools, and perfect personalization. But what greets you? A black loading screen… or worse, a crash. How does that feel? Disappointing? Now, imagine this frustration repeating at every step of the onboarding process.</p><p>That’s how this story begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O4TykMUpl_OPUHUn_hv9Yg.png" /></figure><h3><strong>Step 1: Identifying the Problem</strong></h3><p>I decided to test <strong>windy.app</strong>, marketed as “the best weather app for sports and travel.” It sounded great, but right at the loading screen, I hit a snag — a long, awkward pause, and once, the app even crashed.</p><p><strong>How does a user feel?</strong></p><p>😱 <em>“Can I trust this app?”</em></p><p>Digging deeper, I realized the issue went beyond technical glitches. The app seemed determined to make the user journey harder — unnecessary screens, unclear texts, and zero motivation to make a purchase.</p><h3><strong>Step 2: Diving into the User Journey</strong></h3><p>Here’s how the onboarding experience unfolded:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OV1fhE3XvM51-gEZGQXyQg.png" /></figure><h4><strong>1. Splash Screen</strong></h4><p>The app showed a black screen that lingered too long, especially on iOS. One crash during this stage cast doubt on the app’s reliability.</p><p><strong>Emotion:</strong></p><p>😱 <em>“A crash on my first run? And it’s just a blank screen?”</em></p><h4><strong>2. “Best Weather App” Screen</strong></h4><p>This step promoted the app but added no real value to onboarding. It overloaded users with information and shouldn’t be the first actionable screen.</p><p><strong>Emotion:</strong></p><p>😐 <em>“I already downloaded the app. Show me why it’s better!”</em></p><h4><strong>3. Sport Selection Screen</strong></h4><p>The phrasing “Select your sport” felt limiting, implying only one choice, though multiple selections were possible. Visuals were unclear, making it hard to tell if green items were selected or not.</p><p><strong>Emotion:</strong></p><p>🙂 <em>“Personalization? Nice — features tailored to my sports!”</em></p><h4><strong>4. Location Request</strong></h4><p>Referencing “nearby spots” was too narrow. Users often plan trips to distant locations and want forecasts for those places. This could discourage them at this stage.</p><p><strong>Emotion:</strong></p><p>😐 <em>“Sure, I’ll ride locally, but I need forecasts for Austria, where I’m headed tomorrow.”</em></p><h4><strong>5. Paywall</strong></h4><p>The paywall failed to explain what the app offered or why it was worth buying. No personalization or clear benefits were presented.</p><p><strong>Emotion:</strong></p><p>🤬 <em>“Access to all tools? Which ones? Where’s the promised personalization?”</em></p><h4><strong>6. Spot Search Screen</strong></h4><p>Misaligned messaging: the button read “Add your spot,” but the title said, “Find the nearest spot.” This created confusion.</p><p><strong>Emotion:</strong></p><p>☹️ <em>“I don’t need the nearest spot. I need one in Austria!”</em></p><h4><strong>7. Main App Screen</strong></h4><p>Finally, users reach the app’s main interface — but by this point, frustration has already set in.</p><p><strong>Emotion:</strong></p><p>😐 <em>“Finally, I’m in.”</em></p><h3><strong>Step 3: What Needs to Change?</strong></h3><p>Onboarding is a crucial moment of truth — it’s when users decide if they’ll stick around. If the app doesn’t highlight its strengths right away, trust is lost.</p><h3><strong>Step 4: The Redesign</strong></h3><p>Here’s how I tackled the problem:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZVg5IE_WD8bmh6uhNLN69A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hJ7pr0DiV2QLFKwae-npIg.png" /></figure><h4><strong>Splash Screen</strong></h4><p>Added a logo and a message stating, “Voted the best weather app by the World Meteorological Organization.” This transforms a dead screen into a trust-building moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mP5HTKQzmU-efF-b21en3g.png" /></figure><h4><strong>Personalization</strong></h4><p>Improved sport selection screens with clearer visuals and refined text. Now users can immediately see how the app adapts to their interests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PpYGEQulqT_8NesJ9bstvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rE2Ipx_EK-Ds2BpWrRzd8A.png" /></figure><h4><strong>Social Proof</strong></h4><p>Inserted real user reviews during the personalization process. Seeing others’ positive experiences boosts confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXregh5zVtzCN6mxiMaGcQ.png" /></figure><h4><strong>Paywall</strong></h4><p>Revamped with clear descriptions of key features: accurate forecasts, offline functionality, and data comparison from multiple sources. Users now understand what they’re paying for.</p><p><strong>Extremely important!</strong> Make it so that the benefits are generated based on the sports selected earlier by the user and what they consider important in weather forecasts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qu2_gLNKQzh0PoV6-M8KHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zjX2Aa86Wswi0eDBvmkhtA.png" /></figure><h4><strong>Unified Requests</strong></h4><p>Merged geolocation and notification prompts into one step after the paywall. This keeps early onboarding clean and focused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3qAaf2uypKlLQo_jDAo44A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gvpDvCPGwHVJTXCEiit_dg.png" /></figure><h3><strong>Step 5: The Results</strong></h3><p><strong>The new onboarding flow:</strong></p><ol><li>Builds trust from the first seconds.</li><li>Highlights personalization to make users feel valued.</li><li>Leverages social proof to dispel doubts.</li><li>Offers a clear, informed path to purchase.</li></ol><h3><strong>Step 6: Final Thoughts</strong></h3><p>By focusing on personalization and adding social proof, I created a seamless onboarding flow. Key features are now front and center, unnecessary steps were cut, and requests for geolocation and notifications come at the right time. All screens are consistent and user-focused.</p><p><strong>A Hypothesis for Testing</strong></p><p>If a user’s first session extends without a purchase, a well-timed paywall reminder could nudge them toward upgrading during that same session.</p><p><strong>Thank you for reading ❤️</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=289ded2dba1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>