<?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 Jan Van Echelpoel on Medium]]></title>
        <description><![CDATA[Stories by Jan Van Echelpoel on Medium]]></description>
        <link>https://medium.com/@echlpl?source=rss-e667bacefbad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Y3IMR3kxUILZpF4F7DACKw.jpeg</url>
            <title>Stories by Jan Van Echelpoel on Medium</title>
            <link>https://medium.com/@echlpl?source=rss-e667bacefbad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:10:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@echlpl/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[Say hello to Beatswitch 2.0]]></title>
            <link>https://medium.com/beatswitch/say-hello-to-beatswitch-2-0-89436bad3be2?source=rss-e667bacefbad------2</link>
            <guid isPermaLink="false">https://medium.com/p/89436bad3be2</guid>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[festivals]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jan Van Echelpoel]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 12:05:00 GMT</pubDate>
            <atom:updated>2019-03-05T12:05:00.295Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introducing our newly revamped interface 💅</h4><p>Recently we launched a beta version of our new interface, as we started updating our branding about a year ago. We loved our old interface that lasted four years and many of our clients felt at home logging into Beatswitch but we felt it was time for a change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_ffxb2XLKMOPmL3TEMMbw.png" /><figcaption>Shiny new booking overview screen ✨</figcaption></figure><p>First of all, it’s no change for the sake of change. Without boring you with too many technical details, we had a fair amount of legacy code in our software which caused some pages to visually appear very different from our newer ones, with inconsistency and confusion amongst our users as a result.</p><p>We knew this wasn’t ideal and by introducing our renewed production website which also came with an all-new design in begin 2018, we now had (too) many visual differences across all of Beatswitch’s platform. They were all pretty good, but not very cohesive. So we finally decided to make our visual identity future-proof and consistent across our platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgSMylt-y9Uer4s4N1CTHQ.png" /><figcaption>The new production website which we launched in begin 2018</figcaption></figure><h4>Consistency is key 🔑</h4><p>Beatswitch’s web app consists of a lot of views where we need input from our users. Some of the forms on these views are very complex and are a real challenge to implement in a user-friendly way. Consistency is a crucial keyword here as we need our platform to offer the same level of user experience across all our views. Logically, we also have a lot of views where users need to see an overview of their data. Accessing this data should be as simple as possible. So doing this redesign we took the opportunity to question and improve some of our user interface components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o8tgiwHdcD4xmv40sgZ1YQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ng_u6mJMjH8UmGGGRGwHsA.png" /><figcaption>Out with the old and in with the new</figcaption></figure><p>An example of one of these components that didn’t provide an optimal user experience is expendable rows. We decided to replace them with <em>drawers</em>, a modal-like component that slides onto the page to provide the user with additional information. The information is displayed vertically inside the drawer, causing it to be visually structured and clear, in contrast to expendable rows where showing the additional information felt very busy and packed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ExqQPjOemaBLr3s6tLT-hA.png" /><figcaption>Our new drawer component</figcaption></figure><h4>Design systems to the rescue</h4><p>It became clear that besides a new look and feel (with a strong focus on UX) we also needed more systematic ways to keep up with the demand for new functionalities by our clients and general maintenance needed on our platform. To achieve this, we decided we need to build a design system. Such a system could help us to:</p><ul><li>Align foundations of our design language</li><li>Streamline user experience processes</li><li>Create a scalable and repeatable UI language</li><li>Achieve faster product development</li><li>Maintain consistency</li></ul><p>We started by laying out the foundations of what will become our new system, namely the colors and typography used in our branding, to create a basic style guide. With such a guide in hand, we were now able to build a component library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yKSFS1wgbsRdoftuvToyRg.png" /><figcaption>Extract of the color palette in our style guide, based on <a href="https://refactoringui.com/previews/building-your-color-palette/">this article</a> by Refactoring UI</figcaption></figure><p>We’re not going to dive any further into the (technical) details of how we built our design system — that’s perhaps a great topic for another blog post — but you can always take a peek at our component library/UI Kit at <a href="https://beatswitch.design/">www.beatswitch.design</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6qfffL1EnYWTlXtNgDsDw.png" /><figcaption>Some of the newly designed input components in our UI Kit</figcaption></figure><h4>Conclusion</h4><p>We faced many challenges like backward compatibility across our different codebases when implementing this new interface/design system, but we feel like it’s a huge leap forward. As product design is never done, we now have a future-proof system in place that can easily evolve and keep up with the fast pace of software development. This was something that was needed to be done, and we’re very glad we did. We sincerely hope it brings more joy to our clients using Beatswitch and that it makes the lives of all of those organizing these amazing festivals a little easier.</p><p>Thanks for reading!</p><p><em>Over the coming days and weeks we’ll be sharing more of our new interface on our </em><a href="https://dribbble.com/beatswitch"><em>dribbble</em></a><em> page, so make sure to follow us there.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89436bad3be2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beatswitch/say-hello-to-beatswitch-2-0-89436bad3be2">Say hello to Beatswitch 2.0</a> was originally published in <a href="https://medium.com/beatswitch">Beatswitch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>