 Hi everyone, so this talk is about test-to-test build-in class platform for next class build-in platform for next class. So, this is going to be a bit different from the earlier ones. The dashboard is going to be like the payments have when you send money, when you receive money, send them money all the time, all the time, so this is going to be targeted at the space which basically has J company, multiple apps, we are powering 100 million devices and we have also built deep, so you guys might have used deep, so that it's really hard to start producing all your apps. Then the second requirement, we couldn't use a react net, so these are the two basic challenges we had. We had to create a very small insketch, basically you will use it in multiple places. You just have the component, you guys, you guys already have to start it, multiple places from the top. These basically are really, like, almost in the translation of the tools. There are tools like that, you can translate the, you know, the sexual values or the potential values of this, and second is the pixel representation. So, yes, it's really hard to create a pixel representation because scaling limits are different. Well, if it's scaling it, it's fine based. So, it's really hard to make sense, you know, what to, what to create is the pixel value of a sketch file and what it's a bit of an attack. So, the way it works is basically, so you have a sketch design, which is open here to the sketch file. So, the sketch file basically means generated by the sketch. So, basically, if you see already there's a, which has better information related to each of the, and you say type, let's say this, right, this thing, when this information is attached here, basically this basically reads both this case and combines the code. So, I'll show you the code, how that works. These are all responsive properties, right? These are, these are all designed by the work like experts or as you get to know. This will render. So, if you have a automatically, let's say X20 for the X node, and that way the product may just be looking at 20,000. It doesn't care what screen and what. So, it basically is unaware of the screen stuff. Wherever the small changes is there, you know, like if you just basically remove the, you know, see the flow. But basically that's how the fact is how we even complex all this. So, these are the bigger problems we have. And second is the code. Because there's so much coupling of the code. It's impossible to basically figure out, So, if you're a student, basically it tries to, because we just keep adding like this, like this, like this, like this, or just to make it something like constant. Which is like, and it will give you static. So, this is the new code language we have come up with. So, this is a new notation. And this is some kind of a line. So, basically what's happening is it's waiting for some kind of response. So, it basically shows the, then you can see it from it. Then it will output how much. So, that's all the information that should be there, and the company of code. I don't really care about how a man is in the state. But that's some layer that has to be like, you know, distinction. Like, you know, this is the flow code, and it can output any kind of keyword. So, if you see, you basically say, remove not, remove not patch operator. And this is like an endeavour, which we'll keep on waiting until we get the operator. So, this is what I was talking about earlier, saying, you realize you can't really figure out, it's so big, so big. Before one thing, if you say, it will say, remove not patch operator, you will get the operator. This will say, show me the screen. In the slide, you will assume that this operator is coming and I tell the screen. We will also pass this element. Because basically, you know, you will get the operator. The next thing is, it's saying, you will have to pass the mobile number. So basically, like, now you're asking for a mobile number. You get the mobile number. As soon as you get the amount, you make a remote intake. We are even working on, like, a dummy-based device. So, this is a preview of the, if you see, these are all basically generated. So, this is a cloud-based measurement. There's a tie on the medium. That's how the code has to be done. So, these are the scenarios. Let's say, we will change our part, basically, analysis. Interfer to this thing and generate a visualization, which basically will say that this element has this color that we will fit into the meta-resolution point. And also, the same thing will happen in the phone too. So, this is the same code basically running in both the phone and the app app part. So, these are the things that we have basically developed. Let's do UI, let's do Pro, and the part basically, in this next slide, the part will explore everything. It's the static UI. And Pro is the part basically where you write DSL-based code, which is sequential in nature. So, this is not something like a tie code. So, this is basically for writing sequential tools. Third is the cost platform, like a small reactant for, which will aid to solve the SQL environment. Also, we didn't need to add everything because this part is very hard. So, you can think. Thanks. A round of applause for this amazing session.