Deliver Delight: Why Native Mobile Matters

Users are unforgiving when it comes to their mobile experiences—85% of people are unlikely to do business with a company following a bad mobile experience. Can you afford to not be delivering true native mobile apps?


  • Transcript

    [00:00:00.920]
    Hello and welcome to low code and 30

    [00:00:03.160]
    I’m Jeff Goldberg, part of the evangelist

    [00:00:05.330]
    team at Bendix.

    [00:00:06.969]
    In this webinar, we’re going to discuss

    [00:00:09.150]
    native mobile applications

    [00:00:11.359]
    and why they’re key to enhancing

    [00:00:13.410]
    your employees work experience

    [00:00:15.410]
    and how men dicks eases native

    [00:00:17.570]
    mobile app development

    [00:00:18.850]
    so you can accelerate your business

    [00:00:22.480]
    Loco and 30 is a monthly webinar, Siri’s

    [00:00:25.170]
    dedicated to educating business, and

    [00:00:27.429]
    I t on the benefits of low

    [00:00:29.480]
    code application development.

    [00:00:31.929]
    You may watch any of our previous webinars

    [00:00:34.329]
    on the medics YouTube channel

    [00:00:36.100]
    or visit www

    [00:00:38.340]
    dot mend IX dot com.

    [00:00:40.579]
    Ford slash demos.

    [00:00:43.439]
    We’ve covered a range of topics over

    [00:00:45.460]
    the past year, including citizen Development,

    [00:00:48.060]
    I ot

    [00:00:49.140]
    Dev ops

    [00:00:50.229]
    Aye, aye and machine learning

    [00:00:51.829]
    as well as multi experience platforms

    [00:00:54.600]
    of which will drill into a bit further today

    [00:00:57.030]
    with our discussion on Native Mobile.

    [00:01:01.270]
    Today, our journey begins on the topic

    [00:01:03.579]
    of experience.

    [00:01:05.439]
    Customer experience. To be more specific

    [00:01:08.609]
    from there, will travel into the mobile

    [00:01:10.739]
    application development world and

    [00:01:12.859]
    learn about the different options available

    [00:01:15.390]
    and why men dicks low code approach

    [00:01:17.629]
    to native mobile development

    [00:01:19.319]
    is a customer experience game changer,

    [00:01:22.599]
    then a first for low code and 30

    [00:01:25.219]
    I’ll be joined by Yost Landman

    [00:01:27.159]
    from Rob a bank, and we’ll talk about

    [00:01:29.159]
    robbing banks, journey with Bendix and the

    [00:01:31.189]
    experience his team is having making

    [00:01:33.489]
    native Mobile applications with Bendix.

    [00:01:37.920]
    In one of my past jobs,

    [00:01:39.939]
    I had the pleasure of working for a

    [00:01:41.950]
    restaurant chain of bakery cafes

    [00:01:44.299]
    who made it a point

    [00:01:45.939]
    to make the experience of going

    [00:01:47.980]
    to their stores feel like entering

    [00:01:50.620]
    an everyday oasis.

    [00:01:53.090]
    What this meant, of course, is that when a customer

    [00:01:55.569]
    walks into a store,

    [00:01:57.200]
    ah, warmth swirls around them

    [00:01:59.329]
    along with the smell of fresh baked

    [00:02:01.340]
    goods, making them feel

    [00:02:03.700]
    like they’re part of a community

    [00:02:05.840]
    and in a place where they can relax

    [00:02:08.069]
    from the stresses of the day.

    [00:02:10.840]
    Back in the early two thousands,

    [00:02:12.960]
    this concept of customer experience

    [00:02:15.830]
    it existed.

    [00:02:17.340]
    But it wasn’t as in your face as it is

    [00:02:19.539]
    today.

    [00:02:21.039]
    When you look around

    [00:02:22.419]
    customer experiences in something as

    [00:02:24.530]
    small as the design on top of a cappuccino,

    [00:02:28.270]
    the efficiency for which we can transact

    [00:02:30.330]
    business,

    [00:02:31.580]
    the memories made fresh again through nostalgia

    [00:02:34.969]
    to the wonder the world of virtual reality

    [00:02:37.580]
    conjures to life

    [00:02:41.530]
    in 2018

    [00:02:43.139]
    customer experiences with your brand

    [00:02:45.379]
    started with an interaction on

    [00:02:47.580]
    a mobile phone

    [00:02:48.770]
    more than 50% of the time.

    [00:02:52.439]
    Well, that may be via a website.

    [00:02:55.020]
    Once the customer is engaged,

    [00:02:57.569]
    they expect the more refined

    [00:03:00.060]
    experience, a dedicated mobile

    [00:03:02.099]
    app that’s interactive and fluid,

    [00:03:04.900]
    ready to make their life easier.

    [00:03:08.000]
    The goal here for the APP maker is stickiness,

    [00:03:11.039]
    and it’s in these first touch points where

    [00:03:13.110]
    customer perceptions are cemented

    [00:03:15.689]
    and become very difficult to change

    [00:03:17.979]
    over time.

    [00:03:19.639]
    In fact, in a recent poll,

    [00:03:21.939]
    almost 85% of respondents

    [00:03:24.590]
    stated that they are unlikely

    [00:03:26.599]
    to repeat engaging with companies

    [00:03:28.939]
    offering a poor mobile experience.

    [00:03:33.139]
    And over 30% of those respondents

    [00:03:36.000]
    stated they would tell others

    [00:03:38.169]
    about the negative experience.

    [00:03:40.610]
    With network effects like that, it’s clear

    [00:03:43.610]
    customer experience is a key differentiator

    [00:03:46.620]
    for the success of brands.

    [00:03:50.439]
    At this point, you may be saying,

    [00:03:52.469]
    so what? Who cares?

    [00:03:54.539]
    We won’t sell directly to external customers.

    [00:03:57.669]
    Customer experience is for someone else

    [00:03:59.710]
    to worry about.

    [00:04:01.840]
    Okay,

    [00:04:02.939]
    that’s fair.

    [00:04:04.439]
    But what about your internal customers?

    [00:04:06.840]
    Your employees,

    [00:04:10.039]
    your employees are customers of lift,

    [00:04:12.900]
    Amazon,

    [00:04:14.039]
    Apple,

    [00:04:15.039]
    Google,

    [00:04:16.110]
    Microsoft

    [00:04:17.300]
    Pinterest

    [00:04:18.339]
    and many more brands they see

    [00:04:20.529]
    every day on their mobile phones.

    [00:04:23.040]
    These companies are raising the stakes for

    [00:04:25.110]
    success in the marketplace because they

    [00:04:27.199]
    obsessively focus on customer

    [00:04:29.250]
    experience.

    [00:04:30.839]
    Consequently,

    [00:04:32.100]
    your employees expect better

    [00:04:34.529]
    customer experiences from the Alps,

    [00:04:36.750]
    the use for work

    [00:04:39.100]
    and when they have to do things manually

    [00:04:41.329]
    or log into multiple systems to see

    [00:04:43.470]
    despair, it data

    [00:04:45.000]
    it impacts their engagement

    [00:04:47.009]
    with your company

    [00:04:48.240]
    and with your customers.

    [00:04:52.339]
    I’ll give you an example that serves as a

    [00:04:54.410]
    great transition into the native mobile

    [00:04:56.579]
    part of our conversation today.

    [00:04:59.220]
    Recently,

    [00:05:00.259]
    some of my colleagues were riding up the elevator

    [00:05:03.079]
    to our office.

    [00:05:05.040]
    They were standing next to a field service

    [00:05:07.209]
    worker delivering packages

    [00:05:09.560]
    to the offices in the building.

    [00:05:12.639]
    She had three

    [00:05:14.339]
    yes, three mobile devices in

    [00:05:16.360]
    her hands,

    [00:05:17.839]
    all of them necessary for her to do

    [00:05:19.879]
    her job.

    [00:05:21.639]
    Why,

    [00:05:23.089]
    she said that her job required

    [00:05:25.649]
    data from each one of the

    [00:05:27.709]
    devices.

    [00:05:29.240]
    And while headquarters can see the

    [00:05:31.279]
    data from all three

    [00:05:32.959]
    in one interface,

    [00:05:35.139]
    she’s left toe eyeball

    [00:05:38.040]
    data from one

    [00:05:39.730]
    device to the other

    [00:05:41.540]
    and try to correlate the correct information

    [00:05:44.410]
    related

    [00:05:45.500]
    to where she’s going

    [00:05:46.870]
    and what she’s delivery.

    [00:05:49.939]
    Part of this may be due

    [00:05:52.439]
    thio each device having a special attachment

    [00:05:54.759]
    like some sort of scanner

    [00:05:56.329]
    or a special app that’s designed

    [00:05:58.790]
    for a specific purpose.

    [00:06:02.290]
    Nevertheless,

    [00:06:03.769]
    the friction created from this user

    [00:06:05.870]
    experience

    [00:06:06.980]
    this internal customer experience

    [00:06:09.439]
    has a negative effect from end

    [00:06:11.629]
    to end on the experience chain.

    [00:06:14.949]
    This is where low code and native mobile

    [00:06:17.230]
    come together and solve this problem,

    [00:06:19.660]
    propelling customer experience from the reactive

    [00:06:22.720]
    to the proactive.

    [00:06:30.009]
    Regarding mobile application development,

    [00:06:32.420]
    there are a lot of flavors to choose

    [00:06:34.439]
    from for creating, developing

    [00:06:36.949]
    in making

    [00:06:38.240]
    applications.

    [00:06:39.939]
    But four

    [00:06:41.339]
    different styles stand out today

    [00:06:43.829]
    as the main types

    [00:06:45.329]
    of applications that a developer

    [00:06:47.579]
    or anyone can create.

    [00:06:51.839]
    Native mobile applications, sometimes

    [00:06:53.930]
    called pure native mobile,

    [00:06:55.750]
    are developed using traditional coding languages.

    [00:06:58.740]
    Objective C and Swift for IOS

    [00:07:01.620]
    and Java and Conklin for Android.

    [00:07:05.040]
    Pure native mobile applications offer superior

    [00:07:07.610]
    performance and the tightest integration

    [00:07:09.759]
    with device capabilities

    [00:07:11.569]
    because the languages are optimized

    [00:07:13.579]
    for the operating systems.

    [00:07:16.269]
    The tradeoff is that the pure native

    [00:07:18.439]
    application development

    [00:07:20.189]
    isn’t cross platform,

    [00:07:21.930]
    so you have to maintain two separate code bases,

    [00:07:24.639]
    often using separate development teams.

    [00:07:27.610]
    Puree native is expensive because

    [00:07:29.689]
    it takes more time, resource is

    [00:07:31.709]
    and specialized skills

    [00:07:33.800]
    to build and maintain

    [00:07:37.839]
    hybrid applications are more like a website

    [00:07:40.110]
    for mobile than a true app.

    [00:07:42.540]
    they use HTML, CSS and

    [00:07:44.720]
    JavaScript to create an experience

    [00:07:46.959]
    wrapped in what is called a Web. You

    [00:07:49.279]
    tow work on mobile devices

    [00:07:51.009]
    and be packaged for APP store distribution.

    [00:07:54.339]
    Hybrid applications, Air Cross platform

    [00:07:56.540]
    using frameworks like Cordova and

    [00:07:58.550]
    Phone Gap. To wrap the application and

    [00:08:00.779]
    provide access to device capabilities,

    [00:08:04.139]
    hybrid APS take less time to make

    [00:08:06.329]
    and maintain

    [00:08:07.709]
    impure native APS.

    [00:08:09.879]
    Unfortunately,

    [00:08:11.220]
    developer efficiency gains result

    [00:08:13.250]
    in subpar user experience.

    [00:08:16.089]
    In addition, the rise of progressive

    [00:08:18.370]
    Web, APS and React native

    [00:08:20.430]
    are demonstrating that Cordova and Phone

    [00:08:22.629]
    Gap are showing their age and

    [00:08:24.750]
    waning support among the community.

    [00:08:30.029]
    Progressive Web APS are an advancement on

    [00:08:32.120]
    the hybrid approach. However. They’re

    [00:08:34.259]
    designed to run in standard Internet

    [00:08:36.409]
    browsers like Chrome,

    [00:08:38.509]
    which makes them cross platform.

    [00:08:41.429]
    Progressive Web APS aimed to deliver an

    [00:08:43.539]
    experience similar to a native app,

    [00:08:45.809]
    using service workers connecting the

    [00:08:47.840]
    APP to device capabilities.

    [00:08:50.440]
    P W ays deliver a smooth

    [00:08:52.710]
    user experience and work even

    [00:08:55.000]
    when end users aren’t proud Sing.

    [00:08:57.220]
    Because of these service workers,

    [00:09:00.440]
    PW ways aren’t without trade offs

    [00:09:02.919]
    because they aren’t native code.

    [00:09:05.110]
    They drain the battery faster.

    [00:09:07.330]
    In addition, while P W ays

    [00:09:09.350]
    offer access to device capabilities,

    [00:09:12.000]
    it’s inconsistent and dozen support

    [00:09:14.399]
    all the features. Native APS do

    [00:09:20.110]
    react. Native is a job, a script library

    [00:09:22.759]
    that makes it possible to create mobile

    [00:09:25.080]
    applications that are nearly indistinguishable

    [00:09:28.049]
    from native applications. Made

    [00:09:30.100]
    using Objective C or Java.

    [00:09:33.019]
    It’s directly native, which means react

    [00:09:35.309]
    native ties directly into

    [00:09:37.559]
    native code, toe access, OS styling

    [00:09:40.070]
    and device capabilities.

    [00:09:42.740]
    Because it’s JavaScript

    [00:09:44.580]
    reactive, it’s cross platform

    [00:09:47.240]
    development is faster and less expensive,

    [00:09:50.139]
    and there are many more developers with JavaScript

    [00:09:52.679]
    skills than pure need of

    [00:09:54.700]
    experience.

    [00:09:57.019]
    Standing up a react Native project is

    [00:09:59.100]
    challenging because the library itself doesn’t

    [00:10:01.379]
    have Dev ops built into it.

    [00:10:04.120]
    While of react. Native has a large and diverse

    [00:10:06.340]
    ecosystem of components and native

    [00:10:08.620]
    device integrations.

    [00:10:10.330]
    Getting into the native code may be necessary

    [00:10:12.840]
    from time to time

    [00:10:14.210]
    if what is needed has not been done

    [00:10:16.409]
    before.

    [00:10:20.340]
    So I’ve been talking a lot about the different types

    [00:10:22.899]
    of

    [00:10:23.929]
    frameworks and technologies you can

    [00:10:26.029]
    use to make mobile applications.

    [00:10:28.139]
    But what does that have to do with men? Dicks?

    [00:10:31.139]
    Well, medics being a low code

    [00:10:33.210]
    application development platform and

    [00:10:35.600]
    a general purpose one at that

    [00:10:37.539]
    actually gives you the possibility to

    [00:10:39.679]
    make

    [00:10:40.879]
    a number of these different types of

    [00:10:43.000]
    mobile applications in one

    [00:10:45.490]
    project from a single Kobe’s.

    [00:10:48.080]
    So with men dicks, it’s possible to make

    [00:10:50.370]
    hybrid applications,

    [00:10:52.090]
    progressive Web applications

    [00:10:54.200]
    and now native mobile

    [00:10:56.279]
    applications, all from

    [00:10:58.720]
    the same code base.

    [00:11:01.039]
    How is this possible?

    [00:11:03.139]
    Well, because men Dicks takes a model

    [00:11:05.429]
    driven approach

    [00:11:06.629]
    toe application development. It enables

    [00:11:09.019]
    the platform to abstract

    [00:11:11.049]
    away the complexities of using

    [00:11:13.669]
    these

    [00:11:14.559]
    different mobile application

    [00:11:16.940]
    development technologies.

    [00:11:19.139]
    As a result,

    [00:11:20.669]
    the developer experience is the same

    [00:11:23.190]
    regardless of what type of mobile application

    [00:11:25.799]
    you wish to make.

    [00:11:27.389]
    Furthermore,

    [00:11:28.840]
    because men dicks is extensible,

    [00:11:31.940]
    developers are empowered

    [00:11:34.100]
    toe add capabilities using

    [00:11:36.340]
    code. So using Java script

    [00:11:38.779]
    in this case,

    [00:11:40.100]
    or Java,

    [00:11:41.440]
    which then become reusable dragon

    [00:11:43.970]
    drop widgets and actions that

    [00:11:46.210]
    the rest of the development team can take

    [00:11:48.320]
    advantage of

    [00:11:51.710]
    At medics, we chose to

    [00:11:53.740]
    integrate react native into the

    [00:11:55.820]
    low code development experience that

    [00:11:58.019]
    we pioneered

    [00:11:59.529]
    because we recognize hybrid APS

    [00:12:02.129]
    do not meet the consumer grade

    [00:12:04.429]
    standards

    [00:12:05.509]
    and users expect from

    [00:12:07.559]
    their enterprise applications.

    [00:12:11.840]
    React. Native

    [00:12:13.039]
    has a very high regard

    [00:12:15.110]
    in the tech community, with over 10,000

    [00:12:17.490]
    contributors on get Hub

    [00:12:19.090]
    and has backing from brands like Facebook,

    [00:12:21.720]
    the originators of the framework,

    [00:12:24.090]
    Microsoft

    [00:12:25.379]
    over and many more

    [00:12:27.799]
    companies.

    [00:12:31.809]
    The benefits of bringing men dicks, low

    [00:12:34.070]
    code development capabilities together

    [00:12:36.659]
    with react natives, Native

    [00:12:38.750]
    Mobile application development capabilities

    [00:12:41.929]
    is that

    [00:12:42.840]
    you get all the benefits of react

    [00:12:44.899]
    native. In addition to that,

    [00:12:47.210]
    you get all of the Dev ops

    [00:12:49.559]
    that men dicks brings to bear out of the box.

    [00:12:52.539]
    So all of that hard scaffolding

    [00:12:54.870]
    of new projects for react native

    [00:12:57.139]
    projects

    [00:12:58.100]
    that goes away it’s a simple is just

    [00:13:00.350]
    creating a new app and boom,

    [00:13:02.519]
    you’re right in the environment and your building.

    [00:13:06.039]
    That visual development

    [00:13:07.600]
    with Paige templates, building blocks

    [00:13:09.659]
    and snippets increases

    [00:13:11.779]
    the front end development efficiency

    [00:13:14.210]
    so that you can reuse different

    [00:13:16.840]
    front end elements over and over

    [00:13:18.879]
    again. And you can

    [00:13:21.029]
    easily style and chase us, and I’ll

    [00:13:23.039]
    talk about that in a moment.

    [00:13:25.220]
    Do you reuse and share model

    [00:13:27.830]
    and control aspects of a nap with

    [00:13:29.840]
    other channels

    [00:13:31.059]
    in the same project?

    [00:13:32.720]
    So let’s say you’re building a responsive Web

    [00:13:34.990]
    application

    [00:13:36.240]
    along with a new application

    [00:13:38.379]
    that has hybrid

    [00:13:41.639]
    capabilities.

    [00:13:43.240]
    In addition to that, you can add native

    [00:13:45.500]
    Mobile right in the same project and

    [00:13:47.600]
    use the same domain model and use

    [00:13:49.809]
    the same micro flows and functions

    [00:13:52.879]
    to provide

    [00:13:54.690]
    the appropriate user experience for

    [00:13:56.860]
    the appropriate channel that

    [00:13:59.259]
    the application is intended for.

    [00:14:03.340]
    It’s easy to customize the properties

    [00:14:05.490]
    for the widgets

    [00:14:07.139]
    and the front and elements in the development

    [00:14:09.230]
    experience because they’re all built

    [00:14:11.259]
    with react.

    [00:14:12.940]
    And that’s the great thing, because you get to take

    [00:14:15.039]
    advantage of react natives extensive

    [00:14:17.460]
    library

    [00:14:18.450]
    of components through mend explicable

    [00:14:20.820]
    widgets and JavaScript action capabilities.

    [00:14:23.460]
    So if there’s a react which it you like to

    [00:14:25.509]
    use, you can drop that in and start

    [00:14:27.549]
    using it and create a reasonable component.

    [00:14:31.940]
    Lastly,

    [00:14:33.919]
    this combination of low code

    [00:14:36.240]
    and react native together

    [00:14:38.389]
    gives you the ability

    [00:14:39.970]
    to spend more time focusing on solving the

    [00:14:42.049]
    problem

    [00:14:42.960]
    and enhancing the user and customer

    [00:14:45.009]
    experience

    [00:14:46.129]
    than spending time writing code,

    [00:14:48.740]
    because that low code

    [00:14:50.470]
    capability

    [00:14:51.769]
    enables you to move faster

    [00:14:54.240]
    and build that seem

    [00:14:56.440]
    high quality output.

    [00:15:00.240]
    So what we’ve accomplished at Bendix is an

    [00:15:02.299]
    abstracted cross platform

    [00:15:04.389]
    approach

    [00:15:05.309]
    to delivering native mobile applications

    [00:15:07.690]
    faster than traditional coating

    [00:15:09.899]
    at a lower total cost

    [00:15:11.789]
    without sacrificing quality

    [00:15:14.250]
    in the output.

    [00:15:18.450]
    Recently, I had the opportunity to

    [00:15:20.610]
    collaborate on an application with my team.

    [00:15:23.639]
    At first I was skeptical of what

    [00:15:25.830]
    I’d be able to achieve, creating native

    [00:15:27.960]
    pages and taking advantage of device

    [00:15:30.090]
    functionality.

    [00:15:31.940]
    What I found is that the developer experience

    [00:15:34.470]
    is identical to building any other

    [00:15:36.769]
    kind of medics application.

    [00:15:39.279]
    It was really cool to be ableto add barcode

    [00:15:41.730]
    scanning to the AP,

    [00:15:43.110]
    sets in properties for styling in data

    [00:15:45.269]
    can activity and then see the APP

    [00:15:47.470]
    refresh happened over the air instantly

    [00:15:50.210]
    and start using the capability

    [00:15:52.440]
    that I just

    [00:15:53.669]
    added to this application.

    [00:15:56.639]
    I understand this sounds a bit self serving

    [00:15:58.740]
    because I worked for medics.

    [00:16:00.529]
    So let’s talk to a customer and learn

    [00:16:02.759]
    more about their experience using

    [00:16:04.860]
    medics to build native mobile

    [00:16:07.230]
    applications.

    [00:16:12.240]
    Today, I’m joined by Yost Landman

    [00:16:14.279]
    from Rob a bank. Yost is a business

    [00:16:16.370]
    architect using medics to build native

    [00:16:18.669]
    mobile applications.

    [00:16:20.440]
    Yost Thanks for being with us for low code

    [00:16:22.610]
    and 30

    [00:16:23.940]
    Thank you for inviting me. Great to be here.

    [00:16:27.100]
    You tell our viewers a little bit about

    [00:16:29.250]
    rob a bank and what it is that you do for the company.

    [00:16:32.940]
    OK, Rob a bank is

    [00:16:35.049]
    one of the three large banks

    [00:16:37.120]
    in the Netherlands. Domestically, it’s focuses

    [00:16:39.610]
    on retail banking, but internationally

    [00:16:42.019]
    it’s primarily focused on

    [00:16:44.460]
    banking for food, and this means we

    [00:16:46.700]
    finance food and agriculture business

    [00:16:48.990]
    and in that international area. My role

    [00:16:51.299]
    as ah this is architect is to drive

    [00:16:53.529]
    the architect You’re efficient and road map in

    [00:16:55.809]
    both the domain of financing

    [00:16:58.470]
    farmers

    [00:16:59.889]
    and the domain of what we call

    [00:17:02.070]
    international direct banking. And

    [00:17:04.170]
    that’s all about online retail savings.

    [00:17:06.980]
    Rabobank has been amended customer

    [00:17:09.230]
    for a few years now. Can

    [00:17:11.250]
    you tell me a little bit? Why

    [00:17:13.380]
    rob a bank chose medics to develop

    [00:17:15.710]
    applications a few years ago

    [00:17:17.759]
    in this Ah, this area of online

    [00:17:20.049]
    retail savings.

    [00:17:21.440]
    We were going through a transformation

    [00:17:24.440]
    for ah well, Rabobank, Belgium

    [00:17:26.769]
    and hobble direct in Germany. Because

    [00:17:29.019]
    over the years those banks have grown into,

    [00:17:31.160]
    ah, situation

    [00:17:33.839]
    where we had expensive beckoned systems

    [00:17:36.740]
    at an online banking channel that was

    [00:17:39.460]
    difficult and slow to change.

    [00:17:42.539]
    This costs our savings money

    [00:17:44.829]
    so that the savings that we gathered

    [00:17:46.900]
    from retail customers

    [00:17:48.789]
    to be quite expensive on.

    [00:17:50.960]
    At the same time, the customer experience

    [00:17:53.130]
    in that Web channel was liking behind

    [00:17:55.299]
    compared to the competition.

    [00:17:57.789]
    So we have decided Thio

    [00:17:59.970]
    well, basically redesigned the complete I D

    [00:18:02.150]
    landscape and

    [00:18:03.329]
    for the online banking general, we chose

    [00:18:05.369]
    to build it in such a way that would be

    [00:18:07.549]
    faster change and at the same time, relatively

    [00:18:10.140]
    low cost

    [00:18:11.440]
    on the solution. We, ah, we found,

    [00:18:13.730]
    was a combination of

    [00:18:16.940]
    just a basic

    [00:18:18.240]
    off the shelf web content management

    [00:18:20.410]
    system.

    [00:18:21.309]
    For all the static content in

    [00:18:23.359]
    the Web channel

    [00:18:24.640]
    with a no coat application

    [00:18:27.349]
    platform to build all the interaction components

    [00:18:30.380]
    on that no coats

    [00:18:31.829]
    platform,

    [00:18:33.289]
    the one we chose was medics

    [00:18:35.789]
    because it ah, for us it stood out

    [00:18:38.009]
    from its competition

    [00:18:39.980]
    in ah, user

    [00:18:42.380]
    interferes design and in beckoned

    [00:18:44.480]
    integrations.

    [00:18:45.740]
    So that’s how we, uh, came in contact with

    [00:18:47.819]
    men dicks. And you have I

    [00:18:50.180]
    remember hearing you spoke it. Ah,

    [00:18:52.190]
    use book, a medics world. And I remember

    [00:18:54.390]
    he’s starting off your presentation.

    [00:18:56.809]
    You said

    [00:18:57.750]
    1,000,000

    [00:19:00.200]
    customers

    [00:19:01.220]
    using our

    [00:19:02.730]
    medics built, swept, gentle

    [00:19:04.789]
    for online banking. Yes. So

    [00:19:07.109]
    now you’re making native mobile

    [00:19:09.250]
    APS

    [00:19:10.240]
    with medics. And

    [00:19:12.640]
    can you tell me a little bit about

    [00:19:14.740]
    these mobile absent your building

    [00:19:16.859]
    and the problems that they saw off?

    [00:19:19.240]
    Yes. We’re gonna be building ah

    [00:19:21.279]
    mobile labs for ah again Kabul,

    [00:19:23.390]
    Bank Belgium, and have a direct in Germany.

    [00:19:26.740]
    And, um,

    [00:19:27.980]
    a couple of years ago, we actually had ah

    [00:19:30.369]
    mobile app for, ah,

    [00:19:32.400]
    aisles and Androids,

    [00:19:34.650]
    but it just proved too expensive

    [00:19:36.829]
    to maintain and to

    [00:19:39.069]
    keep improving it.

    [00:19:40.740]
    This is a fairly small team and

    [00:19:43.170]
    there is a real cost pressure.

    [00:19:46.359]
    So now, in order to

    [00:19:48.740]
    at the same time keep the cost low,

    [00:19:50.750]
    but also the customer experience high.

    [00:19:53.269]
    We, um,

    [00:19:54.740]
    wants to build our mobile app

    [00:19:57.339]
    in the same technology as a Web channel

    [00:19:59.720]
    so we can have the same team building

    [00:20:01.890]
    and maintaining it

    [00:20:03.339]
    on dhe and also so we can share

    [00:20:06.089]
    of the technical components between the Web

    [00:20:08.170]
    Channel and the mobile F General.

    [00:20:10.240]
    We really wanted to build this mobile

    [00:20:12.329]
    app with medics

    [00:20:14.440]
    with the IOS and android app. So you have to maintain

    [00:20:16.789]
    those separately and with a small

    [00:20:18.900]
    team that becomes really difficult to do that.

    [00:20:21.549]
    And one of the things

    [00:20:23.009]
    with building the maid Native mobile

    [00:20:25.410]
    app with Bendix is you get that cross

    [00:20:27.460]
    platform capabilities that react native

    [00:20:29.630]
    brings to the table so you can build

    [00:20:31.789]
    once and basically deployed to two

    [00:20:33.940]
    both operating systems. Is

    [00:20:35.990]
    there something special about the native

    [00:20:38.250]
    app versus going with a hybrid

    [00:20:40.890]
    or with the progressive Web application

    [00:20:43.839]
    that made you choose the native

    [00:20:45.890]
    path versus some other options

    [00:20:48.069]
    that you have in mobile application development.

    [00:20:51.599]
    Yeah, we actually tried to build

    [00:20:53.920]
    ah hybrid at first,

    [00:20:56.579]
    So we tried to ah, drives

    [00:20:58.619]
    the harbor bath initially,

    [00:21:01.819]
    and ah,

    [00:21:02.970]
    I have to tell you building and maintaining

    [00:21:05.059]
    a mobile app that offers a

    [00:21:07.180]
    good experience in the first

    [00:21:09.410]
    place. But it’s also very

    [00:21:11.410]
    secure, as you would expect for a bank is

    [00:21:13.430]
    actually not that easy.

    [00:21:14.789]
    And in our small team, we can’t

    [00:21:16.920]
    have a lot of security

    [00:21:19.230]
    expert. He’s on the floor. So we decided

    [00:21:21.539]
    to use it off the shelf, authentication

    [00:21:24.740]
    on basically security as decayed to give

    [00:21:26.910]
    us a head start in that area

    [00:21:28.940]
    and build a proof of concept integrating

    [00:21:31.920]
    that security solution that has its

    [00:21:34.210]
    own native screens for

    [00:21:36.240]
    things like Logan and transaction signing. And we

    [00:21:38.289]
    try to integrate that with ah, hybrid

    [00:21:40.549]
    app built with Mannix.

    [00:21:43.539]
    We got it working perfectly fine in the

    [00:21:45.549]
    end, but

    [00:21:47.430]
    well, we

    [00:21:48.880]
    we realized while evaluating

    [00:21:50.880]
    that technical skills that we would need

    [00:21:53.339]
    to maintain this would be our

    [00:21:55.519]
    to facilitating, is in a small development

    [00:21:57.980]
    team because we will. We actually needed quite

    [00:22:00.250]
    a few different technical skills

    [00:22:03.180]
    to

    [00:22:04.200]
    integrate the

    [00:22:05.579]
    native part with the hybrid part,

    [00:22:08.640]
    So he uses X Ken and switch

    [00:22:10.940]
    from, Ah, hybrid screen doing native scream

    [00:22:13.230]
    and back

    [00:22:15.140]
    and, uh, come back in

    [00:22:17.460]
    the right context.

    [00:22:20.259]
    Right? And at the same time, we realized it’s well,

    [00:22:22.859]
    as you know, building hybrid app.

    [00:22:25.349]
    User experience will be,

    [00:22:28.809]
    well, average at best.

    [00:22:32.539]
    We just didn’t want to settle for that

    [00:22:36.019]
    exactly that moment

    [00:22:37.740]
    way

    [00:22:39.750]
    were in contact with mandates. A

    [00:22:41.769]
    ll the time, of course. But they they

    [00:22:44.329]
    recognized it and offered

    [00:22:46.599]
    this Ah, back then, brand new

    [00:22:48.690]
    and still beta feature of react

    [00:22:50.950]
    native

    [00:22:51.880]
    on dhe. Well, that seemed to actually solve both

    [00:22:54.180]
    the skills issue for us as well as that

    [00:22:56.240]
    user experience issue.

    [00:22:59.339]
    Perfect match.

    [00:23:00.940]
    What’s their experience been like so far

    [00:23:03.460]
    developing native Mobile with

    [00:23:05.470]
    Bendix? What? What’s that been

    [00:23:07.619]
    like and what they like about it?

    [00:23:10.039]
    Well, the team tells me, um,

    [00:23:13.269]
    that these modeling environments in

    [00:23:15.579]
    Mannix ate it works like a charm. It’s ah,

    [00:23:18.640]
    it was fully stable. Said it couldn’t actually build

    [00:23:20.890]
    the features they

    [00:23:22.089]
    they want to build in the sprint, and it works a

    [00:23:24.180]
    nice and and also there. Ah,

    [00:23:27.190]
    really excited. How are manic state?

    [00:23:29.410]
    Makes it easy to write their ah,

    [00:23:31.759]
    custom widgets to integrates with

    [00:23:34.059]
    any react native libraries.

    [00:23:36.309]
    That’s just amazing.

    [00:23:38.759]
    I’ve I’ve been working

    [00:23:41.089]
    with it now for the past

    [00:23:43.319]
    few weeks in the preparation for

    [00:23:45.650]
    this webinar and as

    [00:23:47.720]
    someone who’s

    [00:23:49.220]
    not a traditional developer

    [00:23:51.569]
    but someone who’s learned to develop

    [00:23:53.569]
    software over the years. I was

    [00:23:55.599]
    just blown away by

    [00:23:57.140]
    how easy the modeling environment

    [00:23:59.269]
    makes it for you to be able

    [00:24:01.380]
    to create these consumer great experiences

    [00:24:04.339]
    and then go ahead

    [00:24:06.539]
    and test them out and and see

    [00:24:09.329]
    the result of that

    [00:24:11.650]
    in such a short period of time. It’s just

    [00:24:14.170]
    it’s just a great experience. I imagine your team

    [00:24:16.309]
    feels very simple, amazing, with the basic

    [00:24:18.759]
    understanding of how I D developments

    [00:24:21.240]
    works

    [00:24:22.299]
    that you actually able to do so much more

    [00:24:24.609]
    with Bendix.

    [00:24:25.539]
    It helps you doing the

    [00:24:27.619]
    things that’s that

    [00:24:29.339]
    before we’re only it

    [00:24:31.430]
    could only be done by by

    [00:24:33.549]
    experience. Development,

    [00:24:35.640]
    yes, and in the platform basically

    [00:24:38.089]
    helps them through the complete lifecycle

    [00:24:40.599]
    management as well,

    [00:24:42.240]
    so they can basically focus on delivering

    [00:24:44.640]
    functionality instead of on

    [00:24:46.839]
    on all the technical things that they

    [00:24:48.880]
    also have to do in

    [00:24:51.400]
    in other circumstances.

    [00:24:54.640]
    Yeah, I’m also impressed You know, we’re

    [00:24:57.019]
    now three releases into

    [00:24:59.839]
    the general availability

    [00:25:01.900]
    of the native mobile capabilities,

    [00:25:04.099]
    and the R and D team and the

    [00:25:06.119]
    products team are batting new functionality

    [00:25:08.539]
    every month to the capability. I imagine

    [00:25:10.839]
    your team is always watching

    [00:25:13.369]
    what’s new coming out that they be ableto

    [00:25:15.990]
    take advantage of in these Absent their building.

    [00:25:20.240]
    Yeah, absolutely, absolutely

    [00:25:22.940]
    well, Yost it’s great to hear

    [00:25:25.029]
    that things are going so well for

    [00:25:27.150]
    you at Rabobank and

    [00:25:29.460]
    the progress that you’re making using

    [00:25:31.650]
    Native Mobile and that it’s able to do

    [00:25:34.369]
    the things that you needed to be able

    [00:25:36.470]
    to do, especially with Bendix, to solve

    [00:25:38.559]
    the problems that you have and also

    [00:25:40.940]
    provide these consumer grade opportunities

    [00:25:43.200]
    to customers.

    [00:25:44.140]
    So thanks so much for your time and for joining

    [00:25:46.369]
    us today. Thank

    [00:25:49.170]
    you for having me

    [00:25:55.589]
    to recap were all being trained

    [00:25:57.869]
    to expect a frictionless customer

    [00:26:00.220]
    experience from all of the channels

    [00:26:02.920]
    companies and employers engage

    [00:26:05.460]
    with us.

    [00:26:06.970]
    The smartphone is a main driver

    [00:26:09.279]
    for capturing more of our mind share,

    [00:26:12.039]
    and it’s because makers of the apse

    [00:26:14.279]
    know

    [00:26:15.230]
    that users will interact with them or

    [00:26:17.670]
    if the experience reduces friction

    [00:26:20.180]
    and makes their lives easier.

    [00:26:25.940]
    That’s why I’m Index gives you freedom

    [00:26:28.230]
    to choose what kind of experience you

    [00:26:30.390]
    want to deliver to your customers.

    [00:26:32.980]
    The platform enables you to make hybrid

    [00:26:35.440]
    P W A and native mobile

    [00:26:37.740]
    applications, all from the same code

    [00:26:39.920]
    base, so it becomes a business

    [00:26:42.089]
    decision which technology you want to use

    [00:26:44.599]
    to make your mobile application.

    [00:26:46.740]
    What’s great is that there is this great

    [00:26:49.049]
    reusability across all three

    [00:26:51.140]
    mobile app types.

    [00:26:52.539]
    So as your needs change men, Dicks

    [00:26:54.670]
    makes it possible to reuse and adapt

    [00:26:57.369]
    what you have

    [00:26:58.500]
    to make your applications.

    [00:27:00.940]
    As Yost Land been stated,

    [00:27:02.940]
    Rob, a bank chose medics because

    [00:27:04.980]
    it’s team can move fast, keep

    [00:27:07.309]
    costs low and deliver

    [00:27:09.599]
    a great customer experience all

    [00:27:11.660]
    at the same time.

    [00:27:13.240]
    In addition, his team enjoys the

    [00:27:15.259]
    medics developer experience because it

    [00:27:17.289]
    gives them the flexibility to model

    [00:27:19.809]
    new features and extend their applications

    [00:27:22.589]
    using the latest and greatest technologies.