 Okay. Oh, time starts already. Okay. So no more jokes about Zoomer sessions. I'll give you 30 more seconds. Thank you. So, okay, I'm talking about is about DNA genealogy. And for those of you that have no freaking clue what I'm talking about, there is a short intro on that part as well. Life day more at the end. And everything has been built with Meteo. I see already at least one person with a Meteo t-shirt. Really cool. As promised, I'm not sure what you know about DNA and all that. There's three different types of DNA that we have with the YDNA, which is something that builds people like me, right? Opposite from those 50% of the population that doesn't have a Y, right? So only us male have the YDNA, the empty DNA is the mitochondrial. Everybody has it, right? That one has been used basically to follow your female line, so your mums, mums, mums, mums, mums, right? Until we end up with Eve. The YDNA actually brings us to Adam. So this is about currently there. They're still not sure how far we go back with that one, but it's about 330,000 years, plus, minus. So pretty far back. And then we have the autosomal DNA or ATDNA, which is basically all your ancestors, almost all your ancestors. There's a reason because it's all randomized. You will lose some of the information, which for example, if some of you are interested in a test and look at your ancestral composition, which by the way, there is no pure race. For those that don't understand that, we are all mixed, right? You will find that out. There is no single person I think in the world that is really, really pure, unless you're living in a cave for the last 10,000, 20,000 years, right? And you'll always marry your sister. So, yeah. It happens, it happens. So there's two graphs. If you're interested in, everybody knows that we actually started... Sorry, this is Adam. We started right here, which is another thing that some of those races don't understand. We were all black once, right? We just changed our color in a slightly brighter sense over the years. And then we just populated over there obviously all those Asians in the room. You guys were pretty good. We marched here, took a shortcut, right? Well, guys like me, actually, we went up north. And if there is somebody here from the US and South America, you really went a long way, right? You went all along Bering Street, then you waited for the Ice Age to stop, and then you went all the way down to South America. Crazy dudes. Same for the Australians in here. You also went very, very far. Okay, so, TLDR is about the next generation of DNA tools. The next generation means there is already some other tools existing, but I think something like that is actually missing. So, how does it work? And you will find this on the website as well. I did actually build it myself, run an illustration on 1990 Zines. And this is the winner that I came up with. It's very, very simple. You get a DNA test, so you either spit into a tube, or you actually get a small swab and you just squirt your inside of your cheek, right? Then you send it in. Later, they're going to give you some results back. So, there is a couple of companies there that you can do. There is three main ones in the world, all in the US, Family Tree, DNA, Ancestry, and 23andMe, which you might have heard about. Then this tool is actually updating you automatically on the so-called matches. Matches you don't necessarily mean that you're being closely related, blood related. It can be a wrong match as well. Those of you that know Confusion Matrix, they know there is wrong positives and wrong negatives. So that is wrong. There's a thing called tri-relation. We will show that later what it means, but basically only those that are being tri-related are your blood relatives within the last, let's say, 200, 300, 400 years. Then there is some... Somebody said actually one of the better users said this is a Facebook for family. So there is a closed user group where you discuss certain topics with your family because a lot of adopters and offerings are very, very interested in that stuff. And that is obviously a very, very sensitive area because not everybody wants to find out if he has any children or not. Or the children actually find him later on. Versus the interest, obviously, of that person to find out who are the real biological father or real biological parents in the sense of offerings. Then it locates all of this on a map with the timescale, and that makes it easier when we just say, more or less the time period and we're moving pretty close. So maybe that's actually how we're related to each other. And the main purpose is to solve the puzzle pieces together. It is a puzzle, it's a very, very complicated puzzle, I can tell you. And then you're extending and verifying your family tree. If you remember the orphans, they start basically with a blank page. They don't even have any cousins. No aunts, no aunties that you can call or whatever. And then the whole thing is about solving and optimizing it so that you have more time to communicate with them. So when I evaluated this idea on SurveyMonkey last August, I came up with 237 people that filled out the questionnaire and amazingly, 74% said, yes, I would be willing for that. When I was being completely blown away, I thought, if at all, I'm pretty lucky if it's the hour we're on, 26%. So 74% is like, wow, oops, we missed our supreme leader. I asked them, at the end, it was six questions only. I didn't really explain. You know much more about the solution than them. And at the end, I asked them, are you willing to give me your email address and I'll keep you updated? 138 people gave me their email address. And that again is a wow, right? In my opinion. So there's a lot of talk about MVP or not MVP. I read a good quote which basically says an MVP, if it's not finished within one month, it's not an MVP. So this is now, we're back in June. I started in August, so it's pretty sure it's not an MVP, right? But I knew relatively well what I wanted to do. From the potential, there is more than three. This is actually an outdated number. I think now 3.2 to 3.4 million DNA tests out there. Not people that may test. That is a bit less. But the potential has been pretty big. So finally stopping all that and coming to what is our common interest. So from the architecture, it has been built for the big screen. You will see why that is. Also because actually most of the end users are elderly people, even older than me. So that means big fonts, black and white, for example. It works on mobile tablet, but it doesn't work. It's not specifically been looked at. So one of the principles of Meteor is that it all takes care of the responsive part. Also it comes with MongoDB. As a database on the end, I know it's not ideal. I know there are better, no SQL solutions out there, which I used in the past, but there are some things that are going on right now with GraphQL and so on to solve that problem as well. Then I did something which maybe, now many people have done, I split the front end and the back end. There's two separate apps. Pure front end app and there's a pure back end app. The main reasons are the three S that I showed up here is security, the scaling, and actually the size. The size meaning in how much data actually your users have to download on the front end. Because 80% of the customers are in the US and I can guarantee you our internet is 10 times more supreme than over there. Donald Trump won't change that. The scaling is interesting because the back end is actually a job worker. It submits job. Actually right now there should be some job still working because I just started and it does that all the time. Until there's no job and then it waits. So it's very easy to scale that up if there is ever going to be too slow. But I don't have to do that. On the front end if there's a lot of users then obviously sometimes you have to upgrade a bit earlier and scale it up. Database is separate as well. All of that is hosted because honestly I'm not an assist admin and I don't want to deal with all this stuff. Communication is via DDP which is something that Meteor actually invented. Principles behind is publication subscription. So on your client you're publicizing a certain amount of data that you want to show down to fields and down to other filtering criteria. And on the front end you are subscribing to that. As soon as there is an update automatically your data has been showing on the front end on any connected devices. It's always up to date. It works just. I mean if you haven't tried Meteor just give it a try. They have some examples there. It takes about 20 minutes to get it up into the cloud deploy it including user accounts and everything. If you're following it. So learning I can show you some screens. If you're interested later on just approach me. Compose IO is where I run my database. These guys are really, really good. I was first on Modulo's change to Galaxy which is actually owned by Meteor Development Group. I'm not too happy about their support. Left some comments in the forum there. As a paying customer I think I'm allowed to say what is shitty. So you can see the differences actually from the information that you get is the worst at Galaxy. But at least it runs. Modulo's changed their scripts and the problem is that the data couldn't upload anymore. My script wasn't uploading not running. And I'm not going and updating any kind of scripts or whatever kind of stuff. That's not mine if I run it. So we did a lot of, I did a lot of testing here. I used MailChimp and I, for example, I tested. This is on testing different subjects lines. So it just gave 76.5% versus 60%. Just by changing the subject line. Response on it. I tested different timings and this goes from 47% to 64%. Again, just by sending the same email fully identical at a different kind of time. Just play around. We'll find out where your people have been interested in. This is a small scale with 140 people that I mentioned earlier on, the beta testers. I asked them about features because I want to implement something and build something actually that these people are going to use, not that what necessarily I think has been the same. So there was a different view from my perspective but this is what in the future people will be paying for. So obviously I built what they want, not what I want. And I said before, I did an illustration on 1990 Zines. Completely different. This is actually the winner. This is the one that I like more. Again, I asked all my beta testers, 80% voted here, 20% there. So as good as this guy was, it's a complete comic. I did it for the first time. Pretty amazing. So this is, by the way, is $599. The US dollar gets you that. Pretty amazing stuff what you can find over here. And I test also A and B messages. Again, big differences here. Conversion rate, 33% improvement. I mean, just like the main message is testing, testing, testing as you develop. You know what I took by now. Okay. So while we now, I have about 80 testers out of these 140 people. The beta launch on 1st of June. And by the way, I hired or I'm in the process. I mean, I offered already to the full stack developer. So if you buy chance because I know that nobody looks up, beta has actually discussed forums and I posted the jobs there. None of you looked it up because you don't know. But if you do, it's too late already. Okay. So that's the main message. Sorry for that. And yeah. What else do we have? Probably best if we just finally go into the app. Okay. This is how it looks. The address, by the way, is dna genealogy.tools. I know you guys understand why it's .tools. My beta users are a bit older. Like I said, I have still some problems why there is no .com. .cools.com and so on. So if you're interested to follow it up, right, and you click on this, then you've got a message to leave your details there. You will get updates from it. Normal feature. Everything that has been built, standard package, is actually this user account. It comes with Meteor. You don't have to do anything. This is how it looks. Sorry. I'm not updating this. So what I'm using is a principle of cards. This is a toaster message that comes in because one of those unique problems is that I have two different applications. So how do they talk to each other? via DDP. Yes, but how do they talk to the front end, to the user? Because the backend is a job worker. He does a job and what does he do then? He can tell the front end, update the screen, display new cards and all this kind of stuff like it's doing right now. But the user is sitting there and says, like, why is nothing happening? He clicks and clicks and clicks and thinks the application has crashed or whatever, but he hasn't, right? He doesn't understand the principle that whatever he does is being pushed there and if there's many users, it gets executed but it might take some longer time. Okay, so, that's me by the way. Can you stop the recording please? Sorry, forgot to mention. The reason is because this is some live data. So we have actually