Figment, Inc.

Alert processing was fixed early on Friday (I can confirm this because I received a Winter Storm Warning myself).  As of 9:00PM EST on Saturday the maps are also fixed.  I apologize for any issues this caused.  I’m working very hard on getting fast, accurate, real-time alerts out instead of the long delays there are right now.  Check for more info very soon.

We are aware that WeatherAlert doesn’t seem to be working.  In addition to fixing the issue (related to the source we get weather data from) we are working with the NOAA to get direct alert information for real-time alerts.  Sorry for the inconvenience.  Hopefully all will be fixed ASAP.

*UPDATE*

The alerts are now working (in the app and the push checking), however the map is still broken.  We are working with the data source to get it resolved.  Thanks for your patience.

First, let me apologize for the looooooooooong time in between posts, information, and updates.  Things got really busy outside of the Figment realm.  And the bill-paying job and family take priority over the Figment projects.

But now with 2010 upon us, this will hopefully be a great year for Figment.  I have been compiling a list of things I need to get done and I’ll be getting a start on it this week.  First is the server that WeatherAlert and Current Temperature use.  The hosting is somewhat poor and the data source is the cause of most of the problems people are having with delayed notices or missing locations.  Step 1 is to fine a great new source of data.  Since I charge for the app (to cover the server and data fees) I have to be aware of the ToS for various sources.  A lot of them won’t let you charge, or if you do, you have to also pay them.  These apps aren’t profitable enough for me to be doing that.  Once the server issue is taken care of I’ll be re-writing all the server-side code for alert checking.  I want to get it down so that it is no more than 5 minutes in between checks.  Not the 30+ that is is right now.  Once that is complete I can move on to the other issues that have been on my plate for a while now (custom alert tones, multiple locations, etc).  Current Temperature may see a facelift with the new data source.  There is also the possibility of opening it up outside the US.

Next on the plate is Cage Rattle.  It wasn’t as successful as I would have hoped.  Then again, the CR site itself wasn’t as successful/popular as expected in ‘09.  With lots of strong competition, there isn’t much you can do about that.  I’ll be adding Facebook Connect to the app and will also add the requesting feature to the free version.  The only difference will be that the free version will have ads.  This should maybe expose a lot more users to the site and some fantastic new music.

After that I’ve compiled a list of 6 or 8 different apps I’d like to work on.  My plan is to get at least 3 of them out this year.  Some will work very nicely with the upcoming (still mythical) Apple tablet (the iSlate?).  More on that in the future.

A better website will also be coming soon.  Take care, and happy 2010.

Over the next few days the push service may occasionally go down for an hour or so while I work on some optimization scripts.  I apologize for this inconvenience, but in the end it will be worth it.

WeatherAlert v1.2 and CurrentTemperature v1.0 are both now available in the App Store.

I apologize for the issues early on with CurrentTemperature, but the problem has been quickly resolved, everything should be working and pushing just fine now.

Both apps were rejected for the same crash issue. Once I tracked it down it was simple enough to fix. Hopefully both will be available soon.

I’m also still working on the server and looking for a new data source. I apologize for the massive delay.

Just got feedback from Apple on v1.2.  Apparently they are having a weird crashing situation in OS 3.0.1.  I cannot duplicate the crash, so I’ll be looking into it more.  I may just roll the v1.3 functionality into the resubmission.  Stay tuned for details.

I’ve noticed issues with missing alerts recently. This is an issue with the data source. This isn’t the first time we’ve had issues with them. Currently looking into alternative sources for accurate, timely data.

Today the new server-side component of the push service will be deployed. If you experience anything weird, please send an email.

Update: Turns out the new service us not as accurate as I’d like. Will tweak and try again. Apologize for the delay.

WeatherAlert v1.2 is currently in the review queue. Once approved, v1.3 will be submitted. This update allows users to choose from multiple alert tones.