- using TypeScript saves time as many bugs are caught even before running the code
- TypeScript helps developers to be more productive, with intelligent code hints, autocomplete, and inline documentation
TypeScript is a lot of things. It's self-documenting, robust, and scalable code. It's a way to move ahead faster in projects. And most importantly, it's a source of confidence in your product.Check out Wojtek's GitHub!
With types, you can describe the objects' shape, provide better documentation, and ensure that code will work correctly, limiting runtime errors.
Writing types can even be optional in TypeScript, and because of the power of type inference, you can get many benefits without writing additional code. And if you need even more safety, you can adopt stricter rules when you're ready for it.
TypeScript is not just the language but also the tooling and whole ecosystem behind it.
Many integrations covering every popular IDE or code editor greatly enhance the Developer Experience. As a result, developers are more efficient and simply happier.
What does our CTO think?
Using TypeScript is probably the best low-hanging fruit you can reach for when building apps. It will yield great results in the long run, with much better maintainability, Developer Experience, and vastly reduced runtime errors.
CTO at Vazco
Let’s build it together
If you are building a digital product, you need a reliable, stable, and
technologically advanced partner who will take care of building a team of experienced developers so that you can focus on your business.
At Vazco, we’ve been developing web and mobile apps
since 2009 and have completed dozens of projects. Our clients have benefitted from a mature approach of our engineers, testers, product owners, and designers.
Being located in Wrocław, Poland - a 1M urban area and a major academic and technological hub - gives us
access to great talents.
Frequently Asked Questions
Can TypeScript be adopted gradually?
This depends on many factors, the most important being the experience of developers with TypeScript and type systems in general. It's true that for some TypeScript may be seen as a hindrance for the development speed, as you not only need to type the code itself but also the types. But (similar to tests), the initial investments quickly yield profits with fewer runtime bugs and quicker, more confident development.
I'm starting a new project. Should I use TypeScript from the beginning or add it later on?
You should do it right away, for a few reasons:
- There is absolutely no reason not to do it. The advantages are so significant that omitting them seems a lost opportunity.
- It's easier (and, as a result - cheaper) to do it in the beginning. While it can be easily added later, this still needs some overhead for refactoring, which could be omitted when TS is used from day one.
- Using it from the beginning can create good habits in the development team with more strict rules. As a result, it improves the project's maintainability and potentially reduces the technical debt that could occur otherwise.