Hey, welcome to React Round Up, the podcast where we keep you updated
on all things React related. This show is sponsored by Raygun and produced by
Top and Devs and Onvoids. Top and Deves is very great Top and Deves,
so get top and pay and recognition while working on interesting problems and making
meaningful community contributions. An Onvoid provides remote design and software development services on a
task basis, so clients only pay when tasks are delivered and approved. In
today's episode, we will talk about an ecosystem of UI libraries which are available
for all the main popular frameworks nowadays, including React of course, but also
Angular and View, and we will talk directly with the founder of the company
behind those libraries. We are talking about Prime Tech and the Prime React and
Prime Prime View other such prime prefixed projects. My name is Lucas Spaganini.
I'm your host in the podcast. Joining me in today's episode is Chris Ruin,
Hello everybody, and our special guest and founder of Prime Tech shot Tai
GVG. Hello, Hello guys, and thank you. Thank you for having
me. Yes, it's a pleasure to have you Shatai. So let's just
jump straight to it. Could you please provide us with a brief introduction of
what prime Tech is and what it does as a company, and then we
can just jump straight to prime React and how that particular library could be interesting
for React developers. Yeah, sure, so prime Tech. I'm the founder
of prime Tech. Back back in two thousand and eight, I started as
a hobby project called prime Faces. It's a Java services, a UI library.
And after ten years in two thousand, let's say seventeen and eighteen,
we've started with React versions. So after React we became popular and we also
have other versions. But the companies we can describe it as a UI compound
libry vendor. At some point we have done some of course consulting and training
for our to make a living, but lately, for the last couple of
years we have solely focused on a UI compound development and at these times after
so we are like close to fifteen years of experience in this and we are
These libraries are open source and free, teos under a mighty license more than
close to eighty and idy components from enterprise level requirements like a complex data table.
We also provide simple compouds like a Navatar and simple button, so not
just for a single suite of requirements. We try to cover as much as
we can. And it's an interesting story because we have reached like fifteen people
right now and the core products are free and open source, you know open
source. We have also gone through those stages and there we were traveled having
trouble, maybe trying to figure out how to turn this popular open source UI
projects and make it our main business so that we can also work on it
during the daytime when the light is on instead of just nighttime, because during
the day we had to do a lot of different stuff and at night we
had to work on open source. But things turn out to be very well,
and we tried different things, made some mistakes. At some point we
try to sell the documentation even believe it or not, for ten dollars and
some people bought it just support us. And I never asked for sponsorship for
the prime projects because although I know that it's well at many projects, maybe
nonprofit projects also, although we do it on our NP sponsor a couple of
source projects, you know, it may some enterprise companies may look at it
like red fleg sometimes because because we're a company and when we say okay,
we regarded sponsorship and because I told to them in conferences in meetings, they
kind of shy away from those kind of so it's kind of a redfleg because
they want to invest in your project and then they want continuity, right,
So we never asked for that sponsorship. Try to find out like selling the
documentation, things like that working out on other jebs, and since twenty fifteen,
GIF kind of figured that out how to monetize it, maybe we can
discuss it as well. In the context of React, we are basically offering
some commercial leads on top of the open source core, and that helped us
to sponsor the open source core as well. And that's the only thing we
do. We develop UI compounds every day all day. That's awesome. So
you really went from consulting work up until a point where you are now able
to sustain fifteen people. Is that what you said? Yeah, that's amazing.
That's amazing fifteen people being sustained by a project which also provides a very
comprehensive free version and with a very forgiving license, right, so MIT is
going to let people do whatever they want with them. So they are definitely
several interesting things that we can talk about from a business perspective for anyone listening
that might be interested in selling doing a This is what people are currently calling
micro sauce, right, So microsauce being the concept that you can create something
small which can be served as a not necessarily as a standalone like it or
it sometimes depends on other things to make sense for it to be sold.
But it's a it's a small a smaller, smaller ish product, right,
Like we know that in practice, there's nothing small about everything that you guys
maintain. This is a huge amount of work, like a huge library,
but in the sense that you are selling a library of components, that's something
that people can easily start. So to get to the point where you guys
are, that's ears right. But to start a library and have a go
of selling this library with a premium paid version, that is something that theoretically
doesn't have a very high bar for people to get started. So there is
growing interest from developers to learn from such types of businesses because it's really interesting,
Like there are a lot of folks out there that really care about accessibility,
about performance, about so many things that if you're just doing components for
a specific project, it's hard to justify putting that amount of effort into making
the components super polished. But if you're thinking about it as a product on
its own that's going to be so to many other companies, then that is
a path for you to justify spending time in such details. And there are
definitely people out there that love doing that kind of stuff, So we're definitely
going to go through that. Yeah, exactly. Yeah it's worked. I
mean it's still it's a journey where trying new things, try to increase new
and sometimes failed try and Pillot and I have some interesting things to tell about
prime Wreck as well, because it's kind of different than the other libraries.
The track record of prime Reck is a bit different. We can talk about
it in detail as well. Okay, so let's start with what are the
things that people can use for free and what are the things that are behind
a pay wall. So we we had a payball in the past, like
the style customization, which was which turned out to be a bad idea because
in so like you had this, we had something called the sus Team where
you can purchase that was a visual editator as well, so that the idea
was okay, but it really damaged to growth. So that the core is
open source and free. But in order to customize the styling deeply you had
to that was a paywall, so we made that open source and now introducing
an ether version as well. So I cannot say a payball because I don't
think that maybe we should introduce a payball to the users. It should like
be an optional add on't so they should buy it if they really like it,
not because they have to write. So right now we have the open
source core, all these libraries, especially on the React as well, the
eighty components maybe ninety, I am not sure. Probably I'm not sure,
So let's say eighty components from tables to tabs and everything. And we also
provide you know, the team force templates where you can go purchase me sometimes
the templates, application templates, admin templates, mostly the dashboards. We also
provide a couple of times. We have a design team that creates and the
design and our teams implemented, so they're like on our store, available in
our store. We have our own small team forest, let's say, and
fig ma uik It is also a commercial, so not everyone needs to fig
majuik it, but probably the companies who need it. They can afford it
because they have a design team. So the uik it, the Pigma file
of the components is a commercial on the commercial side. And also we have
something called prime blocks. Probably you know about the Tailent UI. You know
those Talent is the open source core with the utilities, and they provide this
nice looking ready to use copy paste ready blocks. They're not really tempets,
but you just copy and paste. We also have something like that and that's
also paid add on and what else. We also had the pro professional support
because many enterprise companies they just want the contact where they can instead of GIT
up email, they can just contact us using a private issue tracker. So
that's four things I can say, but a couple of more are on the
horizon, like Figma to team generation plug in is on arizing any visual them
editor, and also the prime blocks. The knee version is also maybe and
we are also planning to come up with some uibuilder's kind of tool So mostly
tooling, let's say, add ons on top of the core. But of
course there's no payball and people can get what they need from the library.
Gotcha, gotcha? So that exposes a really big challenge, right because if
the core functionalities are there. And I can also say that you guys are
very generous in the way that you present your products because if you go to
prime react website, for example, there isn't too many call to actions telling
me that there is a paid that there are paid add ons to it.
Right, it just really looks as if it's something free and there is a
banner of especially now talking about the spring cell that you have or the templates.
But besides that, the amount of call to actions for purchasing things is
very very minimal. So I imagine that this also increases the challenge. Right,
So you're trying to make something that is very friendly for those that just
want to try out the free version. Well, at the same time,
you want people to know that there are paid ad ons because you need to
support fifteen people. Yeah, if you go to the website, there's no
banners or you know, sponsor us. We want to make it clean.
So that's one of the reasons. And our first preference is the growth,
So we need to have a big user base for the project. And then
because sooner or later, once they're installed to their project and start playing with
it and seeing the value at some point they will realize that they may need
some pay that and so the highest priority are the you know, adoption and
growth and pamanization with the components rather than monetization. That's something I learned through
the years. Once you have a user base that you know, you're the
community at some point, I mean, have even some users stay that purchased
some stuff from our store without the need of using it. They just want
to support us. And of course there are some people who want the refund.
Of course, you know, there are different kinds of people, but
you know, there's that's the idea. We want the clean user interface mostly
and they should you know, we don't want to put it in there,
you know, make it the highlight, just just there. But of course
there's always room for improvement, trying new things, moving things around in the
UI different. But we don't have any people for sales. That's interesting.
Out of that fifteen people, one person is for custom relations you know,
mailing, invoicing. Another fourteen people are for developers and designers. So the
product kind of sells itself because it's the power of open source. That's why
we love what we love awesome awesome. So just to recap from the React
developers point of view that might want to use this library. So the main
issues that this library solves are the speed at which developers can have well written,
performance and accessible components in their US right. So you want a date
picker, there you have it. You don't need to create it from scratch.
You want like there. There are just so many of them I can
even list them here as an example. There are just too many, too
many components. But yeah, basically, most the way you can think of
in terms of design UI elements you're going to find in Prime React and the
other Prime libraries for other frameworks. So I wonder how this compares to other
UI libraries out there, Like why would someone that is just starting a project
and they decided to use a UI library? So this is not the question
anymore. The question is which UI library to use? Why would they use
Prime? Yeah? In general, So to begin with Prime reacts cases different.
So we had the Prime phases. It became the most popular one for
its own context, Java, Java, Web Jobaba development. We had the
Prime ENGI after the official first part angler Mattel, it came the second most
popular. Prime View is now the hardest UI library for View Jazz, and
so when we turn to the prime React, we've just realized that we made
the mistake along the way. Some thing didn't click with the community. So
people that started after us got more popular. So we like a couple of
months before we went back to the driving board saying okay, we're doing something
wrong, and we've decided to go back to the driving board come up with
a new plan, which started. The implementations started yesterday actually. So one
of the issues with the prime React was this old teaming which is using SAS,
and you had to compile it and team switching functionality. You had to
suite some CSS since we were there were some stuff legas, stuff from two
thousands, two thousand and eight and tens because when we started there were no
CSS variables. Weren't even know sas. So if you do it for a
long time, you face with the technical debt. Luckily Prime View had that
sort of doubt. And this is the turn of Prime Engine Prime React.
So probably in June we will have a new reboot called Mono Repo. We
are moving to a mon what There will be a new package at PRIMARYC slash
Core. So the main difference between PRIMARYC and the main difference that will be
because the newer version will have it, but the idea is different. So,
as I mentioned, I'm doing this for fifteen years and I've met all
sorts of users. So there's some there's a I call it the three types
of people mostly. So some users prefer they're not really good with design,
they just but they want to get something done. They just pick it off
the shelf, like the dayticker you mentioned, and it looks good and it
does Jeb right. And there's another type of people. They want full customization.
They want full control, they want to feel like they can change everything
easily. And there's a third group they don't like they don't like UI compounds
and they create everything from spash themselves. And even we try to get some
people from that clan. Let's say, right to our land, because it
really spiks up, because I mean, maybe you've used some third party library,
right, and because when you import it, when you MPM install it,
you get their problems and bugs and their issues, the maintainer's issues and
things like that. You get all the problems with it as well, not
just the features. So some people who got burnt by it, they maybe
they had a bad experience, so they try. From that point on they
create their own stuff. But they're not that many, I would say,
but probably some corporates with their own design systems, they go they run.
So what we did is that, okay, there's no single solution, right,
so we created this idea called we have two modes style mode and unstyled
mode. So Primaryact also has it. It's not as polished as the other
versions of it, but it will be. So the style mode will be
this nice looking API with design tokens, Figure integration, a nice API with
different presets like you can which from material to bootstep because bootstep like designs,
we have our own designs said, so that you can get that style,
get that component with a nice looking UI, and you can customize it easily.
That's the style mode. If you compare with the recent trends in the
React especially because React and tailment really fits really very well because when you compare
with the Angler review, there's no built in styling in React right, so
and the tailment really fixes that issue perfectly. It's like a perfect combination so
that you can create components that doesn't need an external styling. You can use
Talment with it. So that's why when we realize that tailment based UI libri
is for React got extremely popular, so that gave it us idea, so
we created this unstard mode. In unstard mode, we do not render any
CSS class. Usually components have like drop towers, let's call select. Usually
you can when you open the door with the developer tools, you see like
key desk, select, p select, header, PA, select option classes
like that right, which you need to know you need to customize. In
that case, we remove them. We don't render any class and we get
tailent classes from an object we call it PT. That's called the pass through.
Pass Through lets you access the component internals. So components are like off
the shelf black boxes, right, they gave you call them like select and
it gives you select. But in the end, internally it has many different
dom elements like the panel, the portal, options, the filters and everything.
We provide access to these internals using the pass through properties. And the
pastor is like a Javasco object. It has like header, option, panel,
overlay, shadow, things like that, and it gives you the ability
to pass tail and classes. So we created the same style with tail went
as well. Which means that if you get that two people one purpose that
you know, start more than teaming, and if they're heavily using tail wind,
now you can use tail vint to style the entire prim rect library as
well, which is great because it will really fit well within the rest of
your application. You don't need to learn any API, you can just use
tailings and prime rec provides it. I'm not sure if there's another library that
can do both style and unstalled. Plus you get all the accessibility features,
a huge community and everything as well on top of prim so it's quite different
from what people The scope is kind of bigger, but it's the ideas on
flexibility and customizations that's really really interesting. I think I think I got the
takeover for Lucas here for a bit. I'm not sure where I went,
but yeah, that's that's it. It's been amazing to me how tail and
has has expanded as a library, and really anybody who makes an integration with
them seems to get some of that kind of that love. Yeah, that's
that's that's quite interesting. I really like the that that kind of the option
that you give because I think a lot of other UI components. Yeah,
they don't offer that. It's sometimes you get like they'll give you like only
like one part, perhaps like the accessibility or the performance, but they say,
yeah, you have to do all the styling right or the others are
very opinionated with styling, and then they say it's very you know, it
makes it very difficult to add your own styles. Yeah, exactly. I
mean, look at the competition and even our user base. Okay, well
I do an announcement that okay, now you can style the compounds with tailment,
guys, and you don't want to do all this work yourself, so
that our team has great at these presets. To give you an example,
and our team went nuts and styled everything twice with two different presets. One
is with the different look and field. So we have two presets for the
tailment version because we don't want everyone to style themselves. But as you mentioned,
Chris, there's these when we announce it, some people in our community
say, okay, tailent rocks and I we use it, we love it.
And there are some people they say, okay, we don't we use
talement. We don't want to use it. We don't like that approach with
because these classes become really long and things like that, and then we don't
want to lose anyone. We want to offer different style and it's mostly the
styling. I mean, you know, the React area, they provide accessibility
and there's a headless approach, but still you have to do a lot of
things. I mean, it's like we are trying to find the best of
both first, you know, if there's only material or the libraries in angler
reacting view. But this masterial is like design system, why we need to
based on it. I mean prime reac is kind of the best of furs
and after years of experience, we tried to come up with different ideas so
that people can pick their combination. Okay, start mode with tailwind on start
mode without tailment and things like that. You know. So that's what makes
it different because in react ecosystem, what you see is that they're either opinionated,
they're either tailwinds, they're either not they're either primitives and things like that.
Hopefully Prime React with the recent version, we will be finally picked up
by the community and hopefully people hear more about prime react because it really worked
for other communities and it is the time of React prime react and we are
really excited about it. Three three developers will start working on a new version
of Prime React soon. We'll see very cool, very cool. So lucas
we were we were just talking about how they're they're offering a super flexible way
with you can take the tailwind sort of presets, or you can just say
I just want the components. I'll style them myself. And I think it's
quite a wise decision because you yeah, you're really you're opening your library to
any type of developer. Yeah, I really like that approach. Yeah,
I'm making it as ergonomic as possible so that nobody has a reason not to
try it, right. Yeah, it's it's a tremendous amount of work though,
because scope is larger. I mean, if I can do a tailvent
Ui library focused, I mean just maybe Avatar and selects and things like that.
If you check out Headless, you are just a couple of but it's
popular, you know, but you know, the scope is larger, the
work is harder, but it's more rewarding because we can we can pro you
know, it will be a wider audience for us, even the corporates with
design systems. I mean, we have many people who are tasked with creating
their own libraries for their companies because they have their own design system and they're
now using the prime reac and primary and nonstaffed mode, and they are creating
rappers. Let's say instead of prime select, it's like my select that my
is the organization, the name, and they just wrap it and they provide
inject their own styling and they get accessibility out of the bucks and they can
make the you know, their management happy because they don't need to write a
data table from scratch. Awesome and shut out. Let's see how many business
lessons we can give to people that want to create libraries and have a very
flexible, free plan while at the same time being able to pay their bills.
Right, Let's not consider uy libraries because we don't want more competitors for
you Jesus side. But let's just say someone is creating a utility library.
For example, I think a library that is really interesting is our EXDB.
Not sure if you guys ever heard of it, but the idea is they
used rxgs, which exposes lots of reactive extensions for JavaScript. This is what
our XBS means, reactive extensions for JavaScript. So they created a bunch of
adapters between local state and RXGS. So if you're using RXDB, what it
provides you is a very easy to use database rapper for local state, so
it creates a rapper for INDEXDB and also creates a rapper to automatically pull in
data from your or remote resources. So, for example, let's say that
you have you're creating a CRM. So a CRM is the kind of thing
that you have so much data and there's so much that you want to do
with this data that perhaps it doesn't make sense to treat it as a normal
regular rest API where everything that you need to do you have to ask the
back end. So instead, maybe you really want to just querry the back
end to have the latest refreshed data and perhaps have a web socket connection to
it. But what you really want is for the data to be locally so
that you can manipulate it in the front end. So I'm just giving an
example of a very specific library that as we can see, there are very
there are lots of companies that might be interested in that functionality and it's not
UI related, right, so there are lots of room for people that want
to create libraries and sell them you don't necessarily need to create libraries that are
specific to UI components. There are other utilities, definitely, definitely. And
what I'd like to know from your experience doing that as a business owner is
how would you recommend someone that wants to start a Microsoft business from scratch building
a library and eventually being able to make a living out of it. Yeah,
I mean, it's it's so maybe that In my case, when I
started this, it was like a hobby project. I had no idea of
making turning to a business. And at some point they the clients, tried
to contact us US for some paid development and consulting trends, and I just
realized, okay, maybe there's something in this. But if I I mean
lately, the stuff we do in the future, we are trying to,
you know, on our land a UI landscape. We trying to decide if
that can be profitable, if this feature can be turned it to let's say
a tool support maybe for example, we because you provide APIs and if tooling
is the interesting idea, because when you provide an API, you provide these
features and at some point the develop experience may need some enhancements, and that's
at that point that tooling, because with tooling with like the microcess, because
you know, instead of one time, my suggestion would be that it should
be a recurring revenue, right because you can maybe some amount, you can
sell five licenses or let's say five invoices, but there's no guarantee that you
can get it in the next month, so that you cannot rely on this
business leave your job. So it should better be a recurring thing. That's
what our experience the street as well. So if that like a tooling chain,
if that can be developed for that library, for that utility, that
would be great. And if you if you see some examples. Of course
my many of my experiences on the UI utilities might be different, but utilities
are just like that RXTB. As you mentioned, utilities are great for different
integration modules. Different extended utilities will be great. And my suggestion will be,
of course that any So what we also did was some long term versions,
like you know, the bigger corpors do it as well. So if
you have that utility, but many corporates cannot upgrade every time, so they
usually wait for six months a year. They want the long term support versions.
Because we also provide the LTS versions and they are kind of paid add
ons as well, so that utility, you create new stuff, maybe you
break some stuff, and that you can still provide the long term support versions
in the run time, and the corporates and medium sized companies will definitely will
go on that rout and they can continuous to provide payments every year, every
month on that version, because unlike the startups and freelancers, they cannot jump
to the newer version as well as possible. So I would say tooling some
support to older versions of that you tilted library, that would be great,
and plugging like integration with other environments like optional paid add ons. And I
would never suggest the payball because it's really you know, it doesn't it doesn't
sound good, and people don't like payballs initially. They just make sure that
they adopt your library and make sure they are happy with the core functionality so
that you can start offering some paid at on services, integrations, extra features,
long term support, and you name it. But of course it depends
on the context and different UI is different back end services like authentication. For
example, you're doing authentication, you created ten different modules for different services,
different data integrations. Because I know a startup, what does it They provide
two integration modules is free and for data integration and eight other integrations are eight
and things like that, so different features and so on. It's kind of
fun. Try to monetize it, and if you succeed, it's really fun.
If you fail, you tried local alternatives. And what about the fear
that people have of first imprections. How much do you think that this is
relevant, because I don't want to ignore first impressions. I think they are
relevant. If somebody tries your library and then have they have a bad experience,
they might try it again some time afterwards, but they might never try
it again, yea forever. It's really really important because in our case,
okay, they they people usually evaluate libraries right, They eliate primary act,
they do it installed, they put a couple of compounds, they abit competition
and if if they if they face any issue during setups, you know they
do not get any response. So first impressions are really vital, and if
you lose them, it's really hard to bring them back. Maybe they need
you need to wait for their other project. And if they're the ex is
quite good on their previous project, it's really hard, but it's challenging.
We have done it a couple of times in the past that we had some
bad impressions initially, but we change the develop experience entirely, but it takes
time. As I mentioned, you need to go back to the dragon board
you started the flow because lately we didn't are not promoting primark as much as
were we were in the past. We were doing in the past because lately
we have updated the showcase, all the documentation, teaming and everything, which
is not even live yet actually, so we have some cool stuff that we
didn't bring live. So that's why we are kind of just like you mentioned
the person, if we just promoted now, the users will come in and
just Okay, this is cool, but my preference will is better. So
right now we're holding some of these features as well. And also I would
suggest for open source tolpers if they want growth, they need to pay special
attention to their if they're using discord or forums where they try to gether community
build up a community, they need some extra attention to the new comers,
the new members because they're if they just have a problem initially during setup,
they will leave and problem never come back. So that they did. Those
kind of users need some special attention. But yeah, and the develop experience
if you use it now, will you suggest that because open sources really from
year to years, so you like it, you suggested your colleague and your
friend, your developer friend, Okay, I use this library school, right
and things like that. Yeah, the olope experience is our focus. So
that's why we stopped doing features. You just realize, even if we had
some virtual scrolling frozen columns, it is not affecting our growth. Let's just
improve the showcase, the documentation, tooling, ID plugins, and then because
we can create features anytime, let's focus on the developed experience. Yeah,
that does make a lot of sense. It's not just about supporting tons of
components, it's about the way that you use them. Just like any company.
There are there are many monster sauce out there in the sense that they
do everything, but at the same time it's just so terrible the experience.
There are a few, for example CRMs that they just attempt to do everything
in the world, but when you try to use it, and that's the
selling point, right, like you can do everything there, but when they
try when you try to use them, you most frequently run into a not
so great user experience, So I think this is a similar case. It's
best if you have less things, but they are polished enough that people are
going to use them and they're going to enjoy using it. Otherwise, if
you just put too many features and they're not polished, then at the end
of the day, you don't really have anything. Yeah, exactly, that's
what we realized and went back to the driving board, as I mentioned,
And now you're coming back, Copley gotcham So would you say that, looking
back, you would rather wait a little longer to launch, but make sure
that the version one is very what's the word that they use, They're lovable,
right. People even say that the MVP is the odeal. Now you
need to have a minimum lovable product. Would you say that this is true
or because there are also lots of people that say, if you really,
if you feel proud of what you're publishing, then you took too long to
launch. So we have two very very different views on when to launch a
product. Yeah. On our site, the UI library development never ends,
so you cannot say prime React is done. You can never say it because
it started in twenty seventeen and what is done. I mean, because there
will all basically a new future, a new component and new something. So
rewriting our teaming for a view version, and now it's coming to reck as
well. And at some point that's a major jump between version three and four.
And then we realized that we are adding some other features that were not
in the scope of that version, because that version was supposed to be the
new teaming, the flexible teaming with Figma integration song And when I check out
our roadmap, I've seen stuff like that can be done in the version four
point one version four point two, and it was supposed to be launched in
March, but it was launched this week, so two months late. But
it would have been delayed more like two more months maybe, So I in
a team meeting, I said, okay, guys, if we try to
accomplish all these it will be like end of year and we cannot get it
out of the bucks. So exactly, I'm more like an MVP guy interative
guy, because these libraries are huge and we always try to come up with
something working. We can probably for the primary act version. Next version,
we will create maybe ten sets of compost like taps, inputs, accordions,
dialogues, essentials, let's say essential set of UI components, and then for
every week we will try to come up with a new component and tail integradition,
integration accessible to don Because it will be we will never release it in
time and there is no complete it will never be the perfect as you want
it. That's another lesson that we learn. If you try to make it
perfect, perfect, and the time flies by, and it will never be
perfect anyway until the people start using it providing feedback, you polish it.
So I'm more like on the MVP side of the things, shut Eye and
Chris, I think we should start wrapping up. We're already at forty two
minutes of core content. But before I do that, I would like to
ask, just to catch all questions, is there anything that you believe I
should have asked that you think it's really relevant for the audience of the show,
But perhaps I haven't touched upon yet. I'm not sure. I mean,
yeah, I think the best question was how prime react was different from
other libraries, because then we compete with view. We compete with maybe one
or two libraries with Angler. We als only compete with Angular material, which
is first party but in React, I mean, there are many libraries out
there, I mean, which one to compete against? If I can tell
you five very good libraries. I mean, so that question was really nice.
But again prime React ideology, the idea is kind of different. And
the common question I get is that how React compond development is different than Angler,
Review and other libraries. I think React and views the easiest. Angler
is a bit tricky to implement components, and it's quite a pleasure to work
with a reacting view. And other than that that monetization. Because we have
an interesting story how to turn this open source the thing you love into the
thing you make a livit making a living that we also discuss it and other
data. I cannot really think of maybe other things, but I'm really excited
to show you the next version. Maybe we can do a small, maybe
quick lightning. Just give us a couple of months after summer, we will
launch the new prem React and maybe hopefully you will try it in your next
project. In your next project, definitely I will be waiting for that.
You are very welcome to get back to the show and tell us all about
the changes that you made to make the library more easy to use. For
React developers. Yeah, definitely. Yeah, we'll see how it goes.
All right, let's do some promos, Chris, would you like to get
started? Yeah? Sure, I'll post something post in a while, which
is my my you to me. I don't know if I can, I'll
post at the link. Yeah. So I have a few courses, not
all React but just stuff. My course has come from experiences I've had as
a full stack dev and like where I got really stuck and couldn't find anything.
And yeah, I also have a policy because I know there's probably a
lot of students listening or you know, people who don't have the money to
spend on courses. I if you email me, I will set you up
with a with a free coupon code for the course. So but yeah,
check them out. I think there's I think they're interesting. Of course,
otherwise I wouldn't make them. But yeah, awesome, okay shout I What
about you? What would you like to promote? Yeah? We currently I
think we have a discount at our prime store fifty percent off on everything.
If you need a nice looking template, some prime blocks, you need a
pigma. They're really quite affordable these days. So if you should, I
type it or should I. I mean, if you go to the primaryact
website, you can see that there's a top part notification at primereact dot org
and it's fifty percent off on anything, and if you like to support open
source, you're welcome. But also we have some free templates as well if
you like to check some before trying the premium stuff. Awesome. I just
sent a link to primaryact dot org in the notes in the comment section and
also a link for Chris on you to me so that everyone can also check
that out. On my end, I don't have any special promos, just
going to mention the companies producing the show. Again, so there are many
other podcasts produced by top endevs. If you're interested in other software development subjects,
there are shows about angular view career. There are many many other podcasts
available in the top and devs universe, so definitely check that out if you're
interested in hearing about other subjects while you're working out, driving whatever. And
also again Void, so if you are a company or you know a company
that is looking to either augment their staff or just create an entire system from
scratch, then definitely check out Void dot com u N Void dot com because
they have a very interesting business model which allows clients to only pay after tests
that are delivered and approved. So I think this is going to be for
me in this episode. Thank you so much for sticking to the end.
I hope this was valuable to you in your journey as a React developer and
also with all the super valuable in my opinion, business insights from Shatai about
how he built this business and made it lucrative and made it work in its
own without requiring consulting work or any other sources of income. So I think
this is highly valuable for lots of developers. I hope it was valuable to
you, and I will see you in the next episode.