<?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 Marcos Trujillo on Medium]]></title>
        <description><![CDATA[Stories by Marcos Trujillo on Medium]]></description>
        <link>https://medium.com/@Aracem?source=rss-7981cb02e8d0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s16armGizsY5i5RkilDuTg.jpeg</url>
            <title>Stories by Marcos Trujillo on Medium</title>
            <link>https://medium.com/@Aracem?source=rss-7981cb02e8d0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:23:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Aracem/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[Working with a design system]]></title>
            <link>https://medium.com/jobandtalenteng/https-medium-com-aracem-working-with-a-design-system-f426be09c470?source=rss-7981cb02e8d0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f426be09c470</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marcos Trujillo]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 15:30:19 GMT</pubDate>
            <atom:updated>2019-05-07T13:34:33.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-OnyRsey5GvrLIPJxAfZw.jpeg" /><figcaption>Jobandtalent’s design system</figcaption></figure><p>In 2016 <a href="https://jobandtalent.com/">Jobandtalent</a> was a completely different company.</p><p>We were a <em>Job Board</em>, a site where companies post job openings and people apply to them waiting for an answer that could come from inside the platform, i.e. in a chat, or outside with the method that the companies prefer.</p><p>Back then, the product development cycle was the typical one that we have been familiar with in our careers.</p><h4>How we worked before a design system</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/0*1vM0-lbVmQX9eN_S" /><figcaption>Typical development cycle</figcaption></figure><p>After a phase of ideation and research, some wireframing with feedback from the technical team, the designers would open <em>their preferred design tool</em> and give to the developers a fancy and cool design.</p><p>Developers tried to figure out how to decompose the design into views that could be reused and develop them.</p><p>But, is this decomposition easy for developers?</p><h4>And then the change</h4><p>In the summer of 2016, Jobandtalent decided to pivot the product.</p><p>Why stop at the posting job phase? Why not handle the entire work cycle, from the job search to paying salaries?</p><p>Imagine the challenge. All the teams were involved, a totally new product scope, a lot of new features, and a new look and feel for the app to represent the new concept correctly. We needed to improve these key points:</p><ul><li>Coordination</li><li>Parallelization</li><li>Consistency</li><li>Anticipation</li><li>Speed</li></ul><p>After thinking about how to improve them we come up with…</p><h4>Design System, applying Atomic Design</h4><blockquote>“A design system is a collection of reusable components, guided by clear standards, that can be assembled together to build any number of applications” Will Fanguy</blockquote><p>The design team proposed a solution to improve how we work at Jobandtalent, to start using a Design system: <strong>Atomic design</strong>. The best way to understand what Atomic Designis, is by checking out this gif:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*g0xKezA6_HyIqUk3" /><figcaption>Atomic design in a gif</figcaption></figure><p>Reducing the design to small components, or<strong> atoms</strong>, that could be composed to form bigger ones, or <strong>molecules</strong>, and finally combined all together to form structures or <strong>organisms</strong>. Design as a developer (I apologize to my fellow designers).</p><p>Composition, abstraction, encapsulation, polymorphism…<br>For more information about atomic design <a href="http://atomicdesign.bradfrost.com/chapter-2/">check out this blog post</a> and <a href="https://jobandtalent.design/holistic-design-for-companies-and-candidates-35c94585f84a">Jobandtalent’s design team vision</a>.</p><p>With atomic design developers and designers have a common point of view. New screens could be built with components already developed and the UI could be built in a modular fashion, like <a href="https://www.youtube.com/watch?v=3_q8O8xQnlQ">Lego</a>, and these screens are designed with the same philosophy:<br>Coordination, consistency, speed.</p><h4>Our Components Library</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*RP2f8dAGTrldFQCA" /><figcaption>Jobandtalent android Components Library sample app</figcaption></figure><p>The Components library is a project in wich we built the Jobandtalent atomic design.</p><p>It is a <strong>separated artifact</strong> from the Jobandtalent’s app, published in a <strong>maven </strong>repository that can be <strong>deployed locally or remotely</strong>.</p><p>We can add a new component or make a modification that produces changes that break the components library and/or the app and work with a local deploy of the library without interrupting our teammates.</p><p>It is <strong>versioned</strong>, to ensure controlled changes with low friction in the app and fewer merge problems. A new version requires a PR in the app only including the changes required for that version. This leads to a low level problems due to changes.</p><h4>Custom views</h4><p>Each atom, molecule or organism is built as a <strong>Custom View</strong>. Using custom views instead of plain layout XMLs helps us to easily compose views and makes developing the UI for the new features much easier.</p><p>It also forces us to standardize how the custom views are developed with strong rules that all the team should follow. First, the structure is similar for all the custom views, all sharing a similar API. Naming conventions for setting up, parameters, listeners…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zT2NGuNlz84QumpggHd1FQ.png" /><figcaption>Consistency between components</figcaption></figure><p>All the views have an inner data class <em>ViewState </em>that encapsulates the render information <strong>independent from the business logic</strong>. It’s very important define it as a library not as an app’s custom view . <strong>We use generic names for the data</strong>.</p><p>A view has a title and a description, never a <em>userName</em> or <em>jobDescription</em> even though the view will only be used with users or jobs in the app. Thinking agnostically help to make the library more composable effortlessly. It is also more predictable even for a new team member has no experience with it.</p><p>In summary, 1 component 1 custom view, standardization, more standardization, render logic 👍, business logic 🙅‍.</p><p><a href="https://jobandtalent.engineering/the-power-of-mixins-in-swift-f9013254c503">The power of mixins in Swift</a></p><h4>Sample App</h4><p>One of the best things about of having the components library is the <strong>Sample App</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*NLaXN03bwX2JFUre" /></figure><p>We have a sample of each component in separated activities where we can check how they look and see an example of how to integrate them. Designers and managers can check the components on their phones.</p><p>Also, developing the components in a separated small app with really fast build times (less than 6 seconds without instant run) is really a pro feature.</p><p>The app isn’t only a group of custom views, there is an IconKit representation, color kit representation, all the text styles, and <em>the playground</em><strong><em>.</em></strong></p><p>The playground is a place where we can develop with all the components and tools that we have in the library however complex the view or screen that we have to develop for the app. This has a big benefit in compilation time and development speed.</p><h4>And we don’t forget testing</h4><p>Of course, we don’t forget the testing side of thing. Our library is composed of two modules, one with the design system and another with a set of <em>matchers, actions, and assertions </em>to test all the components.</p><p>All the custom views examples have UI tests to check the integrity of the components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*puYwtdQ3s-dC-eLlShazBA.png" /><figcaption>TallCellViewMatcher example</figcaption></figure><h4>Success example</h4><p>As I commented at the beginning of this post the objective of using the design system and the components library was to improve how we work in Jobandtalent but this wasn’t the only success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*hnMb7fK_iYVU4IZqiEGxPg.png" /><figcaption>Changing the app colors</figcaption></figure><p>During this past two years, we changed the colors of the app a number of times and the font family once. These changes would have been extremely hard to implement without the components library, the design system and the sample app.</p><p>Before using them we postponed the decision to change the font family several times due to the difficulty of changing it in an app with more than 5 years of code. Checking the accuracy of the change in tens of screens and use cases requires a lot of time investment.</p><p>But with the design system, the change is localized and much less difficult. Design team members could check the visual result in real devices with the sample app and fix possible errors or make improvements before changing the app.</p><p>And this is only one example!</p><h4>The Components Library Story</h4><p>Are you interested in knowing what steps we took to build the components library and the reasons for those decisions? Check out the slides of my talk ‘<a href="https://www.slideshare.net/MarcosTrujilloSeoane/working-with-a-design-system"><strong>Working with a design system</strong></a><strong>’</strong>.</p><p>My friends <a href="https://medium.com/u/11fcfb2d5448">Victor Baro</a> and <a href="https://medium.com/u/cb539e52d35a">Jorge Rodriguez</a> wrote about the components libraries from a technical point of view in <a href="https://jobandtalent.engineering/visualkit-ui-framework-74ab8aae0d42">iOS</a> and <a href="https://jobandtalent.engineering/learning-to-develop-jobandtalents-design-system-for-android-54160a571d7b">Android</a>.</p><h4>We are hiring!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//twitter.com/jobandtalenteng/status/1125743791196049409&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/7171964a0e0f5cd8313526de1e33393f/href">https://medium.com/media/7171964a0e0f5cd8313526de1e33393f/href</a></iframe><p>If you want to know more about how is work at Jobandtalent you can read the first impressions of some of our teammates on this<a href="https://jobandtalent.engineering/our-first-impressions-working-at-jobandtalent-part-1-991a48eac2a4"> blog post</a> or visit our<a href="https://twitter.com/jobandtalentEng"> twitter</a>.</p><p><em>The components library is the work of a lot of people that worked at Jobandtalent. Thank you all </em>❤️!<br><em>Thanks </em><a href="https://twitter.com/sefford"><em>Saúl</em></a><em>, </em><a href="https://twitter.com/john_mclachlan"><em>John</em></a><em>, </em><a href="https://twitter.com/edpascua"><em>Eduardo</em></a><em>, </em><a href="https://twitter.com/durbon"><em>Chema</em></a><em>, </em><a href="https://twitter.com/luisrecuenco"><em>Luís</em></a><em>, and </em><a href="https://twitter.com/spejman"><em>Sergio</em></a><em> for reviewing this post!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f426be09c470" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jobandtalenteng/https-medium-com-aracem-working-with-a-design-system-f426be09c470">Working with a design system</a> was originally published in <a href="https://medium.com/jobandtalenteng">Job&amp;Talent Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>