Building a Sports Betting Platform with TDSOFT

Speaker 0: Alright. Thanks, everyone. We have Darius here from TD Soft. Darius, thanks so much for your time today. Why don't you tell the audience a little bit about yourself and a little bit about TD Soft?

Speaker 1: Hey, hey guys. Thanks for having me here. My name is Darius and I run a company in Central Europe and Poland called TDSoft. We built innovative software products for the customers, but also for ourselves. One of the projects we can discuss today is the one that we did for ourselves, which is the better signals.com.

Speaker 0: Yeah. So why don't you, why don't you give a little bit of background into Better Signals? And, also, in the same time, why don't you let us know, as you were starting to build these products, what led you to Directus? What kind of features in Directus kind of made you choose that? And then go into what BetterSignals is in your experience kind of building that out.

Speaker 1: Yeah. So actually starting from the, the Directus as I think this one came first in the company. Actually, we we started to look at this, product, back then it was in PHP, I think. I believe it was a couple of years back. Mhmm.

So it was on our radar. You know, the migration to JavaScript based, you know, engine, was definitely the thing that allowed us to move move forward with it. In addition, some of the developers, actually, it was, you know, It started from a couple of points at the same time. Well, first was obviously me, but then I was looking for a technologies that would allow me to start up projects quicker, you know, go to business logic as quickly as possible. You know, we want to be innovative, deliver innovative solutions, and there is no time to waste.

The, well, also, some of our developers started noticing directives from, articles, related to Jamstack. So it's kind of polar motive in here. Directors fits in quite nicely, and we were able to leverage, the features of directors in the better signals, project. It allowed us to cut the development time quite a lot. I I I was surprised how quickly we were able to deliver that.

Not only this, but we were able to deliver it in a way that was, very, very scalable. So, I mean, we just started a couple months ago. The traffic is still growing, but we're ready for 100 100 times more traffic. And we are not afraid of the costs, as how we set this up. Directors allowed us to really speed up the process.

Maybe, I can tell you a little bit about how we structured the project of Better Signals with Directus. Yeah.

Speaker 2: I'd love to learn more a little bit more about Better Signals, and that use case, you know, what you use direct us for. Exactly. Yeah.

Speaker 1: Okay. So just, and make the photo for better signals. We have a lot experience in the sports industry and the sports betting industry and in the talent industry. We work with sports betting companies, also affiliate companies, therefore, you know, natural idea of better signals, and, the idea of better signals, started. Better signals with, a new take on how we, provide sports tips, because we leverage the new media a lot.

I mean, the deep directors is the content hub that, you know, we push content through, not only on the front end, but also we leverage the, and the flows to and the automations, to automatically publish posts on different media platforms, like Instagram, Twitter, Instagram, and so forth. So, the, the, the whole concept is about delivering quality tips to people in a new ways that are more, you know, attainable with modern market, modern user basis. Got it.

Speaker 0: Yeah. Yeah. And you and you mentioned the front end, you know, gathering content from the front end and the back end as well. What did you integrate with Directus? Because some people do use Directus as their actual interface for customers to come on to whether they're building an app or whatnot.

But most people use, a different software for the front end. So what did you use to integrate Directus with for the front end, and how was that interaction between Directus and the front end? Was it easy? Was it easy to set up and easy to update? Give us a little bit of information about that.

Speaker 1: Yeah. Yes. So in line with, with ReactOS, we we used, a RemX technology that we were really looking at right now because, RemX has this approach of edge computing that, that we really need here. That allows us also to reduce the potential cost of the, you know, upkeep of the project. So we we manage the API of the Lexus.

We use the JavaScript SDK with with Remix, which means that we use it mostly for the back end, but also, you know, we have professional tipsters that provide the content to to our platform, to CMS they get. So there is a kind of customer who is using the the platform, which is our, content providers. So so it's, at the end of the day, Directus is a content hub, a content pipeline that runs everything from the backend. Got it. Got it.

Speaker 2: And I heard that, you know, while you were building this out, you get a little bit of help or assistance, at least in the project from, from one of our own employees, Roger. Is that how did you find him and, how did that discussion go and what'd you learn here?

Speaker 1: It's actually quite funny because, I I didn't knew that, he works for you guys. Thank you for that. But, you know, he was the author of the, the, The, the repository, the starter repository that uses, dynamics, and direct card same time. And, had a couple of, issues, regarding the setup. You know, I'm also tinkering with this software a little bit on myself because I have to have the knowledge of how to build stuff quickly.

And so I have reached out to Kim, over Discord channel, and he replied to me quite quickly. Oh, amazing. Only only later, I found out he actually works for it guys.

Speaker 2: Did he work for us at the time? Or was that I

Speaker 0: don't I don't think he worked for us at the time. I think He should. I think we saw how awesome this yeah. He's been putting out stuff around Dorekas for quite a while, and I think we we snagged him because his stuff is so it helps people, including himself, build tools quickly. He I think he's released and we can put this in the description, by the way, of the video.

I think he's released several games that he said he built in 20 or 30 minutes. You know? So they're pretty simple games, but they're kinda fun to play around with. So, for those of you out there who do build things and kinda use Directus, maybe we'll snag you one day. But yeah.

So I've I've I've followed along with you, Darius, because obviously we've had discussions before this and you and I have built up a little bit of a working relationship. What other additional product projects do you kind of have in mind to use Directus with or, or, you know, do you see Directus accelerating future projects in general for you guys?

Speaker 1: Yes. Definitely. Actually, we are in the middle of building another project, like, this is the project made for the customer. So as a service industry this time, but also sports related. We are building, a really innovative content pipeline, that allow that will allow us to provide, high quality content for multiple websites from one back end only, and actually really, really cuts the costs of, you know, proprietary content, you know, the editorial, before it's getting lost all over the world.

And Directus allows us to actually deliver that within the times, times, and the costs, that was that was not before. Basically, also, what's really interesting about how we can, build stuff with directors is that we can prototype a lot because the cost of prototype is very, very small. With that, can provide the model and structure to the customer, suggest how we will do this feed get the gather the feedback on the live, product from him, and actually modify things, ease without leveraging, you know, tons of documentation, beforehand or multiple hours, long calls. Just, just to try to agree on something that we can't build yet. This time with directors, we can actually first build, a quick prototype showcase to the customer, you know, see his feedback, which is really helpful.

Speaker 2: Yeah. That's awesome. You know, throughout this conversation, obviously, we've, we've talked a lot about how amazing Directus is and and everything we can do. But I'm thinking, like, you know, in the future, obviously, we don't do everything today. So what are, are there some features or, you know, capabilities that you'd like to see out of direct us maybe in future versions or, you something you'd like to see us build within the platform?

Obviously it's also custom, extensible to, to any, to some degree, but, what would you like to see coming in the future as as we progress?

Speaker 1: Yeah. Obviously, we we could come up with a Snyder list. I say now with every product. And I actually got, before this call, I got feedback from developers. Maybe the, this podcast doesn't have enough space to, to, to talk about very, very deep technical details.

There's a couple of points, that, maybe I'll tell you. My story where I seem to get stopped, in one or two, things that would be really, really amazing to have solved. First thing is, If I would want to create a product, with custom front end using JavaScript SDK with single sign on, I have to implement that by myself, the single sign on, and then find a way to authenticate the user. So, single sign on way to authenticate instead of only login password for, you know, SDK JavaScript SDK would be something that, I would devote for. Got it.

Okay. That that wasn't on the list from my developers. So,

Speaker 2: Is that already on on GitHub as as a request?

Speaker 1: Yes. And there's some discussion pending because it's not that easy.

Speaker 2: Yeah. Yeah. We'll start to upload it now then. Yeah.

Speaker 0: We'll we'll link it as well so everyone can upload it for you.

Speaker 1: There you go. Well, yeah. So if you want to create a very, very quick, application that allows you to quickly single sign login, do something, you know, showcase your work and log out, you know, that kind of simple stuff that might be a base of future SaaS product, you know, MVP. This is a little bit harder. We have to register properly and have login in the password or create SSO to something else, for example, you know, create accounts somewhere else to have single sign on capabilities and then only use the API.

So that's one thing. There is a couple things in the, CMS, but I have to say that, the speed of, development in Directus is really encouraging. I mean, we are seeing a lot, a lot of post merged. So for example, I don't feel like I have to push forward and ask for more because I know that there is a lot of stuff happening right now. So, I can be patient enough, in this way for a couple of things to to be resolved, but on the general perspective, you know, the, the benefits, drastically outweigh the issues.

I mean, as I mentioned to you, we can build a model very, very quickly, have an API ready, instantly create a quick front type of front end prototype, and also give the CMS to the customer within days. Awesome.

Speaker 2: Yeah. Well, we'll definitely take that, that feedback to the team as well. See how fast we can get that implemented for you. I know it's difficult though. I've been following that one for a bit.

Speaker 1: Yeah. No expectations. So I I I I I I I'm sorry. Yeah.

Speaker 0: Well, hopefully our developers are watching and encouraged. We are moving towards you know, we do put a lot of releases out there, a lot of pools or PRs that are done quickly, and we're kinda moving towards this continual release motion where we're just continually releasing new features, bug fixes, extensions, whatever that may be. I think part of your last answer kind of, answered some an additional question I was gonna have, some advice for other users, which also, you know, it's easy to develop. And is is there any sort of other hints that you would give users who are looking to either start using Directus or are using Directus and building a similar application? Any, you know, one or two really good tips that you've learned either the hard or easy way that you would give to other users?

Speaker 1: Mhmm. Yeah, for sure. I mean, first of all, try to leverage the, the cloud version, the free cloud version that you have. It's it's good enough. You you can you can start with that.

You don't have to, you know, try to host things by yourself from the day 1. Secondly, we had an, ability to work in a team of, 5 developers, on better signals.com. That we noticed that it's really good to give them some space to actually track things out and see their platform capabilities before they're not jumping into work, because there are some trial cuts they they could take. So actually in, in terms of the recommendation, just, you know, explore the platform by yourself, you know, see the breadth of this before you go dive into some, you know, specifics. That that's something that I can, I can really, advise here?

And yes, leverage the pre cloud version. It it has enough capabilities.

Speaker 2: So Darius, before the call, you were mentioning, really cool flow that you built inside of Directus. I'd love to to see that if we can show that off.

Speaker 1: Yeah. Yeah. For sure. Let me just show my screen for you, and then cool. And the cool thing about Slows is that in this product, they allow us to really streamline their process of content delivered to different platforms.

We use additional automation software to to continue deliver the, the content. But as you can see, it allows us to, show the the processes in a very pleased way. For example, when we when someone from the editors, editorial team creates a new signal, then we get notified. So we can, for example, quality test that and approve this, without having to check the platform every time. We can also, for example, publish every scheduled signal.

So, you know, scheduling is also part of this, flow.

Speaker 0: I also appreciate how it's in dark mode. I myself am a dark mode person, so

Speaker 1: I'm a fan

Speaker 0: of it. I love the contrast.

Speaker 2: Love the icons too.

Speaker 1: You know, it's all about developer experience, right? We invest a lot in developer experience, further experience. So as you can, I can show that you guys, the, the really cool thing is that I show you the one that will be more complex? Yeah. So I could it's really clear.

I mean, even there is a a blog that says hack away, tag or something. It's too clear as we are doing something here for Yeah. Everyone who is not part of the project yet, it's very, very easy to actually understand what's happening there. So the the concept of flows and the visual presentation of flows in this platform is, really, probably best in class.

Speaker 0: Okay. Wow. We're gonna we're gonna sniff that and and quote that in the future as well. Yeah. So I do know in the flows, you are running, running one with JavaScript in line.

That's a new feature. What's your experience been? Was it hard to learn flows? We're putting out more documentation around that all the time. I think we recently announced or released a flows cookbook.

So what's your experience been building Flows? Because this is a feature that as Pedro and I talk to other prospects and users, they really start to understand the power of it. You know, obviously, visually, it's easy, but building it out once you learned it, is it extremely easy to build new flows?

Speaker 1: Yes. So it it needs a minute or 2 to, you know, get accustomed with us, and fully understand their power. So I I don't have much advice here except that maybe, just look at the documentation. I know that documentation is still being built for that. I don't think if I have anything, you know, interesting to say.

Speaker 0: No, it's good. It's it's, it's great to get a look at it.

Speaker 1: Yeah. And, also I can show you our log screen, you know. Oh, yeah. Nice. One of one of the things that are really cool about Directus is, you know, the theming option and being able to, also showcase to the customer the c CMS that he ordered that has his own brand and colors and style.

Mhmm.

Speaker 0: Yeah. I think that's that's what really surprises me. It's just people, you know, don't take advantage as much as they could with the the theming. You know, we're we're building out a theming option where it just makes it even easier to change colors and whatnot. But even putting your logo up there, the whole the whole platform itself is white labelable, so that's awesome to see that you've done that.

Speaker 1: Yeah. Yeah. So brand, consistency and brand awareness is from the 1st day in the Battery Signals comp projects. So it was in a conscious decision to ensure that everything we do is, you know, following the the brand guidelines here, and it looks really nice. Yeah.

I can also show you while you're on the call. I could also show you that we have just created quite simple, you know, data model that allows us to, basically deliver content tips, but not only. For example, creating, you know, a static page. It's just that, that simple model here.

Speaker 2: I like that. I like

Speaker 0: that WYSIWYG editor with a 1,000

Speaker 1: Yeah. And there are these are our tips as you can see. And those are being managed by, by professional, content providers, you know, sports enthusiasts, people who have a lot of knowledge in sports who deliver those insights to us. And then we streamline those into our various media platforms. Got it.

Speaker 0: Awesome. And then this this is where, you know, people put in these tips and whatnot, and then the flows kind of, you know, work it through your process. Correct?

Speaker 1: Exactly. And then they end up here. Got it.

Speaker 0: Alright. Perfect. Well, since I've been following along and we've been interacting again for a little while, I'm excited to hear what the plan is for, you know, the next 6 to 12 months, maybe even further out if you wanna discuss it. But what are some things that you guys at TD Soft are planning to build and release?

Speaker 1: Yeah, sometimes are huge, obviously. In our company, we bought at least 20% of our income into r and d, which means internal product development because we have to level on ourselves, you know, on our own issues before we actually propose to customers on solution. We have full, planning for the whole next year for the better signals dotcom. We are just launching. I I think it'll be it might be even live once the podcast is live, though, or gamify.com platform, which is a business gamification platform for our companies.

We use that on ourselves, and our whole team is working together towards achieving their own personal goals, personal development, and, watching their position on either boats and also buying some stuff from the, company store. I hope that other people will find it best in those. So, maybe I can suggest, interested visitor store visit our website once in a while to see the news as we always have something news in our pipeline.

Speaker 0: Yeah. I know that I'm Pedro and I are a little competitive amongst each other as well as with other employees here. So we will definitely be checking that out because any way that we can officially brag over the other person, I think we're, we're, we're all for that. So

Speaker 1: Yeah. Yeah. The most important thing about, you know, gamification is to be over that other person. It is.

Speaker 2: It's helped you competition is great for work.

Speaker 1: Yeah. Yeah. I mean, we know I can show you our library. It's small, but, you know, we treat self development seriously here, which means that it's not only about tech, but also about personal development and also, you know, Healthy lifestyle, all the things that come together to actually productive life and fulfilling life and not only man, just work. And I hope the same for others.

That's why we published this stuff.

Speaker 0: Yeah. I think that's where, you know, you guys developing, putting 20% of your time to in in revenue towards research and development. I think that's kind of the model that a lot of technology companies use. And, for example, I mean, Google itself has developed so many products just from the free time or the time that they develop or they designate towards developing new fun projects, whether it be a side project, somebody just wanted to mess around with, or actual time that they just wanted to try and build something, that's that's where new and great platforms come about. So I think that's a a great amount of time and a great, option that your employees have.

Speaker 2: Awesome. Cool. Well, I think that's that's it from for our questions. Well, thank you, Darius, so much for your time. And, you know, we'll we'll obviously be following along with TDSoft.

Please let everyone know how they can contact you to perhaps contract out some work or build something with,

Speaker 1: obviously you can spell my name in Google search, right? Yeah. There you go. Easy. You know, I hope there'll be some link in the description or something.

Yeah. We can do that. Yeah. And then I will also, you know, advertise or maybe comment under the, you know, social media appearances. So there will be a way to find me.

Absolutely.

Speaker 2: We'll list all your information here in the description and, and be on the lookout for future projects. But again, thank you for being a part of this. And, Yeah.

Speaker 1: Yeah. Yeah. It was a pleasure, guys. Thanks for having me here and, let's continue building stuff.

Speaker 0: Yeah. Absolutely. Thanks so much. And

Speaker 1: scene.