1 00:00:06,719 --> 00:00:11,359 Hello, Welcome to Adventures in Angular, the podcast where we keep you updated 2 00:00:11,400 --> 00:00:16,320 on all things Angular related. This show is produced by two companies, Top 3 00:00:16,359 --> 00:00:19,879 and Doves and Onvoid. Top and Doves is very great Top and Doves, 4 00:00:19,879 --> 00:00:23,600 we get top and pay and recognition. We're working on interesting problems and making 5 00:00:23,640 --> 00:00:29,719 meaningful community contributions. An Onvoid which provides no design and software development services on 6 00:00:29,760 --> 00:00:34,840 a task basis, so clients only pay after tasks are delivered and approved. 7 00:00:35,280 --> 00:00:39,840 In today's episode, we will talk about a company called Timing and some of 8 00:00:39,880 --> 00:00:45,280 the tools that this company provides for US web developers. My name is Lucas 9 00:00:45,280 --> 00:00:48,920 Spaganini, your host in the podcast, and joining me in today's episode is 10 00:00:48,920 --> 00:00:55,880 a very special guest, Rina Segosh. So, Brina, let me give 11 00:00:55,880 --> 00:00:59,159 you a little bit of intro and then I'm just going to pass on the 12 00:00:59,159 --> 00:01:03,519 ball to you. So. Rinna is a developer relations manager with more than 13 00:01:03,640 --> 00:01:10,319 four years of experience with foodstack development, cloud and AI products. She's been 14 00:01:10,439 --> 00:01:15,239 hacking away tech products since the age of fourteen, much earlier than myself, 15 00:01:15,480 --> 00:01:22,719 and after five years of writing software and evangelizing products at IBM and Digital Ocean, 16 00:01:23,120 --> 00:01:26,959 she has turned to her passion to educate developers and become a developer advocate 17 00:01:27,519 --> 00:01:36,040 as a developer relations manager at Tiny. So Rina very happy to have you 18 00:01:36,079 --> 00:01:38,319 on the show. Thank you for taking the time. Thank you so much, 19 00:01:38,400 --> 00:01:42,079 Lucas. That was a very sweet introduction from you, and I'm really 20 00:01:42,120 --> 00:01:48,319 excited to be here at talk you today. Yes, yes, it's easy 21 00:01:48,359 --> 00:01:52,719 to introduce people that have great accomplishments, so thanks for making it easy. 22 00:01:53,920 --> 00:01:57,280 So yeah, Marina, let's just take it from here. So can you 23 00:01:57,480 --> 00:02:00,920 introduces, Like, just give a pitch of what is tiny, Like we 24 00:02:00,959 --> 00:02:06,799 know that it's a company, but which products does Tiny have that we as 25 00:02:06,840 --> 00:02:13,000 developers should know about? Like why should we care? Right? So, 26 00:02:13,840 --> 00:02:20,800 tiny is a JavaScript based rich text editor component that can embed right into your 27 00:02:20,879 --> 00:02:27,599 web applications. So imagine you are actually writing a description on Shopify today. 28 00:02:28,319 --> 00:02:34,000 You actually are using TINYMCE to write that description any sort of If you have 29 00:02:34,120 --> 00:02:38,159 ever typed any sort of rich text on the web, you most likely have 30 00:02:38,400 --> 00:02:45,280 used tiny MC. It's like trusted by several enterprises like IBM, Microsoft Salesforce, 31 00:02:45,680 --> 00:02:49,680 as well as some of the things you touched day to day like Shopify, 32 00:02:49,960 --> 00:02:53,159 mail Chimp, and so many more products. Right So it is simply 33 00:02:53,199 --> 00:02:59,719 a JavaScript based rich text editor component, but it is really important for developers 34 00:02:59,759 --> 00:03:04,000 because it provides more than just bold italics and underline, which is what we 35 00:03:04,080 --> 00:03:08,080 think of when we think of rich text editor. It provides features like markdown 36 00:03:08,120 --> 00:03:14,599 support, AI Assistant. We're actually, you know, seven point two some 37 00:03:14,680 --> 00:03:19,280 point one is coming up and we have some more support for our AAS system, 38 00:03:19,840 --> 00:03:23,520 So kind of teasing that over here in this podcast as well. So 39 00:03:23,919 --> 00:03:28,800 several great features to really enable your users at the end of the day, 40 00:03:28,879 --> 00:03:31,120 who are creating rich taxs or we're creating some side or sort of content, 41 00:03:31,680 --> 00:03:36,439 to have kind of a seamless experience as they're getting a content as well as 42 00:03:36,439 --> 00:03:40,319 a smart experience if they want to use a awesome awesome Okay, So it 43 00:03:40,360 --> 00:03:46,240 seems to me that this is the most or at least one of the most 44 00:03:46,240 --> 00:03:53,400 super charged reach tax editors on the market today. So is that basically what 45 00:03:53,439 --> 00:03:58,639 you're saying. I would say so in terms of it's not just it's not 46 00:03:58,840 --> 00:04:01,800 just feature rich, right, it's feature rich, but it's also ready to 47 00:04:01,840 --> 00:04:08,159 scale for you. So tiny MC can be something as simple as running a 48 00:04:08,199 --> 00:04:13,520 few features. You can customize it very quickly, or something as complex as 49 00:04:13,639 --> 00:04:17,720 having document converters, revision history all kind of built into the editor. So 50 00:04:18,240 --> 00:04:25,079 you can use TINYMC for a blog post in your web application to type up 51 00:04:25,079 --> 00:04:30,879 a blog post. Or you can also use TINYMC in invoice processing where you 52 00:04:30,920 --> 00:04:34,759 need to edit some invoices, comment and collaborate with other team members. So 53 00:04:34,800 --> 00:04:39,480 it can be as complicated and as simple for a rich text editor as you 54 00:04:39,600 --> 00:04:44,319 want, and it scales interesting. Okay, so you brought up some more 55 00:04:44,360 --> 00:04:48,240 complex use cases that I hadn't thought up at the beginning, because at first 56 00:04:48,279 --> 00:04:56,439 I only thought about something that could export markdown or just export it as HML 57 00:04:56,600 --> 00:05:02,000 and support markdown as input. But this is a lot more complex than that, 58 00:05:02,079 --> 00:05:05,959 because as soon as you mentioned like invoices, I even thought about like 59 00:05:06,079 --> 00:05:15,120 an email editor that like for email marketing, that is not just regular texts, 60 00:05:15,199 --> 00:05:19,040 but something a little bit more complicated. So what I wanted to know 61 00:05:19,199 --> 00:05:28,120 is what are the most relevant use cases for tiny that that come to your 62 00:05:28,160 --> 00:05:31,720 mind and that people generally use it for, because perhaps people are not thinking 63 00:05:31,720 --> 00:05:40,240 about the possibilities of where to use that, right, So if you if 64 00:05:40,240 --> 00:05:44,519 you think about a rich text editor, I think the first thought that you 65 00:05:44,560 --> 00:05:48,680 get is like in content management systems, right where you have the ability to 66 00:05:48,759 --> 00:05:55,560 maybe create a template, have the bold italics underline, have the ability to 67 00:05:55,600 --> 00:06:00,079 paste in some media, spell check your solution, things like that. But 68 00:06:00,120 --> 00:06:03,399 as you said, you can actually extendc to a bunch of different use cases 69 00:06:03,439 --> 00:06:10,240 like email and messaging platform Right there are out of the box templates that you 70 00:06:10,240 --> 00:06:15,399 can actually go to the tiny site and see the email and I believe messaging 71 00:06:15,560 --> 00:06:21,079 template or solution that and you can actually see how an advanced template can actually 72 00:06:21,079 --> 00:06:26,399 fit right into your editor and how you can edit that for email marketing software. 73 00:06:26,920 --> 00:06:32,319 It can also be used for document management systems CRMs. Right TC is 74 00:06:32,360 --> 00:06:35,879 a great way to use it for a CRM, But for example, if 75 00:06:35,920 --> 00:06:42,480 you want an email template where you're like, hey, this is my lead, 76 00:06:42,839 --> 00:06:45,959 this is what my project is worth, you can actually create email templates 77 00:06:45,959 --> 00:06:49,439 often there as well. So there's a lot of different use cases ranging from 78 00:06:49,639 --> 00:06:55,879 CMSs, LMSs, your internal applications as I mentioned, like the IBMS and 79 00:06:55,920 --> 00:06:59,959 Microsofts are using them internally, and then you can also extend it to email, 80 00:07:00,160 --> 00:07:04,839 messaging and CRNS and DMSs and so on and so forth. So it's 81 00:07:04,839 --> 00:07:10,839 a great tool that ranges ranges from a wide ranger solution. It's simply like, 82 00:07:11,079 --> 00:07:13,439 if you have a use case for rich text, or if you have 83 00:07:13,480 --> 00:07:16,720 a use case to collaborate over a piece of document, collaborate over text, 84 00:07:16,759 --> 00:07:21,720 and you want to build that functionality into your web application, Tiny is a 85 00:07:21,839 --> 00:07:27,680 great great place to start. Okay, gotcha, And we were referencing the 86 00:07:27,720 --> 00:07:30,519 Tiny website. For anyone that is just listening to the show and wants to 87 00:07:30,600 --> 00:07:34,839 check that out is Tiny dot cloud. So just step that out in your 88 00:07:34,879 --> 00:07:40,680 browser and you'll be able to see demos of the product and some examples of 89 00:07:40,759 --> 00:07:45,800 solutions and use cases for it. So, Rita, let me let me 90 00:07:45,839 --> 00:07:48,040 make the question that a lot of folks may be thinking at this moment. 91 00:07:48,120 --> 00:07:54,680 There are so many open source libraries out there. There's just so many things 92 00:07:54,680 --> 00:08:00,319 that we can get for free and even customize them their m T. We 93 00:08:00,360 --> 00:08:03,160 can just even bundle in our code base if we want to make changes through 94 00:08:03,160 --> 00:08:11,079 the source code. So, which audience do you think would benefit more from 95 00:08:11,560 --> 00:08:16,279 Tiny and which audience do you think would would not be the ideal customer for 96 00:08:16,399 --> 00:08:22,759 Tiny and would be better served by looking for an open sourced library. That 97 00:08:22,800 --> 00:08:28,079 they can just install and hack it away. Right, that's a that's a 98 00:08:28,120 --> 00:08:33,399 great, great question, uh, And that's something you know we've we've probably 99 00:08:33,639 --> 00:08:39,360 kind of dabbled with even internally a tiny MC and the simple solution can be 100 00:08:39,720 --> 00:08:45,120 if you are working on any kind of project, right, that's beyond just 101 00:08:46,000 --> 00:08:50,039 a hobby project. If you're working on a front facing application. It's a 102 00:08:50,039 --> 00:08:54,519 small side project that you can see scaling and growing. If you're going to 103 00:08:54,559 --> 00:08:58,320 scale your application, then I think tiny MCEE is the way to go. 104 00:08:58,559 --> 00:09:01,519 And I'm you're not just saying that because I work for tiny C. I 105 00:09:01,639 --> 00:09:05,919 work with other editors in the market and as you mentioned, that could be 106 00:09:07,039 --> 00:09:13,039 MIT licensed and things like that. And the thing about that is maintaining a 107 00:09:13,159 --> 00:09:18,679 rich text editor is hard, right. We have over fifty sixty engineers working 108 00:09:18,720 --> 00:09:24,120 on this, and it's because of the complexity that comes with dealing with text 109 00:09:24,200 --> 00:09:28,159 on a website. It's pretty complicated. If you've ever worked with dom mainnipulations, 110 00:09:28,240 --> 00:09:33,840 you know how complicated it is. And that's kind of the reason why 111 00:09:33,000 --> 00:09:37,679 I think tiny is great for these kind of applications that need to scale, 112 00:09:37,679 --> 00:09:41,840 because a rich text editor is not where you want to be spending, especially 113 00:09:41,840 --> 00:09:45,120 if you're a small team of engineers, most of your time developing. You 114 00:09:45,159 --> 00:09:48,200 want to be able to plug this application in, make it look and feel 115 00:09:48,240 --> 00:09:50,559 the way you want it, and then move on to the next thing. 116 00:09:50,679 --> 00:09:54,639 Right, So if you're a small team of engineers, highly recommend. If 117 00:09:54,679 --> 00:09:58,720 you're an enterprise or as SMB or medium sized business, again it's the same 118 00:09:58,759 --> 00:10:03,759 sort of do you really want to be spending a lot of time developing and 119 00:10:05,000 --> 00:10:09,639 wrapping your own rich text editor or do you want to kind of move on 120 00:10:09,720 --> 00:10:13,039 to the next big thing in your project and adapt something that's already tried and 121 00:10:13,080 --> 00:10:18,960 tested. Tiny has over twenty years of experience in the industry. We've you 122 00:10:18,000 --> 00:10:22,320 know, a lot of developers, over a million developers at this point, 123 00:10:22,360 --> 00:10:26,480 have grown with Tiny in these past twenty years, and they've seen us transition, 124 00:10:26,799 --> 00:10:33,000 evolve and adapt to the quality and standard of web development. As you 125 00:10:33,039 --> 00:10:37,879 know, the decades have progressed. So we have twenty years of experience coming 126 00:10:37,919 --> 00:10:41,120 in. But more than the twenty years, it's just we've been stable, 127 00:10:41,320 --> 00:10:45,679 we are consistent, and we've proven to be able to scale to the needs 128 00:10:45,679 --> 00:10:48,639 of our customers. And I think that's really what sets tiny apart from you 129 00:10:48,639 --> 00:10:52,600 know, just picking up a rich Tex editor, because the other thing is 130 00:10:52,679 --> 00:10:58,120 you don't want your users and your web application to come in start typing a 131 00:10:58,120 --> 00:11:01,919 piece of text and then it gets bluggy. Imagine if someone's trying to create 132 00:11:01,919 --> 00:11:07,759 a blog post on your website or content management system, they drag and drop 133 00:11:07,440 --> 00:11:13,519 a image and then the image starts creating all the text. Super buggy. 134 00:11:13,759 --> 00:11:16,000 That's not what That's not the experience you want for your developers as well or 135 00:11:16,039 --> 00:11:20,200 for your users as well. So from a developer experience, it's great because 136 00:11:20,200 --> 00:11:24,440 it's very quick and easy to set up. You can get most of the 137 00:11:24,480 --> 00:11:28,399 basic functionality, in my opinion, up and running in within five to ten 138 00:11:28,480 --> 00:11:33,600 minutes if you're an experienced developer, or even if you're like an intermedia developer. 139 00:11:35,440 --> 00:11:39,000 And on top of that, I really believe that from a user experience 140 00:11:39,039 --> 00:11:43,559 point of view, we are a lot less buggy than a lot of open 141 00:11:43,600 --> 00:11:48,919 source solutions out there, gotcha understood. So it all boils down to how 142 00:11:50,080 --> 00:11:56,080 much quality you're looking for in the shortest amount of time possible. Because at 143 00:11:56,120 --> 00:12:00,679 the same time, let's be honest, if anyone really wanted to spend enough 144 00:12:00,799 --> 00:12:07,960 time and resources they could get an alternative version quote unquote free, because it's 145 00:12:09,000 --> 00:12:11,200 not really free if you have to spend a lot of your time to make 146 00:12:11,279 --> 00:12:16,919 it as good as as what tiny already offers out a box. So at 147 00:12:16,960 --> 00:12:22,879 the end of the day, if you consider that you're still going to have 148 00:12:22,960 --> 00:12:30,559 to spend your time, which might be even more expensive than just the the 149 00:12:30,559 --> 00:12:33,879 commercial license for Tiny, then at the end of the day, it all 150 00:12:33,879 --> 00:12:41,600 boils down to the same amount of financial resources invested. But at one side 151 00:12:41,679 --> 00:12:46,039 you get a component that is ready to go from the start, and on 152 00:12:46,080 --> 00:12:48,799 the other hand, you take a lot more time to get it up and 153 00:12:48,840 --> 00:12:54,159 running. Yeah, it really is that, and it's also technical debt right 154 00:12:56,159 --> 00:13:00,919 if you're I've worked for software engineering teams and one of the I think things 155 00:13:00,960 --> 00:13:03,759 that you need to keep in mind whenever you're introducing a new feature or product 156 00:13:03,879 --> 00:13:09,200 within your major project is how much technical debt is that going to introduce for 157 00:13:09,240 --> 00:13:13,639 a small term. Right. The fact that Tiny is maintained by fifty six 158 00:13:13,639 --> 00:13:16,559 people as engineers, you know they're going to take care of all the bugs. 159 00:13:16,679 --> 00:13:20,559 Especially you know, if you're a commercial licensed customer, you're going to 160 00:13:20,559 --> 00:13:24,559 have the extra one on one support. So I think that is another major 161 00:13:24,600 --> 00:13:31,679 consideration as you are thinking about, you know, a rich text editor for 162 00:13:31,799 --> 00:13:37,440 a business, because it's not only upfront engineering cost, it's also technical debt 163 00:13:37,600 --> 00:13:43,399 maintenance of the component. So there's so many different aspects when you think about 164 00:13:43,399 --> 00:13:48,200 like a software engineering project, especially a full stack project, and I think 165 00:13:48,200 --> 00:13:52,360 it's kind of just determining how much time and money and resources you want to 166 00:13:52,399 --> 00:13:58,559 allocate to a rich tex editor component. Awesome. Now let's talk about it 167 00:13:58,679 --> 00:14:03,600 a bit more from a developers from a developer standpoint, because I think it's 168 00:14:03,679 --> 00:14:07,519 really interesting to understand how much work it goes into building that sort of stuff. 169 00:14:09,080 --> 00:14:13,000 And it's kind of like, I think almost all front end developers at 170 00:14:13,000 --> 00:14:18,480 this point they know that building a calendar is very complicated. So it's something 171 00:14:18,519 --> 00:14:24,960 that any real, any normal person that isn't a developer, would just browse 172 00:14:26,000 --> 00:14:28,960 the web and see a date figure and think, oh, okay, cool, 173 00:14:28,120 --> 00:14:35,279 that's like a day, yeah whatever. Sure, but any front end 174 00:14:35,320 --> 00:14:39,559 developer that has ever tried to create it realize how complex it is to make 175 00:14:39,600 --> 00:14:48,919 it accessible, to make it performant, and also to make it localized. 176 00:14:48,200 --> 00:14:54,000 Right, because it's one thing to just have a component that works in English, 177 00:14:54,200 --> 00:14:58,279 and it's another thing entirely to have something that works for all languages that 178 00:14:58,360 --> 00:15:03,360 exist in the world. So that's like a complete different challenge, right. 179 00:15:05,120 --> 00:15:11,039 And you mentioned that tiny has like forty fifty engineers, so I'm not sure 180 00:15:11,080 --> 00:15:16,639 what is the exact number, but I'm really curious to understand the the challenges 181 00:15:16,679 --> 00:15:22,240 that come in the background to make such such a component happen, Like what 182 00:15:22,440 --> 00:15:30,200 is the amount of people that are working behind and why is why are all 183 00:15:30,279 --> 00:15:37,159 those resources necessary to build a rich taxt editor? Right? No, that 184 00:15:37,159 --> 00:15:43,639 that is a that is a great question, right I. So let me 185 00:15:43,759 --> 00:15:50,600 let me start by breaking down the questions we have about fifty developers working on 186 00:15:50,759 --> 00:15:56,360 tiny MC. As you mentioned, there are different parts of a rich text 187 00:15:56,440 --> 00:16:03,519 editor that goes into building something as cool and feature rich and supported as NMC. 188 00:16:06,159 --> 00:16:11,639 I think the first thing is the web, the web world, right. 189 00:16:11,679 --> 00:16:17,399 The world of web development is constantly upgrading and changing. We have a 190 00:16:17,440 --> 00:16:22,799 new framework every few months, a new update every few warns, and a 191 00:16:22,840 --> 00:16:27,399 lot of improvements and updates from React to Angular to view to the way we 192 00:16:27,480 --> 00:16:33,639 build things with vite. You know it used to be I used to bundle 193 00:16:33,720 --> 00:16:37,879 things and build things with things called like Babbel and things like that, and 194 00:16:37,919 --> 00:16:42,279 now it's all like bite and he has built which are a zillion times faster. 195 00:16:44,360 --> 00:16:49,879 So just having people first understand what is new and what is important in 196 00:16:49,919 --> 00:16:53,639 the web development world that that takes a lot of effort. Now, the 197 00:16:53,679 --> 00:17:00,399 second part is keeping all of the features up to date. Right when talk 198 00:17:00,440 --> 00:17:03,599 about tiny and c features, you can think about like think about it in 199 00:17:03,799 --> 00:17:07,680 a few different aspects. You first have core editing features, right, like 200 00:17:07,799 --> 00:17:14,599 font formatting, code editor, text pattern imports, CSS, character map, 201 00:17:14,680 --> 00:17:18,440 things like that, even like the cute like emoticons. Right, all of 202 00:17:18,519 --> 00:17:22,640 that requires someone to maintain it, come up with a feature, determine how 203 00:17:22,680 --> 00:17:26,240 that icon is going to look, how is it going to work on the 204 00:17:26,279 --> 00:17:30,480 back end, how how do we make sure that introducing this feature is not 205 00:17:30,599 --> 00:17:34,720 going to take away from the performance of the component itself. Then there comes 206 00:17:34,720 --> 00:17:38,119 a little bit more complicated feature right beyond a core editor, as I was 207 00:17:38,160 --> 00:17:41,799 talking about collaboration, right, if you want revision history, if you want 208 00:17:41,920 --> 00:17:48,720 comments on your application or mentions, if you want in app conversations and discussions, 209 00:17:48,759 --> 00:17:52,160 and you let application using a rich text editor that takes a little bit 210 00:17:52,200 --> 00:17:56,880 more effort because now it's not only you talking, you typing a piece of 211 00:17:56,920 --> 00:18:02,759 test, it's you collaborating with someone else live. It's not necessarily real time 212 00:18:02,799 --> 00:18:08,079 collaboration yet, and the keyword is yet, but it is a very asynchronous 213 00:18:08,079 --> 00:18:12,480 collaboration that's happening, and you need to make sure that the person who's opening 214 00:18:12,480 --> 00:18:18,920 a new session of your website is receiving those comments accurately. Then you come 215 00:18:18,960 --> 00:18:22,079 to some other features like imagine if you're doing some sort of content conversion, 216 00:18:22,240 --> 00:18:27,240 right, Like I own an invoice company. I've typed in pieces of text, 217 00:18:27,319 --> 00:18:30,640 everyone has collaborated it, and now I want to export that invoice and 218 00:18:30,680 --> 00:18:36,079 send it over to my logistics team. So I need to export the PDFs. 219 00:18:36,160 --> 00:18:41,039 So there comes engineers who need to understand the nuances of not only front 220 00:18:41,119 --> 00:18:45,559 end technology, but also what does it take to take a piece of HTML 221 00:18:45,680 --> 00:18:48,920 rich tax and convert it into a PDF document, or take a piece of 222 00:18:49,160 --> 00:18:53,720 HTML rich text and convert it such that when I open it as a word 223 00:18:53,759 --> 00:19:00,880 document or I can export word it actually keeps the formatting right. And so 224 00:19:00,680 --> 00:19:04,839 all in all, to answer your questions, tiny EMC probably has over one 225 00:19:04,880 --> 00:19:11,799 hundred plus features, each requiring its own nuances, its own specifications. And 226 00:19:11,839 --> 00:19:15,319 then all of these features need to be compatible. Even though we're wrapping it 227 00:19:15,359 --> 00:19:19,960 around a thin net wrapper around like Angular or react or View, they only 228 00:19:19,960 --> 00:19:25,839 need to be compatible with those frameworks as well. And then finally we need 229 00:19:25,880 --> 00:19:30,039 to make sure that it's all highly pro optimized for performance, because at the 230 00:19:30,079 --> 00:19:32,799 end of the day, you don't want to load a rich text editor and 231 00:19:32,839 --> 00:19:36,759 then your whole website as well. So there's a lot of like lazy loading 232 00:19:36,880 --> 00:19:38,440 and things like that that goes on in the background, and I can dig 233 00:19:38,480 --> 00:19:42,759 into that later. So it's a lot of work when you think about it 234 00:19:42,839 --> 00:19:48,759 as individual features and how big the project actually is, gotcha. So they're 235 00:19:49,079 --> 00:19:57,880 basically on different skill sets among the engineering team, and I imagine that there's 236 00:19:57,960 --> 00:20:06,599 probably a structured software development life cycle or or am I wrong in terms of 237 00:20:06,720 --> 00:20:11,720 like before any release, it needs to go through a performance jack, and 238 00:20:11,920 --> 00:20:18,000 after the performance chack, there's the accessibility check and is that like confidential information 239 00:20:18,200 --> 00:20:23,039 or would you be it would it be okay to share the order of that, 240 00:20:23,079 --> 00:20:26,319 because I think that would be really interesting for the developers listening, Like 241 00:20:26,640 --> 00:20:36,480 how do you order the quality control pipeline of your product to make sure that 242 00:20:36,519 --> 00:20:44,839 what is shipped at the end never gets degraded into any relevant metrics. Got 243 00:20:44,880 --> 00:20:51,240 it. So in terms of like our release schedule just and I'm going to 244 00:20:51,319 --> 00:20:55,440 talk about it, there's nothing confidential. It is like every other software engineering 245 00:20:55,480 --> 00:21:03,680 team, right. Our team has our own infrastructure that kind of maintains how 246 00:21:03,720 --> 00:21:07,559 tiny mc works, the loads and all of that behind the scenes. Then 247 00:21:07,720 --> 00:21:12,640 we have, of course our individual frameworks folks that work with the open source 248 00:21:12,720 --> 00:21:18,359 project who are constantly contributing to that as well. And then in terms of 249 00:21:18,400 --> 00:21:22,480 how it works is we have a lot of test environments and we have our 250 00:21:22,480 --> 00:21:30,720 own dedicated QA team and they're an amazing team. Shout out to Charity who 251 00:21:30,799 --> 00:21:34,480 kind of leads that team based out of Australia. And what they do is 252 00:21:34,519 --> 00:21:37,880 they kind of do a round one of test coverage, right, They're making 253 00:21:37,880 --> 00:21:42,720 sure there's no way breaking issues, there's nothing that changes like all your original 254 00:21:42,799 --> 00:21:47,519 functionalities. Then they have a list of bugs that they're fixing, right, 255 00:21:47,559 --> 00:21:52,279 So every release, they're also focusing on our own technical debt. Were there 256 00:21:52,279 --> 00:21:56,279 any bugs are we kind of helping improve that? Then of course there's the 257 00:21:56,400 --> 00:22:00,279 new features, so there's new features, there's improvements, and then there's bug 258 00:22:00,319 --> 00:22:06,440 fixes that we focus on. And then of course there is quality assurance in 259 00:22:06,640 --> 00:22:12,599 terms of accessibility testing as you mentioned, and we if I if I have 260 00:22:12,680 --> 00:22:18,519 looked at some of the past releases, I think I've typically seen them have 261 00:22:18,000 --> 00:22:26,160 around ninety nine percent test coverage, So it's a pretty great, well tested 262 00:22:26,200 --> 00:22:30,160 product, and that QA team, as I mentioned, does a great job 263 00:22:30,279 --> 00:22:33,480 of that release cycle every time. It's of course an agile team, so 264 00:22:33,519 --> 00:22:37,039 if you want to hear about like how are they managed, you know they 265 00:22:37,079 --> 00:22:41,720 work sprint to sprint, they have their own exit demos, they have they 266 00:22:42,000 --> 00:22:47,440 have a very agile functionality. If you want to ask me all the details 267 00:22:47,440 --> 00:22:49,319 about the engineering team, I haven't been an engineer at Tiny, so I 268 00:22:49,640 --> 00:22:53,400 can't tell you every single process of it, but from what I've seen, 269 00:22:53,480 --> 00:22:57,319 it's a typical. We have a sprint, we work on our feature releases, 270 00:22:57,359 --> 00:23:02,920 we work towards the thing, and then they actually have a code freeze 271 00:23:03,079 --> 00:23:07,759 at the end of that where QA comes in tests all of these to make 272 00:23:07,799 --> 00:23:12,400 sure we have one hundred percent test coverage. Accessibility is checking out, security 273 00:23:12,440 --> 00:23:17,839 compliance is checking out, In fact, I believe tiny MC is software compliant 274 00:23:17,839 --> 00:23:22,359 as well. So you know, we're very high not only on the accessibility 275 00:23:22,400 --> 00:23:25,759 aspect, but also on the security aspect, because at the end of the 276 00:23:25,839 --> 00:23:30,720 day, this is content that people are typing that's personal for them. So 277 00:23:30,279 --> 00:23:36,160 there's a huge series of tests after your software development cycle that QA goes through, 278 00:23:36,200 --> 00:23:40,119 and then and only then do we sort of release Okay, okay, 279 00:23:40,279 --> 00:23:45,720 Yeah, there's lots of complexity that from the from a first glance, I 280 00:23:45,759 --> 00:23:51,359 don't think people would would think of all that that is going on in the 281 00:23:51,359 --> 00:23:56,440 background. Yeah, yeah, definitely. And how much customizations can we get 282 00:23:56,839 --> 00:24:06,720 with the any editor, because I wouldn't want it to have just a general 283 00:24:07,640 --> 00:24:11,359 style. I would want to customize literally everything that I can to make it 284 00:24:11,440 --> 00:24:19,319 as close to my branding guidelines as humanly possible. So in terms of you're 285 00:24:19,319 --> 00:24:26,440 talking in terms of like CSS customization, right or features, I was thinking 286 00:24:26,480 --> 00:24:33,400 I was thinking more of like visual aspects of CSS, but I wasn't even 287 00:24:33,480 --> 00:24:40,920 thinking about customizing the futures. Perhaps you could answer the CSS part of it 288 00:24:40,960 --> 00:24:45,839 first and then go into the features. Yeah, of course. So in 289 00:24:45,160 --> 00:24:51,079 terms of let me start with the CSS part of it, right. It's 290 00:24:51,119 --> 00:24:56,960 eight jobs for the component, which means that you have access to the actual 291 00:24:56,200 --> 00:25:02,440 component itself, the HDML, and you can actually just edit the CSS to 292 00:25:02,680 --> 00:25:07,200 fit it according to your brand guidelines. As I said at the very beginning, 293 00:25:07,279 --> 00:25:11,759 one of the things that I said was, if you've typed any feature 294 00:25:11,759 --> 00:25:15,240 of rich text on the Internet, you've probably typed on TYMC and you didn't 295 00:25:15,240 --> 00:25:18,880 know it was tiny MC. So, for example, if you've ever used 296 00:25:18,920 --> 00:25:22,160 sales Lot or even as I mentioned, Shopify, when you're typing on it, 297 00:25:22,079 --> 00:25:27,920 it doesn't necessarily look like the demo TINYMC rich Tex editor, but it 298 00:25:29,000 --> 00:25:33,160 definitely is a TINYMC rich tex editor, right. So I think at the 299 00:25:33,240 --> 00:25:36,599 end of the day, the answer is, yes, you can customize it 300 00:25:36,720 --> 00:25:40,319 to how you wanted to look and feel. We have a skin that we 301 00:25:40,480 --> 00:25:44,440 provide at the beginning. We also have the ability to go back to our 302 00:25:44,480 --> 00:25:51,720 old skins if you actually have a preference for those. But it's highly customizable. 303 00:25:51,799 --> 00:25:53,960 It's again just a component, and you can always edit how a component 304 00:25:55,039 --> 00:25:59,039 looks okay, cool, And in terms of features, what is the level 305 00:25:59,039 --> 00:26:07,119 of customization that exists within that? So I think the really interesting thing about 306 00:26:07,240 --> 00:26:11,720 tiny MC is you know, even the core editor, it comes with probably 307 00:26:11,839 --> 00:26:15,720 twenty thirty plus features, right, if not even more, and you don't 308 00:26:15,799 --> 00:26:21,839 have to actually import all of those features. So, if you now talking 309 00:26:21,880 --> 00:26:26,240 sort of Angular and Tiny, if you there's like this initialization that you do 310 00:26:26,319 --> 00:26:30,759 with the Tiny editor when you're loading it into your Angular project, and in 311 00:26:30,799 --> 00:26:36,599 that initialization you actually specify which plugins you want to bring into so it only 312 00:26:36,759 --> 00:26:41,920 brings into your JavaScript the plugins that you ask it to load at runtime. 313 00:26:42,359 --> 00:26:47,680 So, for example, if I don't care about collaboration content, I just 314 00:26:47,799 --> 00:26:52,200 need a rich text editor that does basic BoNT formatting, has some visual blocks, 315 00:26:52,240 --> 00:26:56,039 can import CSS, and has text patterns, I can specify I only 316 00:26:56,079 --> 00:27:00,799 want those four plugins, and I will have a very simple editor. So 317 00:27:00,079 --> 00:27:07,079 that's how simple it can get in terms of bringing in new features and functionalities. 318 00:27:07,680 --> 00:27:12,160 Gotcha. And then the bundle sizes. I expect that it's also going 319 00:27:12,200 --> 00:27:15,640 to reflect that, right, it's not going to load any code that it 320 00:27:15,720 --> 00:27:22,200 doesn't need. Yeah, it doesn't load any code that it doesn't need. 321 00:27:22,400 --> 00:27:27,519 And even during as I said, during runtime, it takes advantage of most 322 00:27:27,559 --> 00:27:32,359 likely I'm guessing if most of you're using TENMC or you're not just using it 323 00:27:32,400 --> 00:27:36,039 in minologreas you're using some of the frameworks, and it takes advantage of some 324 00:27:36,079 --> 00:27:41,160 of the performance optimizations that specific frameworks provides. So, for example, Anguler 325 00:27:41,279 --> 00:27:52,559 has lazy loading capabilities and TINYMC takes full advantage of that. Gotcha. Okay, 326 00:27:52,960 --> 00:27:59,720 okay, interesting, we are at twenty eight minutes already. Time time 327 00:27:59,799 --> 00:28:03,599 is line. I to make sure that, Yeah, I want to make 328 00:28:03,640 --> 00:28:07,880 sure that we really cover everything that you would consider to be really major. 329 00:28:08,359 --> 00:28:14,720 So I'm going to throw like a catch all question to you, which is 330 00:28:14,720 --> 00:28:19,440 is there anything that you deem as really important that we should talk about that 331 00:28:21,000 --> 00:28:25,519 I haven't touched yet. Yeah, of course. So I have a few 332 00:28:25,599 --> 00:28:30,119 like product updates in terms of like tiny we recently about a month ago launched 333 00:28:30,160 --> 00:28:34,839 tiny MC seven, which was very exciting and some of the features that I 334 00:28:34,920 --> 00:28:40,480 highlighted over in this podcast, like document converters, revision, history, markedrown 335 00:28:40,440 --> 00:28:45,079 and support, we're all part of that release, as well as things that 336 00:28:45,359 --> 00:28:48,279 to look forward to. In terms of seven point one, we do have 337 00:28:48,400 --> 00:28:53,039 some exciting things around like math equations coming up, as well as enhancement to 338 00:28:53,160 --> 00:29:00,000 our AI assistant. So I think content editing is not exclusive to just type 339 00:29:00,119 --> 00:29:06,160 a piece of text. Now you can just connect it to CHATGBT and ask 340 00:29:06,359 --> 00:29:10,559 prompts and you know, even ask Tragic to say, hey, generate an 341 00:29:10,559 --> 00:29:14,880 email template for me if you have any senior email editor, rather than sort 342 00:29:14,880 --> 00:29:18,680 of having to write from the start. So it has a lot of content 343 00:29:18,359 --> 00:29:23,200 and a lot of features and functionalities, and we're just improving it every iteration 344 00:29:23,279 --> 00:29:29,119 of it. Okay, Okay, that's really interesting. All right, so 345 00:29:30,720 --> 00:29:37,000 Rina, I think we can start wrapping up. There's a lot more stuff 346 00:29:37,839 --> 00:29:44,039 about this, especially in the docs. So if anyone is interested, definitely 347 00:29:44,079 --> 00:29:49,480 recommend going to the website and checking out the product firsthand. So I'm going 348 00:29:49,559 --> 00:29:53,720 to put a link to the website here in the comment section. But then 349 00:29:53,759 --> 00:29:59,279 again, it's just tiny doc cloud for anyone that is listening wants to check 350 00:29:59,319 --> 00:30:04,960 that out. Let's do some shameless promos. So, Marina, what would 351 00:30:06,000 --> 00:30:10,519 you like to to mention? It could be stuff from tiny, or it 352 00:30:10,559 --> 00:30:12,559 could you just be personal for you. It could be things that you're working 353 00:30:12,599 --> 00:30:18,119 on. What would you like to promote? Yeah, of course some shameless 354 00:30:18,200 --> 00:30:22,960 promos. We're Tiny is actually going to be a front end Nation, which 355 00:30:23,000 --> 00:30:26,279 is a huge online conference. So I'm guessing a lot of you are joining 356 00:30:26,319 --> 00:30:32,880 this podcast are actually uh, you know, online listeners and engagers. So 357 00:30:32,920 --> 00:30:37,720 we're going to host a workshop on you know, building out this rich text 358 00:30:37,799 --> 00:30:41,359 editor that's going to include an AI assistant and almost give you this notionlike feel. 359 00:30:42,079 --> 00:30:49,160 We're also going to be heavily giving out swag at front endation that's your 360 00:30:49,160 --> 00:30:52,599 thing, and we have a huge community there, so really excited to see 361 00:30:52,640 --> 00:30:56,079 you all there. And again, tiny EMC seven point one is coming out 362 00:30:56,160 --> 00:31:03,319 soon with some newer and greater things with the assistant and other features, so 363 00:31:03,480 --> 00:31:06,920 just stay tuned for what we're doing with tiny and C. Check out our 364 00:31:06,960 --> 00:31:11,119 discord channel or Twitter. We're pretty active on both, as well as some 365 00:31:11,279 --> 00:31:15,799 YouTube videos that we'll be launching. Awesome, awesome, Okay, all right, 366 00:31:17,240 --> 00:31:22,799 So well my promo is just going to be the two companies sponsoring the 367 00:31:22,799 --> 00:31:26,640 show. So then again, if anyone wants to learn more about software development 368 00:31:26,640 --> 00:31:30,240 in general, Top and Devs has several podcasts, not just this one. 369 00:31:30,319 --> 00:31:34,680 So there are shows about react, about develops, about machine learning. So 370 00:31:37,680 --> 00:31:41,759 look up Top and Devs and you're going to see that there are multiple different 371 00:31:41,759 --> 00:31:45,759 shows that might interest you. And again if you're a company or just an 372 00:31:45,759 --> 00:31:52,759 individual wanting to help, wanting help to execute your idea and you need good 373 00:31:53,079 --> 00:31:59,880 developers and designers, check out Onvoid dot com. Is you and Void so 374 00:32:00,359 --> 00:32:07,359 Void dot com. And the difference between them and every other company that offers 375 00:32:07,400 --> 00:32:10,880 remote design and software development services is that by hiring Onvoid, you actually only 376 00:32:10,920 --> 00:32:15,720 pay after the work is delivered and approved. So it's not just a matter 377 00:32:15,759 --> 00:32:19,519 of them saying, hey, is delivered, now you pay. No, 378 00:32:19,720 --> 00:32:22,599 you actually even have a step where you can do quality assurance and make sure 379 00:32:22,640 --> 00:32:28,799 that it is aligned with your expectations for the work before you approve, so 380 00:32:28,880 --> 00:32:34,680 they have all the incentives needed to actually deliver great quality work on time, 381 00:32:34,920 --> 00:32:37,839 because that is going to reflect on how much they get paid at the end 382 00:32:37,920 --> 00:32:40,519 of the month. So yeah, definitely check out those two companies if you 383 00:32:42,039 --> 00:32:46,319 feel that they ease any of the pains that you have in your life. 384 00:32:46,880 --> 00:32:52,079 But yeah, that's it again. Thank you so much for sticking to the 385 00:32:52,160 --> 00:32:54,640 end of the show. I hope you enjoyed it. Rina. You are 386 00:32:54,759 --> 00:32:59,519 very welcome to go back anytime you want. I'm sure that there are other 387 00:32:59,599 --> 00:33:04,640 projects from tiny that we haven't even touched upon. So if at any point 388 00:33:04,720 --> 00:33:07,799 you want to join the show again and then we can discuss some of the 389 00:33:07,880 --> 00:33:13,920 other stuff that Tiny has available in their portfolio, then let's definitely do that. 390 00:33:14,480 --> 00:33:16,839 And again, thanks for being on the show. Awesome, Thank you 391 00:33:16,920 --> 00:33:21,200 so much, Lucas. Have a wonderful day and I hope everyone enjoyed this. 392 00:33:21,599 --> 00:33:24,200 Thank you, thank you, see you all next week.