Flutter for Business (Mobile World Congress ‘19)

Flutter for Business (Mobile World Congress ‘19)

[SPEAKING SPANISH] Hi, welcome to Mobile
World Congress. I’m Martin Aguinis and I
lead marketing for Flutter at Google. We’re so excited
to be back here. In fact, we were here
exactly a year ago where we launched our first beta. And we can’t wait
to show you what’s been going on ever since. But before we get
into that, I want to share something
that blew my mind. We spend 15% of our time
every day on our phones. That’s over 10
years of our lives. Let’s think about
that for a second. 10 years is how long
it takes us to go through both primary
and secondary school. 10 years ago, many of us had
BlackBerrys in our hands. And companies like Tesla,
Instagram, and Spotify didn’t even exist 10 years ago. Not only that, but we
check it 52 times a day. I see some of you checking
it right now, actually. So this intense use of
mobile brings us back to Maslow’s hierarchy of
needs, which explains, as many of you know,
that we, as human beings, have needs at the bottom, like
basic needs– like food, water, shelter– and at the top,
self actualization. And I’m actually
really excited today to announce a shift
in this hierarchy. We’ve been working on this
research for about five years now. And here are the
latest findings. [LAUGHTER] I’m sure many of you can relate. I think we can actually
add one more layer to this. Now you might be thinking,
Martin, I get it. We use our phones a lot. It’s how we get around, it’s
how we talk to our families and friends, it’s how we check
the news, it’s how we navigate. There’s no way I would have
found this stage otherwise. So it transformed
life as we know it. And it’s completely
revolutionized how customers are
engaging with brands. In fact, the global
app economy is growing at a 37% year-over-year rate. So, given this important
time spent on mobile, I want to introduce
you to Flutter– Google’s toolkit for building
native apps on iOS and Android from a single code base. Today we’re going to talk
about Flutter from three perspectives– business, development,
and design– because Flutter is built to
help with all of those parts. This first talk is
Flutter for business. In fact, Flutter
started within Google because we, as Google,
wanted a great way to develop native apps
without any compromise. And we now use it for our most
revenue-generating product, Google Ads. But it’s also in our
DNA to be open source and to share things
with the world. So from day one, Flutter has
been free and open source for everyone to use. And, in fact, since
MWC last year, we’ve seen global brands from
all around the world using Flutter to
build their apps. And these apps have
powered more than– have powered– [CHUCKLES]
for more than hundreds of millions of users are
downloading these apps. In fact, today we have the
privilege of hearing directly from some of these brands. They’ll come up on stage and
kind of talk to you directly. So what are we going to cover? I’m going to start by reminding
us of some of the challenges that we all have when building
apps for our businesses. And I’m going to talk
about how Flutter addresses these challenges. Then, we’ll actually,
like I mentioned, bring up partners
and talk about how they’ve used it in different
ways and talk about next steps. So I hope that after
this presentation you walk away
better understanding how Flutter helps
your businesses and how you can get started. So let’s start with challenges. Obviously there’s a lot
of challenges associated with building apps
or none of you would be here
watching this today. To visualize some
of these challenges, I thought it’d be fun to play
a little game of roulette. So can someone please yell
out a number zero through 36? AUDIENCE: 29! MARTIN AGUINIS: 29, all right. Let’s test your luck today. Number called was 29– ooh, eight. So you didn’t get it right. But you only had a 3% chance
of getting that number right. And according to AppsFlyer,
only 3% of new mobile app users remain active after 30 days. In other words, if we were
to download an app today, and a hundred people were to
download it, only three of them would be active
users after a month. Shocking, right? Retaining users is one of
business’s biggest challenges today because we have
such high expectations. But it’s not the only one. Here are a few other challenges
that I want to remind us, that I’m sure many of you– I see some of you
nodding– can relate to. So things like time
to market, being able to launch and
iterate your app quickly. High quality look and feel– being able to really
understand that this is a high-quality app,
that’s a native app. Because given that
3% number, users have very high expectations
for their apps. And finally, affordability. It’s not news to you that
it can be really expensive, both in terms of time and money,
to make these applications. So these challenges
all still exist because the current options out
there all involve compromise. In fact, there are two main
ways to build apps today, each which pose a different set
of compromises on these four priorities. We call it the dilemma of
mobile app development. Here’s option one– and this is
what I’d say around 80% of you still do today– which is build two completely
separate iOS and Android applications on two
separate code bases. This requires double the
development teams, it requires, oftentimes, double the money,
and obviously at the end you get a beautiful
result, which is represented by that castle. But to get there, you have a lot
of those compromises like time, like affordability, which
represents that maze. So what’s the alternative? Well, several
companies have created third-party cross-platform
toolkits and these get you there a lot faster
because they’re one code base. But the end quality
is not the same. You don’t get that castle. Why? Well, because oftentimes
they use a web language like JavaScript and then
it actually converts it to the native phone. So what you’re using to build
these cross-platform apps aren’t actually native apps. And we’ve all been
in the situation where you’re seeing
an app and it’s a little bit laggy or there’s
something off and you can tell. And if you’re going to
invest the time to make apps, again with that 3% number
I gave you earlier, it’s really important for
it to be high quality. So another set of compromises
on those four priorities. Flutter’s a third
approach, one that falls for neither of
these sets of compromises. It’s fully native. Everything written in
Flutter compiles directly to native machine code, meaning
what you get on your phone it is exactly what was written. There’s no context switch. But it’s also a
single code base. So you get that straight
path to the castle. Now, at Google,
we’ve been building this for last four years. And we’re really proud of
the progress we’ve made. So now I’d like to show
you a video of a company that many of you might be
familiar with who have recently used Flutter. [VIDEO PLAYBACK] [MUSIC PLAYING] [END PLAYBACK] MARTIN AGUINIS: So I want
to spend the next few slides talking about these
four priorities and how Flutter is different. And hopefully you’ll
understand how you don’t have to compromise
on them with Flutter. So first, reach and retention. Flutter let’s you reach
all of your users. Oftentimes when you’re building
for both iOS and Android, you have certain platform
dependencies– things like scrolling or navigation,
which are fundamentally different on every device. And it’s one of those situations
where we, as users, expect that to happen. So when you’re in
an app and it’s scrolling like an iOS
app on an iOS iPhone– you understand, right? No problems. But when something’s
off, we get really upset. And we’re like, what
is this technology? So, obviously, with
high expectations, we expect apps to have
those behaviors already. Well, Flutter incorporates
all these behaviors directly into the framework. So you and your
development teams can focus on building the app,
knowing that it will already have these critical platform
differences in the app itself because it’s fully native. So if you wanted to customize
a very iOS looking app, you could do that. You can also build a
very brand-looking app and still have those
critical platform differences incorporated. Secondly, time to market. Let me run you through a typical
process, a traditional process, of building mobile apps today. You sit at the computer,
you start writing some code. And then you want to see
the changes, you compile it, which takes about 60 seconds. And then you actually have
to deploy it to the device with the emulator, which
takes, let’s say, 20 seconds. So now you’re looking at
the screen and you say, oh, there’s– I found a bug. So you have to go back, you
have the find where the code is and change it, then you
have to, again, compile it– another 60 seconds– then deploy
it– another 20 to 30 seconds– and on and on. And every time you
discover a bug or an error, you have to go
through this process. Inefficient, right? We, as Flutter, identify that. And so we put something in
a Flutter that changes it, called Stateful Hot Reload
what Stateful Hot Reload is it’s the ability to
change things in your app in real time, in
less than a second, and see it directly appear on
the app as you’re developing. So if I wanted to change
the color of the application or move something a pixel
to the left, I could do it and in 200, 300,
400 milliseconds see it appear on
the application. And that’s what actually ships. As you can see in
the example here, we’re using Hot Reload to
change the word “click to push” and we’re also changing
the business– the logic, so that when you
count, it actually counts down instead of up. And so you can see Hot Reload
happening in real time. And, again,
developers love this. And it allows you to keep
your development teams focused and the developers
to focus on what– actually building
the app, rather than having to wait between
all these builds. Third, Flutter allows you
to build beautiful apps. Oftentimes, a designer
will make something really, really beautiful, hand it to the
developer, and what’s shipped is a little bit different. It’s not actually that dream
of it that a designer had. So for example, to
the left, you can see what a designer made
for this airline app. We have things like a
custom branded menu bar, we have nicely style tabs. On the right is what
actually shipped. It was a lot easier to use
the standard menu bars, it’s a lot easier to
use the generic style. And by the time you
want to incorporate, you kind of run out of time. So you end up compromising. With Flutter, you never
have to compromise or ship an app that’s not as beautiful
as you want it to be. So designers can sit
with the developers and actually build exactly
what they want branded, which you’ll see in a lot of
the app examples later today. So, finally, affordability. I don’t need to stand
up here and tell you that it’s expensive to
build apps because we all know it can get expensive. But not only is
Flutter itself free, it actually allows you to
unify your development teams, it allows you to have a
lot faster and better test and build cycles,
and it also allows you to have that coordination
between designers and developers. So you’re not tied to
that very large budget to get that great app shipped
in a matter of months. So many of us
remember the feeling we had when we first
started building websites. You could go make a
change in the site and immediately see the changes. Mobile, not so much. Flutter was started by
engineers at Google who have been in web and
mobile for a very long time and have identified
these pain points. And that’s why we’re seeing so
much excitement around Flutter. So, given that, today I’m really
excited to officially announce the release of Flutter 1.2. [APPLAUSE] You can go to flutter.dev
and download it directly, or if you already have
Flutter, simply update. The key theme of this is
some polish, bug fixes, and top customer requests. We also have a lot
of great things, like new framework
features and localization. And we’ll actually
get into the details on the next session, which is
a Flutter for developers talk, in terms of what’s included. But I did want to call out a
few other themes that we’re launching alongside 1.2. We are launching a brand new
YouTube channel dedicated only to Flutter. So on there you can find
videos from technical videos for your developers to
really understand Flutter, to case study videos
like the one we just saw, to a lot of other
things that are helpful when you’re building
or going through Flutter. Also Flutter is,
again, open source. So we’ve also seen
some awesome videos from community members
who have volunteered their time to just make
tutorials and other things as well. So you could find it a
lot of it on YouTube. Secondly, we just
launched Flutter Create, which is a competition
for developers to build an app in Flutter
in less than five kilobytes of Dart code. And we have some
really cool prizes but it’s also a fun way
to get quickly involved in the Flutter community and
onboarded with the platform. And that runs until April so
you should go check that out. So now I want to
take a look at some of the apps that have shipped
since we were here last year at Mobile World Congress. [MUSIC PLAYING] So all the apps you
saw up there use Flutter, but in different ways. Now, there are three common ways
people are using Flutter today. The first is to
build a brand new app from scratch using Flutter. So if you have an idea
or an app that you want for your business, now
would be the perfect time because you develop
in one place, ships natively on all platforms. The second way is to actually
build Flutter for the other OS. What we mean by that
is, if you already have an iOS or an
Android application and you want to build the
other one to reach more users, you can build that
other one with Flutter and get it out quickly
and eventually merge the code bases. And thirdly, add Flutter
to your existing app. I’m sure many of you and
your businesses already have applications. The good news is you can
use Flutter for that. In fact, that’s what Alibaba did
in the video you saw earlier. They incorporated Flutter to
re-brand some of their pages, but they didn’t lose the
50 million installs they had– it was simply an update. Instead of me telling you
about all these use cases, I thought it’d be great to
show you a firsthand example and bring up partners
as well to talk about how they’ve
incorporated Flutter in these different ways. So the first is building a brand
new app for iOS and Android, which we’ve seen
many companies do. And I actually I’m
going to show you a video that we filmed just
a few weeks ago in India with Dream 11, which is India’s
biggest fantasy sports company that just shipped
another use case, we see, is building Flutter
for iOS or Android when you already have one. Given that the market
share, obviously– a lot of places that
Android’s a little bit bigger, but there’s still a lot
of users that are on both. Many times, it’s important. And so to talk
about this directly, I want to bring up
on stage Dom, who is head for Abbey Road Studios– digital media. DOM DRONSKA: Hi, everyone. I’m Dom. I’m Head of Digital for Abbey
Road Studios, presumably the most famous and definitely
the oldest studio– recording studio– in the world. And today I’d like
to talk to you how we’re at 87 years of innovation
brought us here on the stage and to build our very
first mobile app, created with Flutter. So what do you think? When you hear
Abbey Road Studios, you probably think about– well, yes, the Beatles. Of course, and for
the right reasons. Not only they gave us
our name, but they also created around 80% of
the music in our studios. And there’s very
good reason for it. They were, essentially,
innovators. They pushed the sonic
boundaries of what was possible in recorded music. And they kept coming back
to Abbey Road Studios because over there they had
engineers and technical tools to make that happen. They wanted to innovate
and we listened and we helped them
to innovate, as well. So the Abbey Road is
the very first purposely built recording studio in
the world, which essentially makes us a start, a beginning,
of music industry as a whole. And it’s a place of crucial
digital innovations, such as stereos. Stereos were invented there. We built our very first
recording desks, mixing consoles, mastering consoles. It’s where the first and
the audio R&D department was set up in the ’50s
of the last century. It’s also where, a
few years ago, we set up the very first music
startup incubator, a home to developments such as smart
microphones, alternative music apps. So we kept innovating. I think this is kind of in
our DNA to watch musicians out there and to do
what’s best for them, to take risks and develop
to innovate technology. And that brings us into Topline. We quite quickly
notice, as Martin, was talking about that
quite a lot of musicians are using mobile and
mobile phones in the music creative process. As we’re using mobiles
for everything, why wouldn’t be
using them to create? So people are kind of
capturing the song ideas. They try to collaborate or
they’re using their email, mobiles to demo the idea of
the sound to someone else. But they struggled
with it a little bit. Basically, there aren’t many
tools out there available which make that possible
for the musicians. So we decided to create
Topline, the very first song writing app from
Abbey Road Studios. This app allows you to
import an instrumental track, single your
vocals on top of it, jot lyrics, share very easily
with a producer, whoever else you’re working with,
and save it all in the Cloud. And when we decided to
do that, we quite quickly created the
prototype and then we had to make that very
important decision. All right, what we going to do? This is the dilemma
Martin talked about. Are we going to
develop for iOS, are we going to develop for Android? We had limited resources,
naturally, and limited budget, as well. So we developed
for iOS initially and immediately were flooded
with requests for Android. They were coming from all
sorts of different directions from the world, all over
our Facebook, Twitter, all sort of channels. We were really overwhelmed
and quite intimidated by the volume. We didn’t expect that at all. So we knew we had
to develop Android. To be true to our vision
of democratization of music making, we
had to develop it fast. We had to give people
that free tool. And we knew we needed help. And that’s when we met Flutter
team, Google Flutter team. And that this is the very first
mobile app from Abbey Road Studios, so, for us, that
was a learning curve. It was a hard, hard task. So we had to rely
on a framework, on Flutter framework, and on the
forum, as well, and the Google team, as well, to
help us to do that. We worked very closely
with our users. We really wanted for that
process to be user driven. So we had a group of
around 100 musicians around the world,
mostly unsigned, speaking to us daily and
feeding features and feeding bugs daily. So they are all
responsible for this map search you’re seeing there. So when you don’t remember
when you recorded your idea or what was it,
you almost always remember the context,
where you were, so we can find it on the map. They are responsible
for the back button, they’re responsible for
the number of the tracks. So they were feeding
those features so fast, we had to keep up with them. And all of that
wouldn’t be possible if it wasn’t for
Hot Reload function. So because of that,
we were actually able to sit our developers
next to the musicians for them to feed and costly
test and iterate. Thanks to that our, UX process
was around 10 times quicker. And I think we can proudly
say that this app was actually designed by musicians and
with musicians at heart. We are really inspired
by the studio experience. And this is what we try to kind
of reflect within the studios, within this mobile app. So, most of the
musicians out there, they know what it means
when the red light shines. It means you’re on air,
you’re supposed to start, so we reflected that in the app. We reflected the shapes,
the shapes of the buttons, the faders, as well, the shapes
of the little knobs there. Those are things which are
usually known to musicians and they know what
to do with it. And all of that
was only possible with the high customization
of the natively available elements. So we had to use customizable
widgets from Flutter and that really made that
beautiful UI shining through. Thanks to the plugins and
thanks to the widgets, we were able to animate
and were able to bring it, the whole experience, to life. And I know it’s hard to
believe, but we quite like the pressure of time. I didn’t think
about it back then, now I can actually say that. That really made
us focus and lean and kind of on point with
everything we’ve done. But that was a hard task. We worked on that project
quite early on last year, so early in 2018. And back then, we worked
with pre-beta Flutter, so super early on. And also, we are trying to
build Android app and audio apps on Android. And very popular, there
aren’t to many of them– for the right reasons. It’s a complex platform,
really fragmented, the audio [INAUDIBLE]
is really demanding. So we kind of, quite early
on we ran into a problem. So we’ve got those four
tracks within the app, as visible on the previous
screens, up to four tracks recording. And whilst you’re kind
of recording audio, that audio then has to be
processed to digital signal, and then has to
be played in sync. And we quite quickly discovered
that from one Android device to another, all of
those tracks were out of sync and out of time. And for musicians, that’s
the end of the road. Like there is no musicians out
there could who’d kind of agree to record and then have it
out of time because that’s– that was, for us, also
a massive showstopper. So we had to develop
a workaround. But that workaround wasn’t
really a tech workaround, we basically gave control
to the users for them to be able to their
buffering time. And to do that,
yet again, we had to rely on Hot Reload function. And when we had our
multiple devices running with the Android
version of the app and we had to test the buffering
from one device to another, Hot Reload really made
it possible for us. So thanks to that, thanks
for all the help from Flutter and for stability of even
at such early release of the framework, we were
able to actually build the Android up in
record 10 weeks! 10 weeks, guys. And this is with just
three developers– two front end and one
Android developer. And this is massive. I’ve built apps all
my life and I actually think that there is
one of developers I’ve built app with
my previous company somewhere in the
audience, as well. And, believe me, my
previous music apps– Android, didn’t take 10 weeks. It took, literally,
months, if not even years. So this is amazing success
on a technical level. And when we finally released
both and when we kind of made it available to all the
people around the world, we had a great success. It was not only used by
musicians around the world and in the studios, but also
it was picked up by the media– by Forbes, Music
Radar, MusicAlly, Sky News, Pocket-lint,
Metro, what have you. Lots of lots of titles
got really interesting and were really
complimentary about our app. And then, finally, last
year we won two really, really prestigious awards– Best Music UK App of The Year
and Best UX to the Year– UX and Design of the Year. And that last one’s
especially important to us because we really wanted the
app to be there for the users, for the musicians, and really
wanted to capture that great UX experience for them. And the judges of
that competition said that the use of our
app leaves a warm place in musician’s heart. And this is definitely
something a sentiment, which is worth all the
effort we went through. And this is what
innovation means to us. It means actually taking
risks, but definitely listening to your users and developing
things to solve their problems. That’s definitely not the
end of the road for us. We really want to work
with partners like Google, with startups as well,
in order to innovate and in order to create more
of those amazing tools. We hope to push the
boundaries of Flutter 1.2, now, in order to be
even more integrated within the audio layers. We really want to
make sure that there is more and more audio apps
on Android and across devices. We want to really–
our startups to enjoy the cross-platform
approach across kind of the speed and
affordability Flutter offers. And then, finally, if any
of you are failed musicians, like most of us on stage– or maybe you
haven’t failed yet– please download Topline
let us know what you think. We’d love to hear from you. Thank you very much, guys. MARTIN AGUINIS: Thank you, Dom. I love this story. I think it’s really cool,
just having follow that app. And not just Topline,
we’ve actually seen apps build with
Flutter featured on both iOS and Android for their designs
and the ways they were built. And examples this is the
Hamilton Broadway musical app, as well, and the
Reflectly app, which you’ll hear about
later today, which is a top meditation app that was
really well designed for iOS. So here’s another exciting part
about Flutter, as I mentioned, which is adding into
your existing apps. And today, I want to
bring up on stage Varun, from Groupon, to talk about
how they’ve done this. VARUN MENGHANI: Hi, everyone. I’m Varun Menghani, and I lead
the Merchant Product Management team at Groupon. So for those of you who are
not familiar with Groupon, Groupon is an online marketplace
where people discover and save on amazing things to
do, see, eat, and buy. And just to give you an example
of the scale of operations, we have almost 50 million
customers worldwide and have worked with up to
a million merchants to date. Our team specifically
focuses on the merchant side of the marketplace,
where we build tools so that merchants can interact
and engage with Groupon and their customers. And the mobile app, the
Groupon Merchant mobile app, is a very important
part of the toolkit in today’s mobile-first world. The app, just to give you some
context, is almost five years old. And it’s deployed on
thousands of devices, actively used by merchants to
redeem vouchers, view payment, and sales reports, respond to
customer feedback, and so on. So our journey with Flutter
started almost a year ago where we were tasked with building
functionality for merchants on Groupon’s as new
program, called Groupon+. At that time, we evaluated
multiple options. Should we build a brand new
app for the new program? Should we extend our
native functionality for this new program? Should we take a
cross-platform approach, to build once and deploy twice? And that’s the time we
came across Flutter. When we looked at
it, we were very excited by its
capabilities of being able to build cross device and
also the speed of application development. However, we also wanted to make
sure that whatever we build integrates well into our
existing functionality and it is stable, and
it’s also performing, so there is no
performance degradation when but when merchants
use the app for business. We ran a POC and we were
pleasantly surprised by the results. And that’s the point at which
we built all the screens and the functionality of our new
Groupon+ program for merchants using Flutter and integrated
that with the existing screens. So what we did was we released
a new experience into the market where if a merchant was a
part of the Groupon+ program, they would see the
Flutter screen, they would see the
new experience. And if a merchant was
an existing merchant, they would continue to see
the existing experience. With the success
of that program, once we released the app,
we found the performance to be really great. We were happy with the overall
implementation of the project and the success of that. We also continue to use Flutter
in other new features that we build, a prime example being
when we revamped the app support for all our merchants–
not only the Groupon+ ones but also the regular ones, And with that, we are excited
to continue building on Flutter. Just to call out some
of the key benefits that our team sees in
working with Flutter is the speed of application
development, the lower learning curve of learning
Flutter as compared to other cross-platform
tools, the test stability and maintainability,
we think that’s really great. And, finally, to quote one
of my Android developers, he says, using Flutter
is also pure fun. So with that, we are excited to
continue building with Flutter. And I’d like to hand
it back to Martin. [APPLAUSE] MARTIN AGUINIS: I see
some of your faces light up when I put
monetization on the slide. Because being able to
make money through apps, obviously especially for
businesses, is important. And we, as Flutter, know this. So we actually have a lot of
integrations with third parties to help with this. And today I want to welcome up
on stage Carl Perry from Square to talk about their
integration with us. [APPLAUSE] CARL PERRY: So as Martin
said, my name’s Carl. I’m the lead for Square’s
developer platform. I’m thrilled to be here today
to talk about our partnership with Flutter. To date, actually, we
found out about Flutter and got engaged really
early in the beta. And we’ve been
incredibly excited and amazed at the
passionate engagement that we see in the
developer Flutter community on a daily basis. In particular, we want to make
it easy for every developer to build applications that take
payments remarkably easy when using Flutter. So I have a question. I always ask questions
in the beginning. How many people
here know Square? And how many of you have heard
the mission that Square has? Not many people, I’ll
tell you really quickly. Our mission at Square
is that we believe that the economy is
better when everybody has access and participates. Nobody should be left out
when the cost is too great or the technology too complex. Our goal is to
enable every seller to participate in the
economy by building beautiful and
remarkable solutions and products that help make
running their business much, much easier. Square started with a really
simple yet revolutionary idea that everybody–
everybody here– should be able to take
a credit card payment. And with the introduction
of our little white reader, we enabled every seller to
participate in the economy by taking credit card
payments directly from their smartphones. Since then, we’ve increased
both the breadth and depth of our product
offerings and solutions. We started initially with our
general purpose, point of sale, and have recently expanded by
providing vertical solutions in Square for restaurants,
square for retail, and square for Appointments
These solutions are targeted at sellers
within these domains and helps them run the entirety
of their business end to end. Additionally, we have solutions
like Square Capital, which provides loans to businesses
so they can grow their business more quickly. The ecosystem of solutions
enables sellers to run, as I said, the entirety
of their business. Since our founding, we’ve
processed over $250 billion in payments. Over 50% of all of our GDP,
or gross payment volume, comes from large sellers. And finally,
Square’s NPS of 70 is one of the highest in
the technology space, and, I believe, reflects
our relentless focus on building remarkable
experiences and solutions that helps sellers more easily
run their business. Our developer platform
is the foundation of the Square ecosystem. It not only deeply
integrates and connects our own first-party
solutions and products, but it enables any developer
to also deeply integrate into those products and
expand the set of solutions that are available to any
seller in the Square ecosystem. In the last year,
we’ve added support for in-person and in-app
payments to our platform. With those two releases, we now
provide a multi-channel payment platform that
enables any developer to build solutions to take
payments in any channel that a buyer may discover
a seller’s products in. We handle payment security
so that you don’t have to. When you’re using Square’s
SDKs and also our solutions, we take care of
every payment type. We enable you to take and
accept all major credit and debit cards. We also accept
digital mobile wallets like Samsung Pay, Apple
Pay, and Google Pay. Our hardware,
software, and SDKs are compliant with PCI standards
and EMV regulations. Any time updates are made
to any of these standards and regulations– it’s
actually happening right now– we take care and we
take on the burden of updating our solutions
and SDKs to be compliant so that you don’t have
to worry about that. From the time that a
customer dips, taps, or swipes their
credit card, that data is encrypted and sent directly
to Square’s data processing environment. No customer data– no PII– is available on your servers,
either as the developer or the seller. All of this is
pre-configured out of the box and taken care of for you. Finally, we have a full-time
dispute management team that challenges all
charge backs that come in on behalf of sellers. We ask for some simple
information from the seller and then our team
takes that information, packages it up, and then sends
it to the banks and networks to challenge those disputes–
all at no additional fees. And finally, we use
machine learning across every single payment that
occurs in the Square ecosystem. With this information, we fight
fraud on behalf or sellers– regardless of whether
they take a single payment or tens of thousands of
payments, they’re protected. As I said earlier, we’ve
been following Flutter since the early beta
and we’ve been impressed with how it lets developers
quickly and easily create beautiful and performant
cross-platform applications. You’ve heard it again
and again, and you’ll hear it after this,
how easy it is to build those types of applications. That’s why we started
working on plugins for two of our flagship SDKs. Our goal is to
enable any developer to build an application that
take payments and, obviously, make money from
those applications. This is an example or a Flutter
plugin for In-app Payments SDK. It sounds like a really long
term, but what it is is it enables any developer to build
a consumer or buyer-facing application where the buyer
will enter their credit card information to
pay for a product. This application, or this SDK,
has an incredibly intuitive interface, which I’ll
actually show you in a minute, that
enables a developer to provide a rich
and guided experience to every mobile buyer when
using the application. Out of the box, in as little
as five lines of code. The Flutter plug-in
for Reader SDK enables any developer
to build solutions for a seller that has
very specific needs around their in-person
payment experiences they’d like to offer. We’re really excited
to enable any developer using Flutter to connect to
our award-winning card readers, and take secure
payments in person. Since launch, what
we’ve seen with Flutter is incredible adoption. In fact, over 30% of
active developers building applications using
our In-app Payments SDK are Flutter developers. Every one of those is building
an application for Flutter. And on the left
here, what you see, this is the actual
product experience you will get inside of your
application on Flutter. And this is in about
five lines of code. This guided
experience is provided to every single developer,
and then they’re able to customize many
different aspects of this as they see and need to
in their application. A great example
of an application that uses Flutter
and our Flutter plug-in for Square Reader SDK
is the Collins Family Orchard. Collins Family Orchard
is a local farmer from Eastern
Washington that grows a variety of organic
fruits at their farm. They then take that
produce and then go to Seattle, where I’m
from, and sell it at all of the local farmer’s markets. One of the things that
they wanted was they needed the ability to easily and
quickly flip between locations. And though Square was able
to meet most of their needs, they wanted to
build a customized app for their growing business. So they built a
branded application using Flutter and the
Flutter Square Reader SDK. And they were able to then
track and take all payments at every one of the
locals farmers markets and then switch quickly between
locations as they needed to. They continue to
update this application as they move forward. As you can see, it’s easy
to build applications that take payments using Flutter. We’re incredibly excited to
continue to work with Google and see what people
build with our SDKs. If you’d like more information
about the SDKs that we provide, go to squareup.com/flutter
and find out more there. If you want to talk afterwards,
I’m going to be here. Thank you very much. Back to Martin. MARTIN AGUINIS: Thanks, Carl. So now we’ve covered different
ways to build Flutter apps. We’ve covered ways to make
payments and make money off of them. And what’s the final step,
as a business, we care about? Actually testing and
deploying the application. So we, as Flutter, have
different partnerships with third parties,
as well, that help with this part,
this final step, of actually integration
and delivery of your apps. So now I want to bring up on
stage another Martin, Martin Jaret, who leads the business
development at Codemagic to talk about this. MARTIN JARET: Thanks, Martin. And hello, everybody. At Nevercode, we
believe that businesses should be able to
test and deliver mobile apps seamlessly
throughout the development process. You should be able to focus
on making a great product and have the testing and
delivery process automated. Before Codemagic, we’d been
building our automated testing and delivery product
with mobile developers in companies like Toyota,
Sainsbury’s, and Walmart. And we really delve deep into
the whole development lifecycle to understand what are
the bottlenecks that teams are facing to iterate
fast and deliver the apps to the hands of their users. We found that
development teams are losing anywhere between
$50,000 to $100,000 every year to all the manual work related
to testing and delivering. So, put into context, it’s
the equivalent of one person in a five-person
team on a holiday– all year round. So let’s think about this. To test the new
version of the app, the developer would need to
build it on the local machine, meaning they have to wait for
the build to finish before they can continue work. They would then personally send
it to the testers or designers, for example. Sometimes there could
be an update in one of the dependencies
that you’re using. And this could limit
the number of devices that you’ll be able to support,
or worse, the app might crash. So you would need to
continuously monitor the app in order to prevent this. Finally, to continuously
distribute the app, the team needs to maintain a
system to manage the versions, keep all the
software up to date, and make sure that the
artifacts are delivered to the correct members of the
team in the right environments. So if we actually
unravel the complexity behind testing
and delivering, we find that there is quite a big
overhead and development teams losing around 20%
of time that could be spent on iterating fast and
delivering apps to the users. Now, we’ve seen the
struggle that companies are facing when setting up their
development process for Android and iOS separately. So after seeing
what Flutter does and how it actually changes the
way mobile apps are developed, we decided to challenge
ourselves, as well, and re-engineer the whole
testing and delivery experience. And we made a dedicated
service specifically designed for Flutter. That service is Codemagic. And we automate
all the manual work to get your app to the users. Codemagic is a free
service and businesses can use it to test and
deliver their app seamlessly and developers can focus
on building a great product and making users happy. Codemagic automatically
builds your app in the Cloud with [INAUDIBLE] in the US. We continuously test the
app to prevent errors even before that they happen. Businesses can set
up multiple workflows and customize all
stages of the pipeline so that they can fit each
team’s specific use case. We can provide
custom integrations and dedicated builder machines
for enterprises working with multiple apps or workflows
that require concurrent builds. But most importantly, we provide
an out-of-the-box solution for testing and
delivering your apps. One of the most valuable
things we learned in this space is how important ease of use
and seamless adoption really is. And I guess you can say that
this is the secret that makes our automation process magical. We released
Codemagic in December together with Flutter 1.0. And since then, we’ve been
growing in Europe, Asia, Australia, and the Americas. And one of the numbers that
we’re really happy about is that, currently, we save
development teams over an hour of development time every day. Put into context,
it’s about $900 in your pocket every month– for free. Growing with Flutter,
we share similar values and hold the community
at a high regard. We stay active at meet ups
happening around the world because meeting the
community and engaging with the developers
really helps us to build a great product for them. But we want more. It’s not enough to
have a service to just test and deliver the apps. There should also
be a platform where testers can install the latest
artifacts, try out the builds, and leave feedback for the team. I’d like to share some
news with you all. Today, Nevercode this
joining the Flutter family of applications with a brand
new product written in Flutter– Testmagic. [APPLAUSE] Testmagic is a free
app built with Flutter. And we’ve made a
platform where you can distribute the latest
builds to your testers on real devices. You can test them and collect
feedback for the team. So in other words, we’ve created
this app release toolset, they’re an ecosystem,
if you will. This magic is built on the
same values as Codemagic with ease of use and seamless
adoption guiding the product development. We’ve involved the
Flutter community in the product
decisions to make sure that when businesses are
adopting the solution, the team is happier with
the user experience. And one of the things I’m
really excited, about whole team as well, is that
after the beta, we’re going to make
Testmagic open source. That’s going to be amazing. So if you’d like to
learn more about it, you can visit us
at testmagic.io. All in all, working together
with Google and the Flutter team, it’s been
absolutely amazing. And going forward, we’re
really looking forward to making new
solutions together. Thank you all so much. MARTIN AGUINIS: Flutter.dev is
your go-to link for everything. We really hope that you
found this presentation to be helpful in terms
of understanding Flutter and the different
things that we offer. As I mentioned at the
beginning, if we’re all spending 10 years of
our lives on a phone, we want to make those the
best 10 years of your life. We want to make sure you have
good experiences on your apps. So we hope you go
and try Flutter and give our team feedback. And I hope you enjoy
the rest of our talks here at Mobile World Congress. Muchas gracias. [APPLAUSE] [MUSIC PLAYING]


13 thoughts on “Flutter for Business (Mobile World Congress ‘19)”

Leave a Reply

Your email address will not be published. Required fields are marked *