 My name is John Furzel. I'm the platform architect with Red Hat Mobile. I've been working in the mobile space since 2008 and have been part of Red Hat family since the feedback and reacquisition in 2014. The Red Hat mobile application platform is an all-in-one solution for developing, deploying, managing and monitoring mobile solutions and integrations into backend systems. Building for mobile is a very different paradigm to developing for traditional web or desktop applications. The type of application, how it's built, where certain pieces of logic should live, are quite different from mobile because of things like bad networks, low connectivity, the volume of data you transmit and the amount of requests you make. It's a lot more difficult to push updates out than it is for traditional web applications where you simply have to deploy an update to the web server and users automatically get the updates through the browser. With mobile applications and in particular when you're looking at the public app store where you can't force users to update, it's very important to think about that update and upgrade cycle. You may have a period of weeks while you wait for a review from Apple before your update gets pushed out. So if you have significant logic in the client side, you're going to find that you're doing more bug fixes, more patches and more updates to the application on device, meaning more updates in the app store and more time spent pushing those out. So keeping the mobile application as thin and lightweight as possible is a really crucial to successful mobile development and the way the platform lays out the solution for you really encourages taking that approach. However, for enterprises and the primary focus of the Red Hat mobile application platform is more so for enterprises, what you find with enterprises is they have mobile device management solutions that are used for managing devices and pushing out updates of applications. So the Red Hat mobile application platform integrates with three of the top mobile device management providers. So as you're building your mobile application within the Red Hat platform, you can hook it up to your MDM provider and have it push the generated application directly into the MDM provider so that it can then be pushed out to devices. So provides a seamless integration. One of the features of the Red Hat mobile platform is the ability to build your mobile binaries in the cloud within our platform without having to have developer tools for the various platforms installed on your local system. One of the key benefits of the Red Hat mobile platform from a developer perspective is that the platform really helps you lay out the architecture of your mobile solution. And I say solution because it's more than just an app. The app on devices, the piece people think about it's the phone in your hand, but it's always or almost always connected to back end systems. So the platform helps you lay out the solution in terms of the mobile piece, a dedicated microservice for the mobile acting as an API server and then reusable Mbass components for integration into back end systems. So the next thing the developer should be aware of is that the Red Hat mobile platform comes with a command line tool that offers all the same functionality as the studio. So as soon as you move into development mode, you have terminal windows open, you have VM or Emacs or Webstone, whatever your preferred editor is, and you're in your standard develop test commit flow. You're really just working in your standard flow there and you can integrate the FHC tool as much or as little as you want into that. The recent release of version for the Red Hat mobile platform at support for being able to use OpenShift as the Mbass part of the solution. So the Mbass is where your Node.js applications live the things that the mobile app will talk to. They can never be hosted as a set of Docker format containers, using Kubernetes and all the benefits of OpenShift and that can be deployed as a non premise offering. There's a range of different technologies at play within Red Hat mobile application platform. On the server side, we have Node.js, so that's JavaScript on the server side, as our API serving layer and back in integration there. On the client side, there's a range of different technologies to match the different mobile operating systems. There's native iOS for both Swift and Objective C, there's native Android, and then there's cross platform and that's one of our more popular ones, the Apache Cordova project. So depending on what skill sets a developer already has, so a typical web developer, for example, who's already familiar with Angular, would be able to get going quite quickly using the Angular quick start application. So there's quite a wide range of skill sets available or required depending on the type of mobile solution being developed.