 the next for show, but it's going to happen about what you can expect for the next few months. So I'm going to share my screen and if you know you can start the recording. Okay, so very briefly what you can expect of the CK for the next few months next year. So basically you know that right now we are in the 1.3 version and we are going to have the next CK release next month, okay, in April. Probably around the 10th or 15th of April. So what we're going to have is in the 1.4, for example, in the new release is more features regarding local analytics. This was one of the most demanded features for the community, like being the Andrea up to be able to render charts, tables and well maps already rendering maps, okay, for the next versions. And this one to be possible in the next 100 release to 4 and the next CK release. So in the CK, as you know now after this workshop, you can like get the calculation from program indicators, okay, but now we can also, the CK is going to give you also information about how we can like draw the different layouts for rendering charts or for rendering tables, okay. This is going to be ready in 1.4 in April 2021 at the TI instance scope, okay, so we are like just in the context of the track identity instances of the enrollment. And then calculations across TI and events and how we can render those calculations is going to be ready in 1.5. 1.5 probably is going to be published in October, November 2021 of this year. Also in April, we are going to have data set indicators with all the calculations. Right now it's not possible, but then this is going to be possible in the next CK release in a few weeks. What else? The utility method classes, this is a work that has been already started like a couple of versions ago, but we are still like adding more and more logic into these utility classes, okay. For instance, we're planning to add more logic for valid data entry that this can happen in the SDK. Ping services is the server that I need to post the data, post or get the data, is active or is inactive, another different kind of helpers, okay. We're going to be, we're going to see more of the utility, how we can use utility classes and methods in the next workshop. Break the glass, right now it's not supported and it's going to be supported in the next in the next release in April. Working lists, also it is not supported. I don't know if all of you know what a working list is, but basically it's a filter that you can define in the server, a filter about how you can render, for example, the malaria cases that has been assigned yet, these kind of things. So basically, we can store all this information in the SDK as well, so the app can render in them when listing the events or listing the TI's, okay. We're going to have this ready also in the next and release, sorry, in the next one and release, yes, and in the next SDK version. And then authentication, open ID as well. This is going to be ready next month, okay, for people that want to, for other organizations that are using the cookies authentication, if they want to use the open ID. Then we still don't know when, but the multi-user multi-server, like given the users the possibility of like, and also this one was quite demanded for the community as well, like, you know, having a mobile that can be shared with different users and every user will have their own like the access to setup, okay. So right now it's not possible, but we plan to have this ready at some point at the end of this year or beginning of 2022, okay. And the same with having separated contexts. And there's an important use case in the community that there are some presentations they have sometimes like two servers, one for the TI, for all the target entity instance data, target data, and events, and they're fabricated, okay. But right now you need to like, you have one or you have another in your device. So we hope in next year we are going to be able to have like the same context of two different servers in the same database in SDK, okay. So then the user is possible for users to change the servers without losing the data. Then also we plan to have like more widgets and visualizations that are in instead of in the application that are in the, as a separate module in the SDK probably. So for example, you need three and that then we can have this in the SDK. So all the implementations, all the other custom applications that are using the SDK can have the same more visual components, okay. So that's a little bit idea because also there are some components that are more tricky to build than others and realization during three can be one example of this, okay. So yeah, having these visual components, the value type forms, the rendering types, something that we're going to talk more about in the second workshop. This now are in the all this is in the app, but we plan to move it probably by the end of the year or 2022 to the SDK as well. Meta to have a little sync, as you have seen during the presentations, when you are like downloading the metadata, you are downloading all the metadata, okay. You cannot specify in the SDK right now, it's not possible to specify, okay, I just want to, maybe I am only want to synchronize or to download just one particular program or one particular dataset or one particular unit. So right now it's you download everything that the user has access to or nothing, right. So we plan to have more clarity for metadata synchronization, okay, but really this is going to be happening in 2022. And then the last one that we have here, the online offline, okay. You know that the, well, one of the measures of having the SDKs, because it contains a local database or everything has been stored in the database, so the app can work offline all the time, right. But maybe you have one setup in, for example, you are working in a hospital that has an intranet there, so you don't, you really don't need to wait 15 minutes, 30 minutes, one hour for this integration to happen. And even you don't need to store maybe nothing in your local storage, okay. So in this case, maybe it's enough that the app will come work online completely, okay. So also this is something that we believe is really cool. We plan to have this, let's hope, by the end of 2022, okay. I don't know if we have, you have any questions, we are a bit above time, so if not, I will move to the next, the last presentation that is what is going to happen now, what is next. So is there any question? Okay, it's not. Okay, this is going to be just five minutes, I promise. The second workshop, okay. So this workshop, it was just an introduction. I know that some of you already know, already the SDK, but this is the first time that you can see this working. So in the second workshop, we are going to go more deeper in the many features that we, topics that we have discussed during this workshop and talking and also presenting new topics as well like the analytics model that we plan to have next month. This is going to happen in May between the fourth and the seventh, okay. It's going to be four days, three hours probably between three or four hours every day, online, of course, unfortunately, we cannot travel this year so far. And the objective is really to be a professional of the access to Android developer, okay, being a professional, but using the SDK, okay. So you know that it's going to be, we are going to have a project, okay. And if you want to finalize the workshop, the second workshop, we are going to give you a certificate, but to give you a certificate, you need to finalize a project, okay. The timeline for the project is still TBD to be discussed, but probably it's going to be the, sorry, the, this is the first day of June, okay, more or less the first week, first day of June, okay. So you can start thinking of the project now, if you like, we are going to give you some proposals, some ideas, okay. But basically here you have two options, so you propose what you want to do, okay, because you may be working for an organization or maybe your organizations, they are like asking you for an Android application based on the access to, or maybe you have your own idea, your own, you say, okay, I have really this idea that I think it's brilliant and I would like to, to implement this in an Android application, okay, that's the way that we recommend it, okay. And the only thing that we are going to ask you is just before like starting the coding, just contact us because we can guide you with and say, okay, but this is too much, this is going to be too complicated, or maybe the other way around, that I don't think is going to happen, but maybe no, you need to add more complexity here, okay. So in this option, if you would like to, you can propose whatever you want to do, but you have to let us know, okay, in Slack or we have Slack channels for Android, it's fine, or we can reach you in email as well, okay. The other option is like you can take one of our project proposals, but you know, it's like not completely defined, it's just to give you some ideas, something that you can do, and you can then, you need to elaborate more and maybe some more complexity there, okay, but it sounds so possible that we are going to give you now like three or four proposals. The best project will be presented in the ANVA conference, okay, but I think it's really, it's really interesting for you. So yeah, we really encourage you to do this, okay, the project, but again, this is a mandatory if you want to get a certificate, but if you are not interested in a certificate, you don't need to do it. In any case, please, because we need to, the Android team, the dev team, we need to really plan our time and see how many projects and how many developers are going to submit a project, so please register here, okay. I know that some of you have already done that like a month ago, but please do it again, okay, so if you can do it like now or after finishing this session, the better, okay. And because we are only going to take into consideration the people that have been registered in this form. And last thing, but important, I think it's obvious that using the SDK in the previous mandatory, okay, we are not going to pass or to assess, evaluate like any Android application that is not using the SDK, okay. It doesn't make sense, all these all these sessions are about using the SDK. Is there any questions regarding this? Okay, I'm sorry, just to add that I posted the link in the chat and zoom, so participants can just click on the link and register if they want to take part in the project. Okay, okay, I'm pleased to do it as soon as possible, like after this session, that will be perfect time. Okay, so my ideas, but again, we are encouraged to use your ideas, okay, but if you are in blank and you don't have and you don't know what to do, well, you have time to think what to do, but we can use some ideas like for example, like building a metadata dictionary, like an Android application that is a metadata dictionary, right. So in this case, we'll only work with metadata. And so we'll only download the metadata in the Android application, you need to use the data layer in order to, for example, to list the programs of datasets and letting the user to order in them by display name or less update. For example, if the user clicks on a program, you can list there the different program stages that the program may have, or if it is a dataset, the different dataset sections. Okay, if you open a program stage, you can list data elements that belong to the program stage. And whenever, for example, you select that element or select a program, you can also show up the description or the most relevant information about this particular piece of metadata. Okay, this is quite open. It's just give you some ideas or something that you can, that you can do. Okay, as actually something that the Android application is not currently doing. So I think this can be interesting also, you know, if you want to promote your application, your Android application to in the community as well. Okay, like other ideas, like, well, hopefully you already have been played a little bit with the Android application. And you know that when you are entering data in an event, when you are entering events, it displays all the of the events like a list, right? What we are proposing here is like, you can change the visualizations, change the layout, and maybe add, give the users the possibility of entering the events following a tabular layout. Like for example, as we are doing with the aggregated values. Okay, in aggregated, you know that you can, you need to add information that all the values are displayed in a tabular layout. For this one, we maybe recommend to use a tablet because it's going to be more user-friendly in terms of visualizations. And then one thing that you need to do is also the data needs to be uploaded or uploaded to front to the server. Okay, and maybe other idea, the last one, like, you know, showing data value changes in a table. For example, you may have like in a tracker program, you may have like a repeatable program stages. Okay, that, you know, that means that you can create like an event or several events for the same program stages. Okay, so it will have, of course, the same data elements. And then you will optionalize what are those changes in a table format, right? So you may have like a table and every row of a table can be an event for instance, and then you can see how the data is like evolving over time. Okay, and for that, you can like use the new module that is going to be exposed in SDK for the new version one for next month. This is just some ideas, as you see, it's quite, everything quite open, but we encourage you to start thinking of this. So if you want to do it, fill the form, fill the, fill the form please, and then think of some ideas and then just let us know in a slack. Okay, Victor or Marcos or Luis, I have this idea, or Jose, I have this idea. What do you think? The thing is, it's appropriate for the project, yes or no, and we are more than happy to help you with this process. Okay, and I think that's all from me. I don't know any questions regarding this.