<?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 Hugo Carneiro on Medium]]></title>
        <description><![CDATA[Stories by Hugo Carneiro on Medium]]></description>
        <link>https://medium.com/@hugodesigns?source=rss-838fbb1dcd44------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CL2YX8pcsRpMLtA00Y1Qqw@2x.jpeg</url>
            <title>Stories by Hugo Carneiro on Medium</title>
            <link>https://medium.com/@hugodesigns?source=rss-838fbb1dcd44------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 05:33:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hugodesigns/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[How AI is taking over app creation | Hugo Carneiro]]></title>
            <link>https://medium.com/@hugodesigns/how-ai-is-taking-over-app-creation-bc74eb162c68?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc74eb162c68</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 10:31:20 GMT</pubDate>
            <atom:updated>2023-06-14T10:31:20.866Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>How AI is taking over app creation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lz_I3b40WUVmqj47V-pZqQ.png" /></figure><h3>Introduction</h3><p>In the realm of technological advancement, artificial intelligence (AI) has emerged as a disruptive force, reshaping industries and revolutionizing the way we interact with technology. The fusion of AI and mobile app development has given birth to a powerful combination that holds immense potential. In this article, we’ll delve into the world of AI app development, exploring its transformative capabilities and the exciting possibilities it brings to the table.</p><h3>The Rise of AI in App Development</h3><p>AI has made remarkable strides in recent years, transforming from a futuristic concept into a tangible reality. As the demand for intelligent and personalized experiences grows, developers are leveraging AI to enhance mobile apps’ functionality, efficiency, and user experience. From voice assistants to recommendation engines, AI-driven features have become increasingly prevalent, driving innovation across industries.</p><h3>Enhancing User Experience</h3><p>One of the key benefits of AI in app development lies in its ability to deliver highly personalized and intuitive user experiences. Through techniques such as natural language processing, machine learning, and computer vision, apps can analyze user behavior, preferences, and patterns to offer tailored recommendations, anticipate needs, and simplify complex tasks. This level of personalization fosters deeper engagement, leading to increased user satisfaction and loyalty.</p><h3>Smarter Decision-Making with Predictive Analytics</h3><p>AI-powered apps have the capability to harness vast amounts of data and extract valuable insights. By employing predictive analytics algorithms, apps can analyze user data, trends, and patterns to anticipate future outcomes and make informed recommendations. Whether it’s predicting consumer behavior, optimizing resource allocation, or identifying potential risks, AI empowers businesses to make smarter decisions and gain a competitive edge.</p><h3>Automating Repetitive Tasks</h3><p>Another significant advantage of AI in app development is its ability to automate repetitive tasks, freeing up human resources for more strategic endeavors. Through <a href="https://enterprisersproject.com/article/2019/5/rpa-robotic-process-automation-how-explain">robotic process automation</a> (RPA) and intelligent algorithms, apps can streamline workflows, eliminate manual errors, and boost operational efficiency. From data entry to customer support, AI-driven automation empowers businesses to focus on higher-value activities while reducing costs and enhancing productivity.</p><h3>Embracing the Power of Chatbots</h3><p>Chatbots have become increasingly popular in app development, providing real-time and personalized customer support. AI-powered chatbots can handle a wide range of inquiries, offer instant responses, and provide round-the-clock assistance. Chatbots continually improve their understanding and response capabilities by leveraging natural language processing and machine learning, creating seamless interactions and improving customer satisfaction.</p><h3>AI Design and Image Creation</h3><p>AI is revolutionizing app design by enabling the automated creation of captivating visuals and graphics. Using <a href="https://machinelearningmastery.com/what-are-generative-adversarial-networks-gans/">generative adversarial networks</a> (GANs) and deep learning algorithms, developers can leverage AI to design logos, create customized images, and generate appealing UI elements. This innovative approach streamlines the design process, saves time, and enhances visual aesthetics, resulting in visually stunning and engaging app interfaces.</p><h3>Overcoming Challenges and Ethical Considerations</h3><p>While AI app development holds immense potential, addressing the challenges and ethical considerations associated with its implementation is crucial. Privacy concerns, data security, and algorithmic biases are among the key considerations that must be carefully addressed to ensure responsible and inclusive AI app development. Developers and organizations must prioritize transparency, accountability, and fairness to build trust and mitigate potential risks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrEUqrGGRL7g&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrEUqrGGRL7g&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FrEUqrGGRL7g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8651cf9b69aeada166c7fe67c3d519d/href">https://medium.com/media/b8651cf9b69aeada166c7fe67c3d519d/href</a></iframe><h3>Conclusion</h3><p>AI app development has emerged as a game-changer, empowering businesses to create intelligent, personalized, and efficient mobile experiences. By harnessing the power of AI, developers can unlock new dimensions of user engagement, predictive analytics, automation, and customer support. However, responsible implementation and ethical considerations are paramount to ensure that AI-driven apps foster inclusivity, privacy, and trust. As we embrace the transformative potential of AI app development, we step into a future where technology seamlessly integrates with human needs, enhancing our lives in unprecedented ways.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc74eb162c68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The difference between UI and UX designers]]></title>
            <link>https://uxdesign.cc/the-difference-between-ui-and-ux-designers-8769b49d5283?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/8769b49d5283</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 00:48:17 GMT</pubDate>
            <atom:updated>2019-02-27T09:41:24.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*26v0oHDf39OCHBTDO4w82w.jpeg" /></figure><p>You commonly see the acronym UI, that means User Interface, slapped together with UX, an acronym that means User Experience. You see recruiters posting jobs for UI/UX designers, you see products aimed to UI/UX designers, and so on, but did you know you that you don’t necessarily need to be both a UI designer and a UX designer?</p><p>Today in this article I’m going to explain the difference between UI and UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s1TbG5OJjqGawd7qSiDXUQ.jpeg" /></figure><h4>What does a UX designer do?</h4><p>A user experience designer, as the name indicates, is a designer that should care, more than anything else, about the user‘s experience with the final product.</p><p>A UX designer’s job is to understand the requirements, figure out the problem, and research. To create user personas, for example, first time user, returning user, and define use cases and journeys for those user personas.</p><p>It is his/her job to produce diagrams and flows to validate ideas, to create wireframes and usable mockups to do user testing.</p><p>A UX designer should always use two methods while assessing the requirements and writing a brief for a project:</p><ul><li>What-How-Why<em> (</em><a href="https://www.interaction-design.org/literature/article/how-to-develop-an-empathic-approach-in-design-thinking"><em>Here’s an article from Interactive Design foundation</em></a><em>)</em></li><li>Obvious-Easy-Possible<strong> </strong><em>(</em><a href="https://signalvnoise.com/posts/3047-the-obvious-the-easy-and-the-possible"><em>Here’s an article by Jason Fried</em></a><em>)</em></li></ul><p>As you can see, a UX designer is a thinker, the person that hands out a bullet proof idea for the UI designers, and later, developers bring to life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6Qs7rqBTnEJXyzZKbD-ig.jpeg" /></figure><h4>What does a UI designer do?</h4><p>Simply put, a UI designer is the person that realises an idea into something that can be seen and sometimes interactive.</p><p>It is a UI designer’s job to create wireframes, mockups, designs, of everything required for the project at hand.</p><p>A UI designer should always ask for feedback, validate and test his/her designs with real users.</p><p>A great UI designer is also quick to realise repetition and from that make sure everything and everyone is productive; It should create frameworks from his/her designs and create reusable components to help with keeping the same visual style throughout the product.</p><p>While the UX designer is the thinker of how something is going and should be used, the UI designer is the person that gives life to those ideas and makes them usable and beautiful to look at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0ciN7r6Z02xtUHhEeyUrA.jpeg" /></figure><h4>Conclusion</h4><p>Next time you see a job opening for a UI/UX designer, you will now understand what they are asking for. They really want a person to be the ultimate designer, to have the skills to think, question, test and validate his/her ideas, as well as the skills to implement those ideas.</p><p>I hope this article helps you distinguish between the two and stops any confusion about what is expected from those two different roles.</p><p>Thank you for taking the time to read this short article. Keep on solving problems!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8769b49d5283" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-difference-between-ui-and-ux-designers-8769b49d5283">The difference between UI and UX designers</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a MVP in today's competitive world?]]></title>
            <link>https://uxdesign.cc/what-is-a-mvp-in-todays-competitive-world-b914f4df845e?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/b914f4df845e</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 09:20:52 GMT</pubDate>
            <atom:updated>2018-07-27T11:55:03.554Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3><strong>What is an MVP in today’s competitive world?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmC1dhOEMw_4awMaT-Uf8w.jpeg" /><figcaption>Photo by: <a href="http://startupstockphotos.com/">Startup Stock Photos</a></figcaption></figure><p>Hello everyone, in this new article I want to pose some questions for you to think about them if you want to launch a new product to the market.</p><h4><strong>What does MVP mean?</strong></h4><p>The acronym MVP means Minimum Viable Product which in a nutshell is a product with just enough features to satisfy early customers, and to provide feedback for future product development.</p><p>The key purposes of a MVP is to:</p><ul><li>be able to test a product with minimal resources</li><li>get the product to early customers as soon as possible</li><li>reduce wasted engineering hours</li><li>accelerate learning</li></ul><p>With that explained, let’s get back to our main question <em>What is a MVP in today’s competitive world?</em></p><p>In today’s competitive world, where the chances of someone else being in the process of developing, or already have developed, a product like yours are very high, how do you think MVP’s should be released to users?</p><p>I believe the concept of MVP is still a viable mentality for a startup nowadays, however I do think that the released product today has to be much more complex than a product released under the same mentality a few years back. Let me explain.</p><p>Let’s take an example of a Project Management tool like <a href="https://asana.com/">Asana</a>, <a href="https://trello.com/">Trello</a>, and many others.</p><p>If you had a business and wanted to release a project management tool as your product you would do some market research and after evaluating what the competition offers you would probably ask a few questions like:</p><ul><li>Should I release my product with the same features that the competition has?</li><li>Should I release my product with just some of the features that the competition offer?</li><li>Should I release my product with just new features that the competition doesn’t have?</li><li>Should I release my product with improved features offered by the competition?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9pQvj1UAqt8CAeMpsmjmw.jpeg" /><figcaption>Photo by: <a href="http://pixabay.com/">Pixabay</a></figcaption></figure><h3>My opinion on what a MVP should be when competing against others</h3><p>Many still believe that nowadays you can still ship a half baked product to the market and quickly improve based on user’s feedback and usage.</p><p>I disagree with that!</p><p>If you are launching a project management tool in a market full of them, I think a MVP should be as complete as the competition. However, you can sacrifice in non-essential places, for example, sign-up and login pages and systems. This means that you don’t really need to innovate everywhere, as long as the basics of what you choose to not innovate are still met and doesn’t pose a blocking instance for your users.</p><p>There’s only two instances in my opinion where you can skip features that the completion offers:</p><ol><li>You practice a completely free business model (even if it’s just for a limited time)</li><li>You have a completely new idea on what a project management tool should be (very unlikely)</li></ol><p>I strongly believe that in a competitive environment you will need to match the competition’s features, and still offer something new or improved, otherwise it will be very difficult for you to market your product. This is something I would like to touch on.</p><p>Even if you have a top-notch product and marketable product you still need a great marketing machine.</p><p>Not easy to have a big marketing budget in the beginning but your product will depend on clever and viral marketing to survive. People will need to be talking about it.</p><p>If you target your product to businesses, you might need to get good sales people and you might be able to get your product out there with fewer features, but to survive in the long term you will still need to match and quickly outrun the competition.</p><p>Let me know your thoughts! Do you agree with my opinion? Do you disagree? And Why?</p><p>Thank you for taking the time to read this short article. Keep on solving problems!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b914f4df845e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-is-a-mvp-in-todays-competitive-world-b914f4df845e">What is a MVP in today&#39;s competitive world?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create Apple App Store cards with HTML & JS]]></title>
            <link>https://medium.com/@hugodesigns/how-to-create-apple-app-store-cards-with-html-js-261a3225724a?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/261a3225724a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Sat, 28 Apr 2018 18:04:06 GMT</pubDate>
            <atom:updated>2018-06-25T13:58:49.214Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Recently for a project at work I wanted to create a list of cards that looked and acted similarly to the cards seen on the Apple App Store for iOS. After searching the web for examples I didn’t quite find one example that looked and acted quite like what I wanted, so I set out to create my own, and now I am here to share it with you all.</p><p><strong>One requirement I had is that when expanding a card, the position of the tapped card shouldn’t change, so that when I close the card I’m right back to the same scrolled position. So let’s begin!</strong></p><p>For this example I only used the following libraries:</p><ul><li><a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.js">jQuery 3.3.1</a></li><li><a href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css">Bootstrap CSS 4.1.0</a></li><li><a href="https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">Font Awesome 4.7.0</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ujUOfCJvPRwrw2AT5t5qFA.png" /><figcaption>What we will be achieving</figcaption></figure><p>I’m not going to explain the HTML or the CSS part so I’ll leave you here with the markup for one card and all the CSS needed for the visuals of our example.</p><h3>HTML</h3><pre>&lt;div class=&quot;list-wrapper&quot;&gt;<br>  &lt;div class=&quot;cards-list&quot;&gt;<br>    &lt;div class=&quot;card&quot;&gt;<br>      &lt;div class=&quot;card-content&quot;&gt;<br>        &lt;div class=&quot;banner-holder&quot;&gt;<br>          &lt;div class=&quot;banner&quot; data-height=&quot;20vh&quot; data-height-expanded=&quot;45vh&quot; style=&quot;background-image: url(https://medium.com/&#39;%3Ca%20href=%22/service/https://upload.wikimedia.org/wikipedia/commons/4/44/4k-wallpapers-0.jpg&#39;%22%3Ehttps://upload.wikimedia.org/wikipedia/commons/4/44/4k-wallpapers-0.jpg&#39;%3C/a%3E)&quot;&gt;&lt;/div&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;container-fluid content-holder&quot;&gt;<br>          &lt;div class=&quot;inner-content&quot; data-position=&quot;20vh&quot; data-position-expanded=&quot;40vh&quot;&gt;<br>            &lt;div class=&quot;info-holder&quot;&gt;<br>              &lt;div class=&quot;date-category&quot;&gt;Apr 28 2018 / Category&lt;/div&gt;<br>              &lt;div class=&quot;like-wrapper btn-liked&quot;&gt;<br>                &lt;i class=&quot;fa fa-heart fa-lg&quot;&gt;&lt;/i&gt; &lt;span class=&quot;count&quot;&gt;6&lt;/span&gt;<br>              &lt;/div&gt;<br>              &lt;div class=&quot;bookmark-wrapper btn-bookmark&quot;&gt;&lt;i class=&quot;fa fa-bookmark-o fa-lg&quot;&gt;&lt;/i&gt;&lt;/div&gt;<br>            &lt;/div&gt;<br>            &lt;h2 class=&quot;title&quot;&gt;Nibh Tellus Pharetra Fusce&lt;/h2&gt;<br>            &lt;div class=&quot;description&quot;&gt;<br>              &lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Nullam quis risus eget urna mollis ornare vel eu leo. Donec sed odio dui. Nullam id dolor id nibh ultricies vehicula ut id elit. Donec ullamcorper nulla non metus auctor fringilla.&lt;/p&gt;<br>            &lt;/div&gt;<br>          &lt;/div&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;close-btn&quot;&gt;&lt;i class=&quot;fa fa-times&quot;&gt;&lt;/i&gt;&lt;/div&gt;<br>      &lt;/div&gt;<br>    &lt;/div&gt;<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><h3>CSS</h3><pre>*.lock {<br>  overflow: hidden;<br>}</pre><pre>.list-wrapper {<br>  position: absolute;<br>  top: 0;<br>  left: 0;<br>  right: 0;<br>  bottom: 0;<br>  overflow: auto;<br>}</pre><pre>.cards-list {<br>  position: relative;<br>  padding: 15px 15px 20px;<br>  padding-bottom: calc(20px + env(safe-area-inset-bottom)); /* For iPhone X */<br>  max-width: 400px;<br>  margin: auto;<br>}</pre><pre>.card {<br>  position: relative;<br>  height: 45vh;<br>  width: 100%;<br>  border-radius: 20px;<br>  overflow: hidden;<br>  box-shadow: 0px 10px 30px 0px rgba(0, 0, 0, 0.1);<br>  transition: opacity 0.2s ease, box-shadow 0.2s ease;<br>  opacity: 1;<br>  margin-bottom: 40px;<br>}</pre><pre>.card.open {<br>  border-radius: 0;<br>}</pre><pre>.card.hover,<br>.card:hover {<br>  box-shadow: 0px 0px 10px 0px rgba(0, 0, 0, 0.1);<br>}</pre><pre>.card-content {<br>  position: relative;<br>  width: 100%;<br>  height: 100%;<br>  background: rgba(255, 255, 255, 0);<br>  overflow: hidden;<br>  transition: border-radius 0.15s ease;<br>  border-radius: 20px;<br>  cursor: pointer;<br>}</pre><pre>.card.open .card-content {<br>  z-index: 500 !important;<br>  background: #fff;<br>  border-radius: 0px;<br>  cursor: default;<br>}</pre><pre>.banner-holder {<br>  position: absolute;<br>  width: 100%;<br>  overflow: hidden;<br>  display: flex;<br>  align-items: center;<br>  justify-content: center;<br>}</pre><pre>.banner {<br>  position: relative;<br>  height: 20vh;<br>  width: 100%;<br>  padding: 15px;<br>  background-size: cover;<br>  background-position: center center;<br>  background-repeat: no-repeat;<br>  background-color: transparent;<br>  overflow: hidden;<br>  z-index: 1;<br>}</pre><pre>.card.open .banner {<br>  height: 45vh;<br>  border-radius: 0;<br>}</pre><pre>.content-holder {<br>  max-width: 600px;<br>  padding: 0;<br>  z-index: 1;<br>  height: 100%;<br>  background-color: transparent;<br>  overflow: hidden;<br>  position: relative;<br>}</pre><pre>.card.open .content-holder {<br>  overflow: auto;<br>}</pre><pre>.inner-content {<br>  top: 20vh;<br>  padding: 20px;<br>  position: relative;<br>  background-color: #fff;<br>}</pre><pre>.card.open .inner-content {<br>  top: 40vh;<br>  padding-bottom: env(safe-area-inset-bottom); /* for iPhone X */<br>  border-top-left-radius: 20px;<br>  border-top-right-radius: 20px;<br>}</pre><pre>.info-holder {<br>  display: flex;<br>  align-items: center;<br>}</pre><pre>.date-category {<br>  text-transform: uppercase;<br>  font-size: 12px;<br>  opacity: 0.5;<br>  margin-bottom: 0;<br>  flex: 1;<br>  margin: 0 1.4rem 0 0;<br>}</pre><pre>.like-wrapper {<br>  position: relative;<br>  cursor: pointer;<br>  padding-left: 40px;<br>}</pre><pre>.like-wrapper .fa,<br>.bookmark-wrapper .fa {<br>  opacity: 0.3;<br>}</pre><pre>.like-wrapper.btn-liked .fa {<br>  opacity: 1;<br>  color: red;<br>}</pre><pre>.like-wrapper span {<br>  position: absolute;<br>  top: 0;<br>  left: 0;<br>  text-align: right;<br>  opacity: 0.3;<br>  width: 35px;<br>  line-height: 24px;<br>  font-size: 12px;<br>}</pre><pre>.bookmark-wrapper {<br>  margin-left: 8px;<br>  width: 24px;<br>  text-align: right;<br>  cursor: pointer;<br>}</pre><pre>.title {<br>  position: relative;<br>  margin: 10px 0 20px 0;<br>  font-weight: bold;<br>}</pre><pre>.description {<br>  font-size: 16px;<br>  line-height: 1.5;<br>  opacity: 0.6;<br>}</pre><pre>.card:not(.open) .description {<br>  overflow: hidden;<br>  /* Clips content to 3 lines when card is collapsed */<br>  display: -webkit-box;<br>  -webkit-line-clamp: 3;<br>  -webkit-box-orient: vertical;<br>  height: 4.2em;<br>}</pre><pre>.close-btn {<br>  position: absolute;<br>  right: 15px;<br>  top: 15px;<br>  height: 28px;<br>  width: 28px;<br>  line-height: 27px;<br>  background: rgba(255, 255, 255, 0.5);<br>  border-radius: 50%;<br>  color: #333;<br>  text-align: center;<br>  cursor: pointer;<br>  opacity: 0;<br>  visibility: hidden;<br>  transition: all 0.15s ease-in-out;<br>}</pre><pre>.card.open .close-btn {<br>  z-index: 600;<br>  opacity: 0.9;<br>  visibility: visible;<br>}</pre><h3>JavaScript</h3><p>Now let’s get to the fun part :)</p><p>Let’s start by creating our initial function and let’s call it initialiseCards(). In this function we will be placing what we need to be run at page load.</p><pre>function initialiseCards() {<br>  // Attach listeners<br>  // Do other things, we&#39;ll get to that<br>}</pre><pre>// Run function on load<br>initialiseCards();</pre><p>Now that we have this created, let’s create the function that will attach our event listeners.</p><pre>function attachListeners() {<br>  $(document)<br>    .on(&quot;click&quot;, &quot;.card-content&quot;, function() {<br>      if ( $(this).parents(&quot;.card&quot;).hasClass(&quot;open&quot;) ) {<br>        return;<br>      }<br>      expandElement($(this));<br>    })<br>    .on(&quot;click&quot;, &quot;.card .close-btn&quot;, function(event) {<br>      event.stopPropagation();<br>      collapseElement($(this));<br>    })<br>    .on(&#39;touchstart&#39;, &#39;.card&#39;, function() {<br>      $(this).addClass(&#39;hover&#39;);<br>    })<br>    .on(&#39;touchend touchmove touchcancel&#39;, &#39;.card&#39;, function() {<br>      $(this).removeClass(&#39;hover&#39;);<br>    });<br>}</pre><p>Let me explain those four event handlers, starting from the top:</p><pre>.on(&quot;click&quot;, &quot;.card-content&quot;, function() {})</pre><p>This event will handle the opening of each card. The <em>if</em> statement prevents the function from running if the card is already opened.</p><pre>.on(&quot;click&quot;, &quot;.card .close-btn&quot;, function(event) {})</pre><p>This second event handles the closing of the opened card. I have used the event.stopPropagation(); to make sure nothing else get’s fired when the card is still closing since it relies on animation timing to close and the click event can go through elements.</p><pre>.on(&#39;touchstart&#39;, &#39;.card&#39;, function() {})</pre><pre>.on(&#39;touchend touchmove touchcancel&#39;, &#39;.card&#39;, function() {})</pre><p>The last two elements are for mobile devices only, and it’s just a nice touch for visual effect. On web if you hover each card, it has the effect of being pushed down, on mobile devices the :hover doesn’t quite work, so instead I add a class that makes the same effect. That class is added on touchstart and removed on three events touchend touchmove and touchcancel. Feel free to play around with these.</p><p>After creating our attachListeners() we will call it from our initialiseCards(). Just like this:</p><pre>function initialiseCards() {<br>  attachListeners();</pre><pre>  // Do other things, we&#39;ll get to that<br>}</pre><p>Next we will create a function that will calculate the height of each collapsed card depending on the content. This is useful because the cards need a fixed height, but if your cards have dynamic content, you need to be able to show it without constraints, that’s why I calculate the height of each card so it just looks like that they are as big as the content inside.</p><p>Create a setCardHeight()</p><pre>function setCardHeight() {<br>  $(&quot;.card &quot;).each(function(index, element) {<br>    var slideHeight = $(element)<br>      .find(&quot;.banner-holder&quot;)<br>      .outerHeight();</pre><pre>    var containerHeight = $(element)<br>      .find(&quot;.inner-content&quot;)<br>      .outerHeight();</pre><pre>    var contentHeight = slideHeight + containerHeight;</pre><pre>  $(element).css({<br>      height: contentHeight<br>    });<br>  });<br>}</pre><p>This function get the height of the banner and the height of the content below the banner and sums them, generating our card height and applying it to the card. Now that we have this function, we will call it from our initialiseCards(), like this:</p><pre>function initialiseCards() {<br>  attachListeners();<br>  setCardHeight();<br>}</pre><p>Finally we just need the the functions to expand and collapse the cards. Let’s start with the expand.</p><pre>function expandElement(elementToExpand) {<br>  // Adds class &#39;open&#39; to help with styling<br>  elementToExpand.parents(&quot;.card&quot;).addClass(&quot;open&quot;);</pre><pre>  // Prevents &#39;body&#39; scroll<br>  $(&quot;body&quot;).addClass(&quot;lock&quot;);</pre><pre>  // Variable set<br>  var elementOffset = $(&quot;.list-wrapper&quot;).offset();<br>  var elementScrollTop = $(&quot;body&quot;).scrollTop();<br>  var netOffset = elementOffset.top - elementScrollTop;<br>  var expandPosition = $(&quot;.list-wrapper&quot;).offset();<br>  var expandTop = expandPosition.top;<br>  var expandLeft = expandPosition.left;<br>  var expandWidth = $(&quot;.list-wrapper&quot;).outerWidth();<br>  var expandHeight = $(&quot;.list-wrapper&quot;).outerHeight();</pre><pre>  $(&quot;.list-wrapper&quot;).css({<br>    top: netOffset,<br>    position: &quot;fixed&quot;,<br>    overflow: &quot;hidden&quot;,<br>    &quot;z-index&quot;: &quot;11&quot;<br>  });</pre><pre>  // convert the expand-item to fixed position without moving it<br>  elementToExpand.css({<br>    top: elementToExpand.offset().top - $(&quot;body&quot;).scrollTop(),<br>    left: elementToExpand.offset().left,<br>    height: elementToExpand.height(),<br>    width: elementToExpand.width(),<br>    &quot;max-width&quot;: expandWidth,<br>    position: &quot;fixed&quot;<br>  });</pre><pre>  // Changes height of banner<br>  var expandedHeight = elementToExpand.find(&quot;.banner&quot;).data(&quot;height-expanded&quot;);<br>  elementToExpand.find(&quot;.banner&quot;).animate({<br>      height: expandedHeight<br>    },<br>    expandingAnimationTiming,<br>    &quot;easeOutBack&quot;<br>  );</pre><pre>  // Changes position of content<br>  var expandedPosition = elementToExpand<br>    .find(&quot;.inner-content&quot;)<br>    .data(&quot;position-expanded&quot;);<br>  elementToExpand.find(&quot;.inner-content&quot;).animate({<br>      top: expandedPosition<br>    },<br>    expandingAnimationTiming,<br>    &quot;easeOutBack&quot;<br>  );</pre><pre>  // start expand-item animation to the expand wrapper<br>  // expand the element with class .about-tile-bg-image<br>  elementToExpand.animate({<br>      left: expandLeft,<br>      top: expandTop,<br>      height: expandHeight,<br>      width: expandWidth,<br>      &quot;max-width&quot;: expandWidth<br>    },<br>    400, // animation timing in millisecs<br>    &quot;easeOutBack&quot;, //animation easing<br>    function() {<br>      elementToExpand.css({<br>        right: 0,<br>        bottom: 0,<br>        width: &quot;auto&quot;,<br>        height: &quot;auto&quot;<br>      });</pre><pre>  elementToExpand.find(&quot;.banner-holder&quot;).css({<br>        position: &quot;fixed&quot;<br>      });<br>    }<br>  );<br>}</pre><p>I left some comments in the code but let me try to explain what is going on here:</p><ol><li>First we add a class .open to the card, this is important as we handle most things with CSS and that is our selector for when the card is open.</li><li>We prevent the body from being scrolled accidentally.</li><li>Next we set most of our variables and do some calculations. In those variables we get the positions and size of the wrapper that contains the cards, these values are going to be the rules for our cards to expand to.</li><li>We set the wrapper to be fixed so that our expanded card gets contained inside it.</li><li>Then we transform our card into a position fixed element but keeping it in its place.</li><li>We move the position of our content and increase the height of the banner.</li><li>Finally we animate to expand.</li></ol><p>Now we just need the collapse function that will basically reverse all the steps you see above.</p><pre>function collapseElement(collapseButton) {<br>  // find the element to collapse<br>  var elementToCollpseParent = collapseButton.parents(&quot;.card&quot;);<br>  var elementToCollpse = elementToCollpseParent.find(&quot;.card-content&quot;);</pre><pre>  // find the location of the placeholder<br>  var elementToCollpsePlaceholder = elementToCollpse.parents(&quot;.card&quot;);<br>  var elementToCollpsePlaceholderTop =<br>    elementToCollpsePlaceholder.offset().top - $(&quot;body&quot;).scrollTop();<br>  var elementToCollpsePlaceholderLeft = elementToCollpsePlaceholder.offset()<br>    .left;<br>  var elementToCollpsePlaceholderHeight = elementToCollpsePlaceholder.outerHeight();<br>  var elementToCollpsePlaceholderWidth = elementToCollpsePlaceholder.outerWidth();</pre><pre>  elementToCollpse.find(&quot;.banner-holder&quot;).css({<br>    position: &quot;absolute&quot;<br>  });</pre><pre>  // convert the width and height to numeric values<br>  elementToCollpse.css({<br>    right: &quot;auto&quot;,<br>    bottom: &quot;auto&quot;,<br>    width: elementToCollpse.outerWidth(),<br>    height: elementToCollpse.outerHeight()<br>  });</pre><pre>  $(&quot;.list-wrapper&quot;).css({<br>    top: 0,<br>    position: &quot;absolute&quot;,<br>    overflow: &quot;auto&quot;,<br>    &quot;z-index&quot;: &quot;1&quot;<br>  });</pre><pre>  // Changes height of banner<br>  var collapsedHeight = elementToCollpse.find(&quot;.banner&quot;).data(&quot;height&quot;);<br>  elementToCollpse.find(&quot;.banner&quot;).animate({<br>      height: collapsedHeight<br>    },<br>    collapsingAnimationTiming,<br>    &quot;linear&quot;<br>  );</pre><pre>  // Changes position of content<br>  var collapsedPosition = elementToCollpse<br>    .find(&quot;.inner-content&quot;)<br>    .data(&quot;position&quot;);<br>  elementToCollpse.find(&quot;.inner-content&quot;).animate({<br>      top: collapsedPosition<br>    },<br>    collapsingAnimationTiming,<br>    &quot;linear&quot;<br>  );</pre><pre>  elementToCollpse.animate({<br>    left: elementToCollpsePlaceholderLeft,<br>    top: elementToCollpsePlaceholderTop,<br>    height: elementToCollpsePlaceholderHeight,<br>    width: elementToCollpsePlaceholderWidth<br>  },<br>    200, // animation timing in millisecs<br>    &quot;linear&quot;, //animation easing<br>    function() {<br>      // Removes class &#39;open&#39;<br>      elementToCollpseParent.removeClass(&quot;open&quot;);</pre><pre>      elementToCollpse.css({<br>        position: &quot;relative&quot;,<br>        top: &quot;auto&quot;,<br>        left: &quot;auto&quot;,<br>        width: &quot;100%&quot;,<br>        height: &quot;100%&quot;<br>      });<br>    }<br>  );</pre><pre>  // Stops preventing &#39;body&#39; scroll<br>  $(&quot;body&quot;).removeClass(&quot;lock&quot;);<br>}</pre><p>One last detail that I haven’t mentioned is that I extended the jQuery default easing functions with a bounce effect when expanding the card. You can use jQuery UI to include a bunch of other easing functions, but for this example I just needed one so I used the following:</p><pre>/* Extends jQuery animate easing */<br>$.easing = Object.assign({}, $.easing, {<br>  easeOutBack: function(x, t, b, c, d, s) {<br>    if (s == undefined) s = 1.70158;<br>    return c * ((t = t / d - 1) * t * ((s + 1) * t + s) + 1) + b;<br>  }<br>});</pre><p>This way we can use easeOutBack in the easing parameter on the .animate() when expanding.</p><p>At this stage you should have something that looks and works like my example. I’ll leave you with a <em>pen</em> with everything we just talked about.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fhcarneiro%2Fembed%2Fpreview%2FYLNyZq%3Fheight%3D600%26slug-hash%3DYLNyZq%26default-tabs%3Dhtml%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Fhcarneiro%2Fpen%2FYLNyZq%2F&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F166082.YLNyZq.small.62aca63e-d315-4323-8c8b-c96013486d04.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/68e556bf691f2a9750e370a2721544a5/href">https://medium.com/media/68e556bf691f2a9750e370a2721544a5/href</a></iframe><p>That is it everyone! I hope you enjoy and make good use of it. Feel free to copy and change it to your needs.</p><p>Leave in comments your thoughts and your changes to it. Would love to see your talented work.</p><p>Until next time, keep on solving problems!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=261a3225724a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a custom selected list using Multiselect for Vue.js]]></title>
            <link>https://medium.com/@hugodesigns/how-to-use-the-most-complete-selecting-solution-for-vue-js-f991b2605364?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/f991b2605364</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Sun, 15 Apr 2018 18:06:41 GMT</pubDate>
            <atom:updated>2018-06-25T13:59:24.468Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><a href="https://github.com/shentao">Damian Dulisz</a> member of the <a href="https://vuejs.org/">Vue.js</a> team and the author of <a href="https://vue-multiselect.js.org/"><strong>Vue-Multiselect</strong></a><strong>, </strong>says that Vue-Multiselect is <em>“The most complete selecting solution for Vue.js”</em> and I have to agree with him.</p><p>Recently I had to create a feature for our product at <a href="https://fliplet.com/">Fliplet</a> that allow users to select resources to embed into their apps. Similar to how <a href="https://codepen.io/">CodePen</a> does it, the user can select from a list of predefined resources and/or type to search for resources that are delivered by <a href="https://cdnjs.com/">cdnjs.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDudS2WZXhATe1cZTAV6lg.png" /><figcaption>Vue-Multiselect example</figcaption></figure><p>Having that functionality in mind and also having in mind that our product is built using Vue.js, I went on a search for a select field component built for Vue.js <em>(I didn’t want to spend time building my own)</em> and I found quite a few, I tried a couple, until I tried Vue-Multiselect and I was amazed with the possibilities. You can <a href="https://vue-multiselect.js.org/">check the website</a>, but basically is a select field that allows single and multiple select, search, tags, and much more — believe me, it is really good. So today I decided to create a quick tutorial that takes that select field and with a bit of code we will create a custom list of selected resources loaded from cdnjs.com.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CLpR9K8IFDRtb0prEE625Q.png" /><figcaption>What we will be achieving</figcaption></figure><h3>Getting started</h3><p>First of all, I will assume you know your way around Vue.js and that you already have your environment set up and running with Vue.js.</p><p>You will need the following resources installed in your project:</p><ul><li>Vue.js</li><li>Vue-Multiselect</li><li>Vue-Resource</li><li>Font Awesome</li></ul><p><strong>Installing Vue.js </strong>— <a href="https://vuejs.org/v2/guide/installation.html">Link here</a><br>NPM is the recommended installation method, but feel free to install it using a different method.</p><pre>npm install vue --save</pre><p><strong>Installing Vue-Multiselect </strong>— <a href="https://vue-multiselect.js.org/#sub-getting-started">Link here</a><br>NPM is the recommended installation method, but feel free to install it using a different method.</p><pre>npm install vue-multiselect --save</pre><p><strong>Installing Vue-Resource </strong>— <a href="https://github.com/pagekit/vue-resource">Link here</a><br>NPM is the recommended installation method, but feel free to install it using a different method.</p><pre>npm install vue-resource --save</pre><p><strong>Installing Font Awesome </strong>— <a href="https://fontawesome.com/get-started">Link here</a><br>Download the files and add them to your project. This is optional, I’m including because I used in my example.</p><p>Now that you have all the components necessary for this tutorial let’s get going.</p><h3>Create the Vue component</h3><p>First we are going to set up Vue and include the Multiselect component.</p><p><strong>Vue</strong></p><pre>new Vue({<br>  components: {<br>    Multiselect: window.VueMultiselect.default<br>  },<br>  data: {<br>    options: [],<br>    optionsProxy: []<br>  }<br>}).$mount(‘#app’)</pre><p>Now the HTML, we will include the markup for the Multiselect select field.</p><p><strong>HTML</strong></p><pre>&lt;div id=&quot;app&quot;&gt;<br>  &lt;multiselect :options=&quot;options&quot; :value=&quot;optionsProxy&quot; placeholder=&quot;Search&quot;&gt;&lt;/multiselect&gt;<br>&lt;/div&gt;</pre><p>Above you can see that the Multiselect field has some <em>props</em> already. You can see the full list of available <em>props</em> in the documentation, but we will be adding more and I’ll explain what the new ones will do and why they are important.</p><p>For now let me explain the most important ones that are the following:</p><pre>&lt;multiselect :<strong>options</strong>=&quot;options&quot; :<strong>value</strong>=&quot;optionsProxy&quot;&gt;&lt;/multiselect&gt;</pre><ul><li><strong>options</strong> — This contains the array of items to display when the users click the select field</li><li><strong>value</strong> — This will contain the selected items in an array</li></ul><p>Now that you know the purpose of those two <em>props </em>let’s take a look at the Vue data <em>prop. </em>You can see we have defined two variables as empty arrays:</p><pre>&lt;multiselect :options=&quot;<strong>options</strong>&quot; :value=&quot;<strong>optionsProxy</strong>&quot;&gt;&lt;/multiselect&gt;</pre><pre>-----</pre><pre>data: {<br>  <strong>options</strong>: [],<br>  <strong>optionsProxy</strong>: []<br>}</pre><ul><li><strong>options</strong> — This must contain the array of items to display when users click the select field</li><li><strong>optionsProxy</strong> — This will be filled in with the items selected by the user</li></ul><p>Options shouldn’t be an empty array however in this tutorial we will be filling it with resources from cdnjs.com, so for now we will keep it empty.</p><p>If you have been following along you should now have something like this:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Fb1s9ufso%2F21%2Fembedded%2F&amp;src=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Fb1s9ufso%2Fembedded%2F&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=jsfiddle" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/dbad392fd752acc05ad9e38791a29bbe/href">https://medium.com/media/dbad392fd752acc05ad9e38791a29bbe/href</a></iframe><h3>Create the custom list used to display the selected resources</h3><p>One of the most valuable things of Multiselect is that the list of items can be an array of objects, and those objects can contain several keys that you can use to display data after the user selected one.</p><p>Let’s have a look at the markup of the list of selected resources.</p><pre>&lt;ul class=&quot;resources-list&quot;&gt;<br>  &lt;template v-for=&quot;(<strong>resource</strong>, index) in <strong>selectedResources</strong>&quot;&gt;<br>    &lt;li class=&quot;resource-item&quot; :data-index=&quot;index&quot;&gt;<br>      &lt;div class=&quot;resource-info&quot;&gt;<br>        &lt;div class=&quot;resource-title&quot; :id=&quot;index&quot;&gt;<br>          &lt;span&gt;{{ <strong>resource.name</strong> }}&lt;/span&gt;<br>          &lt;span class=&quot;version&quot;&gt;{{ <strong>resource.version</strong> }}&lt;/span&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;resource-description&quot;&gt;<br>          &lt;span&gt;{{ <strong>resource.description</strong> }}&lt;/span&gt;<br>        &lt;/div&gt;<br>        &lt;div class=&quot;resource-url&quot;&gt;<br>          &lt;a :href=&quot;<strong>resource.latest</strong>&quot; target=&quot;_blank&quot;&gt;{{ <strong>resource.latest</strong> }}&lt;/a&gt;<br>        &lt;/div&gt;<br>      &lt;/div&gt;<br>      &lt;div class=&quot;delete-controls&quot; v-on:click.prevent=&quot;<strong>removeDependency</strong>(index)&quot;&gt;<br>        &lt;i class=&quot;fa fa-times fa-fw&quot;&gt;&lt;/i&gt;<br>      &lt;/div&gt;<br>    &lt;/li&gt;<br>  &lt;/template&gt;<br>&lt;/ul&gt;</pre><p>Add this block of HTML inside the &lt;div id=&quot;app&quot;&gt; after the Multiselect markup.</p><ul><li>resource-name — This prints out the name of the resource</li><li>resource-description — This prints out the description of the resource</li><li>resource-version — This prints out the version of the resource</li><li>resource-latest — This prints out the URL of the resource</li><li>removeDependency — Run function to remove resource from list</li></ul><p>Here’s a bit of CSS as well to make that list look good:</p><pre>.resources-list {<br>  margin-top: 15px;<br>  padding: 0;<br>  list-style: none;<br>}</pre><pre>.resources-list li {<br>  display: flex;<br>  align-items: center;<br>  min-height: 50px;<br>  padding: 10px 40px 10px 0;<br>  border-bottom: 1px solid rgba(51, 51, 51, 0.1);<br>  position: relative;<br>}</pre><pre>.resources-list li:last-child {<br>  border-bottom: none;<br>}</pre><pre>.resources-list li .resource-title {<br>  font-size: 1em;<br>  color: #333;<br>}</pre><pre>.resources-list li .version {<br>  opacity: 0.7;<br>  margin-left: 5px;<br>  font-size: 75%;<br>}</pre><pre>.resources-list li .resource-description,<br>.resources-list li .resource-url {<br>  font-size: 0.8em;<br>  color: #999;<br>  margin-top: 5px;<br>}</pre><pre>.resources-list li .resource-url {<br>  margin-top: 0;<br>}</pre><pre>.resources-list li .resource-description:empty {<br>  display: none;<br>}</pre><pre>.resources-list li .delete-controls {<br>  position: absolute;<br>  right: 0;<br>  width: 40px;<br>  text-align: center;<br>  color: #999;<br>  cursor: pointer;<br>}</pre><pre>.resources-list li .delete-controls:hover,<br>.resources-list li .delete-controls:focus {<br>  color: red;<br>}</pre><p>Now that we have all the HTML and CSS in place you should have something like this:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Fb1s9ufso%2F18%2Fembedded%2F&amp;src=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Fb1s9ufso%2Fembedded%2F&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=jsfiddle" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/57d1519e26964c48766d0f4774f1d7e4/href">https://medium.com/media/57d1519e26964c48766d0f4774f1d7e4/href</a></iframe><h3>Update Multiselect with important <em>props</em></h3><p>We need to add a few more props to Multiselect to achieve what we want, so let give that a go:</p><pre>&lt;multiselect :options=&quot;options&quot; :value=&quot;optionsProxy&quot; <a href="http://twitter.com/input"><strong>@input</strong></a>=&quot;updateSelected&quot; <a href="http://twitter.com/search"><strong>@search</strong></a><strong>-change</strong>=&quot;searchQuery&quot; <strong>:multiple</strong>=&quot;true&quot; <strong>:searchable</strong>=&quot;true&quot; <strong>:close-on-select</strong>=&quot;true&quot; placeholder=&quot;Search&quot; <strong>:custom-label</strong>=&quot;customLabel&quot; <strong>:loading</strong>=&quot;showLoadingSpinner&quot;&gt;&lt;/multiselect&gt;</pre><ul><li><strong>@input</strong>— Runs a function, this is triggered when the user selects an item from the list</li><li><strong>@search-change</strong> — Runs a function, this is triggered when a user starts a search — This only works when searchable is active</li><li><strong>searchable</strong> — Accepts a <em>Boolean</em>, and makes the select field list searchable</li><li><strong>multiple</strong> — Accepts a <em>Boolean</em>, and allows users to select multiple items from the list</li><li><strong>close-on-select</strong> — Accepts a <em>Boolean</em>, and forces the list to close when the user selects an item — Use this is you want.</li><li><strong>custom-label</strong> — Templated string that will be rendered as an item in the list</li><li><strong>loading</strong> — Accepts a <em>Boolean</em>, and if true shows a loading spinner</li></ul><p>Now that you have updated your Multiselect and understand what we have added and what for, let’s update our Vue component.</p><h3>Update Vue component</h3><p><strong>Data</strong></p><p>Let’s start with the easiest things, let update our variables in the data <em>prop. </em>We will add two more:</p><pre>data: {<br>  options: [],<br>  optionsProxy: [],<br>  <strong>selectedResources</strong>: [],<br>  <strong>showLoadingSpinner</strong>: false<br>}</pre><ul><li><strong>selectedResources </strong>— This will be the array of selected items from the list</li><li><strong>showLoadingSpinner</strong> — This will trigger the loading spinner in the Multiselect</li></ul><p><strong>Methods</strong></p><p>Now lets add our event handlers. We will add 5 event handlers but we’ll be taking a look at them individually, but here’s the full list.</p><pre>methods: {<br>  <strong>customLabel</strong>(option) {<br>    return `${option.name} — ${option.version}`<br>  },<br>  <strong>updateSelected</strong>(value) {<br>    value.forEach((resource) =&gt; {<br>      // Adds selected resources to array<br>      this.selectedResources.push(resource)<br>    })<br>    // Clears selected array<br>    // This prevents the tags from being displayed<br>    this.optionsProxy = []<br>  },<br>  <strong>cdnRequest</strong>(value) {<br>    this.$http.get(`<a href="https://api.cdnjs.com/libraries?search=${value}&amp;fields=version,description`">https://api.cdnjs.com/libraries?search=${value}&amp;fields=version,description`</a>)<br>      .then((response) =&gt; {<br>        // get body data<br>        this.options = []<br>        response.body.results.forEach((object) =&gt; {<br>          this.options.push(object)<br>        })<br>        this.showLoadingSpinner = false<br>      }, (response) =&gt; {<br>        // error callback<br>      })<br>  },<br>  <strong>searchQuery</strong>(value) {<br>    this.showLoadingSpinner = true<br>    // GET<br>    this.cdnRequest(value)<br>  },<br>  <strong>removeDependency</strong>(index) {<br>    this.selectedResources.splice(index, 1)<br>  }<br>}</pre><p>Let’s get into every single one of the event handlers:</p><p><strong>Custom labels</strong></p><pre><strong>customLabel</strong>(option) {<br>  return `${option.name} — ${option.version}`<br>}</pre><p>This one will return the custom label to display in the list of the Multiselect, tweak it as you like. This example looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IySfjNlGvJSVBV5InG495A.png" /></figure><p><strong>Add to custom list</strong></p><pre><strong>updateSelected</strong>(value) {<br>  value.forEach((resource) =&gt; {<br>    // Adds selected resources to array<br>    this.selectedResources.push(resource)<br>  })</pre><pre>  // Clears selected array<br>  // This prevents the tags from being displayed<br>  this.optionsProxy = []<br>}</pre><p>This will be triggered every time the user selects a resource from the list. In this little function we add the selected item in value to the selectedResources array that was defined earlier.</p><pre>this.optionsProxy = []</pre><p>We then clear the optionsProxy array so that the selected item doesn’t stay visible in the Multiselect field as a tag. Feel free to comment this line to see how it looks in the UI.</p><p><strong>CDN JS request</strong></p><pre><strong>cdnRequest</strong>(value) {<br>  this.$http.get(`<a href="https://api.cdnjs.com/libraries?search=${value}&amp;fields=version,description`">https://api.cdnjs.com/libraries?search=${value}&amp;fields=version,description`</a>)<br>    .then((response) =&gt; {<br>      // get body data<br>      this.options = []</pre><pre>      response.body.results.forEach((object) =&gt; {<br>        this.options.push(object)<br>      })</pre><pre>      this.showLoadingSpinner = false<br>    }, (response) =&gt; {<br>      // error callback<br>    })<br>}</pre><p>In this function we do a request to cdnjs.com to retrieve a list of resources based on what the user typed.</p><p>For that we need to clear the existing list by this.options = [] and then we iterate each result and we add them to the list using a forEach() loop.</p><pre>response.body.results.forEach((object) =&gt; {<br>  this.options.push(object)<br>})</pre><p>We also disable the spinner with this.showLoadingSpinner = false</p><p>There’s also an error callback that you can use if you want to.</p><p><strong>Search list</strong></p><pre><strong>searchQuery</strong>(value) {<br>  this.showLoadingSpinner = true</pre><pre>  // GET<br>  this.cdnRequest(value)<br>}</pre><p>This function is triggered when the user searches in the Multiselect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*sfmnhJmhAmg3rHypsqRxpg.gif" /></figure><p>First we initialise the spinner, in case the search query takes some time, with this.showLoadingSpinner = true . Then we run the cdnRequest function that we had a look above, passing it the value the user typed.</p><p><strong>Remove resource from custom list</strong></p><pre><strong>removeDependency</strong>(index) {<br>  this.selectedResources.splice(index, 1)<br>}</pre><p>Lastly we create the function to remove resources from the custom list. This is run when the user clicks the cross in the UI that we have set in HTML.</p><pre>&lt;div class=&quot;delete-controls&quot; v-on:click.prevent=&quot;<strong>removeDependency</strong>(index)&quot;&gt;<br>  &lt;i class=&quot;fa fa-times fa-fw&quot;&gt;&lt;/i&gt;<br>&lt;/div&gt;</pre><p>When a user clicks the cross we take the index of the resource in the array and we remove it by this.selectedResources.splice(index, 1) .</p><h3>Populate list on load</h3><p>The last thing we need to do is to populate the list with resources when users load the page, for that we will use the created() lifecycle hook to query cdnjs.com with an empty string.</p><pre>created() {<br>  const value = &#39;&#39;<br>  this.cdnRequest(value)<br>}</pre><p>If you pass it an empty string it will return all the resources in cdnjs.com <em>(about 3000+)</em>, you can set a different default, you can even not query cdnjs.com and have your own static list. If you do that just remember that you need to add you list to this.options .</p><p>If you have been following along you should now have the following:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Frtogxe4s%2Fembed%2F&amp;src=https%3A%2F%2Fjsfiddle.net%2Fhugodesigns%2Frtogxe4s%2Fembedded%2F&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=jsfiddle" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/56190dbd64fd8c1f28f7e279fffaf975/href">https://medium.com/media/56190dbd64fd8c1f28f7e279fffaf975/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*hZ_LzFydFM90W8AaMS-6yg.gif" /></figure><h3>Conclusion</h3><p>As you can see, with a bit of coding you can create amazing interfaces using this little Vue component.</p><p>I hope you liked this tutorial, I had fun creating it, please leave in the comments how did you find it.</p><p>Until next time, keep on solving problems!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f991b2605364" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A fork in the road]]></title>
            <link>https://medium.com/@hugodesigns/a-fork-in-the-road-7cffa2c6462e?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cffa2c6462e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Sat, 14 Apr 2018 17:30:57 GMT</pubDate>
            <atom:updated>2018-04-14T17:33:50.565Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqD_daCWZ2SZZ4pIGm4WMA.jpeg" /></figure><p>If you are a designer who is also a developer, or a designer who has some skills as a developer, or vice versa, then you might have thought about or even faced the same dilemma that I am about to write about.</p><p>I consider myself a designer who is also a developer, front-end developer to be exact, and recently I have been taking some time to think about my career, and what should I do to improve to take the next step forward, however I have been faced with a dilemma — <strong>Which path should I take to continue further? Design or Development?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6jzEGtbMtOW4eoQJcDImQ.jpeg" /></figure><h3>Designer</h3><p>I have always loved design and being a designer, that is my background, I started as a graphic designer and throughout the years I have moved towards the digital design, from web to product design. I really like the problems that we designers have to overcome when creating a UI that needs to be used by different types of users with different skills. Focus on great UX, focus on solving a problem that will take the company you are working for to the next level is challenging and rewarding at the same time and I love that. I really enjoy having design discussions with my colleagues, find solutions together, I like that design is a cooperative effort to make things better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jZ2LJ9X2paxSkAGetKD9CA.jpeg" /></figure><h3>Developer</h3><p>With that said, I also really love the development part of the process, bring the designs into life. Tweak the interactions, the states, the animations, all of it. It is fun, rewarding and can impress people a little bit more than a static design. But developing is not smooth sail, there are also problems and challenges which I also love to solve. I have no background in math or engineering, so for me it is really challenging to achieve some crazy animations or more complex pieces of code, but gosh I love the challenge and I feel amazing when I finally get it the way I want it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*em-WnC8Go2HslZgGmuGhRg.jpeg" /></figure><h3>Making the decision</h3><p>So as you can probably see by now, I am divided between the two paths because I love them both for similar reasons. Both will keep me on my toes moving forward, on both I will need to keep learning and keep on par with new technologies and standards.</p><p>One important thing that I always kept in the back of my mind is that I aspire to become someone that is influential in the industry, someone that creates something that other designers or developer look up to, someone that helps younger designers or developers. When making these type of choices in your career it is very important to keep in mind your objectives. Your short term objectives but also your long term objectives.</p><p>You should always see your long term objectives and then work backwards to figure out what are you going to do to achieve them with other small and short term objectives. You should use the 666 roadmap rule, think about what you want to achieve in the next 6 years, and then backwards, to the next 6 months and the next 6 weeks. That will help you set a clear vision of what to do.</p><p>So to conclude, and to tell you what I have decided to do for now, I will keep being both, I still want to be a designer and a developer, and want to be great at both. It will be very challenging as I will need to keep on top of my game in two fronts, but I believe I can’t be happy being one without the other. Even though I wrote before that designer shouldn’t be developers (<a href="https://uxdesign.cc/should-designers-be-developers-too-a12e3b86fde9">read here</a>) I since then changed my mind and this is my decision.</p><p>You should think hard about what you want to achieve and what do you see yourself doing in 6 years, 6 months and 6 weeks. Have a clear idea of what’s to come on any of the paths and think if you are ready to go further with it.</p><p><em>I hope you enjoyed the quick post, it’s been a while since I last wrote.<br> Until next time, keep on solving problems!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cffa2c6462e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Graphic Designer to Product Designer]]></title>
            <link>https://uxdesign.cc/from-graphic-designer-to-product-designer-b706be4a2f07?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/b706be4a2f07</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Sat, 15 Apr 2017 10:31:01 GMT</pubDate>
            <atom:updated>2018-07-06T22:01:13.544Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gasTzoGGHw66ZInluQua7g.jpeg" /></figure><p>I’m sure that at least at one point in your life you stopped for a moment and looked back at where you started, as a professional, and what you have achieved so far. I had and still have a lot of those moments, they are good to reflect on everything good and bad, and make sure you don’t make the same mistakes again. That inspired me to write this article to tell you the story of my professional career, how I started as a graphic designer and moved to be a product designer.</p><p>I have always loved technology, art, design and architecture, so for me to choose a field when I was in school was very hard. At first I wanted to be an IT Engineer because of my love for computers and being really interested in learning about programming, even though at that point I had never written a single line of code, but that world fascinated me. Well, I was only an above average student at school, which meant that a lot of the disciplines I had to learn on my way to become an engineer were too much for me which led me to the artistic side, my second option.</p><p>During the last three years of secondary school my love for design grew exponentially. After secondary school I did not go to University, I just went for a one year professional course with another semester of internship part of the course. At this course I had my first contact with web programming, including technologies like HTML, CSS, PHP and ActionScript. Even though I loved learning how to program, how to build websites and web applications I was still more interested in graphic design, I truly believed and still believe that companies need to pay more attention to their image out there and I wanted to be a part of a world where I could help some companies get easily recognised and boost their levels of trustworthiness.</p><p>I started working for a small design agency in early 2009 in Portugal (where I’m from) and on my day to day basis I would design everything a business needs, from business cards to entirely new logos. We also created websites for those businesses, I would design them and build the HTML structure of the website, and another member of the team would integrate other technologies and build the rest of the functionality. I was a glorified graphic designer at that time. Makes me laugh now because nowadays it’s almost a given, that a designer should know the basics of front-end development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ygYE5vqqDbyFs8b3h9eG3Q.jpeg" /><figcaption>Designed by me: <a href="http://amais.pt/">http://amais.pt/</a></figcaption></figure><p>The more websites I created and observing how fast the web and smartphones were growing into our lives, I started to really getting into web design and started to feel a bigger love for the interaction design than the love for graphic design. Keep in mind that this was early 2009, many frameworks that we know today didn’t even exist. I was inexperienced, it was my first job, and everyone was still trying to figure out how to create beautiful, yet functional, websites.</p><p>There was something about designing and then turn that into a thing that people could “touch” and engage with at any time on their computers, that kept me invested and a passion for it started to grow. I was also that kind of kid that when I got a new toy I would spend a week playing with it, until I would eventually open it up to see how it was made and built, and sometimes even to see how it would work. Always have been very curious and that curiosity led me to want to know how websites worked and how they were built.</p><p>From here I started to pay more attention to what was out there, to websites and events that would award best design prizes to other websites, and try to figure it out on my own what makes that website a good website.</p><p>I must confess that the early years of my, still young, career were based on trying to figure out my style, and what makes a good website, completely ignoring UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdZ9L9RF2NKiwNhoHGezjg.jpeg" /></figure><p>A few years after starting my first job I decided to move to London in pursuit of a better career. I initially started working as a freelance designer, I did a few project, mostly websites, but still having some graphic design projects too. That was an interesting year and a half of my life, I learned that don’t be a freelance designer unless you really have a plan, which I didn’t, but in the interest of time I’m just going to say that if you want to be a freelance, keep in mind that you’ll need to be CEO, Designer, Developer, Customer Success and Sales team all at once, every single day. I found the experience very interesting, enlightening and I definitely learned new skills not only as professional, but as a person too.</p><p>After having one of those moments of reflection, trying to decide what to do next and what I wanted for my career, I decided to look for something challenging, something new to me, and something that could make a difference.</p><p>I joined<a href="http://fliplet.com/"> Fliplet</a> in 2014, just a couple of months after deciding not to be a freelance anymore. In the beginning I was a junior designer, I did a little bit of graphic design, but I was mostly working on the company’s new product. Fliplet Studio is the product, an enterprise app building platform.</p><p>Before joining Fliplet I had some notions of what good UX was, but was only after starting working at Fliplet that I really understood the importance of it, mainly because we our users would create apps with our product without needing to know how to code or design, the product had to be easy to use and understand, and above all keep users coming back to build even more apps.</p><p>So you must be thinking <em>“wait, he started his career in 2009 and only 5 years later he noticed how important UX was? What was he doing during that time?”.</em></p><p>Well, I like to think that those early years set the base for what I am today, were the years that the love for digital design grew, the years that made me passionate and care about what I do. That said, it made sense that the next step for me was to pay attention to the user experience with the things I designed and try to improve someone’s (professional) life with something I created.</p><p>With the help of my colleagues, and of course the processes we have for each project, I was becoming better at what I do, paying more attention to little details, started looking into app design, started understanding how people interact with apps and what was considered a standard in the eyes of the users. I must admit that in the beginning it was a bit difficult because I wasn’t used to have a process to follow, and I wasn’t definitely used to think too much about the user, I was only used to design pretty things that would look good on a screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nfm2tizmJ3jIuBgwSJAfEQ.png" /><figcaption>Fliplet Studio v2</figcaption></figure><p>My first major project at Fliplet was to design and create a theme, that ended up containing nine different layouts, this project took us roughly two months to complete, and I’m still proud of creating that theme, because after two years it’s the theme we were still using. Of course we have a lot more layouts now, hell, we even have a new version of the product now, but that initial set of layouts set the rules for the next to come and also for the look and feel of the apps produced by it.</p><p>After that theme was launched to the public we started working on new features. Working on features added a little bit more complexity to the process, because every feature have two sides of it — The one that the app creator interacts with when creating the app in the platform, and the app side, the side the end users will interact with. Building a feature it’s not just about making it look great, and position everything correctly for a great experience, is also about the wording, how you explain each option of the feature, the responsiveness of each action the user makes, and in the beginning was difficult to test this with real users because we were still small and we didn’t have many clients using the product.</p><p>So how did we get it right? You may ask. Well, we didn’t. We did research, we followed our process and we released it to the public, and only after feedback from clients we would change things when appropriate. Basically what I’m saying is that we learned from our own mistakes, but we didn’t shy way from releasing it anyway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO7ubGiaPNzHX1QKr-QYKw.jpeg" /></figure><p>We would always follow the same process — do research, sketch and wireframes ideas, design and prototyping, and at the end implementing in the system. This process still holds today on every project.<br>I must say that it is fundamental that you have a good work process for a project, otherwise you’ll end up wasting time and not deliver great features, websites or anything.</p><p>Of course that sometimes, and depending on the project, you can cut a few corners and shorten each process, but you must be completely certain you can do that, because some team colleagues must depend on that for them to be able to do their work properly.</p><p>I was becoming better at what I do, with a lot more knowledge about good UX design, and now fully engrossed by it.</p><p>I can’t thank enough the people in the team that helped and believed in me, and still do, because I feel I have never grown so much as professional in the first 5 years as I did in the past 3 years. It really is an awesome team.</p><p>As a Product Designer now, I have to come up with new ideas for the product, new way for our users to interact with, and experience the apps they create, and spark some internal discussions about new features. A designer’s job is not only to create beautiful things, it is also, and mainly, to solve problems, sometimes even problems that the user doesn’t know yet.</p><p>I was hungry for learning more, for creating experiences, for evolving as a professional. I still think graphic designers are very important for any business, but I wanted more than that, and I achieved some of my objectives by going down the route of becoming a product designer, where I can touch a lot more people with the product that I’m working on now. It’s never dull, always challenging, always fun. I’m happy to be a part of a team that helped users creating more than 2000 apps.</p><p>I hope you liked my story and I would love to read your stories. Respond to this article with your professional stories!</p><p>Until next time, keep on solving problems!</p><p><em>Like this? Please click the little heart and share with others.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b706be4a2f07" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/from-graphic-designer-to-product-designer-b706be4a2f07">From Graphic Designer to Product Designer</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get better at taking feedback]]></title>
            <link>https://medium.com/@hugodesigns/how-to-get-better-at-taking-feedback-5adaf0e1aafc?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/5adaf0e1aafc</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 09:02:01 GMT</pubDate>
            <atom:updated>2018-04-15T19:59:55.159Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CgeRmi2fhj5tJMoKhu1yFQ.png" /></figure><p>Hello everyone, today I want to talk about feedback. While looking for another interesting topic to write about I found out that How to give feedback is a well discussed topic everywhere. A lot of people want to get better at giving constructive criticism, but only a few really think about the feedback receiver.</p><p>As a product designer I think it’s very important to learn how to get better at taking feedback. What you are about to read will be more focused on my role as a product designer, but the tips can also be applied on different areas of work and even in your personal life.</p><p>You can get feedback in many different ways and it can mean many different things, however in a work environment you will most likely receive spontaneous feedback and expected feedback, but all feedback can be summarised in three different categories:</p><ul><li><strong>Appreciation</strong><br><em>When someone appreciates the work you have done or are doing</em></li><li><strong>Coaching</strong><br><em>When someone gives you constructive feedback for you to improve</em></li><li><strong>Evaluation</strong><br><em>When someone gives you feedback rating your work</em></li></ul><p>Spontaneous feedback, like the name suggests, is when someone gives you feedback without you asking or expecting that feedback at that point in time, as for the expected feedback — you guessed it — is feedback you asked for at some point and you are now receiving it. Ideally in these two different scenarios you should take the feedback the same way, but the truth is that you most likely won’t.</p><p>When you are expecting feedback from someone, because you asked for it or you have a meeting scheduled to discuss a certain piece of work, you will default to viewing that feedback as either coaching or evaluative. However, when the feedback is received spontaneously, as human beings we tend to default our mindset to see it as evaluative, even making it personal. Whether we are aware of it or not, we care about what people think about us, and when we do anything at work, we always put a part of us in it. Therefore, when receiving feedback, our minds start to analyse what the feedback say about us, hence making it personal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6qcuD92cKyjjmSvGzSkRg.jpeg" /></figure><h4>So how can we change our mindsets to take the feedback in these two scenarios without making it personal and actually get something out of it?</h4><p>The easy answer is to just stop thinking for one second and listen. Although one second sounds like nothing in real time, it actually is long enough for you to listen and default your mindset appropriately according to the situation.</p><p>Getting feedback is hard, even when you are expecting it, because you never know what the other person will say and your mind starts to race. That is bad. That will make you lose control and basically ignore all feedback or start interpreting the feedback in a different way.</p><p>Always try to remember the benefits of feedback. Namely, to improve your skills, product, relationships, and to help you meet the expectations that your manager and others have of you.<br>Don’t shut down immediately, there’s always something useful that you can take away.</p><p>For you to actually get better at taking feedback you need to be aware of these flaws. We all do it. We are only human beings, and as like with any other problems we first need to accept our mistakes and face them.</p><p>Now that you are aware that you shouldn’t be too quick to judge, you should listen to the person who is giving you feedback. Let him or her share his or her thoughts without interruption. After the person is done, take a few seconds to replay that information in your head to understand the information given and ask any questions you might have. But, keep in mind that giving feedback isn’t an easy job either. Recognise that the person might be nervous or may not express the ideas perfectly, so it is crucial that you understand what was said and that you make it clear to that person that you understood.</p><p>You should also try to deconstruct the feedback so that everything is clear, but avoid getting into a debate. Here are a few ways to deconstruct feedback:</p><ul><li>Seek specific examples</li><li>Acknowledge the feedback that is not in dispute</li><li>Try to understand more about it</li><li>Seek specific solutions to address the feedback</li></ul><p>When getting feedback you need to be patient. You need to respect the other person, and you need to have a growth mindset — meaning that you’ll see any feedback as an opportunity to grow as a professional and/or as a person.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PUlpXhEZL2W9eUckGQapmw.png" /></figure><h4>But what if a person keeps giving you feedback all the time: feedback that isn’t relevant anymore. What should you do then?</h4><p>It’s important that you notice these situations where you get feedback that is either inaccurate, for many reasons, or just because your work load doesn’t allow you to take more feedback in, because in these situation you should have a conversation with that person and explain why you don’t want or need more feedback at that point in time. If you think the feedback is useful but due to workload you can’t listen to it appropriately, ask the person to log it (Email, GitHub ticket, etc).</p><p>Be respectful but don’t be afraid to reject feedback if you see that there’s no use or you can’t handle it at the moment. If you decide to reject feedback or not taking any action after receiving feedback, always communicate your reasons to the person that gave you the feedback. Otherwise, they might feel underappreciated or if it was your manager or boss they might even think that you are not doing your job.</p><p>You all now have a better understanding on how to react when given feedback.</p><p>Stop to think. Always have the situation into consideration. Don’t be afraid to ask to clarify. Deconstruct the feedback given. And, always let the other people know what you intend to do with the feedback that they gave you.</p><p>I’m interested to hear your opinions and tips that you have from your own experience.</p><p>I hope you enjoyed the post, keep on solving problems!</p><p><em>Like this? Please click the little heart, share with others.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5adaf0e1aafc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should Designers be Developers too?]]></title>
            <link>https://uxdesign.cc/should-designers-be-developers-too-a12e3b86fde9?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/a12e3b86fde9</guid>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Fri, 06 Jan 2017 12:14:12 GMT</pubDate>
            <atom:updated>2017-02-26T17:09:04.481Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYHMK1dDTTx4ejNB0PCpSg.png" /></figure><p>Today I want to share my opinion on whether or not a designer should be a developer too!</p><p>Of course, I want to say yes.</p><p>However, it’s not as simple as that. A designer that knows how to develop (I’m just considering front-end development) is a valuable team member for the obvious reason that they can quickly jump between roles if needed.</p><p>In a startup or small agency, resources are scarce and being able to design and develop your own creations is a Godsend. I started as a junior designer at <a href="https://fliplet.com/">Fliplet</a> and was a developer too. Even now as a Product Designer, I’m still fixing small bugs and helping the developers by creating quick working prototypes. This brings me back to the question: Should a designer be a developer too?</p><p>I don’t think so. Let me explain why.</p><p>In my experience as a designer and a developer in a startup, I often develop a lot of the things I design. This means that I spend a lot of time on development too — time that could be spent designing other features, doing more user testing, or even better, coming up with better solutions to other problems.</p><p>If you work in a bigger team with more designers and developers, all the development should be passed along to a developer so that designers can focus on designing more features, fixing usability issues and many other things that always need to be improved in a product.</p><p>Having said this, the main reason why I don’t think a designer should be a developer is that designers who can develop will usually design according to what they know as developers which is limited to their development skills.</p><p>Even if you are an amazing front-end developer you will only be as good a designer as the skill you have as a developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*F3_FbVx-rqxqUag6vWSa6A.jpeg" /><figcaption>Frank Lloyd Wright, monitoring the construction and testing of load-bearing pylons for the Johnson Wax Building.</figcaption></figure><p>Imagine if an architect was an Engineer too. The houses wouldn’t be as interesting. As history tells us, the boldest buildings were designed by architects who challenged what engineers thought was possible. Designers need to do the same thing. You need to push things forward, be bolder and be creative!</p><p>Of course this doesn’t mean I believe designer’s should never learn how to develop. I do think a designer should be aware of the technologies and how things work. It’s a good skill to be able to create prototypes, but don’t let that take up too much of your time. If it’s possible, always send your work (and your prototypes) to a developer who can take good care of it.</p><p>A key takeaway from my experience: If you start developing your own creations, you will feel good about it! However, the increased knowledge you gain in development will hinder you from thinking creatively and innovatively about new designs, and you will end up limiting yourself.</p><p>I’m very interested to hear your opinions on this subject — or your own experience with it!</p><p>I hope you enjoyed the post, and keep on solving problems!</p><p><em>Like this? Please click the little heart, share with others, and move on to:</em></p><ul><li><a href="https://uxdesign.cc/what-makes-a-good-ux-designer-6959ab22f4e8#.1i0lukvm7">What makes a good UX Designer?</a> — Skills and good practices to have</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a12e3b86fde9" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/should-designers-be-developers-too-a12e3b86fde9">Should Designers be Developers too?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a good UX designer?]]></title>
            <link>https://uxdesign.cc/what-makes-a-good-ux-designer-6959ab22f4e8?source=rss-838fbb1dcd44------2</link>
            <guid isPermaLink="false">https://medium.com/p/6959ab22f4e8</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[articles]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hugo Carneiro]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 11:39:21 GMT</pubDate>
            <atom:updated>2019-05-22T23:54:54.615Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTAoh2jXTwue8wiu0803kA.jpeg" /></figure><p>Hi, I’m Hugo and I’m a Product Designer at <a href="http://fliplet.com/">Fliplet</a>.<br>Today I’m going to dive into what is to be a good UX designer. It will be my personal opinion based on my experience and what I learned throughout the years.</p><p>Great design and UX is as important as you leaving home with your wallet. So let’s start with the big question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5ej5NZHKx760aDbL15nHg.jpeg" /></figure><p><strong>What makes a good UX designer?</strong></p><p>For me the most important skill is understanding people.</p><p>Sounds simple right? Well… it’s not that simple, every person is unique, think differently therefore a good UX designer has to be good at managing users’ expectations. Use empathy to their advantage to understand the users’ needs and come up with a solution to a problem.</p><p>Being able to ask for, listen to and use feedback effectively is also a must have for any good UX designer. Always asking for feedback — on designs, after a project ends, when they work with people in other roles. Good UX designers are genuinely interested in how they can improve and become better. Don’t just collect the information and lock it away. Use it.</p><p>Take the time to think about the feedback you just received and act on it. Good UX designer will use the knowledge from that feedback in the future. It’s a role where you are constantly learning and growing as a professional.</p><p>That’s why I love it! I work at a startup in London and we have what we call <em>“Feature Friday”</em>, every two weeks the whole Fliplet team, all the departments, gather together and the product team, myself included, presents new ideas such as new layouts and news features, for the purpose of gathering feedback and spark internal discussions to take the product to the next level. I use these occasions to show different things, get other people to see it and interact with it, and get as many feedback as I can and also pay close attention on how people explain problems to me, this not only shows me how they think and what they were expecting, but also enables me to come up with a better solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO7ubGiaPNzHX1QKr-QYKw.jpeg" /></figure><p><strong>Have a process when designing something!</strong></p><p>There are 4 important steps that a UX designer should take when working on designing or redesigning a project:</p><ul><li>User Research</li><li>Design</li><li>Testing</li><li>Implementation</li></ul><p><strong>User research </strong>should be every UX designer’s starting point for a project. Research teaches us about the users, their behavior, goals, motivations, and needs. It also shows us how they currently use our product, where they come up against problems and, most importantly, how they feel when interacting with our product.</p><p>Being a good UX designer sometimes means putting your personal taste aside because what you think is intuitive might not work for your users, which is why doing research with the actual users is very important to the success of your designs. You should know that sometimes companies don’t really have a way to research with actual users, in this case base your decisions on research done by others.</p><p>Empathy is key here. Your job is to try to understand why users are behaving the way they are when engaging with your product, not to try to change that behavior or influence it, but accommodate it within the product.</p><p>As a beginner in UX design, it’s something that I’m still trying to master myself at every given opportunity.</p><p><strong>Designing</strong> a satisfying user experience involves meticulously planning a Customer Journey for the users and helping them find what they are looking for through an intuitive process.</p><blockquote><em>“Design is not just what it looks like and feels like. Design is how it works.”<br>- Steve Jobs</em></blockquote><p>The design of your product revolves around functionality and usability, rather than colours or pictures. Having established during your user research what your users expect from your product or site, what their goals are and how they like to operate a system, it is functionality and usability that always comes first.</p><p>Usually I like to start with some quick sketches so that I can show a flow to other colleagues and gather even more feedback.</p><p>Next I proceed to creating some wireframes that are intended to look at:</p><ul><li>the allocation of space on that page</li><li>the distribution of images and content</li><li>how content is prioritised</li><li>what functions are available</li><li>what behavior is intended and accommodated</li></ul><p>After having a visual representation including the results of the user research and feedback from your colleagues you should do a prototype of it. This allows UX designers to explore and experiment with ideas and feedback, as well as check functionality and usability. This is also a great stage to show the project to your colleagues and receive even more feedback, now that they can also explore and engage with your creation, which ties in with the next process.</p><p><strong>Testing</strong> is a fundamental part of the UX designer’s job and a core part of the overall UX design process. Giving your creation to others for testing it allows you to improve upon the original product design and to see if the changes you made during the “design” phase stand up to scrutiny. It’s a great way to eliminate problems or user difficulties that were unforeseen in the design phase before getting started on the implementation phase.</p><p>At Fliplet I like to get the people that have less involvement with the product to test. I always like to do testing with people that have similar skills of those from our clients.</p><p><strong>Implementation</strong> can vary from company to company. Some UX designers may have to implement the designs themselves due to small teams or budget constraints, fortunately for me, Fliplet has an awesome team of developers and I can leave the implementation of my designs to them and I’m confident they will take good care of it.</p><p>If you are in the same position as me, there is still one important step before you hand over the prototype or the designs to developers. You must create a document briefing the developers on what is expected, the functionality need and overall how things should work. This is very important because most developers might not be aware of the project goal, so it’s your job as the UX designer to let them know, so that they can do what they are great at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uNOvOde7r50sLw6bqm3kbg.jpeg" /></figure><p><strong>Seek inspiration from others and don’t be afraid of being vulnerable.</strong></p><p>Good UX designers approach problems collaboratively and not defensively, and they admit when they don’t know the answer or when they are wrong. In other words, they show vulnerability and they are honest about it. They ask questions to learn more and they take other people’s thoughts and opinions into consideration before gunning ahead. They look to developers, project managers and others for inspiration and ideas.</p><p>Cooperate and be humble. Your team will appreciate!</p><p>Still fight for what you believe in, but fight with an arsenal of humility. Don’t make bold claims and proclamations about what will happen, rather, draw others in and rally for the best possible outcome.</p><p>I hope you enjoyed this post on how to become a good UX designer.</p><p>Until next time, keep on solving problems!</p><p><a href="http://uxdesign.us5.list-manage1.com/subscribe?u=e6ed326be9b869e7dc97a6719&amp;id=44948c461b">UX Links</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6959ab22f4e8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-makes-a-good-ux-designer-6959ab22f4e8">What makes a good UX designer?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>