Beginner's Guide to IoT and Mendix Application Development



hello everyone and welcome to a new mendax community webinar my name is Yun Rufus and I will be your host for today today's webinar will be about a beginner's guide to IOT and mendax and will be presented by assignment black technology evangelist at Bendix during the webinar you can submit your questions in the question window in GoToWebinar after the presentation we will go through them one by one the questions and answers will be added to the webinar page afterwards along with a recording of the webinar before we start please take a look at the handouts window and go to webinar to find the presentation slides thank you for joining and enjoy the presentation I'll now give the floor to Simon thanks Jan so in this webinar what I want to do is I want to cover a number of things regarding IIT so the first part I want to give you an introduction into IIT and the landscape variety so what type of technology makes up this landscape I want to then take you through the device management so what device management is how you can use it IOT Brokers so how those are influenced in the IOT and how those communicate and control the protocols I then go into some details about MTG tier the protocol show you an awesome demo of a IOT application and then finally I'll show you how to actually build one of these IOT applications so to introduce myself I'm sorry in black one of the technology evangelist from mendax I work with the evangelist team to build a critical mass of of people and users within mendax and spread the word of the technology so if the Internet of Things is obviously a hot topic at the moment the Internet of Things by 2020 is supposed to have 30 billion devices so everything from your toothbrush to your car will have an IOT device and all of this ite information will be streamed as data and applications will need to be able to control that data and be able to react to that data to build experiences on top of these services so the IOT landscape is obviously quite wide and large we have to have a number of different components in order to build an IOT solution the first one is you need to have some things so you need to be able to monitor something so we need like a car a toothbrush and so on these are what we refer to as things those things usually come with a number of sensors these sensors might be recording things like their temperature the movement velocity and so on and they sensors will stream data out to a particular system we only had things like actuators and agents which will act more on the device side to be able to control certain things based on sensor information and based on triggers from the device we have communication so we need to have certain communication protocols in IOT because obviously these are streaming lots of data they need to be small amount of packages and data packages so that they can make it very easy to communicate this information so protocols such as rest MPT t ZigBee and so on all our communication protocols designed for IOT landscape and then finally edge computing is all around building logic and computing into applications that are near the sensors so if you imagine you have a number of sensors on trucks or planes you want to be able to process that information as quickly as possible so we edge computing is all about creating those services close to the sensors so that they don't have to send that data off to the cloud process it and then react to it so we've IOT and when you're setting up an IOT application you need to have a device management so lots of IOT services out there will provide the device management portal and this allows you to do a number of things it allows you to provision authenticate certain devices to using things like password security certificate security to secure access to your your devices you then want to configure and control your application so being able to configure those devices being able to control them from one central portal you want to be a monitor and diagnose very sensor data and these information you're getting from these devices and finally be able to perform software updates so update those software from one central portal all of your sensors around the globe so usually what these IOT services providers like AWS and bluemix and so on provide is they provide two things the first one is the device management which I said without before and the second one is an IOT broker and what an IOT broker does is it's a lightweight and scalable middleware which allows you to communicate and control the communication between the IOT applications and the devices itself so the devices will push information to the IOT brokers and the applications will then listen in to that information to react to those different communications and different information usually these brokers will communicate via two different methods one is rest which is a common protocol most people have heard of and but the other one is mpg T so M PTC is very popular within the IOT space allowing you to do very short and quick messages between your iot devices and your broker portals so a little bit about entering TTT that's what we'll use today as our demonstration so it's a lightweight protocol for sending messages and these messages are usually sent over the topics so the topic is essentially a hierarchy as delimited by a slash and it will tell you information about what kind of sensor type it is what location and so on that information is then sent to the broker along with a payload of information and that broker will then send out that information to the different devices that are subscribed to that broker and in revoke MPT T we have two methods we have a subscribe and we have a publish so subscribe means that we were listening to any messages that get published to the broker and publishes for submitting data to that particular broker okay so the first part what I want to go through is an actual demo of an application so this is an application that we built for the IBM interconnect event which uses IBM IOT and is around the concept of logistics so being able to track cargo ships and those containers and being able to react to the information from those particular containers so I'm just going to switch to the demo now so if we look at my dashboards here I've got a dashboard of all of the information about my particular container so I can see information about the movement the temperature light and humidity and at the moment we've just got some static data in here we can see the light level recorded over time and we can also see some temperature information and so on so I'm now going to do is I'm actually going to start sending this application data to IBM Watson and I'm going to create be able to see that information populating in my application once I get an alert from the application I can then start to do something about that particular alert so let's have a look at the data let's send some data now I'm actually going to push through the clouds and information and this is actually coming from one of my live sensors so I've got here a sensor with me which is a TI sense attack which allows me to sense and view a lot of data about movement sensor light temperature and even C so for instance if I close my hands over the actual sensor will see that the light now drops down to zero if I open it up we can now see that light will spike so obviously it's very important especially in the logistics industry that cargo is is delivered in a consistent state things like temperature light and so on can actually damage that cargo and have an influence on that particular cargo value so let's actually try and trigger a an alert in the application so within the application we've built the application to be able to handle so vents from our device so if we actually shine a torch for instance our our sensor will see that the light will spike up in this application to over 2000 watts and will now get a push notification into our application so this is obviously our web version of the application but we've also built a mobile version of the application and the mobile version allows us to view the same information but it's for a person on the cargo ship so being able to actually view that data live and be able to react to those events so we can see at the top here we've got our push notification now and we can view that push notification and start to drill down and see what occurred and what happened with that particular incident we can swipe between different information like temperature light humidity and drill down on that information to see what is good occured with it so we see previous history of all of that data that has gone on on that particular sensor as we've been going through when the application triggers those alerts it would also generate a block chain in the block so it will create a block in this block chain to actually create us an immutable ledger of everything that's gone on when we've been actually creating these alerts so we can have no disputes as to what's been happening with these particular IOT devices and what has been going wrong in the application so this is a common trend that we see in the industry is people starting to combine IOT and blockchain to be able to make sure that they can read the data and they can sense the information but they can actually then record that so there's no disagreement in what's been going on on those IOT sensors within this application it's also created us a and inspection so within the inspection we can see that we have – we have had an inspection with light to high and if we drill down on that inspection we can see and start to insert some information into this inspection so we can do things like take a photo we can add in information about when the inspection occurred so using some native dialogues from the device like the camera the calendar the GPS location and so on we can also set the location as well so set a GPS location of where we are where the incident occurred if we now is to submit this inspection we can now see that information and see a PDF version of that application so what this application will do is it will be stored in box technology so we can have a central repository of all of our information all of our inspections in one place so if we go to the completed section now we can see that we've got that particular inspection we can view that inspection and we can see some additional information so we can see the actual box renderer here rendering our PDF and we can see the information that we submitted about the longitude and latitude and what we've entered in as our information if we've added any pictures in here as well those would be added into the information so this kind of shows you how you can combine mendax with these different services whether it be IOT services blockchain services or box technology for your document storage within the application as well we've implemented the functionality of swipe functionality so this is actually a widget that was added recently to the App Store so being able to swipe away certain notifications in the application so this is so all of the functionality you can download today from the mendax app store you can customize and you can add these to build your experiences in your applications so that kind of gives you an idea of the type of applications you can build but what the community team has been hard at work at has been taking this application we've built as evangelist team and being able to create this as an IOT tutorial as well so this is something that is being released to the App Store at the moment so you can go online today and you can take this tutorial and start to build out your own IOT application and this is what I'm going to be using today for my particular demo is I'll take you through the IOT tutorial and so to build and show you how you can use technology like mqtt to build you out your application so if you look on the at mendax app store under i RT we have a number of connectors and modules be able to have the logistics tutorial which will take you through a step by step journey to build your application we have an AWS iot connector which allows your app to specifically connect into AWS iot and we have a generic MQTT connector to use MQTT on a variety of different mqtt brokers whether it be on amazon or whether it be on IBM or s AP and so on so to give you an idea where you usually start when you start to build an IOT application usual media will start with a device management or IOT broker so let's take a look at one of those so this is actually the IOT broker that we're using for the actual demo so this one is based on IP WS and here we can see a dashboard of things like the number of connections the type of protocols have been using to actually communicate those messages and the number of inbound messages and what types they are within each broker and each device manager you can register a number of things so things are what you're actually going to be monitoring so it might be the for instance a car it might be a IOT sensor like we've got here today and we can drill down on those things and start to set those up we can set their details up both of them so we can give them information about what type they are so each device will usually have a type and that type describes what information you can pass through it what details it has and what type of of actual application is what sensor is within here we can also set up security as well so one thing you have to do with AWS is you have to use certificates to be able to secure your access and send data and receive data from those devices other IT brokers like the IBM Watson for instance or the S AP portal as well allow you to do this without having to do certificates so simply by a password for instance if we look at some other examples IOT bro because you can see the same sort of patterns in each of them so if we take a look at the IBM Watson IOT platform we have the same concepts we have a list of the prices which then have a list of a type and those devices can then send the information to those particular partners so we can see for instance here we've got some devices already connected which are actually sending data to the actual portal so once you set up your devices you've communicated those set those up in the IOT portal you can then start to connect to those in your mendax application and start to use that data so let's actually take a look at our mendax app application and let's start to actually implement the actual features so if we just switch now to our local machine so this is actually the iot tutorial that's now available on the App Store and when you first come into the application you can select a shipment but what you've also got on the top here as well is a view tutorial you click on view tutorial this will then take you into the documentation and give you a step-by-step guide on how to connect up your application into our example IOT service so we've already hosted an IOT service for you which you can connect into to using this as an example and start to use that data so if we drill down on the shipments we can see that shipment and we can see the same sort of data that we had in our example data on the example application we showed earlier then the moment the data we've got here is static it's not collecting any information from our IOT service so we actually want to connect this up now we want to do what's cool to subscribe we want to be able to subscribe to the information from the IOT service so that we can get any of the updates that are being published to the AWS broker so if we go into our modeler now we can open up the modeler and see the same page that we have open on the desktop and we can start to add in the functionality that we need to be able to subscribe to that data so the first thing we want to do is we want to add on a button so that we can actually subscribe to that information so I've already got a microphone set up here for the SUBSCRIBE which I'll go through in a second and if we drag that on to our page we can now have a button to subscribe to that information now let's have a look at what that actual microphone is doing so these bad parts are edition checks to make sure that we've got the right information the right topic and the right configuration so that we can retrieve it and we can then send that to our subscribed method so we now got an activity here for the AWS IOT which allows us to subscribe to any MT TT topic if we drill down onto those properties we can see that we have two set and a broker host the broker host is essentially URL of where you're actually going to send this information we've got the broker port usually this is 183 if you're using MTG T but you could have set this up on a different protocol to use for instance different security and so on we then have a timeout which will allow us to basically if we can't get a connection it will timeout after a number of milliseconds after triangle then we have the topic name so the topic name is actually where we're going to actually subscribe to so in this case it it's a hierarchy and we'll show you later in when we come to publish well that topic kind of looks like we then have it on message might flow so this is important especially when you are receiving data you want to be able to process that data so we put this application up to a microphone so that when we receive data from RM TTT we will then be able to process that data so if we click on show we can show this microphone and it simply has two parameters and at the moment we just log in the information so these parameters are important because you need to have a topic string and also a payload string so the topic will tell you what where you're sending it from and where it was is coming from the payloads will tell you what information is being sent so usually this payload is sent in JSON format that could also be an XML format as well or some other format simply it's just a string of data that you're sending the actual application so what we can do now is if we run this application now we can actually subscribe to the IOT service and we can then see the information in our log lines so when we click the button on our application which should be now updated here we go so we've got our subscribe button if we click Subscribe this will now subscribe to the topic completed device 1 so we've got the information here it said it's completed if we click OK and we go back into our modeler we can see in the console that we've started to get information from our IOT service so here we go we've got sensor data received we can see that payloads which is in JSON format and we can then start to use that information so let's actually use that information in our application let's take an example payload and let's start to use that data so we actually want to map that data and store it in the mendax application so that we can then update this dashboard so at the moment this dashboard is just using historical data but we want it to be able to use the live data in the application so let's connect that up to actual data now so what I'm going to do and show you is how we can actually take adjacent payload from our application how we can build a mapping and how we can then use that mapping when we call that service and we can process that data so now let's copy this payload in into our application if we go into our application now we can now start to create ourselves a JSON snippet if we right-click on any of the folders we can select consume services and JSON structure so we've been here we can paste our JSON snippet so what data are we actually going to receive from our IIT broke up we can click refresh and it will automatically detect each of the types of what the data is so now we've created a structure we now need to I'm mapping so we need to now be able to map that data that we've got in the structure to our own database so again if we click Add and we click on import mapping we can now select a JSON structure which you just created earlier and we can select all of the items that we want at the moment we want all of them and it will now bring up this dialog for us so the moment these are highlighted in red and that's because we haven't mapped those up to a different data model in our application to an entity that is existing in their model so if we need to actually map that up we can drag from our connector usually this is on the right hand side it might be somewhere else with other people we've already got a sense of data entity we can simply drag that on to here and it will ask us then to select each of the art items that we want to map this up to but I don't want to have to manually map each of those so I'm going to map those automatically if we click map attributes by name it will automatically detect which attributes it needs to map it up to and it will then map those to the data items if it was a new entity it can automatically create those attributes for you so you don't need to have to create each of those attributes and each of those entities is available for you okay so we've now got our structure we've got our mapping we now want to change this microphone so we can import the data and we can see that live in our dashboard updating so let's delete the log lines and let's add on to new activities the first one is we're going to do an import mapping so we can import with mapping we're going to select the payload which is as a string and we're going to use the mapping import mapping to which is the one we've just created we can then decide to store that in a variable which allow us to actually see that data and do something with it so in our example for instance that we showed earlier what I was doing is I was using that Center data and making some decisions within the microphone so we can add on certain things like exclusive splits to say okay if the sense of data and the accelerometer is greater than 100 for instance then we could then do something in the application we might want to trigger an alert a push notification for instance like in the example we showed or store some information and an alert in the application so now once we've imported the application we need to do one more thing which is actually save and refresh that data so I'm just going to drag on an existing microphone that's already pre-built all this might flows doing is it's just making sure that that data that we retrieve is saved against the right information and right shipment that we're using again all of this information is available in the tutorial and it's a step by step guide on how to actually use it so I've got a couple of errors which I need to fix I need to give it some data so I need to say the topic that I'm giving it and also the sensor data okay so let's rerun this application now locally save our changes and now when we run this and we subscribe to the information we should start to get live information from our sensors in the application here we go so if we open up the application now we can see our shipment we can drill down on it and well now when we hit subscribe we should start to see information be populated in our dashboard so we should see the light level go Emily also should see some information in the actual graph as well change so actually with this particular data we've connected up to the example IOT break on AWS which comes with this tutorial so you can easily connect up and start demoing and using these IOT services okay so I've obviously shown to you from from at the moment I'm showing you how to subscribe to the data so how to actually connect up to the broker and view that data I've shown you how to actually map that data using the the JSON mapper and then finally the last bit I want to show you is actually how we do the second method of MQTT which is published so how do we actually submit data to the broker and how did that then influence the data we've got here because at the moment we've not got much change in the light we might want to trigger a light alert for instance and trigger it so that it goes above 3000 4000 for instance so let's do that now let's switch back to the modeler let's create a new flow for that flow so I've already created a microwave for this which allows us to publish so it will create current retrieve the topic that we want retrieves the configuration and we've now got a different type of mapping we've got an export mapping so if we take a look at the data now we can see we've got similar sort of data that we're sending it in adjacent snippet but instead of an import mapping we've got an export mapping it does the same as an import mapping but the other way around so it will export rather than import if we go into the microphone again we can see that we've got a similar connector here but this one is actually for publishing and the only difference here compared to the subscribe is we're actually sending a payload here so actually sending data to the IRT service so that we can then see that data in our dashboard because we're actually subscribing to that data so let's go through our page again and let's drag on the published data if we drag on the publish data now we can now connect this page up so that we can start sending it new data to the service so let's actually change the data that we're going to send we're going to send a light level of let's say 4,500 click OK and rerun this application what it will now do is it will start to send that data to the IRT service so if we're going to the shipments now we can see that we've got one shipment still we can drill down on it if we first subscribe what we usually do with this subscribed method is we actually put this in and a start up flow so that we don't have to keep clicking the button every time that for the demonstration purposes I just wanted to show how we can actually subscribe to it so if we click the button our publish data it will now trigger some data send that to the AWS IOT and because we subscribe to that data will now get that information any other application that's subscribed to this data as well will also get that information as well so you don't have to you don't have it's not a one-to-one binding you can have multiple systems communicating using and subscribing to the same topics and also multiple devices submitting to the same sort of topics as well usually you would have one topic per device so you could then make it unique so you know where it's actually come from okay so they scribes actually bound listen into the that's been coming from our IOT broker the second one was being able to actually process that information that we've got from the IOT broker and use the import mappings from Bendix the third one is finally obviously being able to publish the data so being after you publish the main functionality show you see first was being here so in this example MC we're using AWS as our example but we have examples and ways to use it for other services like Azure RIT or AP IOT and IBM IOT so those type of IOT services is probably best to use the general MT GT service that's on the App Store and if you simply search for that you can add that into your projects so it's very similar to the AWS IOT example the ADA bs IOT example just has a bit more features that are specific for AWS so let's switch back to our things so if you have cover those topics is there any answers and questions so thanks very much Simon that was very a very good presentation you can now ask your questions in the questions window in GoToWebinar and so I'll give everyone some time to come up with a couple of questions if you want to know anything about IOT about this sample app that Simon showed you you can ask them right here right now or if you want to follow this tutorial you can go to the medics documentation at docs.bmc.com all right so we have a first question by a pin the amount of data is growing if you capture all of the IOT data so will the default Postgres database handle this and do we have any best practices with big data ok great so yeah that's a very good question obviously these devices do generate a lot of data that's why in the applications that we've built we've actually built a scheduled event which will actually clear the data so we're only storing the last kind of 30 seconds of data and that's purely because in a membe exercise what we want really are concerned about is actually doing a logic on the application so actually being able to trigger and build experiences we don't want to be generating and storing historical data if you want to store a historical data in a kind of big data format then obviously you could write that data out to a big data solution to out here over to store that as well also some of our other customers and clients have decided to do all of the triggers and alerts on on the actual IOT site so being able to do those or less on AWS IOT for instance or Azure so they have big big solutions you can do the alerts and triggers on AWS and the logic there and they simply push that then to mendax so you could still use kind of MQTT topics but you could reduce that by just using it for alerts so for instance if you wanted to send an alert to the mendax application or there's an alert on the edge of the left side for instance if the light's gone too high you could use an PTT just for the alert spot rather than the actual data part so yes it's we're not a big data solution and it can handle obviously a fairly large amount of data but if you're looking at multiple different sensors and so on yeah we would advise using a good data solution and only storing the last kind of few seconds of data within vendek's all right great thanks we have another question by he'll he says I understand why we listen to censors but I don't understand why we need to send data and publish publish to broker yeah I think yeah it's a good example so one example that is often used when demoing the sort of item and PTT annuities functionality is for instance in a home system for instance so you have a home automation system and you have a security system for instance you might want to have an application where you press a button and it will then based on that button click it will actually be able to lock the door for instance also when you're you have these sensor data's there all publishing as well so publishing on the mendick sides could be useful if you're wanting to use the same publish method that a device is using for instance or you wanted to communicate multiple different devices so MQTT is useful anyway even if you're not sending big data because of the subscribe and publish methods so if you publish data on there on the mandate side then all items that are subscribing to it will then be able to listen in to that information so like in my example of a home automation if you click lock my doors for instance it will then go off to the census and then actually lock the doors so it could be five or six different doors that are listening into that particular one topic alright great thanks so you just chilled this IOT app and you've built the stuff in my group with it within half an hour but a lot of this stuff is already in place if you start your first IOT app how much time would it really take to build something that you know generates some some nice results and actually you know have some use for the business for example yes so the key thing is obviously you need to have some form of data and so Beyonc have some a sentence is obviously important and there's lots of useful sensors out there useful example IOT connectors that you can connect into for sample data we are using in our example a system called Texas Instruments so if I just take a picture of those you can see what they are so the texas instrument has a number of different sensors on it so it has set a humidity it has temperature so on and things like that so and multiple sensors which would and it allows you to easily integrate into your iot broker so the IOT brokers are easy to set up as well you can just go on to your 82's or to go on to IBM and you can set your own your own IOT service up for free and then so you connect up into mendax then you simply have to obviously do the SUBSCRIBE method which i showed earlier and then the publish method as well so it's pretty simple to be able to connect it up you can probably do it in in a few steps if you've got the sensors already set up and the IOT broke already set up all right great and what about the team size so if you're starting an IOT out how many people would you need can you do that on your own I mean I think you can but might take a long time yeah I think I think the key with the IOT applications is there's quite a few different moving parts so you would probably need some form of team to be dealing with the actual hardware part and the sensors part of it because of your monitoring lots of IOT type data you need obviously a team dedicated to more of the hardware part of the application in terms of actually building the experiencia mendax once that data is in the MQTT broker then it's really simple to them build our applications so you probably only need a team of one or two men these developers do to build a mendax application on top of the saya tea service but obviously you've got to have other teams interacting together to be able to get that data and be able to the communication and so on alright great so we have a question here from George with the wave of IOT technology coming those medics have a reduced cost model somewhere between the free version and the full enterprise version that will be more independent for small developers to use mendax to build IOT apps at a more reasonable cost because the free edition well it's good but it's it's really only good for building prototypes yes that's a good question probably one I can't answer it's not being caught the sales team so there's probably one will have to do a lot to come back to you that's based on licensing and things like that yeah all right thanks so is there anyone else who has any questions for Simon then anything about the IOT app brokers building there's stuff on a technical side or you know maybe what uses IOT in general for your business what can you do with it and why would you need it in the first place because you know IOT is buzz word things I'll just give people one minute to think of any think of any questions I'll ring quick I went quicker through my application that I built it was getting a no problem yeah it's ok there because we have the recording so afterwards people can just go through the webinar page and watch it at their own pace pause it and of course we have the tutorials so they can build it themselves shop and they have your guidance in video definitely yeah with your explanation so that's that's good too so maybe it's a good idea to give you some background in some bits on how I built the dashboard so that's always quite useful it's actually a dashboard here is we're using a number of different widgets the first one I'll see is the chart widget we've got a Google Maps widget at the top here and then we've got a number of just different sensor data that we're pulling the data is being refreshed that is a microphone timer that will refresh the data on the page so that we can get the live updates from the data that's coming in through the background of the application so that's how we kind of built the application and in the application as well we have obviously the alerts as well so the alerts on the mobile phone and triggered by the push notifications we make those decisions using a microphone in the background all right okay so we have another question from Yap he says how do the devices communicate to the broker especially from within a container okay yes a – there's a number of different particles you can use in the example that we're using at the moment the sensor tag actually communicates over Bluetooth to a mobile phone device and that mobile phone device then sends the data via mqtt to the broker you can do it by other methods as well so there's technology like ZigBee and a few other different different protocols which are lightweight protocols which allow you to communicate with a central hub so if you imagine in a an example like that home automation most warrant housing on automations will have a central broker hub which the all of the devices will communicate see so under a particular protocol which is you know something like blue tea for something a low low range and radar saticon of the signal and then that device hub will then communicate with an IRT broker so if we have a look in our example I had one earlier here so usually when we look at the kind of communication this published step here is usually done by a intermediate step especially if you're on a container for instance you might have obviously a number of senses and those might have no connection to the internet at all so what usually happens is they have a central device management system these close to the sensors probably on each container or on set of containers which will then receive that sensor data and will store it until it can then submit it to the actual broker so you might have your own broker network essentially I would write on the ship before be on set send it to a cloud environment okay thank you so John asks does the IT broker charge for the use of the brokerage services and yes it does so it depends on each of the the broker service so usually it's done by messages they don't I don't think they charge by devices but I'm not entirely sure and so usually it's per a number of messages but you get quite a bit of bandwidth for our chief attesting that yeah you'd have to look up into the different services for that I think their price models are pretty clear anyway saying yeah I think it's usually just like a bulk of X number of messages in a window so it might be 5000 in a mum France and something like that all right we have a question here from Brandon what would be shown if the IOT device went down so is there a specific error handling built in the micro flow activities yes say if you don't actually send anything to the MTT broker it doesn't matter say the SUBSCRIBE method you will just listen in to any day to the center if there's no data then it just doesn't execute that microphone and so it's not like if we don't send data to it it's going to fall over I have built some logic into it too to have some standing data so in my application just for demo purposes what I do decide if I turn off the push to cloud now so I'm actually turning off the sensor data you'll start to see that Graff will flatten out and then we'll get some examples I'll sample data eventually so if no data is being sent it just simply doesn't execute the microphone okay I think that's critical see you as soon as you see in a second it will sort of there'll be a new graph because it will just use some sample data I've just added into the database so we go it's just a song a sample graph yeah exactly all right I think those are the questions for today so let's round up thank you all very much for joining it was a great presentation and we'll send you an email with a link to the video and we'll post the questions and the answers on the webinar page and if you have any questions afterwards you can always ask them on the forum or contact some admin –ax so thank you all very much and see you next time

2 Comments

  1. vibdib said:

    how does mendix compare to xamarin?

    June 30, 2019
    Reply
  2. Ravi Kumar said:

    can we use mendix for creating IOT application ??

    June 30, 2019
    Reply

Leave a Reply

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