Create Engaging Apps with a Multi-experience Development Platform

  • Transcript

    [00:00:00.140]
    Hello and welcome to this located 30.

    [00:00:02.669]
    My name is Simon Black, and I’m a platform evangelist

    [00:00:05.150]
    here of Bendix

    [00:00:06.799]
    in today’s Loco to 30 will take

    [00:00:08.960]
    a look at how you can create engaging APS

    [00:00:11.490]
    using a multi experience platform.

    [00:00:16.000]
    In this webinar will cover what you previously

    [00:00:18.339]
    missed in our local and 30 Siri’s.

    [00:00:21.190]
    We’ll take a look at the evolution of experiences

    [00:00:24.269]
    and what it means to be a multi experience

    [00:00:26.359]
    platform.

    [00:00:28.640]
    Well, look at how medics addresses multi

    [00:00:30.750]
    experience, development platform

    [00:00:32.789]
    and showcase to you. An example. Use

    [00:00:34.789]
    case with a demo off the platform.

    [00:00:41.399]
    These low code and thirties run on a monthly

    [00:00:43.590]
    basis,

    [00:00:44.640]
    and they cover a range of topics

    [00:00:46.799]
    everything from collaborative visual

    [00:00:48.890]
    development through to comprehensive

    [00:00:50.979]
    application security.

    [00:00:53.090]
    And if you want to catch up on anything cute list,

    [00:00:55.679]
    you can find all of our webinars on

    [00:00:57.750]
    our YouTube channel

    [00:00:59.020]
    and that men next dot com such demos.

    [00:01:01.640]
    So make sure you subscribe to get the latest

    [00:01:03.759]
    updates in Loco. 10 30

    [00:01:08.340]
    Over the past decade, the way that

    [00:01:10.359]
    uses interact with technology has

    [00:01:12.530]
    dramatically changed.

    [00:01:14.340]
    The world has moved away from destiny only APS

    [00:01:17.060]
    to Web mobile of finally

    [00:01:19.290]
    multi channel

    [00:01:20.939]
    But we’re now in a new era of multi experience

    [00:01:24.140]
    where users expect to be our to pick up

    [00:01:26.140]
    their workloads on any device,

    [00:01:29.010]
    whether it be using a mobile tablet,

    [00:01:31.450]
    wearables or voice

    [00:01:33.739]
    seamless See moving between these different experiences

    [00:01:37.000]
    on the device is remembering where

    [00:01:39.200]
    the use of WAAS in their journey

    [00:01:44.840]
    it’s not just us that is noticed this trend.

    [00:01:47.370]
    Analysts like Gardner have adapted

    [00:01:49.409]
    their mobile development quadrants to

    [00:01:51.409]
    reflect this change in consumer needs

    [00:01:54.379]
    each time the quadrant builds on top of the

    [00:01:56.379]
    previous adding new required

    [00:01:58.379]
    functionality.

    [00:02:00.719]
    Originally, mobile development was split

    [00:02:02.780]
    into two quadrants,

    [00:02:04.519]
    the Mobile Enterprise Application platform

    [00:02:07.079]
    on the mobile consumer application platform.

    [00:02:10.520]
    Both of these types of platforms provided

    [00:02:12.939]
    middleware to help support developers

    [00:02:15.400]
    to create mobile APS to support

    [00:02:17.449]
    different operating systems,

    [00:02:20.219]
    but had different features to support

    [00:02:22.610]
    consumer on enterprise workloads.

    [00:02:27.020]
    Soon M. C, A, P and

    [00:02:29.090]
    M E A P most into

    [00:02:31.150]
    the M, A. D. P or the mobile application

    [00:02:33.740]
    developer platforms

    [00:02:35.520]
    as it was a clear need from organizations

    [00:02:38.300]
    to be able to build multiple form factors

    [00:02:41.090]
    using a loco platform

    [00:02:43.120]
    and support all types of applications,

    [00:02:45.250]
    including B to C, B, T. A

    [00:02:47.500]
    and B to bay.

    [00:02:50.120]
    This year, the Quadrant has once again

    [00:02:52.280]
    evolved,

    [00:02:53.490]
    becoming the MX DP or multi

    [00:02:55.750]
    experienced of our platform.

    [00:02:58.120]
    This is the result of a huge increase in

    [00:03:00.349]
    the use of new interfaces. Such

    [00:03:02.460]
    a chat a our voice.

    [00:03:05.520]
    But to support these new types of interface is

    [00:03:08.039]
    the platform needs to provide a number off Dev

    [00:03:10.189]
    ops tools

    [00:03:11.379]
    and support cloud native architecture,

    [00:03:14.060]
    allowing a range of developers to

    [00:03:16.069]
    quickly build and scale out multiple

    [00:03:18.599]
    user experiences.

    [00:03:23.979]
    The Mendez platform has always strived to drive

    [00:03:26.229]
    innovation

    [00:03:27.219]
    and deliver new features that our customers

    [00:03:29.310]
    and analysts are seeing as being essential

    [00:03:31.650]
    to support great user experiences.

    [00:03:34.659]
    This is why

    [00:03:35.639]
    this year Mendes was named a leader

    [00:03:37.919]
    in the gardener multi experience development platform.

    [00:03:40.250]
    Cultural and Gardner

    [00:03:42.270]
    predicts that by 2023

    [00:03:44.569]
    more than 25% off the mobile

    [00:03:46.949]
    APS, progressive Web, APS and

    [00:03:49.110]
    conversational amps

    [00:03:50.689]
    at large enterprises will be built

    [00:03:52.930]
    and all run

    [00:03:54.060]
    through a multi experience development platform.

    [00:03:58.360]
    So if he interested in knowing why

    [00:04:00.603]
    we were named a leader

    [00:04:02.193]
    on, we want to see more information about

    [00:04:04.592]
    the quadrant.

    [00:04:05.612]
    You can download this from our website,

    [00:04:12.002]
    but we believe there are three core reasons,

    [00:04:14.263]
    while we’re named a leader in this Quadrant

    [00:04:17.153]
    and these are that we deliver great

    [00:04:19.302]
    user experience across all channels,

    [00:04:22.473]
    we help organizations adopt design

    [00:04:24.882]
    ups, best practices

    [00:04:26.923]
    and finally, architectural foundation

    [00:04:29.473]
    allows for scale performance on

    [00:04:31.552]
    portability.

    [00:04:35.942]
    The medics platform comes with a series

    [00:04:37.992]
    of out the box page templates. Themes

    [00:04:40.862]
    aloud of widgets.

    [00:04:42.492]
    To ensure your user interface works

    [00:04:44.862]
    across all platforms,

    [00:04:48.562]
    users can access their applications

    [00:04:50.603]
    any time, regardless of connectivity,

    [00:04:53.223]
    by leveraging the oflife first mobile

    [00:04:55.353]
    strategy.

    [00:04:57.502]
    Any app built in the plant fall can

    [00:04:59.552]
    be presented in multiple four factors.

    [00:05:01.862]
    River it beyond mobile, tabler, web

    [00:05:04.473]
    or wearables.

    [00:05:08.932]
    More Maur organizations are

    [00:05:11.093]
    embracing agile C I. C D

    [00:05:13.202]
    tools and develops within their application

    [00:05:15.512]
    delivery passes.

    [00:05:17.552]
    These concepts are built into the core

    [00:05:19.572]
    platform of men, Dex, but take

    [00:05:21.603]
    develops a stage fervor to include

    [00:05:23.862]
    design ops,

    [00:05:25.802]
    design ops, conceptual e lays on top

    [00:05:27.892]
    of devil bes tow operationalize your

    [00:05:30.192]
    organization’s approach to product design.

    [00:05:33.283]
    It makes designed an integral part off

    [00:05:35.492]
    the application life cycle.

    [00:05:37.752]
    Applying design thinking techniques. Just

    [00:05:39.913]
    test assumptions from initial concept

    [00:05:42.562]
    to solution, design and delivery

    [00:05:45.903]
    by leveraging our two id’s, the

    [00:05:47.942]
    Medics studio on the Studio Pro,

    [00:05:50.673]
    the entire development team, including Business

    [00:05:52.802]
    90 Stakeholders can collaborate

    [00:05:55.083]
    and build together.

    [00:05:57.502]
    Both The ideas use visual models to build

    [00:05:59.622]
    full stack application. It’s

    [00:06:01.949]
    the studio is focused on our sits and

    [00:06:04.069]
    developers

    [00:06:05.509]
    business users who may have no experience

    [00:06:07.670]
    in development

    [00:06:08.649]
    can kick start their idea and start

    [00:06:10.750]
    to design an application or concert.

    [00:06:12.759]
    Peter, an existing one

    [00:06:14.709]
    around citizen developers to rapidly

    [00:06:16.759]
    test assumptions before delivery

    [00:06:19.050]
    off a full application

    [00:06:22.240]
    of the right hand side. We have the studio pro

    [00:06:24.629]
    folks that are I T developers

    [00:06:27.250]
    Inside the studio. Pro developers can create

    [00:06:29.379]
    code extensions, integrations

    [00:06:31.899]
    and review. All changes may bar business

    [00:06:34.029]
    users in the studio,

    [00:06:36.250]
    but having two ID’s, the medics

    [00:06:38.350]
    platform can cover both know code

    [00:06:40.540]
    on local development.

    [00:06:45.180]
    To ensure the applications of built A speed

    [00:06:47.620]
    is important, we accelerate every part of

    [00:06:49.740]
    the application life cycle.

    [00:06:51.930]
    The medics platform covers everything from capture

    [00:06:54.079]
    requirements, planning, development

    [00:06:56.350]
    deployment, A review

    [00:06:58.310]
    allowing applications to be built 6 to 10

    [00:07:00.449]
    times faster

    [00:07:01.620]
    than traditional development

    [00:07:03.759]
    by rapidly iterating over an application

    [00:07:06.220]
    user can ensure that they’re delivering

    [00:07:08.360]
    requirements off their users

    [00:07:13.569]
    to deliver effective experiences

    [00:07:15.769]
    across devices.

    [00:07:17.139]
    It’s important that we have an architectural

    [00:07:19.290]
    foundation that supports these different

    [00:07:21.540]
    work raids.

    [00:07:23.209]
    User interfaces such as A, I and

    [00:07:25.230]
    II T require a scalable architecture

    [00:07:28.079]
    to deal with potential heavy workloads.

    [00:07:31.810]
    Oh Ben, it’s applications are dear to 15

    [00:07:34.100]
    factor app. Architecture.

    [00:07:36.250]
    Ensuring portability at scale across

    [00:07:38.480]
    infrastructure,

    [00:07:40.360]
    the platform utilizes contain the technology

    [00:07:42.470]
    such as Cloud foundry, doctor or kubernetes,

    [00:07:45.550]
    too. Sure applications come support high

    [00:07:47.759]
    availability on auto recovery.

    [00:07:54.449]
    The use case that we’re going to look at today is

    [00:07:56.709]
    for a microbrewery.

    [00:07:58.610]
    Expect Rich has a several balls and

    [00:08:00.720]
    rest right across the UK, where they sailed

    [00:08:02.987]
    their beers, wides and no alcoholic beverages

    [00:08:06.867]
    as an additional revenue stream. They want to

    [00:08:09.067]
    provide tours of the brewery

    [00:08:11.747]
    during a tour. Visitors want to be able

    [00:08:13.766]
    to use their mobile device to identify

    [00:08:15.966]
    certain beers on order Personalized

    [00:08:18.107]
    bottles.

    [00:08:20.166]
    These bottles will be manufactured and shipped

    [00:08:22.716]
    to. The customer has several locations.

    [00:08:25.666]
    After the customer’s purchase, their personalized bottle.

    [00:08:28.336]
    They need to be able to easily check the progress off

    [00:08:30.437]
    the order.

    [00:08:31.826]
    To do so. Expect free to provide several

    [00:08:34.006]
    support Service is

    [00:08:35.407]
    by their Alexis skill on their online

    [00:08:37.787]
    chap pot.

    [00:08:40.966]
    Help support these processes. The

    [00:08:43.037]
    menace platform allows for creation of multiple

    [00:08:45.206]
    user experiences,

    [00:08:46.866]
    these could be developed inside. One application

    [00:08:49.317]
    or part of several.

    [00:08:51.027]
    Allowing data and service is to pass between

    [00:08:53.157]
    them and allow the different experiences

    [00:08:56.126]
    to access data across applications.

    [00:09:00.187]
    So let’s jump into the demo to give you

    [00:09:02.216]
    a glimpse into the power off. The medics pratfall

    [00:09:06.907]
    in this demonstration will showcase how we can

    [00:09:08.986]
    build out multiple device experiences

    [00:09:11.567]
    for our consumers.

    [00:09:13.517]
    By leveraging the mandates platform, we can build

    [00:09:15.777]
    out different device experiences on

    [00:09:17.966]
    allow those to communicate together

    [00:09:20.177]
    to bring a great user experience to our

    [00:09:22.216]
    consumers.

    [00:09:24.336]
    The first user experience will look at is

    [00:09:26.456]
    building out. Native mobile applications

    [00:09:29.667]
    will be utilizing the men dicks, a native

    [00:09:32.076]
    capabilities which would launch last month.

    [00:09:35.616]
    As part of this release, we really stay Testing

    [00:09:38.067]
    Tool, which is called the Make it native APP,

    [00:09:40.767]
    allows you to test out your applications

    [00:09:43.157]
    by leveraging the device features and functionalities

    [00:09:46.277]
    without going through the APP store approval.

    [00:09:49.356]
    You can connect it up to an application and

    [00:09:51.756]
    launch it to be able to test those native

    [00:09:53.966]
    capabilities.

    [00:09:56.226]
    When we launched this particular application, we

    [00:09:58.356]
    can see the new features and functionalities

    [00:10:00.976]
    that are available. It was part of this application

    [00:10:04.370]
    by leveraging native capabilities were

    [00:10:06.570]
    able to give that great user experience

    [00:10:09.200]
    for a particular device

    [00:10:11.779]
    experiences that consumers are used to

    [00:10:14.049]
    when using applications such as Facebook

    [00:10:16.370]
    and Instagram.

    [00:10:17.870]
    He used the same technology, which is called React

    [00:10:20.169]
    native,

    [00:10:21.100]
    allowing you to transition easily between

    [00:10:23.139]
    those pages

    [00:10:24.259]
    and allows you to great give great

    [00:10:26.549]
    user experience to your consumers.

    [00:10:30.450]
    Inside this application were able to browse

    [00:10:32.850]
    a number off items from our store

    [00:10:35.409]
    but also able to order new items

    [00:10:38.799]
    to order new items. We can simply use

    [00:10:40.870]
    our scan feature,

    [00:10:42.379]
    which is his image recognition to detect

    [00:10:44.710]
    certain bottles

    [00:10:46.480]
    was just detected a bottle. It can then

    [00:10:48.850]
    choose to buy this particular item or

    [00:10:50.990]
    no. In this case, we

    [00:10:53.000]
    can see we’ve got a new bottle

    [00:10:55.009]
    item and it’s currently suggesting

    [00:10:57.450]
    that this is worth $4. Because we

    [00:10:59.500]
    are ordering two bottles,

    [00:11:01.789]
    we can slide and increase this. This will.

    [00:11:03.840]
    Ultimately, they are prosper price for

    [00:11:05.990]
    us using

    [00:11:08.909]
    clients. I logic we can make

    [00:11:10.970]
    sure that all of that decisions and calculations

    [00:11:13.820]
    are performed on the device,

    [00:11:16.470]
    meaning that we can do everything without

    [00:11:18.620]
    connectivity

    [00:11:19.690]
    working completely offline on this mobile

    [00:11:21.960]
    application and sink that dates back

    [00:11:24.190]
    when needed,

    [00:11:26.399]
    we can add some personalized text to our

    [00:11:28.409]
    particular bottle. So in this case, we want to have

    [00:11:30.570]
    our name displayed on the label.

    [00:11:33.320]
    If we select next week, then choose

    [00:11:35.409]
    where we want this particular item to be delivered

    [00:11:38.059]
    or collected from a number of convenient

    [00:11:40.110]
    locations,

    [00:11:42.299]
    we can select collection.

    [00:11:43.789]
    And from here, we can select from a map of

    [00:11:45.879]
    you each of those occasions

    [00:11:48.129]
    on where it wants to be delivered.

    [00:11:51.200]
    When it’s delivered to those particular locations,

    [00:11:53.419]
    it will be placed in one of our smart lockers

    [00:11:56.330]
    inside their smart lookers. We can open

    [00:11:58.720]
    them up using our mobile device.

    [00:12:01.991]
    This is something we showcased at our medics

    [00:12:04.322]
    world event.

    [00:12:06.522]
    If we hit the buy button here,

    [00:12:08.581]
    it will then give us a congratulations message

    [00:12:11.111]
    to say we’ve purchased this particular item.

    [00:12:14.392]
    It will also send us a push notification

    [00:12:16.711]
    to our device so that we can actually

    [00:12:19.042]
    conceive and confirm that we’ve ordered

    [00:12:21.442]
    this particular item.

    [00:12:26.022]
    Now, as we’re working with this particular application

    [00:12:29.032]
    are consumers might want to add

    [00:12:31.192]
    new functionality or they might request

    [00:12:33.442]
    new functionality.

    [00:12:35.022]
    In this case, they want to be able to authenticate

    [00:12:37.442]
    before actually buying this particular

    [00:12:39.552]
    item. So using their biometrics

    [00:12:42.192]
    I d. Such as their fingerprint or their

    [00:12:44.272]
    image recognition. We want to be able to

    [00:12:47.422]
    check their identity before

    [00:12:49.822]
    actually allowing them to purchase.

    [00:12:52.662]
    So to do so, we’re actually gonna implement a

    [00:12:54.692]
    new feature.

    [00:12:55.812]
    And we’re gonna implement that using the minute studio

    [00:12:58.231]
    pro inside the minute

    [00:13:00.251]
    Studio pro. We can build out our pages

    [00:13:02.652]
    logic and data for our application,

    [00:13:05.552]
    regardless of what user experience

    [00:13:07.581]
    and device we’re using

    [00:13:09.721]
    here, we can drag and drop and build out our experience

    [00:13:12.081]
    for our mobile application,

    [00:13:13.961]
    but also build out the logic behind

    [00:13:16.142]
    certain buttons on dhe

    [00:13:17.812]
    interfaces.

    [00:13:19.542]
    In this case, we’re gonna build out a

    [00:13:21.881]
    new functionality which is gonna be to

    [00:13:24.152]
    identify them using their fingerprint

    [00:13:26.442]
    recognition.

    [00:13:27.892]
    If we drag on a new activity to this by

    [00:13:29.942]
    flow, we can then check and

    [00:13:31.942]
    shoes from a number off act

    [00:13:34.111]
    actions and activities.

    [00:13:36.412]
    These can be even native to the mend,

    [00:13:38.562]
    its platform or downloaded from our

    [00:13:40.711]
    APP store.

    [00:13:42.172]
    APP stores are component library allowing

    [00:13:44.581]
    you to accelerate and extends the

    [00:13:46.581]
    capabilities off the platform

    [00:13:48.861]
    itself.

    [00:13:50.361]
    In this case, we want to check their biometric

    [00:13:52.402]
    authentication.

    [00:13:53.792]
    We want to be able to see whether

    [00:13:56.221]
    they have the right authentication or no.

    [00:13:58.721]
    So we’re going to say whether this fingerprint is

    [00:14:00.831]
    okay or not,

    [00:14:04.251]
    we can then add in a decision point

    [00:14:07.501]
    inside that decision point. We can then

    [00:14:10.001]
    decide whether it’s a valid fingerprint.

    [00:14:12.201]
    All off. If

    [00:14:19.201]
    it is, we want them to be able to purchase

    [00:14:21.331]
    the items.

    [00:14:22.491]
    Otherwise we want to be introduced.

    [00:14:25.932]
    Display a message to them saying it’s no

    [00:14:28.081]
    valid fingerprint.

    [00:14:45.751]
    Well, we need to do now is actually redeploy

    [00:14:47.831]
    application.

    [00:14:48.912]
    So by running locally, this will build us a new

    [00:14:51.052]
    version of our application.

    [00:14:52.741]
    It will hot reload this on our mobile device

    [00:14:55.591]
    and allow us to now start testing out that new

    [00:14:57.652]
    functionality.

    [00:14:59.032]
    So let’s go ahead and scan that new item

    [00:15:01.182]
    again to scan our bottle,

    [00:15:03.351]
    festival

    [00:15:07.491]
    it by

    [00:15:09.231]
    selection, personalized text,

    [00:15:16.892]
    select our location.

    [00:15:18.672]
    And finally, when we hit by now,

    [00:15:20.442]
    we brought up this option to authenticate

    [00:15:22.861]
    with our fingerprint.

    [00:15:24.282]
    If we touch our fingerprint on that item

    [00:15:26.501]
    now, it

    [00:15:29.491]
    will now confirm us and allow us to

    [00:15:31.511]
    purchase this item.

    [00:15:34.052]
    So we’re now get a confirmation as a push notification

    [00:15:36.611]
    again off our item.

    [00:15:39.251]
    Now, the next functionality that we want

    [00:15:41.381]
    to showcase

    [00:15:42.511]
    is that’s quite often consumers

    [00:15:44.601]
    forget or want to be able to change

    [00:15:46.812]
    their order on the go.

    [00:15:48.942]
    One of the convenience functionalities

    [00:15:51.251]
    that were out there at the moment

    [00:15:52.851]
    is being until order and change information,

    [00:15:55.172]
    using your voice

    [00:15:57.052]
    to eventually extended this application and

    [00:15:59.241]
    added in voice capabilities

    [00:16:01.451]
    So we can ask

    [00:16:02.701]
    Alexa,

    [00:16:04.211]
    ask brewery to change my order.

    [00:16:09.272]
    How would you like

    [00:16:10.522]
    your last

    [00:16:13.682]
    address? Quantity.

    [00:16:17.772]
    How many? 10.

    [00:16:23.772]
    Thanks. We have updated you’ll rest.

    [00:16:26.052]
    3779

    [00:16:28.501]
    and 10 tend to order.

    [00:16:30.721]
    Value is now trying to

    [00:16:32.772]
    have a great rest of your day.

    [00:16:37.331]
    So now by using Amazon Alexa,

    [00:16:39.491]
    we’ve been Alberto, actually update our

    [00:16:41.621]
    order and this is pushed this through

    [00:16:43.861]
    into our mobile application because

    [00:16:46.162]
    we’ve now got push notifications in our application,

    [00:16:48.841]
    we can see here that our last order

    [00:16:51.451]
    has been updated by 10 bottles.

    [00:16:54.621]
    So we have experiences across

    [00:16:56.851]
    different devices. But all of that data

    [00:16:59.221]
    is flowing in together to bring a

    [00:17:01.251]
    unique experience to our consumers.

    [00:17:03.812]
    So far, in our demonstration, we’ve showcased

    [00:17:06.132]
    how you can leverage native capabilities

    [00:17:08.892]
    to bring a great user experience to your consumers,

    [00:17:12.011]
    as well as leveraging voice capabilities

    [00:17:14.511]
    to allow your consumers to ask questions

    [00:17:16.602]
    about their order status,

    [00:17:18.392]
    update their order on the go.

    [00:17:21.412]
    But these user interfaces only cover a

    [00:17:23.422]
    small portion of the amount of experiences

    [00:17:26.231]
    that modern enterprises need to cover.

    [00:17:29.541]
    One important feature and user

    [00:17:31.561]
    experience we need to cover is being able

    [00:17:33.652]
    to create Web applications,

    [00:17:36.011]
    the respond to the browser,

    [00:17:38.311]
    whether they be in

    [00:17:39.791]
    native or whether they be on the mobile

    [00:17:42.122]
    device, tablet or Web.

    [00:17:45.051]
    And also, we need to be able to support

    [00:17:47.241]
    on communicate with our customers

    [00:17:49.692]
    by leveraging a chap bar were

    [00:17:51.832]
    able to provide 24 7 support

    [00:17:54.402]
    to our users.

    [00:17:56.372]
    So let’s switch over to our browser now to

    [00:17:58.551]
    see those new functionality.

    [00:18:02.071]
    So here in this online up occasion, we can

    [00:18:04.162]
    do the same process as we did on

    [00:18:06.402]
    our mobile application.

    [00:18:07.932]
    We can choose certain products and

    [00:18:09.981]
    update the quantity

    [00:18:11.491]
    by simply typing for certain informations.

    [00:18:13.721]
    We might want a House house wine.

    [00:18:16.231]
    We can slide this information

    [00:18:18.291]
    the quantity to update our total.

    [00:18:21.071]
    Now this application runs across device.

    [00:18:23.491]
    Whether it be on mobile

    [00:18:25.501]
    or tablet,

    [00:18:27.061]
    it will respond to the actual device

    [00:18:29.412]
    it’s on

    [00:18:30.392]
    at the box. All medics applications

    [00:18:32.461]
    utilized, responsive design

    [00:18:34.451]
    allow you to create beautiful applications

    [00:18:36.751]
    across device.

    [00:18:38.541]
    You can also build your own custom look of feel

    [00:18:41.051]
    for different device types on build

    [00:18:43.241]
    out native applications like a showed you earlier

    [00:18:45.602]
    in the previous demonstration.

    [00:18:51.632]
    So within this application, we’ve also built

    [00:18:53.761]
    into it A friendly chapel

    [00:18:55.662]
    on Mike here is able to actually ask

    [00:18:57.862]
    us questions on Be able to support

    [00:19:00.332]
    us in the 24 7 manner.

    [00:19:02.951]
    And this is because we’re using online chapel.

    [00:19:05.592]
    We’re using IBM Watson

    [00:19:07.862]
    to allow us to actually are certain

    [00:19:10.061]
    questions and respond with certain information

    [00:19:12.892]
    that is combined with men. Dicks

    [00:19:14.892]
    data

    [00:19:16.011]
    the information about our orders information

    [00:19:18.311]
    about so delivery times

    [00:19:20.741]
    are stored in the mend, its application and

    [00:19:22.842]
    supplemented with information from IBM

    [00:19:25.061]
    Watson

    [00:19:26.192]
    So we’ve trained this box here to respond

    [00:19:28.471]
    to certain questions.

    [00:19:30.061]
    So if we say I would

    [00:19:32.162]
    like to know the

    [00:19:34.201]
    status

    [00:19:35.721]
    off my order,

    [00:19:42.192]
    it will ask me for the order i

    [00:19:44.251]
    d. We can use the order I d that

    [00:19:46.261]
    we created earlier. So it was

    [00:19:49.142]
    S I

    [00:19:51.491]
    3779

    [00:19:57.951]
    and it will respond back with the status

    [00:19:59.971]
    for this particular order so we can see now

    [00:20:02.162]
    it’s currently in the manufacture tree stage.

    [00:20:04.787]
    So I looked up that particular order in

    [00:20:06.817]
    the medics application and presented

    [00:20:09.086]
    a particular stage toothy user now

    [00:20:12.086]
    within this chap. But we’ve also embedded some

    [00:20:14.297]
    voice controls so that we can actually

    [00:20:16.386]
    use our

    [00:20:17.846]
    a p. I’s available in the Web

    [00:20:19.866]
    here to actually capture a certain

    [00:20:22.176]
    audio and convert that into test

    [00:20:24.856]
    so we can ask,

    [00:20:29.517]
    Tell me a joke.

    [00:20:32.467]
    We also we see it’s transcribed that

    [00:20:34.656]
    into text Nelle, and we can submit that

    [00:20:36.967]
    to our chat box,

    [00:20:38.487]
    and it will come back with a relevant joke.

    [00:20:40.537]
    In this case, Can a kangaroo jumped higher than

    [00:20:42.616]
    a house?

    [00:20:43.547]
    Of course, houses can’t jump.

    [00:20:46.336]
    So very intuitive chap

    [00:20:48.346]
    bought that we’ve created here

    [00:20:50.426]
    on. It just goes to show how easy

    [00:20:52.747]
    you can embed these type of experiences

    [00:20:54.906]
    in your application and bring a new

    [00:20:57.017]
    level of user experience to your consumers.

    [00:21:01.287]
    Now, as we’re going through this application, we might

    [00:21:03.576]
    decide you’re in the development stage

    [00:21:05.626]
    that we want to make a change. This application

    [00:21:08.186]
    on as a citizen developer, someone

    [00:21:10.537]
    from the business, I want to be able to make

    [00:21:12.767]
    those changes and being control of foes

    [00:21:15.636]
    and to do so every mend its application

    [00:21:17.886]
    has a feedback button on the right hand side

    [00:21:20.156]
    Here, this allows you to do a number

    [00:21:22.176]
    of things, allows you to submit

    [00:21:24.267]
    feedback for certain items that

    [00:21:26.517]
    you want to work on.

    [00:21:27.856]
    So by clicking on the feedback

    [00:21:29.906]
    icon here, we can enter certain

    [00:21:31.936]
    information.

    [00:21:33.136]
    And in this case, we’ve forgotten to aunt in

    [00:21:35.656]
    the descriptive text that we want

    [00:21:37.737]
    to add on also a example

    [00:21:40.307]
    delivery date for when we want this particular

    [00:21:42.807]
    item to be delivered to us

    [00:21:44.567]
    so we can enter some feedback. And we say I

    [00:21:46.866]
    would like

    [00:21:49.166]
    a delivery dates

    [00:21:52.086]
    on personalized

    [00:21:55.396]
    text

    [00:21:57.836]
    it sent.

    [00:21:58.977]
    This will send all of this information into

    [00:22:01.567]
    our online project management portal where

    [00:22:03.866]
    we gather those requirements, we can manage

    [00:22:06.054]
    the Mao and we can start to develop

    [00:22:08.054]
    our application together.

    [00:22:10.344]
    So if we switch now into the mend, its home

    [00:22:12.584]
    portal, this is where we can start to

    [00:22:15.034]
    manage out those feedback items.

    [00:22:18.003]
    So all applications built on the platform

    [00:22:20.463]
    will were built using theme index

    [00:22:22.503]
    online still here,

    [00:22:23.953]
    so you can manage your requirement, your

    [00:22:26.233]
    projects and invite a number of stakeholders

    [00:22:28.874]
    to those applications.

    [00:22:31.604]
    We drill down on this particular project we can see

    [00:22:33.693]
    in the feedback section. This is where we can manage

    [00:22:35.874]
    out those feet back.

    [00:22:37.243]
    We could view details about

    [00:22:39.273]
    who submitted them,

    [00:22:40.713]
    where they submitted them

    [00:22:42.203]
    on information such as, what

    [00:22:44.344]
    browser? They were on device, and

    [00:22:46.493]
    it will have a screen shot with it

    [00:22:48.983]
    as a product own. I can then decide whether I want

    [00:22:51.153]
    to accept or deny this particular request.

    [00:22:54.023]
    In this case, we can market has accepted

    [00:22:56.243]
    that we can market for a particular sprint.

    [00:22:58.693]
    This will create. It’s now a user story so

    [00:23:00.773]
    that we can collaborate with people from the business

    [00:23:03.054]
    and I t around that particular requirements.

    [00:23:06.903]
    So now we’ve got that particular requirement. We want to

    [00:23:08.933]
    go and implement it.

    [00:23:11.134]
    So it’s always important to have that change

    [00:23:13.153]
    request in place in order to trap

    [00:23:15.324]
    through all of the changes in the platform.

    [00:23:18.743]
    Now, if we go back to our application, one of the other

    [00:23:20.973]
    features that’s available is part his feeble.

    [00:23:22.993]
    But is this pencil icon?

    [00:23:25.513]
    If we press this, this will take us into the

    [00:23:27.544]
    edit mode within the men

    [00:23:29.683]
    Dick Studio.

    [00:23:31.044]
    If remember, back to my descriptions Mendik

    [00:23:33.233]
    studio. It focused, at sits and

    [00:23:35.304]
    developers

    [00:23:36.493]
    business users who want to be involved. You’re

    [00:23:38.523]
    in the development life cycle.

    [00:23:40.384]
    I want to be able to quickly update changes

    [00:23:42.693]
    in their browser here.

    [00:23:45.604]
    So the change we want to make is we want to add to

    [00:23:47.874]
    fields. The 1st 1 is we want to have

    [00:23:49.973]
    a text field so we can

    [00:23:52.334]
    input the personalized text

    [00:23:54.193]
    and we want a date picker so that we

    [00:23:56.273]
    can actually implement the information

    [00:23:58.284]
    such as the delivery day

    [00:24:01.314]
    Now in this Brown’s ahead. We could just simply

    [00:24:03.513]
    drag and drop Conseco design

    [00:24:05.653]
    first approach to application

    [00:24:08.074]
    build rather than building from a data

    [00:24:10.273]
    up. We can build from the pages

    [00:24:12.653]
    and then create the relevant data in our structure.

    [00:24:15.963]
    Two here on the left hand side here, ask us to select

    [00:24:18.233]
    an attribute. So where do we want it? And she stole

    [00:24:20.273]
    that data

    [00:24:21.604]
    and you’re noticing these selected attributes. We don’t

    [00:24:23.784]
    have a field yet for our personalized

    [00:24:26.344]
    text.

    [00:24:27.324]
    So let’s create a new attributes

    [00:24:29.773]
    to steal that information

    [00:24:38.173]
    and it will automatically associate that

    [00:24:40.443]
    particular field Now to our new data

    [00:24:42.653]
    writer. The final piece

    [00:24:44.683]
    you wanna add is a new date for the delivery.

    [00:24:47.943]
    So by leveraging the mending

    [00:24:49.943]
    studio. We can really empower our

    [00:24:52.094]
    developers and our business uses across

    [00:24:54.854]
    the enterprise.

    [00:24:56.213]
    So again, we don’t have a field for that particular

    [00:24:58.594]
    delivery day. So we can just at that inn. Now,

    [00:25:05.753]
    when we run this application, what it will do

    [00:25:07.763]
    is it will build us this application.

    [00:25:10.153]
    It will connect to the database of our choice

    [00:25:12.273]
    on update all the fields necessary for

    [00:25:14.544]
    this particular application.

    [00:25:16.564]
    So all of those changes are completely version

    [00:25:19.023]
    now, and they will be checked out

    [00:25:21.233]
    on updated by our users

    [00:25:23.443]
    in the studio pro.

    [00:25:25.334]
    So if we want to actually pull those changes

    [00:25:27.453]
    through and check them out, what we need

    [00:25:29.503]
    to do is switch over to the studio Pro

    [00:25:31.644]
    environment,

    [00:25:32.614]
    and from there we can actually update

    [00:25:35.114]
    of view those changes that they’ve made.

    [00:25:37.344]
    Now, if I press update, what this would do

    [00:25:39.443]
    is it will lock the changes in

    [00:25:41.584]
    our Web modeler environment

    [00:25:43.384]
    so that they cannot change this

    [00:25:45.604]
    particular application whilst we’re

    [00:25:47.814]
    updating those versions.

    [00:25:49.864]
    So by doing this, we’re able to give control

    [00:25:52.604]
    to those technology uses

    [00:25:54.683]
    in the desktop environment

    [00:25:56.213]
    crunchy version a troll and check everything

    [00:25:58.513]
    before committing it into the main line.

    [00:26:01.733]
    So here. We’ve updated all those changes and if we go

    [00:26:04.023]
    into

    [00:26:04.903]
    our page here

    [00:26:06.233]
    will see those same changes in

    [00:26:08.443]
    our application.

    [00:26:09.884]
    So changes across both studios

    [00:26:12.453]
    are kept in sync.

    [00:26:16.324]
    So now we’ve got those changes to our application.

    [00:26:18.773]
    We need somewhere to deploy this

    [00:26:20.794]
    on. The great advantage of mandates is

    [00:26:22.834]
    that we can deploy application and

    [00:26:24.933]
    run it in any Kyle stack on

    [00:26:26.943]
    premise or private cloud offering

    [00:26:29.584]
    giving true flexibility of England to deploy

    [00:26:31.854]
    and utilize any type

    [00:26:33.854]
    of infrastructure.

    [00:26:36.874]
    Now, for this application is connected up to

    [00:26:38.993]
    our medics Cloud.

    [00:26:40.644]
    If you go back to the developer portal,

    [00:26:42.703]
    this is where we can manage out those environments

    [00:26:45.554]
    on. We can see certain versions off this

    [00:26:47.554]
    application being built.

    [00:26:50.034]
    Now. One of the major advantage of Bendix is that every

    [00:26:52.273]
    part of the platform has an A p I,

    [00:26:55.084]
    including the bill capabilities.

    [00:26:57.614]
    So being out of build a new version and deploy

    [00:26:59.913]
    into an environment,

    [00:27:01.334]
    this is especially important when

    [00:27:03.473]
    building out your own devil pes tule chains.

    [00:27:06.413]
    In this case, we build out our own Dev up Still

    [00:27:08.634]
    change for this demo which levels it leverages

    [00:27:11.163]
    Amazon Alexa

    [00:27:12.413]
    to build and employ our application

    [00:27:15.134]
    so we can ask, Like so

    [00:27:17.513]
    asked Mendez t build my app

    [00:27:24.183]
    building Revision 82 with version number

    [00:27:26.483]
    1.0 dot zero.

    [00:27:29.483]
    So we can see here that

    [00:27:31.023]
    they’ve

    [00:27:32.023]
    started a builder application will see

    [00:27:34.253]
    our screen here updates with

    [00:27:36.443]
    the new build

    [00:27:42.384]
    here. We also we have 82

    [00:27:44.263]
    currently being built once it’s built,

    [00:27:46.294]
    were able to then stage it into

    [00:27:48.473]
    acceptance and production by using

    [00:27:50.653]
    the voice capabilities again.

    [00:27:54.084]
    So now there are application is being built.

    [00:27:56.693]
    We can ask.

    [00:27:58.114]
    Alexa

    [00:27:59.834]
    asked minutes to deploy my app to

    [00:28:01.963]
    acceptance.

    [00:28:05.153]
    Deploying version one. Don’t theory. Don’t

    [00:28:07.384]
    0 82 to acceptance.

    [00:28:12.104]
    So now that we’ve initiated

    [00:28:14.153]
    that particular build on deploy

    [00:28:16.554]
    into acceptance, it will go through that

    [00:28:18.653]
    process of updating application, updating

    [00:28:21.384]
    the relevant data base and then make this

    [00:28:23.493]
    particular version available on our acceptance

    [00:28:26.034]
    environment.

    [00:28:36.604]
    So we can see here. The APP has

    [00:28:38.653]
    stopped on acceptance

    [00:28:56.003]
    so we can see here now Our application

    [00:28:58.104]
    is updated with the new version.

    [00:29:00.253]
    We can actually go interview that application now

    [00:29:02.614]
    in our browser.

    [00:29:03.903]
    So we deployed out to an environment

    [00:29:06.233]
    running on the mend. Its clouds

    [00:29:07.844]
    in this case amend its cloud runs with car foundry.

    [00:29:10.064]
    A DBS is our infrastructure

    [00:29:12.173]
    around for scale and portability

    [00:29:14.794]
    across environments.

    [00:29:16.794]
    So we see here we have our new personalized

    [00:29:18.804]
    texts on delivery day deployed

    [00:29:20.913]
    out to our acceptance environment.

    [00:29:25.163]
    So in the last 30 minutes, we’ve been able

    [00:29:27.344]
    to demonstrate to you how the medics platformer

    [00:29:29.753]
    dresses,

    [00:29:30.804]
    multi device experience platforms

    [00:29:33.394]
    and how we can leverage the capabilities

    [00:29:35.874]
    to bring great user experience to

    [00:29:38.183]
    our users across device

    [00:29:40.394]
    on also across interface.

    [00:29:43.403]
    I hope you’ve enjoyed this loco than 30.

    [00:29:45.773]
    Make sure you check out our community weapon

    [00:29:47.894]
    are which we running later this month,

    [00:29:50.403]
    which will cover some or user

    [00:29:52.413]
    interfaces such as wearable devices

    [00:29:54.913]
    via hololens

    [00:29:57.864]
    will now move on to the question and answer

    [00:29:59.903]
    section.