<?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 Devexperts on Medium]]></title>
        <description><![CDATA[Stories by Devexperts on Medium]]></description>
        <link>https://medium.com/@Devexperts?source=rss-d60e6d2867d5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ZXnQnJiizm7y_Lr5OPpR6w.png</url>
            <title>Stories by Devexperts on Medium</title>
            <link>https://medium.com/@Devexperts?source=rss-d60e6d2867d5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:30:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Devexperts/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[The Winning Hand: Institutional Crypto Trading Solutions]]></title>
            <link>https://medium.com/devexperts/the-winning-hand-institutional-crypto-trading-solutions-fc6447ec4d87?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc6447ec4d87</guid>
            <category><![CDATA[cryptocurrency-exchange]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[cryptocurrency-investment]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Thu, 13 May 2021 16:04:55 GMT</pubDate>
            <atom:updated>2021-05-24T10:44:21.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FR0vGAq8d64xKZXcL8hTuw.jpeg" /></figure><h3>Zombies vs Goblins</h3><p>The beginnings of the crypto market are unlike any other asset class: the first clients weren’t institutions but retail. The initial exchange solutions weren’t built upon financial grade technology, agreed standards, security, testing and experience gained from other financial markets.</p><p>In fact, one of the most famous original exchanges started out as something completely different. At its peak, it was the world’s largest Bitcoin exchange in terms of market share, handling over 70% of the world’s BTC transactions. A year later, in 2014 the exchange was filling for bankruptcy.</p><p>That exchange was Mt. Gox, but it didn’t start out as a crypto exchange. The name actually stands for “<strong>M</strong>agic: <strong>T</strong>he <strong>G</strong>athering <strong>O</strong>nline e<strong>X</strong>change’’. It was originally built by a programmer as an exchange platform for trading fantasy virtual playing cards, like these:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*DAGWMP3riAegJ3QCgSxqZg@2x.png" /><figcaption>Source: Magic: The Gathering Arena</figcaption></figure><p>The fantasy card trading exchange didn’t really take off and was closed down, but the domain was kept. A few years later the developer came across Bitcoin and realised people needed a place where they could exchange the cryptocurrency. He repurposed the website, adapted the exchange software, and stuck with the same name and domain — Mt. Gox.</p><p>The Mt. Gox exchange became wildly popular, but it was too much for the creator to manage. Ultimately, the exchange was sold to someone who was better equipped to continue expanding its reach.</p><p>The technical and security requirements needed to build an exchange for transacting wizards, zombies and goblins are much less sophisticated than those needed for trading financial instruments. These discrepancies led to constant issues for Mt. Gox, including database leaks, security breaches, theft, fraud and transaction delays — more or less the exact things in which mainstream financial exchanges invest a lot of resources to avoid.</p><p>Despite all these challenges, however, Mt. Gox continued to grow and was processing over 70% of the world’s bitcoin transactions at its peak. That was until 2014 when it was hacked again and “lost” 850,000 Bitcoins, which was 7% of all Bitcoins that existed then. That many Bitcoins would be worth over 50 billion USD at the highs we’ve seen so far in 2021. The full story of Mt. Gox is very complex and the bankruptcy case along with the investigations are still ongoing.</p><p>This history of the original technology behind crypto exchanges is similar across some of the other early exchanges. They were built by techies who had successfully created crypto exchanges, but didn’t necessarily have experience building robust platforms for financial markets. Key considerations like execution methods, standards, and APIs had been reinvented or in some cases skipped.</p><h3>Enter the Wizards</h3><p>The crypto market needed major reform before institutions would be able to take up trading. Even with enormous interest in this new asset class, no sane risk department, at any respectable financial institution, would ever let their trading desks touch crypto without having at least some basic familiarities to the traditional financial markets model.</p><p>When we talk about institutional firms, we broadly cover:</p><ul><li>Investment banks, brokers &amp; FCMs</li><li>Market makers and LPs</li><li>Mutual, pension and hedge funds</li><li>Insurance firms, endowments and other asset managers</li><li>Proprietary trading firms, High-frequency trading firms (HFT), algorithmic trading firms, and professional traders</li></ul><p>Technology is just one of the areas that differentiates the market for institutional clients. The lines among the different cryptocurrency industry providers are increasingly blurred between retail and institutional.</p><h3>The Winning Hand</h3><p>Let’s take a look at the important items for institutions to keep in mind when getting into the crypto space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*97a4FTkKhk6rJH_scmJu-w@2x.png" /></figure><h3>Protocols</h3><p>Most crypto exchanges started out with just a UI and added APIs later on. These were their own protocols built from scratch. Protocols need to be straightforward for an institution to integrate into an exchange or OTC market maker. They have to be nimble and quick to offer seamless integration, given changes in liquidity. Ideally, the protocol is something institutions are well versed in, such as FIX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*NVOXTKjqKP-hdnqGDGDpQQ@2x.png" /></figure><h3>Hedging</h3><p>Institutions will never allow their trading desks to go into an asset unhedged. This changed after CME launched Bitcoin futures in 2017 and options in 2020. This also allowed firms to have exposure without some of the issues that come with spot crypto. There are also OTC forwards and options coming to the market, though, they do have some issues that are still being worked out as it’s difficult to have an agreed market price.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*NRCCo2QAADqF4xdSpmq55g@2x.png" /></figure><h3>Custody and Settlement</h3><p>Given the risks that come with holding crypto in wallets or directly on a hard drive, the recent increase in firms offering insured and secured crypto custody has really helped institutional firms get more comfortable in this area. In addition to securing assets on and off line, the firms have also become trusted third parties for settlement assistance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*7X0ablaxvEskG6uQuz50xQ@2x.png" /></figure><h3>Liquidity</h3><p>Institutions want to know that they can easily enter the market and close their positions when needed without causing the price to change. Exchange volumes are still comparatively small to traditional markets. That said, the rise of OTC market makers and brokers makes it cheaper to trade and liquidity continues to grow. Liquidity creates more liquidity</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*8l7EP5k8AlSL-A7jTorp4g@2x.png" /></figure><h3>Regulation</h3><p>Institutional firms need to stay in line with the rules set out by the regulator. In a market that is in its infancy and evolving rapidly, so too is the regulation. While many regulators have allowed crypto trading, rules continue to change and terms are not yet in line with other asset classes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*a_jyjHqaiFsi00aj8s6dLQ@2x.png" /></figure><h3>Enhanced Security</h3><p>Security weaknesses at some of the original exchanges have spooked institutions. Firms need to trust that assets are secure on the platforms on which trades are executed. This covers a vast area from network security through to multi factor authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*1pjoe1hbo2bL9DBAYTI0wQ@2x.png" /></figure><h3>KYC</h3><p>Institutional firms need to rest assured the counterparties they’re executing against have gone through the proper level of KYC procedures, ensuring they fall in line with regulation and settlement risks are minimized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*2q0_zF00R64AAAAFlCgSpw@2x.png" /></figure><h3>Technology</h3><p>Institutional firms want to trade on technology they’re used to and that offers high availability, disaster recovery, low latency and high throughput. They require technology that’s been used in other markets and has been thoroughly tested. Firms also need seamless APIs and intuitive UIs that work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*9DgMYGGNSZG0w4BNBmZe2g@2x.png" /></figure><h3>Reliable Data Feeds</h3><p>The crypto market is highly volatile and fast-paced, which often leads to off market pricing. It’s important to have protection against spikes and stale quotes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*_3KAM0ySlaXpT1JB8xPGUQ.png" /></figure><h3>Conclusion</h3><p>This hand of cards is by no means a full house for institutions right now. Much reform and development is needed to help onboard financial institutions. We’ll likely see a lot more ongoing improvements in the space, turning what was originally a retail-dominated pastime into a full-fledged institutional market. That may not be what Bitcoin’s creator had envisaged, but it certainly seems to be the way things are headed.</p><p>To learn more about Devexperts’ crypto trading solutions for financial institutions, please <a href="https://devexperts.com/contact-us/">get in touch</a>. Our platform solutions support exchange and OTC trading across multiple instrument types.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc6447ec4d87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devexperts/the-winning-hand-institutional-crypto-trading-solutions-fc6447ec4d87">The Winning Hand: Institutional Crypto Trading Solutions</a> was originally published in <a href="https://medium.com/devexperts">Devexperts</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 Build a Mobile Trading App]]></title>
            <link>https://medium.com/devexperts/how-to-build-a-mobile-trading-app-1f1153822f7f?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f1153822f7f</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[trading-software]]></category>
            <category><![CDATA[mobile-software]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 12:19:35 GMT</pubDate>
            <atom:updated>2019-08-02T12:28:55.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="developing a mobile trading app" src="https://cdn-images-1.medium.com/max/1024/1*jM7uQkfhywFs8puUniO8IQ.png" /></figure><h3>Our 4 Keystones of Mobile App Development</h3><p>It’s safe to say we’ve done it all: our financial mobile development experience started from software for the now outdated BlackBerry and Pocket PC, alongside mobile web, which included time-worn WAP, and then we transitioned to iOS and Android development, settling on them for now. Here we will reflect upon these experiences which shaped our four keystones of mobile development and brought our software to the top of its game.</p><h3>1st Keystone: Code Reuse and its Perks</h3><p>Today, most mobile apps are available on multiple platforms, challenging developers and compelling them to cut the amount of codebases. The less codebases we have, the cheaper and faster it is to support the whole solution and update it with new functions. We want to reuse one general code as much as possible.</p><figure><img alt="Trading software for PocketPC" src="https://cdn-images-1.medium.com/max/1024/1*lfXoiVmLmbVqPviBlTEN6Q.png" /><figcaption>Trading software for PocketPC</figcaption></figure><p>One of the most popular answers to this challenge is having one codebase and adapting it with a cross-platform UI engine. There are two common methods for accomplishing this goal.</p><p>The first one is developing a hybrid app. In this method, base material for a “native” application is a website’s mobile version, which is inserted into a platform native framework to imitate the native code. There are dozens of hybrid frameworks available, the most notable ones are PhoneGap, Ionic, Framework 7, and Mobile Angular UI.</p><figure><img alt="hybrid frameworks" src="https://cdn-images-1.medium.com/max/489/1*Oust72H3QucTNqAaL-dcOw.png" /></figure><p>The second method is to use full-fledged cross-platform frameworks, such as React Native, Xamarin, and Flutter. Such frameworks are more native than those used in the first method, each of them requires a code in a specific language (JavaScript, C#, Dart, etc.) inserted into a framework that generates a real native code for supported mobile platforms.</p><figure><img alt="cross-platform frameworks" src="https://cdn-images-1.medium.com/max/537/1*25Z22Px8zo9rfoPJpDgwHg.png" /></figure><p>Unfortunately, these methods for reusing code have several common issues specific to the technology, and we had a chance to see them for ourselves, because at some point in the past we have created our own similar framework. We don’t use it now, but it gave us a better insight into frameworks from the developer’s side.</p><p>The stumbling point when using frameworks is a drastic difference in visual and behavioral aspects of mobile platforms: design languages, navigation (e.g. back button in Android and lack of it in iOS), interaction, and animation. Applying them makes applications look unfamiliar and broken. These frameworks give us very slow, unstable and hard to support results due to required integration with a native code. A lot of large popular complex applications were written with them, but eventually they ended up developing native UIs. A great case in point is Airbnb, which advocated for React Native from 2016 till 2018. It worked fine for them but in reality a small percentage of their app was React Native, and eventually they <a href="https://medium.com/airbnb-engineering/sunsetting-react-native-1868ba28e30a">realized</a> that they “wound up supporting code on three platforms instead of two and were ultimately unable to meet their original goals, having a number of technical and organizational challenges” that they were unable to overcome.</p><p>Another method used in mobile development is a thin client. Here we minimize client’s logic, but in most cases UI reaction speed becomes suboptimal, because every input goes to a server, and UI reacts only after a network response. This process makes interactions very slow and unresponsive, leading to very poor user experience with an impression of a lagging application. At best, it is inconvenient, and at worst, an application could be unusable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s_8cQMzUW3w3YDJp8TMmgg.png" /></figure><p>At some point, we researched ways to reuse the code without the methods described above, because we faced the challenge of making a mobile version of one of our desktop products, and these ways could not cope with the task. That’s how we came up with the idea of code translation without reusing UI, the part responsible for the platform’s specifics. Instead, we apply translation to the code responsible for logic, taking the best from both approaches presented above. We used to apply our own in-house solution dxByte. It solved a basic task of translating Java code to be Objective-C suitable for the further use without additional adjustments. Our translator may seem to be just a kludge, but we are not the only company that came up with such a solution. Now we use, as some other companies do, Google’s solution j2Objc, which was published in 2012 and became very powerful through the years. Now it’s a tool with almost full JRE inside, 1.8 Java language level support, default methods, and stream API. The current version stands in stark contrast to its first almost unusable release. Modern code translation tools open ways to use more complex models. Who could have ever imagined that someday we would be able to translate a desktop program codebase and reuse it in a mobile application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYNnWkbpya-Doyr_y6RoSg.png" /><figcaption>Initial desktop application and the result of its code reuse for mobile platforms</figcaption></figure><p>Lots of software developers actively seek solutions for code reuse among platforms, and there are definitely other approaches besides j2Objc and cross-platform frameworks. After Kotlin became overwhelmingly popular, especially in mobile development, its authors from JetBrains went even further by proposing a Kotlin/Native instrument, which applies modern language code to a server-side, mobile app, and web. This kind of technology is not perfect yet — it has some adverse beginnings, but there is a great chance that soon enough they will be adequately stable for a wider audience.</p><h3>Considering all methods of cross-platform development, we advocate for reusing the code as much as possible via code translation and multi-platform languages, keeping in mind that all kinds of hybrid approaches do not work in the long run for high quality apps.</h3><p>If you aim for a complex quality app, it is more likely that sooner or later you will have to rewrite it with a native code, as Airbnb recently concluded. To be fair, some global companies still manage their development processes with these approaches, but they are an exception rather than a rule.</p><p>In the mobile world, there is a competition defined by user requirements and needs. Mobile apps must be familiar, easy-to-use, and responsive: users prefer working with comfortable behaviour patterns and with the speed of response that matches the speed of actions, which brings us to the next keystone.</p><h3>2nd Keystone: Networking in Mobile Development — We Need to Find the Right Solution</h3><p>Networking is a tricky issue due to frequently slow and unreliable connections to servers. In the perfect world of mobile networking, an app sends a request to a remote service and gets a response — it is as simple as that. In the real world, an app makes several request attempts to a remote service, and often not all of these attempts are successful. So when it comes to working on interactions with a server, a majority of developers choose either the easiest and most direct solution, or some industry standard. It’s not always for the better, particularly when an application works with a stream of rapidly changing data (market data, to be precise). It is critical for an application to display data updates quickly and often. Moreover, it’s unacceptable for an application with dynamic data to display a message “Please try again” when the loading of data is interrupted, which is quite common in the mobile world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_E6AAllThCUQhkHHPfKmQ.png" /></figure><p>In our scope, these challenges are very real, and we need to be responsible for them. If we analyze a particular use case and data set, we can learn to transfer them cost-effectively or to make connectivity breaks invisible to a user. Moreover, we want to make responsible transport code for solutions of these issues, and the code of the application itself would work at the level of “send data — receive data” without manually solving each case. We haven’t considered text protocols as a transport method because we opt for speedy and frequent deliveries. So we developed our own transport framework MOBTR. It is a binary protocol that considers all known specifics of our data. We were able to optimize work with the network exactly for our special case currently used in the development of trading frontends.</p><figure><img alt="MOBTR framework" src="https://cdn-images-1.medium.com/max/1024/1*P-ANj_jIkfAoI2_C3BRDnw.png" /></figure><p>Our solution doesn’t necessarily suit everybody and doesn’t have to be in demand by everybody. It’s about conducting such analysis and choosing relevant instruments.</p><p>Optimization of data traffic helps a lot in terms of slow and unstable connections. We suggest optimizing this process by transferring only delta of numbers (obtained through subtraction). Trading apps are convenient in that line. Quotes don’t drastically change, usually only one or two of their decimals do, so subtraction works perfectly for optimization, because we need to transfer smaller values.</p><p>Optimizing data transfer for mobile is not a one-fits-all approach. In case of frequent data updates, go binary. If you need more performance, go data aware, find a way to minimize the transferred values. In case of specific requirements, go custom and develop or adapt a transport framework according to them.</p><p>There are two great examples of messengers that used different approaches: Telegram and Whatsapp. Whatsapp chose a usual way for startups: it was developed to work with a standard protocol, and its performance is close to none, when the connection is weak. Telegram is faster, because it has its own binary protocol specific for its data that performs well in bad network conditions.</p><h3>3d Keystone: Staying on a Bleeding Edge</h3><p>Things tend to change. Devices change a lot, and they do it fast. Today mobile phones can do what computers couldn’t 10 years ago, and smartwatches can do what phones couldn’t 5 years ago. Staying on the bleeding edge with such speedy changes is hard, and some choose the wrong way to act (or fail to act at all). Here are two dud approaches, if you don’t want to keep ahead of the game.</p><ol><li>Keeping things old school. It’s easy and stable, which makes it almost impossible to go wrong, except you get no evolution at all. Development teams utilizing this method produce apps with zero response to environment and no room for growth. On top of that, they spend more time on maintenance than anyone in the industry.</li><li>Being modern and using all the frameworks on GitHub! You will spend a nice long time making it all work together, managing your dependencies, and optimizing the binary size.</li></ol><p>Before doing all that, just watch The Silver Bullet Syndrome by Hadi Hariri to make things easier. Spoiler alert: there is no silver bullet in software development, but there are approaches that will make things work in terms of staying on the bleeding edge:</p><ol><li>Don’t drag your feet. Somebody will outrun you and make it better and faster.</li><li>Don’t rush. We can drown in latest trends, and it will make the code more complex, and its development will be harder. At the same time these modernization efforts don’t pay off.</li></ol><p>What should we do? We need to find a balance. We need to track what’s going on with the technology and experiment accordingly.</p><p>We also need to introduce something modern to our solutions only when we have answers to the following questions:</p><ul><li>What does it bring to this particular project?</li><li>What will it cost us?</li></ul><p>A common mistake is to search for solution in an instrument. In most cases, it is not about programming language and not an item in a library (although it happens sometimes), but in the code itself, its architecture</p><p>Gradually we actualize the code by applying everything that can be useful. At the same time we move evolutionary, not revolutionary: we’re not rushing to rewrite all applications to a new language from scratch as soon as it starts getting popular.</p><p>For example, we use the latest versions of j2objc, Swift, and Kotlin in our work, where it’s relevant and doesn’t ruin everything. Meanwhile we rewrote our transport protocol MOBTR and saved all good ideas of an old version that are still relevant. Years of feedback converted our framework into a better tool, yet it stays a cross-platform mobile data transport framework, it is still aimed at mobile development, and it is still an efficient, compact, and ready-to-use solution. This is one more lesson we’ve learned through our mobile development experience: aim for evolution, not revolution. Do not rush, do not drag, most often the tool is not the problem, the code is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Go2Q_BhwjoSbMyH3oOUxQw.png" /><figcaption>Award-winning UI developed by Devexperts</figcaption></figure><h3>4th Keystone: No F5 in Mobile Development</h3><p>It’s an important feature of mobile development that is usually omitted. In web development, you can change the code, then refresh a page, and a client will get the newest version.</p><p>It doesn’t work this way with mobile applications. There is no physical possibility to remove the code of an installed application. You can forbid an application to connect to your server, but it’s beyond the borderline of developers’ decency. That’s why we need to understand that the written client code can live a long life and we must develop its best version possible.</p><p>What should we do? We should pay particular attention to client-side code and think about backward compatibility.</p><p>Down the line, our years of mobile development have shaped four keystones that optimize it to the max:</p><ul><li>Reusing code as much as possible</li><li>Analyzing the transmitted data and finding a suitable solution</li><li>Avoiding going too slow and breaking the speed of light at the same time</li><li>There is no F5 in mobile: once written, the client-side code is here to stay</li></ul><p><strong>How do you deal with the code reuse challenges? <br>What methods of cross-platform development do you deem fit for financial software?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f1153822f7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devexperts/how-to-build-a-mobile-trading-app-1f1153822f7f">How to Build a Mobile Trading App</a> was originally published in <a href="https://medium.com/devexperts">Devexperts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is a Market Screener the Missing Feature for your Business?]]></title>
            <link>https://medium.com/devexperts/is-a-market-screener-the-missing-feature-for-your-business-55891e60c2ff?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/55891e60c2ff</guid>
            <category><![CDATA[stock-market]]></category>
            <category><![CDATA[stock-trading]]></category>
            <category><![CDATA[market-screener]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 10:42:14 GMT</pubDate>
            <atom:updated>2019-07-11T10:42:14.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cis4QmBpe75fTjVcI6iO3g.png" /><figcaption>B2B use cases for three types of clients: brokerages, stock trading courses, and financial media</figcaption></figure><p>A market screener is the technical analysis tool for minimizing the task of narrowing down relevant data to help your customers make more precise decisions. Market screeners are available to financial institutions as an out-of-the-box solution, as SaaS with the capacity for easy integration with native Java and universal REST APIs for brokerages, stock trading courses, and financial media outlets.</p><h3>An Added Value Service for Brokerages:</h3><p>Brokerages can offer market screeners as a tool for traders to create customizable alerts and rating systems. By using a market screener as part of a brokerage’s service, traders can receive notifications from within their own criteria and metrics, then seamlessly transition a trader onto the brokerage’s platform to double check their analysis and charts against the trading book and make the trade.</p><p>Filters can be totally customizable, and users may create searches and alerts by integrating intuitive scripting languages — an easy to use algorithmic method of monitoring all your favorite criteria and indicators, saving huge amounts of time and increasing the accuracy of the analysis.</p><p>Brokerages can easily add new unique features to their trading or analysis software. Market screeners can be customized and integrated into any trading platform or a web page. It delivers strong competitive advantages without the need for costly development, licenses and hardware investments.</p><p>Let’s say an investor is looking to invest in the retail market according to the following criteria:</p><ul><li>P/E less than Retail Industry Median</li><li>EV/EBITDA 12 Months-Most Recent less than Retail-Industry Median</li><li>P/S less than Retail-Industry Median</li><li>Current Price greater than or equal to $5</li></ul><p>For the found set of stocks, if a user is looking for a buying opportunity, the following can be done:</p><p>Using embedded filters for Technical analysis, the user looks for stocks with RSI below 40. If he is not very satisfied and wants to make the request more precise, he can switch to the code editor and implement his idea:</p><p><em>Fetch stocks with daily volume around 100k for which the RSI(14) has been decreasing for a 3</em> <em>day-period that ended 2 days ago, increasing for the last 2 days and is below 40. Sort it by market capitalization.</em></p><p>by using the following code in a scripting language:</p><pre>def avgVol = avg(volume, 30); // calculate average 30 days volume<br>filter 90000 &lt; avgVol &amp;&amp; avgVol &lt; 110000; // fetch stocks with average volume around 100k<br>def rsi = RSI(n=14); // 14 days RSI // calculate RSI(14)<br>filter isDecreasing(rsi, 3)[2] &amp;&amp; isIncreasing (rsi, 2) &amp;&amp; rsi &lt; 40; // set parameters for RSI (14)<br>sort marketCap; // sort by market capitalization<br>set limit = 50; // take top 50</pre><p>He gets a small number of stocks which match his precise criteria. He clicks on tickers to see charts for them and if the radar tool is integrated with the trading platform of a broker he can further open a chart in his trading platform for a better appearance.</p><h3>Educational Platforms can Offer Traders a Unique Educational Experience:</h3><p>A Market Screener can be used by educational platforms to teach traders how to make decisions or find entry and exit points. As well, prospective traders will be able to find instruments with very high potential for growth or decline, and select instruments that fall into multiple criteria that no one else can select; instruments that combine fundamental and technical analysis, with historical performance.</p><p>An educational platform is able to integrate their own unique infrastructure or platform and customize it to suit their needs. Traders are able to test strategies on historical market data. With a scripting language feature, educational platforms can create incrementally advanced programs and scenarios as well as offer niche and specific training on isolated metrics and criteria.</p><p>Educational companies can teach students how to select certain criteria to achieve their desired result and prove their investment strategies.</p><h3>Financial Media will know more and offer more:</h3><p>A market screener offers additional value for their readers. It can be offered as a free service, a pro-subscription, or both. This allows the media outlet to offer additional features and services to keep readers coming back. A fully customizable market screener can act as a unique tool for readers to further educate themselves with concrete data, with the option of offering a more advanced pro-subscription tool.</p><p>A Financial Media outlet can support its news or market analysis departments to help generate more up-to-date content. Copywriters and market analysts can be alerted quickly to market changes by honing in on particular market instruments with an extensive array of metrics and use a scripting language for narrowed analysis thereby being able to offer more timely and accurate news for their readers.</p><p>To illustrate the benefits for financial media, think of how news today is consumed, as opposed to 7–10 years ago.</p><p>Nowadays, everything is moving online, including newspapers, making it worthwhile for the editors to invest more money in their news web portal. Before that, in a printed magazine that was issued in the early mornings, the quotes of most popular indexes were printed, and thus static. Now, these quotes are live and constantly being updated on financial news websites.</p><p>As well, many media outlets request that their readers be registered and logged users. An online news source can learn what a specific user is interested in and adjust the displayed quotes on the website according to the requests they’ve entered into a market screener that has been integrated into their services.</p><p>Not only will the quotes become targeted, but also news articles, e.g. if the user is consistently interested in the oil sector (because that’s what he requests in the market scanner), he will be shown articles about the oil and gas sector, selected among thousands of other articles published daily in a popular online news source. That will make the reader feel more informed and individually approached. In other words, the filters set by a user in an integrated market scanner is an opportunity for news outlets to offer individual user experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55891e60c2ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devexperts/is-a-market-screener-the-missing-feature-for-your-business-55891e60c2ff">Is a Market Screener the Missing Feature for your Business?</a> was originally published in <a href="https://medium.com/devexperts">Devexperts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatbots: The New Tool in a Trader’s Toolbox]]></title>
            <link>https://medium.com/devexperts/chatbots-the-new-tool-in-a-traders-toolbox-f19d51bd9f2f?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f19d51bd9f2f</guid>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[trading]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 10:46:49 GMT</pubDate>
            <atom:updated>2019-03-18T10:46:49.780Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AD0QLIflQp5dKmSZPsRLlg.png" /><figcaption>Chatbots offer a new way for brokerage firms to engage clients, creating well-informed buyers.</figcaption></figure><p>Time is money, money talks and now, when it does, its voice is automated. Chatbots are not just for lazily skipping through songs on your favorite playlist anymore.</p><p>“Okay, Google — Hey! OKAY GOOGLE! How will chatbots revolutionize the way brokerage firms assist their clients?”</p><p><strong>Now playing </strong><em>Revolution </em><strong>by</strong><em> </em><strong>The Beatles</strong></p><p>Chatbots are not perfect, but they have come a long way from the annoying little paper clip in the corner of your Word doc. As a brokerage, it is not your job to discover the next stage of bot evolution, but to listen when it arrives.</p><p>Chatbots are one of the most underutilized resources of the modern brokerage firm. This is not to say that brokerages have been ignoring the technology entirely. However, a chatbot left alone will rust. In order to use this technology to its fullest, bots require updating.</p><p>As it stands, chatbots can provide support to banks and brokerage firms to answer customer questions or provide guidance. This guidance is not only valuable for the client, but also trackable in order to create more conversions, personalized sales approaches, and predict market sentiment.</p><p>With an administration panel, a chatbot makes it possible to broadcast messages with a call to action to all users, or to a selected group of users, who for example were interested in trading Altcoins on specific terms.</p><p>In addition, chatbots can gather information which is easily transferable in order to construct ideal landing pages for conversions.</p><p>Chatbots have been an exceptionally cost-effective channel for brokers to reach, engage, increase retention rate, and convert their clients into actual buyers. Chatbots can handle customer complaints and provide responses to almost any question you’ll find in an FAQ. But, Chatbots can always — and must always — adapt and improve.</p><p><strong>“</strong>HEY SIRI!<strong> </strong>How are chatbots evolving in order to create new paths for brokerage firms to fit their client’s individual needs?”</p><p><strong>Now playing </strong><em>Money, Money, Money</em> <strong>by ABBA</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*DaoVFsAHwQQ86ZMxrPuNog.png" /><figcaption>Chatbots can provide support to banks and brokerage firms to answer customer questions or provide guidance.</figcaption></figure><p>It is essential to always be on the look-out for new ways to advance our relationship with this technology and any successful brokerage knows the importance of successful relationships. What they may not yet know is that these relationships are no longer restricted to person-to-person. Fostering a relationship with a chatbot won’t lead to heartbreak. Unlike a neglectful lover, a chatbot will remember you forever, learn your needs, and learn patterns in your behavior to bring you the missing piece in your crucial moment of need.</p><p>As a chatbot learns and grows, it will personalize itself to you. If something you’ve been interested in has become too volatile, a chatbot can inform you based on trends in your conversation, saving you time by providing you with the information you need at critical times.</p><p>For example, you ask your chatbot to tell you the price of Bitcoin against the USD. Ten minutes later, you ask again. Three minutes after that, you ask a third time.</p><p>Your chatbot knows you’re interested in Bitcoin. It gets it, you can stop now.</p><p>A fourth time, five minutes later, you ask: “What is the price of Bitcoin against the USD?”</p><p>Now, using the data gathered from your past conversations the chatbot can give you all of the information you need as well as retain the information from all users interested in Bitcoin. This allows the chatbot to not only know the market but also understand where it is going based on the sentiment of tens of thousands of traders around the world.</p><p>You now have an automated, well informed financial advisor, so what is next?</p><p>As a trader, one must balance numbers, headlines, social trends, and their own intuition on the edge of a golden knife. Markets are rapidly changing and decisions must be made with matching speed. Time is money, to the trader more than most.</p><p>Imagine a brokerage where you are able to provide each trader with a personal assistant, powered by natural language processing (NLP) and voice user interfaces. An assistant that never forgets, has a calculus degree from MIT, and every market in the world whispering in their ear.</p><p>The voice at the forefront of technology speaks in code.</p><p>Are you ready to listen?</p><p>“Alexa, what is the future looking like for chatbots in brokerages?”</p><p><strong>Now playing </strong><em>You Get What You Give</em> <strong>by the New Radicals.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/114/1*7j7Kr_f6tq7QHEKmKdwLlw.jpeg" /></figure><p><em>by Evgeny Sorokin,</em></p><p><em>SVP of Software Engineering at </em><a href="https://devexperts.com"><em>Devexperts</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f19d51bd9f2f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devexperts/chatbots-the-new-tool-in-a-traders-toolbox-f19d51bd9f2f">Chatbots: The New Tool in a Trader’s Toolbox</a> was originally published in <a href="https://medium.com/devexperts">Devexperts</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 Use Chatbots in the Online Trading Industry]]></title>
            <link>https://medium.com/chat-bots/how-to-use-chatbots-in-the-online-trading-industry-4fa7870fb3ea?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fa7870fb3ea</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[economics]]></category>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Fri, 30 Mar 2018 15:56:01 GMT</pubDate>
            <atom:updated>2018-03-30T17:09:43.635Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>How interactive agents with AI capabilities can help brokers to convert, activate and engage traders.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVtIPmezZjGn3HOxn6vLfQ.png" /></figure><p>Financial companies are known to be mostly conservative, and currently their chatbots tend to offer semi-automated support services and basic information related to the account of the user, such as statements. Brokerage firms move slowly and typically limit their offerings to stock prices or general information about the markets.</p><p>Despite frequent talk of innovation by participants in the retail finance space, in reality these channels are often explored with precaution.</p><p>Chatbots, in fact, have not had disrupted their business yet. Indeed, many brokers <a href="https://www.financemagnates.com/forex/bloggers/chatbots-marketing-forex-trading/">played with chatbots</a> after Facebook F8 in 2016. Most of these chatbots are dead. Even if they are not, the basic functionality of those that are still in operation makes it seem clear that their owners did not advance the project go further than the time-boxed proof-of-concept phase. Being marketing machines, such brokers shouted one more time about how they are always at the forefront of technology before they stopped paying much attention to the ongoing evolution of chatbots’ domain. A recent <a href="https://financefeeds.com/hong-kong-brokers-reluctant-deploy-chatbots-survey-shows/">survey</a> shows that 81% of Hong Kong brokers do not plan to introduce a chatbot.</p><p>It is not the fault of technology that brokers’ chatbots didn’t take off. After all, what would you expect from low-value chatbots which are limited only to delivering market quotes to the traders?</p><h3>Why Stock, FX and Crypto Brokerages May Want a Chatbot</h3><p>Nowadays brokers’ chatbots typically offer real-time quotes, generic FAQ, account statements, information about trader’s positions and notifications about sharp price moves or margin calls. Most companies stop here. While useful, this is far from being a game changer.</p><p>Chatbots have much more potential. Conversational UIs, powered by even the most basic machine learning algorithms, perform much better than emails, blog posts and FAQ pages. The key point is data about your prospects and personalization: in contrast to one-way communication channels, chatbots can learn more about their users, by analyzing all conversations held, and adapt.</p><h3><strong>Functions of Chatbots</strong></h3><h4>Support</h4><p>More and more banks and brokers are deploying chatbots to reduce the costs of customer support and sales. Many questions are typical and frequently asked, and canned responses with a touch of natural language processing (NLP) tools can significantly reduce the number of incidents, which require actual human interaction.</p><p>For example, chatbot can handle a typical <em>“Where is my withdrawal?”</em> inquiry by checking the status in a CRM and providing a response like<em> “Your request #123 to withdraw 275 GBP is being processed. We expect the money to be sent today; however in certain cases we may need to review your request further which may result in a delay of up to 3 days”</em>. Even though the processing involved has been fairly superficial, it gives the satisfaction and arguably maintains almost the same quality level as if such a request was handled by a human customer support representative.</p><p>Quick access to simple operations via a messenger with a chatbot on the backend helps to relieve the support staff from tedious activities and let them concentrate on more complicated issues. Also it could be a real delighter for traders to do things on the go without the need to open a trading platform: close all positions, check the unrealized P&amp;L etc.</p><h4>Convert</h4><p>Most people prefer to engage with programs that are human-like, and this gives chatbot-style techniques a potentially useful role in interactive systems that need to elicit information from users, as long as that information is relatively straightforward and falls into predictable categories. Bot can qualify leads: collect information from visitors, auto-assign conversations, and create leads in Salesforce. After following up any queries a trader may have, they analyze aggregated queries and send out relevant appeals, news or opportunities.</p><p>For example, if a trader requests the price of Litecoin, a logical step could be a personalized offer to open an account: <em>“George, you recently asked me about Litecoin. Would you like to trade Litecoin, Bitcoin, Ether and 100+ more cryptocurrencies on our new multi-asset trading platform? Click here to find out more”</em>.</p><p>Another example is to throw a question or a series of questions followed by an offer, e.g.: <em>“Hi Amy, we’re doing a survey on what traders use most, fundamental vs. technical analysis. Hope you don’t mind if I ask you just one question — which one do you prefer?” then, after words of gratitude: “John Doe, our expert in the energy futures market is conducting a free webinar on advanced technical analysis this Wednesday. Would you like to attend? It starts at 20:00 GMT”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*Et0_pzVkKhwdULs1iF9AOQ.jpeg" /></figure><p>Chatbots certainly should be integrated with a brokerage’s CRM, trading platform and back office systems to bring the trader closer and motivate them.</p><p>Personalization ultimately produces higher conversion and activation rates.</p><h4>Engage</h4><p>Chatbots give the ability to start small talk or engage in casual conversations between customers and businesses without human interaction. The sky’s the limit for engagement techniques: fine-tuned news feed, unique educational or entertainment content, games, contests, personalized memes, polls, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*nwN1I_BGbscFCFM9d1Rbyw.jpeg" /></figure><p>Bot can send performance insight to inform the trader if he made it into the top-10 list of progressive traders according to this chatbot statistics, or if he was more profitable than X% of other broker’s traders.</p><h4>Sell</h4><p>Chatbots have the ability to initiate and close sales, where a sale equals the placement of an order or a deposit. Let’s investigate such scenarios.</p><p>The user sets an alert, for example, <em>“Notify me when a Bitcoin is less than $7000”</em>. If this event occurs, the chatbot notifies the user adding a call to action <em>“Would you like to trade the Bitcoin now?”</em> In other words, any interest of the user to a financial instrument is followed by a call to action which facilitates a transaction.</p><p>A second scenario illustrates how chatbots help discover new opportunities. For example, a trader may ask, <em>“What are the top performing US stocks in the past 3 months?”</em>, the chatbot would then find such stocks and show them with an executive summary helping the user to make a trading decision.</p><p>In a third use case, being connected to a trading platform, the chatbot can analyze the trader’s exposure to the market and warn of potential threats, for example,<em> “The U.S. Nonfarm Payrolls are out today at 13:30 GMT, which may cause significant volatility. Would you like to manage your positions now?”</em></p><p>Chatbot can be smart. If it knows the user’s deposit history, open positions and margin requirements, it can make calls-to-action more targeted: <em>“Your equity is $1040.34. Should EUR/USD drop more than 100 pips, your position “#123 Buy 1 lot EUR/USD @ 1.12345” will be liquidated. Would you like to top up your account to avoid this? The suggested amount is $450”</em>.</p><p>In addition, it can broadcast general messages to a wider audience: <em>“Federal Reserve Governor speaks at 3:15pm EST, don’t forget to top up your account!”</em></p><h3>Conclusion</h3><p>Sophisticated chatbots break new ground in conversion and activation of prospects into sales. Being a diligent conversational partner this AI remembers the history of the dialog and is continuously self-learning. Thus a chatbot can connect with a user on a more intimate level, it has the ability to get under a traders’ skin by adding value that improves their day-to-day lives. However, only a chatbot with a well-designed architecture and advanced functionality can enrich a company’s communications. Chatbots still remain an underrated channel these days among brokerages, it is a good time to explore whether your business may need one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/171/1*keFBhhoE288ULG-WsSWflg.jpeg" /></figure><p><em>by Evgeny Sorokin, Head of R&amp;D at </em><a href="http://devexperts.com"><em>Devexperts</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fblue-sea-697d.quartiers047.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fblue-sea-697d.quartiers047.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%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/c90883b0516ddbe5c59960c12a04bc64/href">https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*QsdjZrMVeuaIJuyaqvsrWg.gif" /><figcaption>👏👏Clap below to recommend this article to others👏👏</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fa7870fb3ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chat-bots/how-to-use-chatbots-in-the-online-trading-industry-4fa7870fb3ea">How to Use Chatbots in the Online Trading Industry</a> was originally published in <a href="https://medium.com/chat-bots">Chatbots Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2018 UI Trends in Financial Software Development]]></title>
            <link>https://medium.com/@Devexperts/2017-ui-trends-in-financial-software-development-3ce2aeb66e4?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ce2aeb66e4</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 09:52:24 GMT</pubDate>
            <atom:updated>2019-07-29T12:35:07.804Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Specialists in every field like to share their opinions on the current and upcoming trends and we’re no exception. In this article we elaborate on </em><strong><em>2018 UI design trends</em></strong><em> and the impact they have </em><strong><em>in financial software development</em></strong><em>. The trends are illustrated with some great mock-ups from our portfolio.</em></p><h3><strong>1. Semi Flat Design</strong></h3><p>Starting from semi flat we hit the mark because it’s our main focus. Some new trends are a <strong>“blast from the past”</strong> and we’re sure they won’t live long. Some of them we’ve been using since the dawn of time. And some new trends have no use in our work so we’ve retained only those which are effective for us. But semi flat is a good starting point in UI of financial trading platforms, where we can provide good illustrations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KvaDrWF-7ZJ48_YtuJb0pg.png" /></figure><p>Graphics hardware and CPU are more powerful today. We’ve moved away from flat colors because of information overload during trading activities. Now shadows are big enough to help distinguish several information layers, to show an object’s dominance over others by emphasizing it with another color or shadow. This is how the user sees the screen now: a new layer is visually above and doesn’t fade into other layers or a background, so they can understand what to look at first.</p><p>Semi-flat is definitely not new to us as we’ve always been using it. Flat design never entirely prevailed, as some volume was always needed. But I would advise you not to use it everywhere. In several current projects (examples are ahead) we’ve moved forward into more graphic diversity. Among these elements are gradients, feathering, and blur. For control elements, we‘ve used thin shadows or highlighting to indicate they’re clickable.</p><p>There is a special term — <strong>affordance</strong>. Affordance is a visual clue to further use and functions of an item. For example, a button looks like an element to press or a call to action, hyperlinks are in the blue familiar color and underlined, there are easily recognizable metaphors behind icons — “+”, “?”, “i”, etc., cursor types, and so on. So the user is not forced to think about what he is expected to do next. This is where semi-flat serves well.</p><p>For Android, semi-flat works perfectly because we do our projects according to their producers’ guides — we use their Native Development Kit to program the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYNmWA6QxDGKTXTfbynfFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pL26mVFuyN_DSUFDqdPPQ.png" /></figure><h3><strong>2. 3D</strong></h3><p>3D is ideal for advertising, merchandising, and making posters and promo materials stand out. But 3D has only recently come into use in trading systems.</p><p>We know clients have questions about three-dimensional graphs. We emphasize caution, because we care about information accuracy. In trading platforms people deal with big money; if they misread information they can make a wrong decision. This is why 90% of graphs are 2D, which they’re familiar with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Yhmp8Or-a7NxrVvDj0lyA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DHGcl90WLEjQ6i5PWQwUQ.jpeg" /><figcaption>VR trading tools by Devexperts</figcaption></figure><p>There is one good example of 3D though — a volatility surface in 3D. Traders know how it looks and how to analyze it, and they are used to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7fU23hXKXGQJxURraGz2WQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1IXcsepRxJERDSayY7w4aw.png" /><figcaption>3D Volatility surface</figcaption></figure><h3>2. Animation</h3><p>Watch the animated .gif below. This example is great for start pages to entertain you while waiting.</p><p>This example of animation is an irrespective unreal object. It’s not connected to the main idea of an app and isn’t tied in with a trading platform.</p><p>So let’s go further and see examples of respective relative animation use — how components appear, disappear, and interact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*s5y7Zc93r8Q32B423rHRTw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*oP9qaNIiLMmND7Ya8yokVA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*yhCj-BbH5hPLiqQzfpCzjw.gif" /></figure><p>When users have a positive UX experience they feel a connection to the system. They see how pages turn, how objects and lines fade in or out, how lists drop down, and how a button is pressed. If it happens abruptly it creates discomfort because users aren’t prepared for sudden changes. It’s better when it goes smoothly, but also not slowly. Animation should be close to human expectations. Too much animation can be frustrating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*sWKDExvibEM8rxNRhmoUgQ.gif" /><figcaption>Error bubble animation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*RpWbxykQFBEKq7HReYgg4w.gif" /><figcaption>Tab bar animation</figcaption></figure><p>Here’s a quick example: button color change under a cursor should be 0,3 seconds. And even 0,3 seconds seems too long when you interact with a system for several hours. You want the system response to be faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/223/1*9rMnqp06DlYv9rDxXVRPeg.gif" /><figcaption>Dropdown menu animation</figcaption></figure><h3>4. <strong>Courageous colors</strong></h3><p>We use brave colors in one of our current projects. It’s a mixture of cyan with light blue (azure) and intense yellow (golden) — two complementary colors bolstered by a complex gradient background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GQFAwyyq37JXSblrKiYKIQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyN4_z5hlDJhloWNUWHB4Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8iJll2zOjlqe-RdAOec7g.png" /></figure><p>In the past, colors were dull and flat. Now the trend lies in using vibrant hues. And we see no reason against this: it’s done to stand out, to attract attention, to look tasty, to advertise itself. But still our first priority as a UX/UI design team is to solve a task. If a client works at night and they don’t need bright colors on a black screen, we’ll adopt a less vibrant/more calm color design to meet their request.</p><p>The advantage of this trend is that several unavoidable colors keep everything in one style. The disadvantage is we can’t step aside If we think that we used these colors too much, so we are restricted in color choice.</p><p>Although the usage of gradients is possible, it can be even complex gradients consisting of 3 or 4 hues nearby in the color spectrum.</p><p>Interface color choice should be based on human preferences. People like colors which can be found in nature — from a rainbow to shadows and reflections — because we’re used to them. This knowledge isn’t new and has been around for ages.</p><h3>5. <strong>Color Transition</strong></h3><p>Although color transition stands for a simple gradient, we’ve moved further into this and added more hues. It’s not just the basic transition between two colors, but a mixture of several colors and angled or radial overlaid gradients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-wP8WxR--IhIetFyhvA4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbtBctGKeBiiabT_nlhyKw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FffltvuIG_TXQl0CK-tu3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJ9IDGcheqDUn5zGMx5dog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rq7htom6T4lSsLpRg3xzCQ.png" /></figure><p>In Android we use semi-flat (because of producer’s guides as was mentioned above), and in iOS it’s used nearly always.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmfHPUDl--wYG2XHYquPRQ.png" /><figcaption>Android trading platform</figcaption></figure><h3>6. <strong>Responsive Design</strong></h3><p>Responsive design is one design, created and adjusted for a web screen or a tablet. The design will spread on the screen according to the rules the designers set depending on what device is in use.</p><p>The horizontal/vertical orientations of tablets and smartphones are responsive design examples. Users rotate a device and the layout changes position to fit the new screen size; something extends and something collapses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d50mRdPCmBUXikVFwr-tSw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ugklt0f3OQtpYm9BZJIlqQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*qaPem8knyDtjBjP-Wp2eKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5zRi-dTky9dh_5dTSZRKlQ.png" /></figure><h3><strong>7. Custom Graphics and Illustrations</strong></h3><p>Graphics and Illustrations work well on pages with additional functionality. They’re unique, created upon request, and coordinate with the main style. We have a specific example: a custom illustration for an Android tablet sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSP_zgkCHqSNpz3-r9BPhA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*0rFdhJDV97T6qj-CUVUYgg.png" /><figcaption>Android Tablet</figcaption></figure><p>The illustration makes the menu look more interesting and attractive. Its creation was the result of design team’s brainstorm: when they reviewed the mock-up, they realized that an empty space can be filled in with an interesting drawing.</p><h3><strong>8. Creative Use of Neutral Space and Grid</strong></h3><p>This works great on web sites or applications with enough free space. We can’t afford it because we don’t have a single free pixel. But this trend goes well for landing or log-in pages, presentations and maybe learning centers.</p><p>We use Native Grids in any operating system. Developers of these systems state, for example, that according to their guides the space between content areas in mobile should be 8dp, text in the app bar should be Medium 20 Spreadings, button style is Medium 14sp, all caps, etc.; specific metrics are also applied for tablet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bEGqfEx04kTzgCJ-pNwiXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCnAkrynIYl3cB8PnHm1NQ.png" /></figure><p>Though it’s more standard and monotonous, we adhere to these guides because it helps our end-user. They’re familiar with baseline grids and they know where to find a wanted object.</p><h3>9. <strong>Split Content</strong></h3><p>We definitely use this — and again, it’s not new, it’s been in use since the first trading platform. There are several widgets and they split the screen in five, six, seven, or even more sections. But it’s essential for trading as it helps keep a lot of data accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqrPbZr8TLDlIAvLwlcAyA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DTyPBP7H91E9U1-wL94H-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCBJ-igL5GXllNcBvGg6Jg.png" /></figure><h3>10. <strong>Hidden Navigation</strong></h3><p>And here we took over modern trends in 2018. The technology originally came into use for big data front-end terminals in 2010. Before we started implementing this we had a few menu items and it was easy to allocate all of them in a row at the top or at the bottom of the screen. But after the number of items rose beyond 10 we knew we needed to hide them but be able to show them upon request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*BdfvmkazPWVOxgiBMY4Sdg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bE7iiSc5p2trBwx1b0u_tQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*ZBK4PFAPFEBs1hDntzoCww.png" /><figcaption>dxMobile and Gedik Trader Mobile</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*irGC8kc06EWB-52YmJzNCg.png" /></figure><h3><strong>11. Tiny Design Details</strong></h3><p>These are everywhere in trading software. It’s not only tiny elements or notification icons, but also in accuracy and pixel perfection</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Vte_VSEtkYTF58ALNX3Ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHY5UNwDEI3RZE0pNOSHXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4um82lW15uy4ANr8d4M-pw.png" /></figure><h3><strong>12. Animated Logo and Typography</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*3Lh8UT4RkI98vA30XFjA2A.gif" /><figcaption>dxMobile splash screen animation</figcaption></figure><p>When we do white labeling, we get a logo and color set from our client and work with it. Color set is a starting point, because the logo position is already established. In both white labeling and custom solutions, an animated logo can only show up during page loading to make the wait shorter, so this is a single-time animation. If the logo stays animated for the whole time the user is working in the application, it can disturb their eyes and pull attention.</p><h3><strong>13. Color Transitions in Typography</strong></h3><p>We use these for additional eye appeal and better information representation. The color transition in our apps goes vertically; it’s called condition formatting. Condition formatting colors cells according to the rules set by a user — for example cells, with negative numbers are in bright colors. Other examples include: market depth widget, where the cells are colored depending on their value, order book in gradient, and heat map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgekGLC6K4l5Nvgj0koShA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*dRjJfyczqVXnGmrpwsZMmw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GfZ-0qsANo8F3UdxFgFJfg.png" /></figure><h3>14. <strong>Visual Hierarchy</strong></h3><p>This is always in use, according to the producers’ individual guidelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lg8NQYRIt-l7i5XgVjEzJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zXDLbYr_mziPSkfh5Ts41w.png" /></figure><h3>15. Tiny Typography</h3><p>In highly loaded<strong> </strong>information systems such as our trading platform, everything is small but not tiny. We reduce letters and numbers until a certain degree in order to fit in as much information as possible, but keep it readable, fundamental and appropriate.</p><p>We’re interested in making our systems accessible for the visually-impaired. We want to appeal to all segments because they represent a wider audience for our products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lO8vquzsQwJuiNgBnfVyTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSkOQ0Hs87bVTrqZnuGi-w.png" /></figure><p>We would like to mention some UI trends which are inefficient for heavy loaded<strong> </strong>information systems:</p><ul><li><strong>Cinemagraphs</strong> — demand too much space</li><li><strong>Landing pages</strong> — can only be used for financial learning centers</li><li><strong>Full screen forms</strong> — are used to fill in some extra space, and we don’t have any extra space</li><li><strong>Videos everywhere </strong>—<strong> </strong>the devil’s delight, as they load space and memory</li></ul><p>Every pixel is a valuable space for tables, charts, numbers, and anything else that’s essential. Another waste of pixel space is visual noise. Our goal is to make every effort to streamline and improve user interaction — color composition, animation and hidden navigation, lights and shadows.</p><p><em>Nik Slezkinsky, Head of UX/UI Department at Devexperts.</em></p><p><em>All illustrations in this article belong to Devexperts.</em></p><h4>Join us on <a href="https://www.instagram.com/dx_design_team/">Instagram</a> | <a href="https://www.behance.net/devexperts">Behance</a> | <a href="https://dribbble.com/devexperts">Dribbble</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ce2aeb66e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chameleon: A Cozy Palette Management Tool]]></title>
            <link>https://medium.com/@Devexperts/chameleon-a-cozy-palette-management-tool-bd5feb77eadb?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd5feb77eadb</guid>
            <category><![CDATA[coloring]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[uikit]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Thu, 22 Jun 2017 19:30:35 GMT</pubDate>
            <atom:updated>2017-06-23T15:08:38.377Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When a product suite is constantly evolving it can be a challenge to keep under control the combinatorial explosion of colors; particularly when you have to maintain a number of related products. This article describes the challenges, explores the different approaches and unveils the solution our UI designers and developers uncovered while customizing Devexperts trading applications.</em></p><h3>The Problem</h3><p>At Devexperts we produce Desktop, Web and Mobile UI trading applications. These applications look alike and have similar skins. They can be customized on request for a client, and this leads to the development of custom skins. In general, the first release of a custom skin for each customer is based on the initial product and slightly evolves during the product life cycle, which can last many years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DuHdUI9T62xLySyB9grjZg.png" /><figcaption>Rich set of apps for just one trading product</figcaption></figure><p>Now let’s look at the case in question.</p><p>Any trading application is a complex interface, consisting of multiple colors. Assigning different pixel-perfect editions for desktop, tablet, and mobile screens will triple that number. In addition, the designer works with several skins such as “day” and “night” themes or countless white-labels. This makes the situation difficult to manage and can result in a designer juggling thousands of colors.</p><p><strong>Typical use-cases are:</strong></p><ul><li>inspecting colors used in controls across all applications, editions and their white-labels</li><li>controlling the opacity of an element</li><li>adjusting the color appearance of any element</li><li>comparing</li><li>finding outdated colors, then updating and recoloring them synchronously in one product lineup</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ugvj5RFSUa8Aozmvpqpzwg.png" /><figcaption>Before-after example of full whitelabel for Gedik web app. We execute such tasks on a regular basis.</figcaption></figure><p>The labor intensive work outlined above is achieved by repeating every color occurrence in code. We use semantic names for these occurrences and call them variables. As you can imagine a certain amount of automation and discipline is needed in the color management process. But how can we embed automation? And what can be a good instrument for designers to control and manage changes — and for developers to apply them?</p><h3>Our goal</h3><p>We set ourselves the goal of improving navigation, and simplifying (for all the parties involved in the development) the management of one or more color palette at a time.</p><p>This issue was uncovered by one of our designers while buried in color palette pages on Confluence wiki. They discovered that the amount of variables became innumerable.</p><h3>Possible solutions</h3><p>First we turned to some well-known applications.</p><h4>Confluence or another Corporate Wiki</h4><p>This is actually where we were stuck for quite some time. Here is why we abandoned Confluence pages:</p><p><strong>1. Comparison problems:</strong></p><p>When using Confluence pages, one palette of an individual skin takes an entire page. When you have a mobile app with five skins it means you have five separate tabs and need to switch between them. Of course you can put all of the skins into one Confluence page with an aggregated color palette — just create a column for all five skins. This can solve the problem for some time. But for proper tracking of changes you need to create a new column for each “release” of the color palette. So the number of columns dramatically grows and as a result — it decreases the overall page performance in a browser<a href="#_msocom_1">[EG1]</a> and makes the data harder to scan with the naked eye. In addition, it’s impossible to compare two or more palettes of different projects without odd mouse clicks.</p><p><strong>2. Time-consuming search of changes:</strong></p><p>A second example: working on a white-label project a designer made changes to a UI element, colored it in red, and after that informed a developer to apply it. In general, palettes do not change all that often between stages. They also stay consistent across editions, and any changes usually touch a small subset of variables. Despite this the developer has to manually find what was changed<strong>, </strong>scrolling pages all the way up and down, or, if they are lucky enough, using the search field. Sometimes they may even have to look at the page history of years-old releases, if variables look confusing.</p><p>Both a designer and a developer have to check whether the variables across several palettes are aligned, verify that the differences are intentional and a human mistake did not take place. Confluence has a special diff function that can be used to compare versions of color palettes. But it was designed for code or plain text. A table structure with colors and variables often ends up misaligned even when trying to check quite minor changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Y_m-MUUUhibyylOCjgEAQ.png" /><figcaption><em>Confluence comparison page shows a mess for just only 2 variables reallocated</em></figcaption></figure><p>Take note that in addition you cannot name any changes in the history. So if you want to compare a new palette with a certain previous release, you need to remember the exact date and time of the release.</p><h3>Spreadsheets / Excel-like Software</h3><p><a href="https://docs.google.com/spreadsheets/">Google Sheets</a> may first spring to mind. That would probably work fine for a small company with 2–3 applications or websites. Particularly, if you’re not expecting to work with multiple versions at the same time, or require a substantial expansion in the future with regards to themes, white-labels and skins.</p><p>However, it has the same weaknesses as a wiki. Let’s imagine the following situation: you have one color palette for one product consisting of 100 colors. After receiving orders for 10 white-labels and 4 app editions (desktop, web, tablet, smartphone) you will get 4k colors. Multiply this by Development, QA and Production stages and you’ll end up with 12k colors.</p><p>All web-based table/spreadsheet software uploads all of the columns of stored color palettes. You can use the hide/ unhide option to select a specific subset of color palettes, but this is not convenient for the most popular case when you need just two exact color palettes out of 10 or 20+ palettes. Although Excel is a mighty tool, it requires you to perform extra mouse clicks and strain your eyes.</p><p>In addition, you also need to be disciplined and follow the same structure, which you defined to pre-existing skins, when you are in the process of creating another palette.</p><p>The revision history function in Google Sheets works in a similar way to Confluence pages and cannot visualize useful diff data between two exact versions (releases) of color palette. To compare the differences between the current and the previous version there is a whole class of software called VCS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZeHsj0Z-ZP-zSkA53Foiuw.png" /><figcaption>Revision history shows every small change as a separate line. No option to compare versions.</figcaption></figure><h3>Version Control Systems</h3><p><a href="https://en.wikipedia.org/wiki/Version_control">VCS</a> is a great tool for text files. But here 2 major problems arise:</p><p><strong>1. Comparison problem:</strong></p><p>VCS helps us to work with multiple revisions of one file. But engineers often need to compare two different palettes, and different palettes are represented with different files. VCS is not much help here, because it doesn’t consider these files as related.</p><p><strong>2. Color preview:</strong></p><p>VCS cannot depict colors in an accurate way, which is essential for a designer. Without a good preview you have to keep in mind the text color codes and check on them each time, which increases cognitive load. Basic color representation in some code-highlighting systems gives a better understanding of what is going on for one column of text, but it fails in comparison with a table structure with multiple columns and large colored cells.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*IfcUw_SF1n8hRj8vGm8bZw.png" /><figcaption>Example of color badges in text highlighted by Sublime plugin</figcaption></figure><h3>Chameleon</h3><blockquote>With all mentioned problems and use-cases in mind and, after thoroughly exploring every possible option, we have developed a tool called Chameleon.</blockquote><p><a href="https://github.com/Devexperts/chameleon">Chameleon</a> is a web tool for color management that can be used for white-labels, releases and during all the production stages of new products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKs8kI2SJFRo1-mP94k-yg.png" /><figcaption>Inspecting colors for two palettes in Chameleon</figcaption></figure><p><strong>Features for the Design Team:</strong></p><p>1) Observe a list of variables and see how it was used in different color palettes for different projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*etGGsvh21PAhoNuDg-b-Eg.png" /><figcaption>Account info button color used in different apps</figcaption></figure><p>2) Observe colors for all variables involved for a particular project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*np_XoevuOumk01NzC2Qn9g.png" /><figcaption>Part of color list for desktop app</figcaption></figure><p>3) Control and review changes during a current editing session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*WUns0i7VEZsOPufaVC8X7w.png" /><figcaption>One change registered after editing color input</figcaption></figure><p>4) Compare changes in a current palette with any version of this palette in the past.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O4RpcHMFt_4iUlcnC70wiQ.png" /><figcaption><em>Diff view between 2 versions of palette showing additional colors for new “Error Tooltip” objects</em></figcaption></figure><p><strong>Features for the Development teams:</strong></p><p>1) Design updates in production releases:</p><p>Successful business projects go through milestone (releases) which are deployed in a production environment. In this case the color scheme of master and released projects must be separated. Sometimes, development teams get requests for new developments in already released versions. It saves significant time if a designer and a developer are able to load a snapshot of a released color scheme and slightly change it, rather than use color schemes of master versions which may quietly change since the release went to production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*ikucsoDQwwSuKjvLrWLJ0g.png" /><figcaption><em>Snapshots of released (R0, R1) and current (Head) color schemes</em></figcaption></figure><p>2) Incremental design updates:</p><p>Development team members should be able to get diff between already applied versions of color schemes, and its current version for each release of their UI component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*TVN8Obp5DpFsmOyRoiJvCw.png" /><figcaption><em>Selecting first and second palette versions to compare</em></figcaption></figure><p><strong>A few words about the technologies we used:</strong></p><p>Since this is a typical small-scale enterprise web app, we decided to use the tools which are most familiar to us and which would help us implement the solution quickly. For those who are interested in this particular example, we used:<em> Spring-boot, H2 Database Engine, jsoup, Junit, WebJars, AngularJS, Bootstrap, Swagger.</em></p><p><strong>The team:</strong></p><p>Anna Kislovskaia, Oleg Golubev, Alexey Karasavov, Dmitry Tikhonov, Nail Valeev, Andrey Kezhevatov.</p><p>We opensourced <a href="https://github.com/Devexperts/chameleon">Chameleon on GitHub</a> for everyone. If you have thoughts on how to improve Chameleon, we would be pleased to hear from you — just leave a comment below!</p><p><em>Press </em><strong><em>Like</em></strong><em> if you enjoyed this article and </em><strong><em>follow</em></strong><em> us to see more of our design materials. Stay in touch!</em></p><h4>Join us on <a href="https://www.instagram.com/dx_design_team/">Instagram</a> | <a href="https://www.behance.net/devexperts">Behance</a> | <a href="https://dribbble.com/devexperts">Dribbble</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd5feb77eadb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Work on Design Use Сases. Symbol Library]]></title>
            <link>https://medium.com/@Devexperts/how-we-work-on-design-use-%D1%81ases-symbol-library-990143a75506?source=rss-d60e6d2867d5------2</link>
            <guid isPermaLink="false">https://medium.com/p/990143a75506</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[devexperts]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Devexperts]]></dc:creator>
            <pubDate>Sat, 08 Apr 2017 13:02:34 GMT</pubDate>
            <atom:updated>2017-10-13T11:39:32.142Z</atom:updated>
            <content:encoded><![CDATA[<p>dxMobile is part of our extensive finance software product line gathered under one brand. It was launched on web, desktop, and mobile platforms (both iOS and Android). It is a complex product that boasts rich functionality for financial analysts, professional traders, and researchers. It provides the ability to trade, use analytics, charting and newsfeed for different vendors and brokers. All products in the line have their unique color palettes and style guides. Designing mobile apps, we aspire to maintain the entire functionality of the base platforms (web and desktop). As one could expect, a transition of massive web components to a mobile platform would require a very thorough adaptation. Needless to say, it is crucial for us to keep the platform up to system guidelines and modern trends. We have been designing this app for a couple of years already so we have faced and solved numerous different cases during this time. This article, is an attempt to describe one of these cases on our Android application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUJonf7k0XQM6DxwvfeQGg.jpeg" /></figure><p>Symbol Library is a big catalog of trading instruments with a complex tree structure. We’ve found this case to be the most interesting in our work during the past couple of months. First, we’ve received a request from the analysts to introduce a specific search/filter ability. Use case: a user-trader is looking for a certain trading instrument. In the forex version, the list is limited to a couple dozen instruments so the user is able to monitor the simple watchlist, but in the case of Brokerage, they interact with hundreds of instruments. They may know the instrument title in full, partially, or only by the folder title. The catalog may be extensive and the hierarchy transition chains may be long, therefore our filter should be available on each screen of the catalog hierarchy (parent — subsidiary — sub-subsidiary, etc.) and should not have the user navigate from the current folder.</p><p>This is where the problem occurs. Referring to Google Material guidelines there are two standard ways to introduce search — Persistent Search or Expandable Search. Unfortunately, these methods do not allow the user to search/filter and move through the catalog simultaneously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWhlLKPDQwU6EiJSc7Sp7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCw_611wRwmENyKIdwDeuw.png" /><figcaption>Persistent Search &amp; Expandable Search in Google Material guidelines</figcaption></figure><p>Having researched miscellaneous applications that provide operations with catalogs and analyzed their pros and cons, we came to the conclusion that search should be performed with a separate component under the action bar. The action bar should contain a hierarchy chain and a number of instruments in the current folder. Very long chains will inevitably appear so we’ve added the ability to horizontally scroll it. By tapping on the folder title in a chain, the user can quickly move through the catalog (without losing the search query).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-h2K_3CIzp6kU3txznB0iA.png" /></figure><p>After performing a search query, user can see how many matches there are in their current folder. If there are none, they will be transferred to one of the previous folders that do have matches (in case when there are no matches at all, they will see a placeholder text which explains the situation). Numbers highlight search matches. This pattern is not common for most of the catalogs but is convenient for the current case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEZBHKKkNHP8-sMMunUW9Q.png" /></figure><p>In addition, standard search (global quick search without the catalog structure) is always available from the side menu and its implementation is standard, so the only innovation here is the ability to switch to the symbol library mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cMYRrk63vnuDGNDGLfxOdA.png" /></figure><h3>Not Only Smartphones</h3><p>Besides the smartphone application, we also support the tablet version. We strive to make it as consistent with both the smartphone version and the guidelines as possible. However, according to the requirement that stipulates taking the tablet useful space in its entirety and provide as much data as the device is able to display, issues we’ve dealt with often needed an unusual way of resolving. The principal unique feature is the structure of the application. Components that show up on smartphones as individual screens are available from the side menu and are represented as separate widgets on the tablet. All further actions (such as placing orders or setting an alert) are executed within modal dialogs. On a single page (which is equal to separate screen) a user could set from 1 to 4 different widgets. Each widget could be modally opened as a full-screen component. The number of pages is unlimited, which also provides an option to set an infinite variety of workspace combinations. The structure is created to satisfy the needs of different types of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QoQ9PU41qVo3bd8AYhr7DA.jpeg" /><figcaption>Workspace edit mode and portrait view</figcaption></figure><p>Using this approach we’ve faced such problems as compatibility of different widget types (e.g., chart or watchlist) with various widget formats (1x1, 1x2, 2x1, 2x2). Even though some of the combinations are less useful than others, it is our goal to make the content comfortable for use on different form-factors. Which, according to our practice, is not an impossible task. As the application may be purchased by different vendors, we need high customization potential — and also application of styles that differ completely for different customers. Our widget-style approach works like a construction kit enabling us to provide the exact sought-for solution for each client.</p><p>The most frequent use case of Symbol Library on tablets has been noticeably affected by the widget structure too. In this use case, the user has the Watchlist widget (a list of instruments which contains bid and ask prices and a bit of additional information) and the Chart widget (this component provides detailed information about the trading instrument, user having an ability to compare prices, explore and customize the chart, look through additional market data and trade) on the same screen. This layout provides an ability to look quickly through the instrument list, set the selected instrument on the Chart widget, analyze it, and make fast trade decisions. It’s not that simple though to search quickly for new instruments through a standard watchlist. This is where our Symbol Library comes into play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JglwdN5FRUECY7AcuD_MTQ.png" /><figcaption>Symbol Library widget 1x2 and 2x1 format</figcaption></figure><p>In the majority of apps, the search function is provided by alteration of the current content display or applied globally (above the current structure level). This is a basic approach resulting in global search being always available from the app header. However, we needed to consider two additional cases. First, global search should have two modes: simple and catalog view. Second, an introduction of search/filter ability inside the widget. We started with the widget’s inner structure. In order to avoid the smartphone way of implementing catalog inside the widget (with a back button), we decided to show content in a cascade (it also saves a lot of usable space). This option is perfect for wide widgets (2x1, 2x2 or full-screen). In this case, 4 content columns (folders) can be showed. For narrow formats (1x1 or 1x2) there are 2 columns. In the widget header, we’ve placed a scrollable hierarchy chain (which is consistent with the smartphone), so the issue with transferring through the history is addressed (in order to open another folder, the user can also tap into the column content, of course). What about the global search though? Its catalog view should almost replicate the symbol library structure so all we have to do is to add a proper mode switch control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYXc3WFHZqsjzpUIWW9HJw.png" /><figcaption>Symbol Library search query and Simple Search</figcaption></figure><p>In conclusion, it will not be redundant to remind that all of the decisions have been made through difficult discussions with analysts and product owners and tested both in-house and in focus groups. It wasn’t that easy of a task so we’ve spent quite a while working hard at our workplaces, sketching on whiteboards with markers in our hands, and deliberating in the meeting rooms. That said, we hope this information will help you resolve your own cases. Stay in touch!</p><p><em>Alex Sotnikov, UI Designer at Devexperts. Nik Slezkinsky, Head of UX/UI Department at Devexperts.</em></p><p><em>All illustrations in this article belong to Devexperts.</em></p><h4><strong><em>Join us on </em></strong><a href="https://www.instagram.com/dx_design_team/"><strong><em>Instagram</em></strong></a><strong><em> | </em></strong><a href="https://www.behance.net/devexperts"><strong><em>Behance</em></strong></a><strong><em> | </em></strong><a href="https://dribbble.com/devexperts"><strong><em>Dribbble</em></strong></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=990143a75506" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>