Sharing a success story: A low-cost, customer-drive and co-developed Android EMM
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 90 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/47608 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
2
10
13
14
26
35
37
45
48
54
55
56
63
64
68
73
74
77
78
80
82
85
89
00:00
Android (robot)Enterprise architectureLaurent seriesComputer virusMultiplication signMetropolitan area networkExpert systemBitAndroid (robot)Cartesian coordinate systemMicrosoft CSystem callSpeech synthesisEstimatorProcess (computing)GoogolComplex (psychology)Computer animationMeeting/Interview
01:57
Compilation albumAndroid (robot)Laurent seriesEnterprise architectureExpert systemMultiplication signData managementFitness functionProof theoryDevice driverLatent heatWhiteboardComputer animationMeeting/InterviewLecture/Conference
02:51
Android (robot)Enterprise architectureLaurent seriesProjective planeField (computer science)Expert systemProof theorySurfaceGoodness of fitThermal expansionMilitary baseSoftware developerComputer animation
03:40
Android (robot)Enterprise architectureLaurent seriesGoogolEnterprise architectureSuite (music)Android (robot)Computer animationMeeting/Interview
04:31
Android (robot)Enterprise architectureLaurent seriesPressureSummierbarkeitFrequencyWeb pageVideoconferencingMultilaterationEnterprise architectureSound effectReal numberTorusWebsiteAndroid (robot)Revision controlComputer animation
04:55
Android (robot)Laurent seriesEnterprise architectureComputer networkDirectory serviceFunctional (mathematics)PredictionCovering spaceData managementGoogolInformation securitySynchronizationEncryptionTelecommunicationScalabilityProcess (computing)Office suiteLimit (category theory)Point cloudComputing platformView (database)Term (mathematics)Application service providerService (economics)Complex (psychology)Connected spaceDirectory serviceRevision controlAndroid (robot)Mobile WebFront and back endsInterface (computing)Software developerProjective planeSoftware frameworkWeb 2.0Video game consoleMultiplication signCartesian coordinate systemGoogolCovering spaceAnalytic setGoodness of fitGroup actionData management2 (number)Local ringProof theoryLoginProper mapPoint cloudServer (computing)Sinc functionOrder (biology)Table (information)Scaling (geometry)Mobile appEnterprise architectureInformationPersonal area networkVolume (thermodynamics)Set (mathematics)Machine learningSoftware as a serviceOpen setLimit (category theory)Software maintenanceReal numberBitService (economics)Internet der DingeView (database)Office suiteTelecommunicationProcess (computing)ScalabilityInformation securityEncryptionWebsiteÜberlastkontrolleContext awarenessVideo gameSource codeDecision theoryTraffic reportingComputing platformArchitectureData storage deviceAreaReal-time operating systemMusical ensembleSocial classControl flowEntire functionTrailFunctional (mathematics)Line (geometry)Device driverDisk read-and-write headOperator (mathematics)MathematicsExpert systemSource codeComputer animation
13:32
Application service providerComplex (psychology)Service (economics)Android (robot)Connected spaceTerm (mathematics)View (database)Enterprise architectureLaurent seriesServer (computing)VelocityMathematical optimizationPoint cloudArchitectureRevision controlPlastikkartePredictionAndroid (robot)Decision theoryProjective planeRevision controlInformationMobile appFocus (optics)TelecommunicationShared memorySet (mathematics)Analytic setSoftware developerSoftwarePoint cloudVelocityEnterprise architectureMachine learningFeedbackArchitectureReal numberBitData loggerLastteilungMultiplication signCollaborationismCASE <Informatik>Process (computing)Cloud computingMathematical optimizationSoftware frameworkStrategy gameView (database)Latent heatGoodness of fitFunctional (mathematics)Internet service providerLevel (video gaming)Game controllerSystem callScalabilityRight angleInstance (computer science)FamilyProduct (business)Different (Kate Ryan album)Film editingVirtual machineControl flowStructural loadScaling (geometry)Computing platformTerm (mathematics)Group actionComplex (psychology)Service (economics)ArmPoint (geometry)Message passingMonster groupProof theoryArithmetic meanDisk read-and-write headBeat (acoustics)Online helpReading (process)GoogolInformation securityConsistencyGenderMathematicsWave packetOrder (biology)LoginCodeForm (programming)Vector potentialWeightVideo game consoleCausalityPatch (Unix)Communications system2 (number)Computer animation
21:50
Enterprise architectureAndroid (robot)Laurent seriesComputer hardwareRevision controlProcess (computing)Software testingWebsitePoint cloudScalabilitySoftware as a serviceComputer networkAndroid (robot)Point cloudComputer hardwareWebsiteBitSoftwareCartesian coordinate systemSoftware testingScalabilityRevision controlProcess (computing)Reverse engineeringDevice driverPoint (geometry)Structural loadMobile appOrder (biology)Real numberCybersexCASE <Informatik>Multiplication signStudent's t-testEnterprise architectureRight angleFitness functionComputer animation
24:08
Enterprise architectureAndroid (robot)Standard deviationRepeating decimalGoogolLaurent seriesAndroid (robot)Open sourceMultiplication signOrder (biology)Human migrationRevision controlSuite (music)EmailMathematicsInformation securityField (computer science)Domain nameExpert systemEnterprise architecturePoint cloudStandard deviationCloud computingGoogolMobile WebCartesian coordinate systemStorage area networkMixed realitySource codeWordBitState of matterProcess (computing)Metropolitan area networkAreaSource codeComputer animation
26:44
Android (robot)Laurent seriesEnterprise architectureAreaExterior algebraOracleAndroid (robot)Vertex (graph theory)Process (computing)Game controllerData managementVapor barrierProjective planeCustomer relationship managementBitResultantGoodness of fitPower (physics)Right angle1 (number)Multiplication signWebsiteRevision controlSource codeComputer animation
Transcript: English(auto-generated)
00:01
Thanks. So hello there. Sorry, it's hard to compete with a man shaft playing very soon. So we're happy that you are here. Thank you for coming. So we are just going to introduce myself quickly. So I'm Laurent, I'm a nomadic CEO, entrepreneur.
00:24
I founded three years ago WYSI. And before, since 2006, I'm working fully in Android and the Google ecosystem. I'm here with Jeremy, a CTO, who has since three years with us at WYSI.
00:44
So the idea today is to share with you our experience of success story as a low cost, customer driven, and co-developed EMM. So let's start. I'm going to edit a little bit the story in the beginning for the first 10 minutes to make it a bit more interesting.
01:01
So I started on a beach in Australia with my wife, you can see me here, or in a house. It's a real picture speaking to the birds. I was resting there after selling my company in France two years before. Well, I got a phone call from one of my previous customers, CIO of a courier company in France, who told me,
01:22
Guy, I need you. You should come back to France, where people are demonstrating, where you have traffic jams, but basically weed well. Because I need you, I have an issue. I'm changing my fleet of device from Microsoft C to Android.
01:41
I have the application. I have the Zebra devices. Everything is there. I need to deploy in like 8 to 10 months, but I have no MDM. And in fact, I have been looking at the market. My experts have been looking at the markets. And they came back to me with basically solutions,
02:00
solutions which are complex, which are slow to deploy, which we need experts to deploy them, and usually pretty expensive. So that's not what I'm looking for. I'm looking for a solution which is simple, easy to use, that I can deploy fast, not losing time
02:20
on technicalities, which is made for nodes. Basically for people, like I like to say, idiot proof. For people who are not specifically technical, specifically like manager of depot centers, managing drivers. They need to be able to onboard phones. They need to be able to block them, et cetera, et cetera.
02:43
And of course, not expensive. So this doesn't fit. What I have right now in the market doesn't fit. So are you ready for the challenge? So I was sitting on my beach, and I thought, what should I do? Should I go for it, or should I stay on my beach in Australia?
03:00
So I called Jeremy, and I said, Jeremy, are you up to the challenge? Sure. Sure? So we decided to go, to go for the challenge. And I came back to France, and we started to deploy, to work on this project. So first thing, hey, Henry, is it feasible in 10 months? Because in fact, we didn't have really,
03:21
we had a team, an expert team in Google Cloud technologies. So some Android development, but we didn't have, we had zero experience in EMM at the beginning. So we needed to employ some people doing this. So first, is it possible? Let's start to do a proof of concept. So we contacted with experts in the field. And of course, first, experts told us, basically,
03:42
don't go there. Nothing to see. It's not for you. OK, you are too young, too inexperienced, et cetera. So the people who accepted to speak to us basically told us, you are totally nuts to try to do this. This is going to take three years, $5 million investment to do this. So you're going basically to fail.
04:03
But luckily, we contacted Android Enterprise with our customer, which was already a customer of Google. In fact, previous company I founded in Paris was the first G Suite reseller historically in Europe. So I knew some people at Google and Android.
04:21
And my customer also, my ex-customer, knew some people. So we went there. We discovered what Android Enterprise was doing. And we said, OK, it's possible. 10 months later, which is August last year, we deployed 6,000 devices, zebra devices, in a three week period for our customer.
04:43
And in fact, this video is one of the customer testimonials on the Android Enterprise main website page. So you can check the video. Sorry it's in French, but you can check it. And three months later, we listed our public version
05:02
of the EMM on the Android solution directory. So that's, in short, the storyline, the 18 month storyline, 18 months ago. And in fact, I'm leaving first try again next week to spend two months there, because I'm missing it.
05:21
But I was full time here working on this project since. So to be more serious now, what challenge did we face doing this? We faced some functional challenge and some technical challenge. So let's speak about these challenges. So first functional challenge, make it easy to use. Like I said, idiot proof.
05:41
Make it easy to use for IT users, of course, IT admins centrally to deploy, but also for local business managers. OK, the web console interface should be used by non-technical people, by people who manage drivers, who manage packets, delivery, et cetera. And we don't need to be trained to use an application like this.
06:03
Second challenge was very important, align to the business needs. Set up alerts that matters to the business, because it's very well to be secure, et cetera, et cetera. But if you don't have the right information at the right time to manage your business, you're not good. You're not better than the others. So one of the big subject we had is how do we bring back
06:24
all the information needed in order to set up the appropriate alerts for their business. The second is anticipate. The beauty of the cloud solution, because you'll see, of course, the solution is SaaS cloud, with the history we have, is that we keep all the logs of everything
06:42
for all the actions on the device, on BigQuery, on GCP. So we have all the logs. We can do predictive analytics. We can use TensorFlow to do machine learning later on, so after a certain amount of time. So right now, we are at this time with this customer, where you can start to do this. So predictive analytics is something which will bring a high value to our customer.
07:01
And then cover end-to-end business needs. And for this customer, one of the business needs that many, many customer using fleet of devices here have is cover the full fleet lifecycle management, in order to know, where is my device? Is my device operating currently? Is it in stock, ready to operate?
07:20
Or is it in maintenance somewhere? Repair, et cetera, et cetera. So we included this in the application to cover all the business needs. And finally, align with major Google Android features. So this is the same story as I had with Google Cloud in the beginning, is that you will say, yeah, but Android wants me to do this way that way. I want to do it. I want to do it another way.
07:42
But what does it take for you to change a little bit how you want to work and have a much higher value after? One example I like to give is the example of a English customer where we did a proof of concept. He had his own app. And he didn't want to load it on the Google Play Store, private app on the Google Play Store. He said, I want to, you know, it's too dangerous.
08:01
It's on Google Play Store, et cetera. I want just to publish it from my own servers. So we convinced him for the POC to do it. He uploaded the application. Jeremy did it. He was live there doing it. You know, they did it. And in fact, through Google Play Protect, they discovered that they had trackers installed on the new application, that most of the development was outsourced.
08:21
So they discovered advertising trackers on the main business app they were going to deploy. Okay, and the guy, they looked at us. They looked at the developer. And you can see, you know, in his eyes, we can see, you know, he was angry. We see his developers. But that's one of the things. So you need to basically to align what you can get out of what Android and Google does.
08:40
Okay, and you can get a lot, an awful lot, all of it. So that said, now we go into technical challenges. And that's for CTO. Thank you, Laurent. So I'll come back on some of the technical challenges we faced during this project. So as a big as a context, the project consists
09:02
in managed remotely 6,000 devices. So speaking about enterprise mobile management, the first thing we have to ensure is the device security. That was one of the big challenge. Okay, make sure that we push the right restriction.
09:21
Make sure that we also consider user experience because the more restriction you push, the more you have to deal with user experience. Data encryption, data synchronization, make sure that all the data is encrypted. Make sure that all the devices are synchronized
09:40
with the backend. Communication is obviously one of the biggest challenge because you have to communicate with a large fleet of connected devices. For those who do IoT or Android or things, you understand what I mean. So communication has to be real time, but it has to be also cost efficient.
10:03
Scalability, reliability, performance. Okay, I'm not talking about a B2C applications with billions of users, that's right. But still, we are facing some data volume scale that we have to handle properly. So first of all, we generate around three gigabytes
10:22
of data every day, you know, among the thing, logs and data history. So we have to store that in big data table properly. We have long jobs, back office data processing, storing the data is great, but you have to process them.
10:41
And lately, 6,000 devices connected to a backend represent roughly 50 requests per second. So it's not that high, but still, you have to set this up correctly, manage instances, and mostly make sure you propose the good ratio
11:00
between performance and cost. Analytics, one of the key thing of this project is the data, so storing the data is great. But now you have to propose great reports, KPI to be very pushy to the customer, propose to him the best view of what happened through the data for him to take the better decisions.
11:24
And eventually, limit the cost. We are talking about cloud infrastructure, performance versus cost, that's always the same motto. So limit the cost is one of the key thing, especially once you go live. But also when you define the architecture.
11:40
That being said, between you and me, I will say that that are not real technical challenges. This is basics. If you want to go, if you want to afford such a project, you have to consider this not as technical challenges, but as basics. When you create an application on the Google Cloud Platform,
12:01
when you speak about device security, there are frameworks, existing frameworks you should use as bricks, as basics, to build the entire project. So that, definitely, and because we have a lot of experience as developers, certified developer on Google Cloud Platform, that definitely just basics.
12:20
And if you follow me on the social network, you will see that I like the motto, if you want to play in premiership, you better master the basics. And that this is definitely what happened and one of the key success of this project. So, due to new technology, due to the work of Google,
12:41
both on the Google Cloud Platform side and Android Enterprise, we can work very efficiently on those topics. So, security, scalability, and performance. We just play with the frameworks and the API proposed and the managed services proposed by Google and the Android team, okay?
13:02
The real challenge is master the basics and then face the real technical challenges, which are, stay aligned with Android disruption. So when we start the project, the true story, because of customer history, we start with Android Open Source, AOSP,
13:22
and after a while, and maybe also because Android team was very pushy about this project, we make a switch to Android GMS. So we start over with a new approach, device ownership, new API, new framework. So that's something you have to understand when you use such a technology,
13:41
be able to flip and change strategy, technical strategy. So you have to handle with new services, complex documentation, well documentation, but still complex, and that documentation evolves through the project. So my job consists in reading over and over the same documentation, make sure that I'm,
14:03
stay updated with the last information. Also, one of the challenge you, as a technical guy, you can miss, is stay connected with the Android tech team and the manufacturer. You have to be a player of the community,
14:20
give feedback, raise issue, answer issue of other guys, because the more you provide, the more you get. If you want to stay updated with those new technology, you have to provide feedback. And because sometimes the API is not working, because sometimes there is some issues, because sometimes you are facing something
14:41
that nobody faced before, even the Android team. So that's very important to provide feedback for them to do a better job, provide patch, correction, fixes, improvements, and also get answers from the other developers. I know this is an Android event,
15:02
or that spirit of sharing is very Android, I think. On Android enterprise side, it's not different. You have to keep that in mind. Last point, which is very important, the long-term view of Android or cloud platform is not always aligned with the day-to-day issues you face during the project.
15:21
And that's very important to understand, that to stay connected, to understand where they go, to provide the correct answer, I mean, to provide all the information to your customer for him to take the right decision. So sometimes we get challenged by the customer, saying, hey, we want this and this. Okay, maybe if you wait a little bit, it will collapse on the framework,
15:41
or maybe if you change a little bit your mind, if you change your approach, it could match. Okay, that's true on a functional level, and that's also true on a technical level. Last thing, optimal cloud architecture. So we chose to build the entire solution on the Google Cloud Platform, which really help us.
16:02
We spare a lot of time by not thinking about performance, by not thinking about load balancing and how to manage instances, et cetera. We just write, we just think about the right architecture. Thanks, I mean, a huge experience. Once you have that, this is the basics I talk about.
16:21
You need to serve the right architecture to make sure you will handle the traffic, you handle all the specificities of your project. Once you have all of that, you can focus on the very one point, which is stick to your customer needs. So I mean, in my opinion, velocity and agility are the two criteria you have to keep in mind,
16:42
because the specifications change so many times during the project, because you know this guy, they have a job, they are operational, so they are thinking over and over about the process, and they are improving it during your development. So if you are not comfortable enough with the basics, with the frameworks offered by Google and Android,
17:02
you cannot have this high velocity and high agility required with such a project. Just to highlight a little bit the history of the project, we start in October 2016 by the proof of concept, making sure that the technology is able to take control of the device remotely.
17:24
Start the project December 2016, start over in March 2017 due to a flip from AOSP to GMS, and by the way, so we choose device ownership, and by the way, we use also Firebase Cloud Messaging as the communication system.
17:40
Start over, deliver the solution four months later, in July, one month's testing, go live in August, and we enroll 5,000 devices in three weeks, App Engine run very well,
18:01
that's great to see that. Second version of just in October 2017, and eventually we release the public version and get the Android Enterprise Partnership in January 2018, so for those developer as a conclusion, for those developer who work on such a project, that's a very short period of time.
18:25
Thank you. So yeah, I like about the scalability, I like to also tell the story of our customer, when we had developed with 200 devices plugged, you know, was working, said, but can you prove it's going to work with 10,000 devices when we had no doubt, because it was plugged to GCP. So we still emulated it, put 10,000 device,
18:42
and it worked. So, but the question was here, is he going to work with a high load? When you work really on real cloud solutions, it's no issue, there is no issue about the scalability. So what lessons have we learned? Was it easy? No, hell no, it was not easy. It was like pretty difficult to do.
19:00
It was a damn difficult job, but we succeeded because we had three things. We had first, a customer committed to co-develop with us. Okay, so that's one, the first very important thing. We had a use case and a customer. The second, we had the Android partnership. So a close collaboration to Android enterprise,
19:20
the people, the tool set, the smart APIs, and I want to thank the people here. If you have people here from Android, about the help they've provided. And we had time and resources. We had one year work with a skilled team of 10 people, because we employed people skilled in this, you know, after we faced the first challenge. So that's why we made it a success. And the second lesson learned is,
19:42
and that's really important, and that goes more to the functional business side, but what's the real value? I mean, again, I'm oversimplifying a bit, because I'm a CPA by training, by the way. So I'm not an engineer, so it's easy for me to simplify the technical side, and I have a great guy who does the job here, so that's all good.
20:01
But for the customer, I mean, today, everything which is like the security, the app store, all these things is given by Android. You know, you just plug, okay? You have to plug, it's given. You don't have to spend time and resources and make sure it works. Can you imagine redevelop Google Play Protect? It's impossible, okay? So you just use what Google, what Android is providing,
20:23
and immediately, you can work at the level which is important for the customer, which is the business value. And where comes the business value from? Business value come from data. Okay, we all know it. Everybody speaks only about data. So data for what? Data to have the alerts at the right time
20:41
inside your business process. Data to do cost savings. So for example, we can bring back all the detail of the call logs, the data logs from the phones directly on a console, okay, which all the other EMM, you have to call the telco to have the information. You don't have it immediately.
21:01
So data is key. And of course, AI ready. As I discussed before, predictive analytics. You know, if you have a large fleet, you should be able to understand your data, to do prediction, to apply machine learning. It's a must-have in the future. Okay, or you cannot do it the first month you deploy. You need, of course, a certain set of data. But it's a must-have.
21:21
So we focus on all these things. Okay, that's a real focus for our customers. And of course, easy to set up and to run. That's, you know, that's the basic, I like to compare to, I'm not going to, I know you're in Germany, but SAP, you know, you want to use SAP, you need to be trained. Okay, you want to use the more modern
21:41
accounting software online. You don't really need training. It's a bit like more, you know, more user-friendly. It's a bit the same thing for us. So quickly, I want to go through the five best practice for a successful deployment of a large amount of device in our short period. That's not only about us. It's a bit, you know, the experience we have lived.
22:05
So that's, first one is choose the best trade-off between speed, cost, business impact, and deployment setup. Take an MSP, Managed Service Providers. The quicker you go, the less it costs you per device, because they put a team on it and it's finished. You use your people internally.
22:21
Okay, then you're going to put two, three people. You can do it month by month, a little bit each month. Okay, be more cost-efficient for you. But you have to adjust the business impact, you know, when you do it, et cetera. So that's the first thing, to set up straight. Then, very important, select your hardware and Android version based on your apps and process requirements. Don't do the reverse. We have seen people who have been choosing,
22:41
oh, I like this Android device from this manufacturer, because it's very cost-efficient, et cetera, et cetera. Okay, and then some end up with an AOSP device, which is not GMS, so you're going to use it with Android Enterprise, by the way. So it doesn't fit, you know. The application wants to do something
23:01
to the device which is not possible. So that's really also the first really important point. Third one, test on a P dot size to optimize the deployment process. Real site with 200 people, like this case, it was a delivery depot with 200 drivers. They were fully equipped. So we did the full deployment, the full test, and then we had a smooth process for the other depot.
23:27
Then go SaaS cloud to avoid scalability issues. I think you have understood it. We are on GCP. We told you 50 times already. But I mean, that's, you know, like today, you develop an application on the cloud, like you don't develop, you don't create a new car
23:42
which is not at least hybrid. Okay, the same thing. There is not even a question. In order to do this, of course, you need to anticipate the network and we fill out. So you need to anticipate before to have all your people work, you know, you have the right Wi-Fi in it, et cetera, to be able to carry the load of the application. So that was the five best practices to finish.
24:03
This is a bit crammed together. So, oop, sorry, we go like this, huh? It will be easier to read. So remember how Google disrupted the Microsoft business when they created G Suite, you know, Gmail on the cloud, et cetera,
24:21
when nobody believed it could go somewhere. I had customer in front of me who said, you know, going to cloud, you're gonna, imagine putting my email on the cloud, doesn't make sense, it's much more secure internally. Okay, until the guys in San Francisco, in LA, you know, it was like a movie Hollywood thing, they had all their email out, you know,
24:41
of all, with all the stars, and they said, oh, we should go cloud, it's more secure. Okay, and now, there is no question anymore. Even Airbus has been going G Suite or cloud recently, and Microsoft has a cloud offering now, and is a leader also in a cloud infrastructure. So, Microsoft, Google was a bit in advance, pushed the order to go,
25:01
and I believe that Android Enterprise is doing the same thing currently, and is disrupting the enterprise mobility segment by setting new standards for Android Enterprise, GMS, so we go totally open source to something like more, you know, if you want to enjoy the security, the play store, go GMS, okay, and they bring together the OEM, the EM player, everybody,
25:24
around the same standards. But they take care, Android takes care then of the security and the application store, so it's pretty easy once you've done this. You can focus on the business process, on the value, on the data. This has created a playing field for new entrants,
25:41
like us, okay, basically, to do things which are not possible before, to do, totally impossible. That's why I thought we were crazy 18 months ago when we started. People, you know, experts from the domain. It has facilitated also an easy migration. The time is going to be finished where you are in one EMM, you stay 10 years, you need to stay because you have the ability to migrate.
26:01
The time is finished where you choose a device, whichever, and you have to stay there because you are with this, you know, Android 4 version of this, on this device, you cannot migrate. You should be able to start deploying a fleet, and in the meantime, new device go out, change the devices, okay, why not? You'll need to be still stuck with one devices. So that's the, that's what's happening.
26:21
It'll take three, four, five years. Like for the cloud, it has taken like five years to be an evidence for everybody. So it'll take a bit of time. But, and then, specifically, we are transiting now from Microsoft C, you know, for enterprise fleets to Android. It's happening, it's happening when people change their fleet. So let's give four or five years. And the next one, which, can you go down?
26:42
Because now we are, okay, the next one is, yeah, it opens, for me, the door for new, new Android vertical, or Android-only vertical solutions. Okay, for, as a real alternative to the,
27:01
to the one-feet-tall EMM solution. Very often, I say, I would compare, you know, like, you know, once you had Oracle SAP providing everything in the enterprise, from CRM to accounting to things, of course, a big project doesn't always work, you know. Anyway, that, you know the story, okay? I'm not getting, some are convinced, some are not convinced, depends on which side of the barrier you are here.
27:21
But then Salesforce arrived, and say, we're going to do CRM, very good, Wells, SaaS, Claude, et cetera. Everybody laughed at Benioff and at Salesforce, and they became the leaders in a SaaS, in a CRM, so one, one. So we believe the same thing will be happening on the EMM side, okay, which we should maybe change the name, because EMM is really technical,
27:41
nobody knows what it is. So on the control of management of device, et cetera, I don't know, maybe you have to find a new name. Same thing will happen, and a very complex solution will slowly be replaced by really business vertical solution, bringing business value where, for aligned to the business processes.
28:01
And for this one, there is no need to manage Apple and Android, because of course, if you are in a shop, in a luxury Dior or Karna shop, of course, or whatever shop, you go both shops, you're going to have a nice iPhone tablet, or iPad iPhone, because luxury for customers.
28:21
Okay, but 90% of the users in industry, manufacturing, career, restaurant, all the other shops, will use Android. So Android only is good, because also we can be fully aligned with what Android is, how Android is evolving. Next version, no problem, we are only on Android.
28:40
It's there immediately, you know? Day comes out, maybe a few weeks later, because my CTO will tell me you are a bit too rough, and tell me to do this thing for the day after. So, but it will be there, it will be there much quicker than the other ones. So that's why, that's why we are here, and that's why we decided also to go, to go along the way of creating, which seems to be, at the time, a bit crazy for people, a new EMM, EMM in a segment full of
29:02
very powerful players today. So, before we drop the mic, if you have some questions, we are here. First of all, thank you too. Thank you for your talk.
29:21
Are there any questions? Are you, yeah, will you go, no. I can give you my mic.