 Hi again Red Hat Developers, we're at day two of Summit 2017 in the Dev Zone. Today we have Rob Harvey and he's going to talk to us about UX Convergence. Take it away Rob. Hi, thank you everybody. I'm Rob Harvey, I'm the Chief Operating Officer for Intando. Intando is the lightest weight open source digital experience platform on the market. We're working with Red Hat right now, we've just signed a collaboration agreement around the future of a lightweight, low-code, modern application development suite. What I'm here to talk to you about today is UX Convergence, it's something we see a lot of in the industry. This is solving a big problem, we essentially see a state of web disruption. In this new world here we see a proliferation of applications, many, many apps, new devices that are coming up, IoT devices, contents that are spread across the business and these businesses are functioning in silos. These silos really, they don't talk, they're not really incentivized to talk together and so this continues to compound the problem of this proliferation and of the apps that sit within. We see evolving user engagement, devices like mobile phones, consumers are used to these very rich user experiences and they're accustomed to this every day and so they're looking for the enterprises to provide more. Their customer engagement has evolved, frameworks, Java's been Java for many years and what we're seeing in the market is now the adoption of new front-end technologies, angular, material. These are moving faster than anything, the rate of lightning speeds here whereas something like Java has been Java for a very long time. This is creating something that we call the UX Jam. It's essentially a breakdown in an organization where you're experiencing, the customer experience is starting to deteriorate. User experience is going south, not north. What we see is UX divergence, UX divergence very simply is where somebody experiences the same type of functionality in different applications, the same feature in different applications in different ways. We can look at something like notifications, it's a great example, calendar services, task management. In this case we're showing six different applications and many of these call the notifications and maybe alerts, there may be events that are occurring but the users are experiencing these notifications in different applications in different ways. The answer to this is what we call UX convergence. It's a harmonization of user experience across applications, across business silos and even across new devices like IoT. As we look at UX convergence, we almost see this as the microservices of user experience. We want to build a common set of services across the omnichannel. In that example of notifications, if you were to base your platform on a UX convergence model, users can experience a notification in a common way, in one way. This is a great way to demonstrate a holistic type of user experience across that application channel. UX is broken down into three pillars. We see three pillars of user experience or really user convergence. It's patterns, orchestration and abstraction. Patterns, they're the DNA, they're the styles that sit within the company, they're the brand guidelines, these are the CSS styles, the components, the features that make their way into the applications, the building blocks that you use to build an app. The problem is that patterns don't really define everything. Red Hat has a pattern fly group here and they're focused very much on the patterns, but patterns don't define the experience. The experience comes from an orchestration of those patterns. It comes from building common processes that correlate to a user experience. With orchestration, we see that happening within the JBoss BPM suite. Abstraction. Abstraction is one of the major pillars. If you think about building an orchestrated pattern, we now have the ability to follow a use case. We have the ability to create a new calendar appointment or register for a service, register for a coupon. This now has to be exposed in a common way. This is the abstraction layer that we wrap around UX convergence, around user experience in order to make it consumable in a standard way. We are looking today at an integration with Red Hat Fuse. As we start to grow UX convergence, we're going to see more and more develop in these areas. As an example with calendar, everybody's got calendar. I've got one calendar in my pocket. It's on my phone. I've got 20 apps that connect to this calendar. With UX convergence, what we're looking for is a common way to interact with calendar. I don't want 20 calendars. I want one. By following the pillars, looking at essentially patterns, we define what that look and feel is for the calendar itself. What are my color schemes? What are my objects or my elements that are going to make up this specific experience? When we look at the orchestration, when I go to create a new appointment, what is that process going to entail? When finally, I need to expose this out to Gmail as a service or my Facebook account as a service. All the things that interact with calendar, all the things that can fill my calendar, I need to create that abstraction layer. These products need to know how to integrate in a standard way through standard APIs. This is the concept of UX convergence. It's not just technology. As you look at deploying something like this across an organization, we're looking at building new governance models, new delivery methodologies to successfully adopt this technology. Requires UX sponsorship at the highest levels of the organization, new steering committees to be developed, standards bodies, everything from policies to culture. Best practices need to feed this. It is becoming something that the industry in its whole needs to start looking at. We look at modern application development, which is a key platform that Red Hat has launched. Modern application development is needing, they're really desperately needing something around UX convergence. What's next for UX convergence? We see the need to disseminate, distribute, and control these standards within the organization. What we intend to see, and this is really possible now with DevOps and CIDC, we see the ability to distribute these standards within the organization, bridge the silos that exist within really any enterprise company. Federation becomes something that's quite key and something that you need to focus on. I want one calendar in each of my apps. I want one calendar service that shares my appointments across multiple calendars, multiple tools, multiple services, multiple applications. The integration of the DevOps models, the automated acceptance testing, these are the developing standards around UX convergence. Intondo is a platform that essentially is scaling up to support this challenge. Not to focus on attacking these silos and trying to get them to converge on a standard set of experiences, but really adopt these into the silos with minimal amounts of complication. We're looking at a true autonomy within these silos while maintaining some level of control at the organization level. Finally, if you're interested in learning more, we'd love for you to stop by the modern application dev area. We're over in the JBPM booth, the JBoss BPM booth. Come by, talk to us. We've got a demo. We'd love to show you a little bit about what we're doing in the world of UX convergence. And that's it. Thank you for your time.