At Wootric, we've gotten quite a few requests from customers who've built their app using the Ionic Framework to test our web SDK with the framework. Here's how we did it.
PART II. [Go to Part I]
Our mission at Wootric is to help you win customers for life. One way we do this is by giving you the power to survey your customers across multiple channels. We serve customers in over 70 countries worldwide and have received over 2 million survey responses across web, mobile app, email and SMS.
by German Monfort (@gmonfort) and Prabhat Jha (@prabhatjha)
by Prabhat Jha (@prabhatjha) and Ryan Smith (@rnsmith49)
TLDR: Our partner Stitch enables our customers to automatically import their Wootric data into Amazon Redshift, Google BigQuery, and Postgres data warehouses. Their open source Singer project means that you can use the integration even if you're not a Stitch customer.
The Rails core team takes security very seriously which means that we have a great foundation to build our apps on. Thanks to them, we didn't need to focus on security vulnerabilities in our early stage of development. But the more code we write on top of core, the more we risk introducing a vulnerability into our web application.
2016 has been a wild ride. The engineering team at Wootric has had our fair share of ups and downs and I thought it would be fun to collect some of our best war stories for posterity. Here is a list of things that happened, and what we are doing differently as a result.
At Wootric we've been huge fans of PostgreSQL from day one, and we still are. It's a robust and reliable fully-featured open source database and in most cases it fulfills all the data storage needs for your application. On the other hand, we work on getting customer feedback such as NPS at a huge scale, so it was only a matter of time until we started experiencing the first performance issues[…]
