Contraptor

When I started at my current job (back in 2011) they were using Tevron's CitraTest product to automate software hosted on citrix. The first task I was given was to see if we could find an alternative to CitraTest, well Sikuli was the answer. All of the existing code was written in VB.NET, but with a simple wrapper class and use of XML-RPC, we dropped CitraTest completely for a free MIT-Licensed software. It has worked great for years actually.

You might use this instead of a simple IFTTT alert exactly because IFTTT is so simple. In other words, ifWeather.com is designed to be more of a weather alert management console for people that would like to setup and manage multiple alerts for multiple locations. I think that we in the technology industry forget that for so many other industries the weather really matters, and not just the weather where you or your phone are.

A couple examples: - a surprising percentage of people that have signed up so far are photographers that want to be alerted to ideal forecast conditions for several locations. - My wife is a hydro-geologist, so a lot of her sampling needs to be done after specific weather conditions. Her sample locations are spread all over a large region and it's a real pain for her to check weather conditions for so many locations daily.

Thanks for checking out the site.

The service engine I've been building to power http://www.ifweather.com is powered by their API. I'm not sure I would have picked their API originally had I known the company was run by just two guys, but I am very pleased with the API so far. I'm happy to hear that the API is "going to be a big priority for us going forward". Many best wishes and best of luck to Adam and Jay as this new sunrise for your business begins.

When I first read the headline, I thought there was a new python API or SDK for the already existing Textract OCR solution from Structurise. We've used Structurise's product called Textract for years at work, so it was definately around first. I'm not sure if the creators of this new solution/product were aware of the prior's existence, but using the same product name for a product that solves a similar problem seems like it would be an issue... or at the very least confusing.

Here's a link to StructuRise's Textract product page: http://www.structurise.com/textract/