On every wall of our HelloSign office, there hangs a list of our nine core company values. These include things like extreme ownership, transparency, and making our users awesome.
While every value is important to our team, one we hold in particularly high esteem is “constant improvement.” Over the last 6 months we’ve taken constant improvement to heart as we made our HelloSign API more empathetic to developers and more customizable for the companies who wish to embed the eSignature experience into their app or website.
The result has been a suite of new updates for API users, present and future. Check them out below!
This post was originally published by Freddy Rangel on Medium.
You might ask yourself, “why in the world would anyone want to torture themselves by supporting IE8?” Even Google doesn’t support IE8! But there are actually many companies that must support IE8 for one reason or another. At the company where I work, HelloSign, we allow third-party companies to embed our document signing software directly in their applications. Many of our customers support IE8. Therefore, we must support IE8 as well.
Everybody seems to be talking about data these days, and for good reason. Organizations large and small are collecting more information than ever before and using it to gain valuable insight on performance metrics, company health, and customer behavior. At the same time, advanced technologies like message brokering and interactive query engines, once only accessible to large enterprise companies, have rather rapidly permeated down into the mainstream.
On the surface, these are some pretty cool developments! Making sense of large amounts of data can support a lot of important business decisions. So while a few talented folks may impressively continue doing things the old fashioned way, most of us should be trying to embrace increasingly large pools of data in more effective ways. For HelloSign, this was a big motivation for us as we recently chose to overhaul our patchwork of siloed systems and reporting tools. As a company we had reached the size and complexity where we needed a more consistent and reliable integrated data solution.
This project was, as you might expect, a big endeavor! The title of this article “6 easy steps” is a bit tongue-in-cheek, but after putting in the work we can now look at things with the clarity of hindsight. All the moving parts have come together and really begun to make sense. From a BI perspective, we’re in a much improved place, and it’s made us realize that the knowledge we’ve gained may be useful to others. We therefore wanted to share our methods, results, and some of the lessons we learned along the way.
This post was originally published by HelloSign engineer Freddy Rangel on React University. It’s so helpful that we wanted to share it here, too.
Without any modifications, React is really fast as-is. There are, however, a few things that you can do to improve performance. While working at HelloSign, I discovered some quick fixes that made our apps incredibly snappy. With these simple changes, I was able to reduce render time from over 3000 milliseconds to less than 200 milliseconds.